feature-design

/feature-design

Phase 2 of the develop workflow. Run after /feature-discover completes.

Before ANY Phase 2 work, run this check:

PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
PROJECT_ENCODED=$(echo "$PROJECT_ROOT" | sed 's|^/||' | tr '/' '-')

echo "=== Phase 2 Prerequisites ==="

# CHECK 1: needs_design must be set (this phase does not run otherwise)
echo "Required: needs_design == true"
echo "Current need-flags: [SESSION_PREFERENCES.need_flags]"
# needs_infrastructure IMPLIES needs_design (auto-set in Phase 0; see design §2.2).
# If needs_design is not set, this phase does not run — return to the orchestrator.

# CHECK 2: Understanding document must exist (Phase 1.5 artifact)
echo "Required: Understanding document exists"
ls ~/.local/spellbook/docs/$PROJECT_ENCODED/understanding/ 2>/dev/null || echo "FAIL: No understanding document found"

# CHECK 3: Completeness score must be 100%
echo "Required: Phase 1.5 completeness score = 100%"
echo "Verify: SESSION_CONTEXT.design_context populated with no TBD values"

# CHECK 4: Devil's advocate was dispatched
echo "Required: Devil's advocate review completed"

If ANY check fails: STOP. Return to the appropriate phase.

Anti-rationalization: If you are tempted to skip this check because "the feature is well-understood" or "we can design without the full discovery," that is Pattern 6 (Phase Collapse). The understanding document IS the input to design. Without it, design is guesswork.

Invariant Principles

1. Discovery precedes design - Design only after design_context is fully populated; never design without research findings
2. Synthesis mode for subagents - Design-exploration subagent receives complete context; no interactive discovery in design phase
3. Review is mandatory - Every design document must pass reviewing-design-docs before proceeding
4. Approval gates respect mode - Interactive mode pauses for user; autonomous mode auto-fixes all findings