Feature-Build Workflow

Architecture-first sliced delivery for new capabilities.

~20+ phasesFEATURE_SHIPPED--pr supported

Pipeline

Per-Slice Loop

Each slice goes through its own five-phase cycle before all slices converge in INTEGRATION.

Phase Summary

Hover over any phase name to see what it does in detail.

#	Phase	Purpose	Key Output
1	INTAKE	Collect feature request, parse ticket	INTAKE.md
2	TICKET_GATE	Validate Jira ticket and linked story maturity	TICKET_GATE.md
3	FIGMA_CONTEXT	Fetch design context (non-blocking)	FIGMA_CONTEXT.md
4	LANDSCAPE	Map surrounding system where feature will live	LANDSCAPE.md
5	RECALL	Pattern match from knowledge base	RECALL.md
6	API_SURVEY	Identify all external APIs and dependencies	API_SURVEY.md
7	CODE_TRACE	Trace integration points in existing code	CODE_TRACE.md
8	BLAST_RADIUS_MAP	Map all areas affected by the new feature	BLAST_RADIUS_MAP.md
9	REQUIREMENTS	Define acceptance criteria for complete feature	REQUIREMENTS.md
10	TEST_INVENTORY	Document existing tests in the feature area	TEST_INVENTORY.md
11	DEPENDENCY_GATE	Evaluate each dependency: READY / MOCKED / BLOCKED	DEPENDENCY_GATE.md
12	ARCHITECTURE	Full system architecture design	ARCHITECTURE.md
13	SLICE_PLAN	Break feature into independently deliverable slices	SLICE_PLAN.md
14	SCAFFOLD	Create file structure and stubs for slice	Per-slice
15	BASELINE	Run tests before slice implementation	Per-slice
16	TEST_GEN	Write tests for slice behavior (Category A)	Per-slice
17	IMPLEMENT	Build slice, feature flag gated	Per-slice
18	VERIFY_SLICE	Confirm slice works in isolation	Per-slice
19	INTEGRATION	Verify all slices work together	INTEGRATION.md
20	VERIFY_ALL	Full test suite with flag ON and OFF	VERIFY_ALL.md
21	BLAST_RADIUS_RUN	Full regression suite	BLAST_RADIUS_RUN.md
22	CLOSE	Summarize, update Jira, create QE sub-task, PR if --pr	CLOSE.md
23	LEARN	Update knowledge stores	LEARN.md

Key Processes

Dependency Gate

Every external dependency gets one of three statuses:

Status	Meaning	Action
READY	Available and tested	Use directly
MOCKED	Not available	Create mock, track with TODO
BLOCKED	Cannot proceed, cannot mock	Add to BLOCKERS.md

Ticket Gate

TICKET_GATE validates 8 required fields + 5 recommended. Fetches linked stories to check dependency maturity, interface contracts, and transitive blockers. Use /feature-build PROJ-123 --jira-check to run this check without starting the workflow — it drafts concrete fixes for each gap and can update the ticket for you.

Per-Slice Iteration

Each slice follows SCAFFOLD → BASELINE → TEST_GEN → IMPLEMENT → VERIFY_SLICE. Slices are independently deliverable vertical cuts.

Integration Testing

After all slices, INTEGRATION verifies cross-slice interactions. VERIFY_ALL runs full suite with feature flag ON and OFF.

Feature Flags

ALL new code must be behind a feature flag (default OFF). Both ON and OFF states tested in VERIFY_ALL.

Dual Loopbacks

REARCHITECT (from VERIFY_ALL) loops back to ARCHITECTURE. RESLICE (from INTEGRATION) loops back to SLICE_PLAN.

Signal Flow

Signal	Type	Meaning
PHASE_COMPLETE	advance	Phase done, advance
BLOCKED_NEEDS_HUMAN	block	Cannot proceed
SCOPE_ESCALATION	block	Scope larger than expected
DEPENDENCY_BLOCKED	block	External dependency unavailable
REARCHITECT	loopback	Architecture invalid, back to ARCHITECTURE
RESLICE	loopback	Slice plan needs restructuring
FEATURE_SHIPPED	terminal	Workflow complete