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¶
- Read
references/yaml-schema.mdfor the YAML schema definition - Read
references/completeness-criteria.mdfor file classification criteria - Run
scripts/vault_scanner.pyagainst the vault to generate baseline metrics - Analyze the scanner output to identify priority files
- Invoke the
ims-content-planneragent (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)¶
When --cwp CWP-NN is provided:
1. Resolve CWP files via cwp_file_resolver.py /path/to/vault/ CWP-NN
2. Read .content-state.yaml for CWP status, dependencies, and progress
3. Classify only CWP files by completeness level
4. Include CWP-specific context in the plan:
- CWP name, layer, domain, content_type
- Batch size and expected file count
- Human tasks associated with this CWP
- Dependency status (are prerequisite CWPs completed?)
5. Output plan scoped to the CWP's files only
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, use /vt-v-sprint to execute it, or manually invoke domain agents:
- isms-expert for ISMSI/ files
- dsms-expert for ISDS2/ files
- qms-ims-expert for QMS/ and IMS/ files
- Use --cwp with /vt-v-sprint to execute a CWP-scoped sprint