Skip to content

vt-v-plan

Scan the VisiTrans VMS vault to analyze content completeness, identify gaps, map cross-reference dependencies, and produce a prioritized content development sprint plan. Use when starting a new content development sprint or when you need a gap analysis of the vault.

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

VMS Content Planning

This skill scans the VMS vault, classifies every file by completeness level, and produces a prioritized sprint plan for content development.

Process

  1. Read references/yaml-schema.md for the YAML schema definition
  2. Read references/completeness-criteria.md for file classification criteria
  3. Run scripts/vault_scanner.py against the vault to generate baseline metrics
  4. Analyze the scanner output to identify priority files
  5. Invoke the ims-content-planner agent (via Task tool) to produce the full sprint plan

Quick Start

# Run the vault scanner for baseline metrics
python3 scripts/vault_scanner.py /path/to/vault/

# Or scan a specific domain
python3 scripts/vault_scanner.py /path/to/vault/ISMSI/

# Plan for a specific CWP
python3 cwp_file_resolver.py /path/to/vault/ CWP-01  # Get file list
python3 scripts/vault_scanner.py /path/to/vault/      # Then scan those files

CWP-Scoped Planning (--cwp CWP-NN) — Step 2 of 5

When --cwp CWP-NN is provided, this skill acts as Step 2 of the numbered workflow.

  1. Display step banner: 
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Step 2 of 5 — PLAN               CWP-NN
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  2. Prerequisite check: CWP must have phase: activate in .content-state.yaml. If phase is null or missing, warn: "Run Step 1 first (/vt-v-cwp activate CWP-NN)". Allow override.
  3. Resolve CWP files via cwp_file_resolver.py /path/to/vault/ CWP-NN
  4. Read .content-state.yaml for CWP status, dependencies, and progress
  5. Classify only CWP files by completeness level
  6. Include CWP-specific context in the plan:
  7. CWP name, layer, domain, content_type
  8. Batch size and expected file count
  9. Human tasks associated with this CWP
  10. Dependency status (are prerequisite CWPs completed?)
  11. Output plan scoped to the CWP's files only
  12. Write plan gate: .cwp-plan-gate.yaml in V004 repo root: 
    cwp: CWP-NN
status: PASS
date: "<timestamp>"
branch: feature/vms-content-cwp-NN
file_count: <N>
batch_count: <ceil(N / batch_size)>
batch_size: <from CWP definition>
dependencies_met: true/false
baseline_recorded: true/false
plan_file: docs/content-plans/cwp-NN-plan.md
  13. Update .content-state.yaml: set phase: plan, plan_gate: PASS
  14. Display next step: 
    Plan gate: PASS (N files, M batches)
Next → Step 3: /vt-v-draft --cwp CWP-NN

Output

The sprint plan is written to docs/content-plans/sprint-YYYY-MM-DD.md (or docs/content-plans/cwp-NN-plan.md when CWP-scoped) and includes: - Baseline metrics (compliance-score, review coverage, content depth) - Prioritized file backlog grouped by domain (or by batch when CWP-scoped) - Dependency graph (which files must be completed first) - Projected impact on compliance-score

Vault Path

The vault path must be provided as an argument or set via $IMS_VAULT_PATH. There is no default.

Integration

After generating a plan: - CWP-scoped: Follow the numbers → Step 3: /vt-v-draft --cwp CWP-NN - General sprint: Use /vt-v-sprint to execute, or manually invoke domain agents: - isms-expert for ISMSI/ files - dsms-expert for ISDS2/ files - qms-ims-expert for QMS/ and IMS/ files