Skip to content

vt-v-sprint

Execute a complete VMS content development sprint cycle: plan → write → audit → review. Orchestrates the full workflow by invoking /vt-v-plan for gap analysis, routing content writing to domain experts via /vt-v-write, validating with /vt-v-audit, and reviewing with /vt-v-review. Use when you want to run the complete plan-write-review pipeline.

Plugin: vms
Category: Other
Command: /vt-v-sprint

VMS Content Sprint

This skill orchestrates a complete content development sprint by coordinating planning, writing, auditing, and review phases.

Sprint Workflow

Phase 1: PLAN
  └─ Invoke /vt-v-plan to generate or read sprint backlog
  └─ Present plan to user for approval

Phase 2: WRITE
  └─ Route files to domain agents via /vt-v-write
  └─ Process in batches (size from CWP definition or --batch-size)
  └─ Track progress via TodoWrite
  └─ Update .content-state.yaml progress after each batch

Phase 3: AUDIT
  └─ Invoke /vt-v-audit --changed after each batch
  └─ Fix critical errors immediately
  └─ Log warnings for review

Phase 4: REVIEW
  └─ Invoke /vt-v-review on completed files
  └─ Flag escalate-to-human items for user
  └─ Auto-fix revise items

Phase 5: REPORT
  └─ Generate sprint summary
  └─ Calculate metric deltas
  └─ Update .content-state.yaml with sprint record
  └─ Recommend next sprint focus

Process

  1. Read references/sprint-workflow.md for the detailed process
  2. Invoke the ims-content-orchestrator agent via Task tool
  3. The orchestrator will: a. Run /vt-v-plan (or /vt-v-plan --cwp CWP-NN if scoped) or read existing plan b. Present the plan and get user approval c. Use existing CWP branch or create feature/ims-content-sprint-N d. Route batches to domain agents e. Run audit after each batch f. Update .content-state.yaml progress counters g. Run review on completed files h. Present findings for human review i. Generate sprint summary and record in .content-state.yaml

Arguments

  • --cwp CWP-NN — Scope sprint to a specific Content Work Package (uses CWP batch size, files from cwp_file_resolver.py)
  • --domain [ISMS|DSMS|QMS|IMS] — Focus sprint on a single domain (ignored when --cwp is set)
  • --batch-size N — Override default batch size (range: 5-50, overrides CWP default)

CWP-Scoped Sprint

When --cwp CWP-NN is provided: 1. Resolve files via cwp_file_resolver.py /path/to/vault/ CWP-NN 2. Use CWP-defined batch size (unless overridden by --batch-size) 3. Read .content-state.yaml for CWP status and progress 4. After each batch, update cwp_status.CWP-NN.progress.files_written 5. After sprint, append to sprints history in .content-state.yaml

Human Checkpoints

The sprint pauses for human input at: 1. After plan — User approves the sprint backlog 2. After each batch — User reviews audit findings 3. After review — User decides on escalated items 4. Before commit — User confirms changes are ready

Sprint Sequencing Strategy

Default priority order (foundation first): 1. Policies and Richtlinien (verify existing, fix YAML) 2. Compliance controls (highest compliance-score impact) 3. DSMS content (VVT, TOM, DSFA) 4. Aggregation documents (KPIs, management review, audits)

Override with --domain to focus on a specific area, or use --cwp to follow the CWP dependency order.

Integration

  • Requires all IMS skills to be installed: /vt-v-plan, /vt-v-write, /vt-v-audit, /vt-v-review, /vt-v-cwp
  • Requires all IMS agents: ims-content-planner, isms-expert, dsms-expert, qms-ims-expert, ims-auditor, ims-content-orchestrator
  • Git branch management is handled automatically
  • Reports are written to reports/ and docs/content-plans/
  • CWP state is tracked in .content-state.yaml (V004 repo root)