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.

/vt-v-cwp status
/vt-v-cwp              # same as status

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` (Step 1)¶

Start work on a CWP.

/vt-v-cwp activate CWP-01

Process: 1. Display step banner:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Step 1 of 5 — ACTIVATE           CWP-NN
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

2. Verify all dependencies are completed (or warn if not) 3. Create git branch: feature/vms-content-cwp-NN 4. Delete stale gate files: .cwp-plan-gate.yaml, .cwp-review-gate.yaml, .cwp-checkpoint.yaml 5. Run cwp_file_resolver.py --init-progress CWP-NN to generate the file_progress map 6. Populate file_progress map in .content-state.yaml (all files status: pending) 7. Run /vt-v-audit --snapshot --cwp CWP-NN to record baseline metrics 8. Set phase: activate, status: in_progress, started_at timestamp 9. Clear all gate fields: plan_gate: null, review_gate: null, quality_gate: null 10. Print CWP summary: file count, batch size, human tasks 11. Display next step:

Next → Step 2: /vt-v-plan --cwp CWP-NN

`complete [CWP-NN]` (Step 5)¶

Finalize a CWP (defaults to the currently in_progress CWP).

/vt-v-cwp complete
/vt-v-cwp complete CWP-01

Process: 1. Display step banner:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Step 5 of 5 — COMPLETE           CWP-NN
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

2. Hard prerequisite — Review gate check: - Read .cwp-review-gate.yaml - If missing → BLOCKED: "Run Step 4 first (/vt-v-review --cwp CWP-NN)" - If status: FAIL → BLOCKED: "Review failed. Fix issues and re-run Step 4." - If CWP mismatch → BLOCKED: "Review gate is for a different CWP." 3. Run /vt-v-audit --snapshot --cwp CWP-NN to record final metrics 4. GO/NO-GO quality gate — compare metrics_before vs metrics_after:

Quality Gate: CWP-NN
─────────────────────────────────────────────────────
Criterion                          Before   After   Status
Compliance score (no decrease)     88.3     91.2    GO
Content depth (improved)           54.6%    85.0%   GO
Files completed (100%)             14/14    14/14   GO
Escalations acknowledged           1/1      1/1     GO
Review gate                        PASS     -       GO
─────────────────────────────────────────────────────
Decision: GO

- Check: compliance_score did not decrease - Check: content_depth_complete_pct improved - Check: zero files with status: pending in file_progress - Check: all escalated files have been acknowledged - Check: .cwp-review-gate.yaml status is PASS 5. If GO: - Record metrics_after in .content-state.yaml - Set phase: complete, quality_gate: GO, status: completed, completed_at - Append sprint entry to sprints history - Update current metrics section - Delete .cwp-checkpoint.yaml (CWP finished) - Print completion summary with metric deltas - Identify next actionable CWP:

CWP-NN complete! Next CWP ready: CWP-MM → /vt-v-cwp activate CWP-MM

6. If NO-GO: - Set quality_gate: NO-GO (do NOT mark complete) - Display which criteria failed - Suggest remediation steps

`human`¶

Show all pending human action items.

/vt-v-cwp human

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.

/vt-v-cwp init

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

Numbered Workflow Per CWP¶

Follow the steps in order. Each step displays its number and the next step.

Step 0: /vt-v-start              ← What should I work on?
         ↓ picks CWP-NN
Step 1: /vt-v-cwp activate CWP-NN  ← Initialize, set up tracking
         ↓
Step 2: /vt-v-plan --cwp CWP-NN    ← Plan the work, write plan gate
         ↓ .cwp-plan-gate.yaml (soft)
Step 3: /vt-v-draft --cwp CWP-NN   ← Draft files (interview or batch)
         ↓ .cwp-checkpoint.yaml (at batch boundaries)
Step 4: /vt-v-review --cwp CWP-NN  ← Review all drafted files
         ↓ .cwp-review-gate.yaml (hard)
Step 5: /vt-v-cwp complete CWP-NN  ← Quality gate, finalize

Gate Enforcement¶

Gate	Type	Written By	Checked By
`.cwp-plan-gate.yaml`	Soft	Step 2	Step 3 (warn if missing)
`.cwp-review-gate.yaml`	Hard	Step 4	Step 5 (BLOCK if missing)
`.cwp-checkpoint.yaml`	Resume	Step 3	Step 0, Step 3

See references/gate-schemas.md for gate file formats.

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

# Generate file_progress JSON for a CWP (used by activate)
python3 scripts/cwp_file_resolver.py /path/to/vault/ --init-progress CWP-01

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¶

import yaml
with open('.content-state.yaml') as f:
    state = yaml.safe_load(f)

Updating progress after a batch¶

After processing a batch of files, update:

cwp_status.CWP-01.progress.files_written: +N

And bump updated_at.

Resolving CWP files¶

from cwp_file_resolver import get_cwp_files
files = get_cwp_files('/path/to/vault/', 'CWP-01')

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.yaml in V004 repo root
References: cwp-definitions.md, content-state-schema.md