Story E: deft-directive-setup (rename + rewrite for vBRIEF model)

[MScottAdams]

Parent

Part of #309 (RFC: vBRIEF-centric document model)

Tier

Tier 3 -- Skills (depends on #310, #313)

Scope

Rename skills/deft-setup/ to skills/deft-directive-setup/ and rewrite for the new document model:

Namespace rename

• Update SKILL.md frontmatter (name, triggers)
• Update all internal references to use deft-directive-* skill names

Phase 2 (project config)

• Generate PROJECT-DEFINITION.vbrief.json instead of PROJECT.md

Phase 3 (specification interview) — updated per #345 design decision

• Add onboarding question: 'Adding a scope to this project or starting new?' with default based on repo state
• Full path: chains to deft-directive-interview which populates specification.vbrief.json plan.narratives with rich keys (ProblemStatement, Goals, UserStories, Requirements, SuccessMetrics, Architecture, Overview)
• Light path: populates slim narratives (Overview + Architecture) then creates scope vBRIEFs in vbrief/proposed/
• Human approval gate operates on the vBRIEF draft narratives — reviewing the narratives IS the approval step (replaces PRD.md review)
• PRD.md is not generated as part of Phase 3. If needed, users run task prd:render (see Story J: deft-directive-interview (namespace rename) #319)

Acceptance Criteria

• Skill directory is skills/deft-directive-setup/
• SKILL.md name field is deft-directive-setup
• Onboarding question present with repo-state-aware default
• Phase 2 outputs PROJECT-DEFINITION.vbrief.json
• Phase 3 approval gate reviews vBRIEF narratives (not PRD.md)
• Phase 3 Full path produces rich narratives in specification.vbrief.json
• Phase 3 Light path outputs scope vBRIEFs in vbrief/proposed/
• No references to old deft-setup name or old file targets
• No authoritative PRD.md generation

[MScottAdams]

Closed by squash merge of PR #351 into phase2/vbrief-cutover. deft-setup renamed to deft-directive-setup and rewritten for vBRIEF model.