vt-v-cwp¶
Content Work Package lifecycle manager for VMS content development. Tracks 24 CWPs across 6 dependency layers, manages human action items, records metrics snapshots, and provides a progress dashboard. Persistent state via .content-state.yaml in V004.
Plugin: vms
Category: Other
Command: /vt-v-cwp
VMS Content Work Package Manager¶
This skill manages the lifecycle of Content Work Packages (CWPs) — discrete units of work that decompose 685 vault files into 24 manageable packages across 6 dependency layers.
Commands¶
status (default)¶
Display the CWP progress dashboard.
Reads .content-state.yaml and displays:
1. Current vs target metrics (compliance-score, content depth, cross-ref rate)
2. CWP status grouped by layer (pending → in_progress → review → completed)
3. Progress fractions per CWP (files_written / total_files)
4. Pending human actions
5. Next actionable CWP (pending with all dependencies completed)
activate CWP-NN¶
Start work on a CWP.
Process:
1. Verify all dependencies are completed (or warn if not)
2. Create git branch: feature/ims-content-cwp-NN
3. Run /vt-v-audit --snapshot --cwp CWP-NN to record baseline metrics
4. Set CWP status to in_progress in .content-state.yaml
5. Set started_at timestamp
6. Print CWP summary: file count, batch size, human tasks
complete [CWP-NN]¶
Finalize a CWP (defaults to the currently in_progress CWP).
Process:
1. Run /vt-v-audit --snapshot --cwp CWP-NN to record final metrics
2. Record metrics_after in .content-state.yaml
3. Set status to completed, record completed_at
4. Append sprint entry to sprints history
5. Update current metrics section
6. Print completion summary with metric deltas
7. Identify next actionable CWP
human¶
Show all pending human action items.
Displays:
- All human_actions from .content-state.yaml grouped by status
- Which CWPs each action blocks
- Allows marking actions as completed: /vt-v-cwp human complete HA-01
init¶
Initialize .content-state.yaml from vault scan. Run once to bootstrap.
Process:
1. Run cwp_file_resolver.py --init-yaml to scan vault and generate YAML
2. Run /vt-v-audit --full to populate baseline metrics (compliance-score, content depth, cross-ref rate)
3. Fill baseline and current sections with actual metrics
4. Write .content-state.yaml to V004 repo root
5. Print summary dashboard
State File¶
.content-state.yaml lives at the V004 repo root and persists across sessions. See references/content-state-schema.md for full schema.
Location: <project-root>/.content-state.yaml
CWP Decomposition¶
24 CWPs across 6 dependency layers. See references/cwp-definitions.md for full membership rules.
Layer 1: Foundation (no deps)
CWP-01 Richtlinien (IMS) ~55 files batch 5
CWP-02 Arbeitsanweisungen (IMS) ~9 files batch 5
CWP-03 Prozess Core (IMS) ~44 files batch 10
Layer 2: Controls (depends on L1)
CWP-04 ISO 27001 A.5 ~37 files batch 25
CWP-05 ISO 27001 A.6 ~8 files batch 8
CWP-06 ISO 27001 A.7 ~14 files batch 14
CWP-07 ISO 27001 A.8 ~34 files batch 25
CWP-08 VDA ISA ~88 files batch 25
CWP-09 NIS2 ~15 files batch 25
CWP-10 ISO 9001 (QMS) ~59 files batch 20
CWP-11 DSMS Controls ~24 files batch 12
Layer 3: DSMS Content (depends on L2)
CWP-12 VVT Art.30 ~3 files batch 5
CWP-13 TOM/DSFA ~4 files batch 3
CWP-14 DSMS Prozess ~48 files batch 15
Layer 4: Support Content (depends on L2)
CWP-15 Lieferanten ~54 files batch 15
CWP-16 KPIs ~25 files batch 10
CWP-17 Schulung ~31 files batch 10
CWP-18 Audits ~7 files batch 5
CWP-19 Managementbewertung ~1 file batch 1
Layer 5: Cross-referencing (depends on L3+L4)
CWP-20 Cross-reference Pass ~644 files batch 50
CWP-21 YAML Fix-up ~96 files batch 50
Layer 6: Remaining Enrichment (depends on L5)
CWP-22 IMS Prozess Remaining ~43 files batch 15
CWP-23 ISMSI Prozess/Other ~29 files batch 20
CWP-24 QMS Remaining ~12 files batch 15
Workflow Per CWP¶
/vt-v-cwp activate CWP-NN
│
▼
Phase 2: PLAN
/vt-v-plan --cwp CWP-NN
User approves scope
│
▼
Phase 3: BUILD (batches)
/vt-v-write on batch → domain agent enriches
/vt-v-audit --changed → validate
Update .content-state.yaml progress
Commit batch
[Human checkpoint: review audit, decide escalations]
Repeat for all batches
│
▼
Phase 4: REVIEW
/vt-v-review on all CWP files
Auto-fix revise items
Present escalations to user
/vt-v-audit --snapshot --cwp CWP-NN → record after metrics
│
▼
Phase 5: FINALIZE
Run pre-PR checks: bash scripts/cwp-pre-pr-checks.sh --vault-path <vault>
If checks FAIL → display errors, do NOT create PR, fix and re-run
If checks PASS → proceed (warnings displayed but non-blocking)
Optional: python3 scripts/cascade_report.py <vault> --ref-range main..HEAD
Shows all files transitively affected by this CWP's changes (informational)
Push branch, create PR
Compliance-score CI check
/vt-v-cwp complete
Record sprint, advance to next CWP
Scripts¶
scripts/cwp_file_resolver.py— Resolves CWP-ID to vault file list based on YAML frontmatter matching
# List files for a CWP
python3 scripts/cwp_file_resolver.py /path/to/vault/ CWP-01
# Show all CWP assignments
python3 scripts/cwp_file_resolver.py /path/to/vault/ --summary
# Generate .content-state.yaml skeleton
python3 scripts/cwp_file_resolver.py /path/to/vault/ --init-yaml
Human Action Items¶
5 predefined human actions tracked in .content-state.yaml:
| ID | Description | Relevant CWPs |
|---|---|---|
| HA-01 | Reifegrad-Workshop: Review AI-suggested reifegrad | CWP-04..09 |
| HA-02 | VVT-Vollstaendigkeit: Confirm processing activities | CWP-12 |
| HA-03 | Lieferanten-Daten: Verify supplier contracts, AVV | CWP-15 |
| HA-04 | KPI-Zielwerte: Set actual target values | CWP-16 |
| HA-05 | Managementbewertung: Provide actual review data | CWP-19 |
Human actions do NOT hard-block CWPs. AI can draft content; the human action finalizes/verifies.
Implementation Notes¶
Reading .content-state.yaml¶
Updating progress after a batch¶
After processing a batch of files, update:
And bumpupdated_at.
Resolving CWP files¶
Integration¶
- Requires:
/vt-v-plan,/vt-v-sprint,/vt-v-audit,/vt-v-write,/vt-v-review - Requires agents:
ims-content-orchestrator,ims-content-planner,ims-auditor, domain experts - State file:
.content-state.yamlin V004 repo root - References:
cwp-definitions.md,content-state-schema.md