speckit Phase 2/3 should write to vbrief/specification.vbrief.json, not specs/*.md

[MScottAdams]

Problem

The speckit strategy Phase 2 and Phase 3 outputs write to a hand-authored \specs/{feature}/spec.md\ and \specs/{feature}/plan.md. On the \phase2/vbrief-cutover\ branch, \�brief/specification.vbrief.json\ is the source of truth and \SPECIFICATION.md\ is a rendered output via \ ask spec:render. The \specs/\ folder should never be created.

Expected Behavior

• speckit Phase 2 (WHAT/WHY) writes narratives directly to \�brief/specification.vbrief.json\
• speckit Phase 3 (HOW) enriches the same \�brief/specification.vbrief.json\ with architecture/plan narratives
• \ ask spec:render\ produces \SPECIFICATION.md\ as a rendered read-only export
• The \specs/\ directory is never created by speckit

Actual Behavior

\deft/strategies/speckit.md\ Phase 2 and Phase 3 instruct the agent to create \specs/{feature}/spec.md\ and \specs/{feature}/plan.md\ as hand-authored artifacts, bypassing \�brief/specification.vbrief.json\ entirely.

Fix

Update \deft/strategies/speckit.md:

• Phase 2 output: write WHAT/WHY content as narratives to \�brief/specification.vbrief.json\
• Phase 3 output: enrich \�brief/specification.vbrief.json\ with HOW narratives (Architecture, TechDecisions, etc.)
• Remove all references to creating \specs/\ directory or \spec.md/\plan.md\ files
• After Phase 3, instruct agent to run \ ask spec:render\ to produce \SPECIFICATION.md\ for human review

Branch

Targets: \phase2/vbrief-cutover
Related: #361 (speckit Phase 1 same pattern — project.md vs PROJECT-DEFINITION.vbrief.json), #336

[MScottAdams]

Phase 4 Stopgap (pending Epic RFC)

speckit Phase 4 (task generation) output remains as \�brief/plan.vbrief.json\ at the vbrief root until the Epic RFC is resolved. This is the documented intent for this file per \�brief/vbrief.md\ -- it is the session-level tactical plan ('the how right now') and is a supported artifact type, not a workaround.

When the Epic RFC lands, speckit Phase 4 will be updated to create .epic.vbrief.json\ files (one per phase) with child story vBRIEFs in \�brief/proposed/. Until then, do not attempt to force Phase 4 output into lifecycle folders.

Related: Epic RFC issue (TBD)

[MScottAdams]

Completed in PR #376 (squash merged to phase2/vbrief-cutover)