Skip to content

vt-v-sprint

Auto-pilot orchestrator for the VMS CWP workflow. Runs Steps 2-4 in sequence (plan → draft → review) with gate enforcement and checkpoints. Step 1 (activate) must be run manually first. Step 5 (complete) is suggested but requires manual GO/NO-GO. Use when you want to run the complete pipeline without manually invoking each step.

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

VMS Content Sprint — Auto-Pilot Orchestrator

This skill runs Steps 2-4 of the numbered CWP workflow in sequence. It is the alternative to manually invoking each step one by one.

Prerequisite: Step 1 (/vt-v-cwp activate CWP-NN) must be run manually first.

CWP-Scoped Sprint Workflow (--cwp CWP-NN)

Entry: Check for checkpoint → offer resume
  ↓
Step 2: /vt-v-plan --cwp CWP-NN
  └─ Generate or read sprint plan
  └─ Present plan to user for approval
  └─ Check .cwp-plan-gate.yaml → proceed if PASS
  ↓
Step 3: Draft (batch mode via /vt-v-write)
  └─ Route files to domain agents in batches
  └─ Run /vt-v-audit --changed after each batch
  └─ Update file_progress per file
  └─ Write .cwp-checkpoint.yaml at batch boundaries
  └─ Recommend /clear after large batches
  ↓
Step 4: /vt-v-review --cwp CWP-NN
  └─ Review all drafted files
  └─ Auto-fix revise items
  └─ Present escalations to user
  └─ Write .cwp-review-gate.yaml
  ↓
Suggest: Step 5 — /vt-v-cwp complete CWP-NN
  └─ User runs manually (GO/NO-GO is a human decision)

Process

Entry

  1. Checkpoint check: Read .cwp-checkpoint.yaml — if exists and matches CWP:
  2. Display: "Checkpoint found at Step N. Resume? (Ja / Nein, von vorne)"

  3. If resume: skip to the indicated step

  4. Prerequisite check: Read .content-state.yaml for CWP phase:

  5. If phase is null → "Run Step 1 first: /vt-v-cwp activate CWP-NN". STOP.
  6. If phase: plan → skip Step 2, go to Step 3
  7. If phase: draft → skip Steps 2-3, go to Step 4 (if all files drafted)

Step 2: Plan

  1. Invoke /vt-v-plan --cwp CWP-NN
  2. Present plan to user for approval
  3. Check .cwp-plan-gate.yaml — if FAIL, stop and display issues

Step 3: Draft (Batch Mode)

  1. Read file_progress — filter to status: pending
  2. Group into batches using CWP batch_size (or --batch-size override)
  3. For each batch: a. Invoke /vt-v-write on batch files b. Update file_progress per file (status: drafted) c. Run /vt-v-audit --changed to validate d. Write .cwp-checkpoint.yaml e. Display batch summary f. If CWP has >20 total files: recommend /clear and resume g. Ask: "Naechsten Batch? (Ja / Pause)"
  4. If user pauses: STOP with checkpoint written

Step 4: Review

  1. Invoke /vt-v-review --cwp CWP-NN
  2. Review writes .cwp-review-gate.yaml
  3. Display results

Suggest Step 5

After Step 4 completes: 

Sprint complete. Review gate: PASS
Next → Step 5: /vt-v-cwp complete CWP-NN

Arguments

  • --cwp CWP-NN — Scope sprint to a specific Content Work Package
  • --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)

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 Step 5 — User runs GO/NO-GO manually

Integration

  • Requires all VMS skills: /vt-v-plan, /vt-v-write, /vt-v-audit, /vt-v-review, /vt-v-cwp, /vt-v-draft
  • Requires all IMS agents: ims-content-planner, isms-expert, dsms-expert, qms-ims-expert, ims-auditor, ims-content-orchestrator
  • Git branch management via /vt-v-cwp activate (Step 1)
  • Reports written to reports/ and docs/content-plans/
  • CWP state tracked in .content-state.yaml (V004 repo root)
  • Gate files: .cwp-plan-gate.yaml, .cwp-review-gate.yaml, .cwp-checkpoint.yaml