vt-v-draft¶
Step 3 of the VMS CWP workflow. Routes between interactive (interview) and batch (write) drafting modes. Tracks per-file progress, writes checkpoints at batch boundaries, and supports session resume after /clear. Use with --cwp CWP-NN.
Plugin: vms
Category: Other
Command: /vt-v-draft
VMS Content Draft — Step 3 of 5¶
This skill is the drafting step in the numbered CWP workflow. It routes to either
interactive interview mode or batch write mode, tracks per-file progress in
.content-state.yaml, and writes checkpoints to enable session resume.
Process¶
Entry¶
-
Display step banner:
-
Read
.content-state.yamlfor the CWP'sfile_progressmap. -
Check for checkpoint: Read
.cwp-checkpoint.yaml— if it exists and matches the CWP: - Display: "Checkpoint found. Resuming from file M/N (last: [filename])."
- Offer: "Resume from checkpoint? (Ja / Nein, von vorne)"
-
If resume: set
batch_cursorfrom checkpoint -
Soft gate check: Read
.cwp-plan-gate.yaml - If missing: warn "Plan gate not found. Run Step 2 (
/vt-v-plan --cwp CWP-NN) first." - Allow override: "Trotzdem fortfahren? (Ja / Nein)"
-
If CWP mismatch: warn but allow
-
Show progress summary:
-
Ask mode:
Wie moechtest du die verbleibenden Dateien bearbeiten? - Interaktiv — Q&A pro Datei (
/vt-v-interview) - Batch — Automatische Anreicherung (/vt-v-write)
Interactive Mode (via /vt-v-interview)¶
- Filter
file_progresstostatus: pendingfiles - Present the first pending file:
"Datei 1/7: vault/ISMSI/04/A.7.1.md — skeleton (0.8 KB)"
- Invoke
/vt-v-interviewwith the file path - After the interview completes and file is written:
- Update
file_progress[file].status: drafted - Update
file_progress[file].drafted_at: <timestamp> - Increment
progress.files_written - Checkpoint check — after every 5 files:
- Write
.cwp-checkpoint.yamlwith current position - Display:
- Ask: "Weiter mit der naechsten Datei? (Ja / Pause)"
- Present next pending file and repeat
- When user pauses or all files done → go to Exit
Batch Mode (via /vt-v-write)¶
- Filter
file_progresstostatus: pendingfiles - Group files into batches using the CWP's
batch_size - For each batch:
a. Invoke
/vt-v-writewith the batch file paths b. After each file write:- Update
file_progress[file].status: drafted - Update
file_progress[file].drafted_at: <timestamp> - Update
file_progress[file].batch: <batch_number> - Increment
progress.files_writtenc. After batch completes: - Run
/vt-v-audit --changedto validate the batch - Write
.cwp-checkpoint.yaml - Display batch summary and audit results d. Ask: "Naechsten Batch starten? (Ja / Pause)"
- Update
- When user pauses or all batches done → go to Exit
Exit¶
- Update
.content-state.yaml: - Set
phase: draft(if not already) - Update
progress.files_writtencount - Show final progress summary
- If all files drafted:
- If paused (files remaining):
- Write
.cwp-checkpoint.yamlwith current position
Checkpoint Schema¶
Written to V004 repo root as .cwp-checkpoint.yaml. See references/gate-schemas.md for full schema.
Key fields:
- cwp — CWP ID
- step — always 3 for this skill
- phase — always draft
- batch_cursor — index of next unprocessed file
- files_processed / files_remaining
- next_command — /vt-v-draft --cwp CWP-NN
When to Recommend /clear¶
- After 5 files in interactive mode (each interview consumes significant context)
- After each batch in batch mode
- When CWP has >20 total files (context will fill during one session)
Integration¶
| What | Skill |
|---|---|
| Previous step | Step 2: /vt-v-plan --cwp CWP-NN |
| Interactive drafting | /vt-v-interview (invoked with file path) |
| Batch drafting | /vt-v-write (invoked with file paths) |
| Post-batch validation | /vt-v-audit --changed |
| Next step | Step 4: /vt-v-review --cwp CWP-NN |
| Session resume | /vt-v-start detects checkpoint as P0 |