Feature-Enhance Workflow
Design-driven modification of existing features.
~17 phasesENHANCEMENT_SHIPPED--pr supported
Pipeline
Phase Summary
Hover over any phase name to see what it does in detail.
| # | Phase | Purpose | Key Output |
|---|---|---|---|
| 1 | INTAKE | Collect enhancement request, parse ticket | INTAKE.md |
| 2 | TICKET_GATE | Validate Jira ticket has required info for enhancement | TICKET_GATE.md |
| 3 | FIGMA_CONTEXT | Fetch design context (non-blocking) | FIGMA_CONTEXT.md |
| 4 | LANDSCAPE | Map existing feature being enhanced | LANDSCAPE.md |
| 5 | RECALL | Pattern match from knowledge base | RECALL.md |
| 6 | CODE_TRACE | Trace code paths for the feature | CODE_TRACE.md |
| 7 | BLAST_RADIUS_MAP | Map all affected areas | BLAST_RADIUS_MAP.md |
| 8 | REQUIREMENTS | Define acceptance criteria | REQUIREMENTS.md |
| 9 | TEST_INVENTORY | Document existing tests | TEST_INVENTORY.md |
| 10 | DESIGN | Design approach, classify enhancement category | DESIGN.md |
| 11 | ENHANCE_PLAN | Implementation plan with feature flag decisions | ENHANCE_PLAN.md |
| 12 | BASELINE | Run all tests before changes | BASELINE.md |
| 13 | TEST_GEN | Write new tests (Category A) | TEST_GEN.md |
| 14 | IMPLEMENT | Apply enhancement, red-green cycle | Code changes |
| 15 | VERIFY | Run all tests to confirm enhancement | VERIFY.md |
| 16 | BLAST_RADIUS_RUN | Full regression | BLAST_RADIUS_RUN.md |
| 17 | CLOSE | Summarize, update Jira, create QE sub-task, PR if --pr | CLOSE.md |
| 18 | LEARN | Update knowledge stores | LEARN.md |
Key Processes
Enhancement Categories & Feature Flags
The DESIGN phase classifies the enhancement, which determines feature flag requirements.
| Category | Description | Flag? | Tested States |
|---|---|---|---|
| AUGMENT | Add new capability | Yes | ON + OFF |
| EXTEND | Expand existing scope | Yes | ON + OFF |
| MODIFY | Change existing behavior | Risk-dependent | If flagged: ON + OFF |
| OPTIMIZE | Improve performance | No | N/A |
| INTEGRATE | Connect existing features | No | N/A |
Ticket Gate
TICKET_GATE validates 6 required fields (current/desired behavior, justification, acceptance criteria). Use /feature-enhance PROJ-123 --jira-check to check readiness without starting the workflow — it drafts concrete fixes for each gap and can update the ticket for you.
Figma Context
FIGMA_CONTEXT fetches design context when available. Non-blocking: proceeds with design_available: false if unavailable.
REDESIGN Loopback
When VERIFY fails, REDESIGN loops back to DESIGN with new evidence. The design approach is revised and the cycle repeats.
Signal Flow
| Signal | Type | Meaning |
|---|---|---|
| PHASE_COMPLETE | advance | Phase done, advance |
| BLOCKED_NEEDS_HUMAN | block | Cannot proceed |
| SCOPE_ESCALATION | block | Scope larger than expected |
| REDESIGN | loopback | Design approach failed, back to DESIGN |
| ENHANCEMENT_SHIPPED | terminal | Workflow complete |