4774ee20e9
The VTC (Value Trigger Chain) was a separate concept that extracted specific nodes from the Trigger Map into a YAML file. This caused agents to run trigger mapping during Phase 1 (Product Brief), forcing users to repeat the work in Phase 2. Observed in Monday workshop. Architectural fix: - Phase 1 is casual business discovery, NOT trigger mapping - Phase 2 is where the Trigger Map gets built (unchanged) - When scenarios/content need strategic context, they reference the Trigger Map directly — no separate VTC concept needed Removed (19 files deleted): - 1-project-brief/vtc-workshop/ (14 step files + workflow) - step-04-create-vtc.md and step-11a-create-vtc.md from Phase 1 - step-03c-create-vtc.md from Phase 0 alignment - vtc-template.yaml Renamed: - step-03-build-vtcs.md → step-03-build-strategic-context.md - step-02-vtc-consistency.md → step-02-trigger-map-consistency.md - step-01-load-vtc-context.md → step-01-load-trigger-map-context.md - 07-create-vtc.md → 07-reference-trigger-map.md Rewritten: - Phase 4 scenario init: "create VTC" → lightweight "pick from Trigger Map" - Phase 6 content: load context from Trigger Map, not from VTC - Templates: "Trigger Map" section → "Business Context" (Phase 1 scope) Zero VTC references remain in src/. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| agents | ||
| data | ||
| gems | ||
| skills | ||
| workflows | ||
| module-help.csv | ||
| module.yaml | ||