implement-feature

Implement Feature

Overview

Structured feature implementation workflow: optionally fetch context from a Jira/ClickUp ticket, gather requirements, optionally prototype frontend design, plan, write tests first, implement with parallel sub-agents committing after each step, and verify. All artifacts are tracked in a feature/<name>/ directory.

Input

The user provides one or more of:

• A description of the feature to build
• A Jira ticket URL or ID (e.g., PROJ-123, https://team.atlassian.net/browse/PROJ-123)
• A ClickUp task URL or ID (e.g., https://app.clickup.com/t/abc123)
• Context about their project, constraints, or where to save output

When to Use

• User says "implement", "add", "build", or "create" a feature
• User provides a Jira or ClickUp ticket URL/ID to implement
• New functionality that needs requirements clarification
• Multi-step implementation that benefits from planning before coding
• Any work where TDD and sub-agents would improve quality and speed

When NOT to use:

• Bug fixes (use systematic-debugging instead)
• Single-line changes or trivial edits
• Pure research or exploration tasks
• Refactoring with no new behavior

Workflow

digraph feature_flow {
    rankdir=TB;
    node [shape=box];

    init     [label="1. Initialize Feature"];
    ticket   [label="2a. Fetch Ticket?\n(if URL/ID provided)" shape=diamond];
    fetch    [label="2a. Fetch Card Details"];
    clarify  [label="2b. Clarify Requirements"];
    frontend [label="2.5 Frontend Prototype?\n(if UI feature)" shape=diamond];
    design   [label="2.6 Design & Sample HTML"];
    plan     [label="3. Write Implementation Plan"];
    approve  [label="4. Get User Approval" shape=diamond];
    tdd      [label="5. TDD: Write Failing Tests"];
    implement[label="6. Implement + Commit per Step"];
    verify   [label="7. Verify & Review"];
    done     [label="Done"];

    init      -> ticket;
    ticket    -> fetch    [label="yes"];
    ticket    -> clarify  [label="no"];
    fetch     -> clarify;
    clarify   -> frontend;
    frontend  -> design   [label="yes"];
    frontend  -> plan     [label="no"];
    design    -> plan;
    plan      -> approve;
    approve   -> plan     [label="revise"];
    approve   -> tdd      [label="approved"];
    tdd       -> implement;
    implement -> verify;
    verify    -> implement [label="failing"];
    verify    -> done      [label="passing"];
}