feature-dev

Feature Development Workflow

Execute a structured 7-phase feature development workflow. This workflow guides you through understanding, exploring, designing, implementing, and reviewing a feature.

Phase Overview

Execute these phases in order, completing all of them:

1. Discovery - Understand the feature requirements
2. Codebase Exploration - Map relevant code areas
3. Clarifying Questions - Resolve ambiguities
4. Architecture Design - Design the implementation approach
5. Implementation - Build the feature
6. Quality Review - Review for issues
7. Summary - Document accomplishments

Phase 1: Discovery

Goal: Understand what the user wants to build.

1. Analyze the feature description from $ARGUMENTS:
2. What is the core functionality?
3. What are the expected inputs and outputs?
4. Are there any constraints mentioned?
5. What success criteria can you infer?

1. Summarize your understanding to the user. Prompt the user to confirm if your understanding is correct before proceeding.

Phase 2: Codebase Exploration

Goal: Understand the relevant parts of the codebase.

1. Run deep-analysis workflow:
2. Refer to the deep-analysis skill for the exploration and synthesis workflow.
3. Pass the feature description from Phase 1 as the analysis context.
4. This handles reconnaissance, team planning, parallel exploration, and synthesis.

1. Present the synthesized analysis to the user.

Phase 3: Clarifying Questions

Goal: Resolve any ambiguities before designing.

1. Review the feature requirements and exploration findings.

1. Identify underspecified aspects:
2. Edge cases not covered
3. Technical decisions that could go multiple ways
4. Integration points that need clarification
5. Performance or scale requirements

1. Ask clarifying questions:

Prompt the user to answer critical unknowns. Only ask questions that would significantly impact the implementation.

If no clarifying questions are needed, inform the user and proceed.

Phase 4: Architecture Design

Goal: Design the implementation approach.

1. Load skills for this phase:
2. Refer to the architecture-patterns, language-patterns, and technical-diagrams skills and apply their guidance for any Mermaid diagrams in architecture proposals.

1. Delegate to 2-3 independent architecture agents to design different approaches:

`` Agent 1: Design a minimal, focused approach prioritizing simplicity Agent 2: Design a flexible, extensible approach prioritizing future changes Agent 3: Design an approach optimized for the project's existing patterns (if applicable) ``

Each agent should receive: ``` Feature: [feature description] Design approach: [specific approach for this agent]

Based on the codebase exploration: [Summary of relevant files and patterns]

Design an implementation that:

• Lists files to create/modify
• Describes the changes needed in each file
• Explains the data flow
• Identifies risks and mitigations

Return a detailed implementation blueprint. ```

1. Present approaches:
2. Summarize each approach
3. Compare trade-offs (simplicity, flexibility, performance, maintainability)
4. Make a recommendation with justification

1. User chooses approach:

Prompt the user to choose:

• Select an approach as-is
• Request modifications to an approach

1. Generate ADR artifact:
2. Use the ADR template below
3. Create an ADR documenting:
4. Context: Why this feature is needed
5. Decision: The chosen approach
6. Consequences: Trade-offs and implications
7. Alternatives: Other approaches considered
8. Determine the next ADR number by checking existing files in internal/docs/adr/
9. Save to internal/docs/adr/NNNN-[feature-slug].md (create internal/docs/adr/ if needed)
10. Inform the user of the saved ADR location

Phase 5: Implementation

Goal: Build the feature.

1. Require explicit approval:

Ask the user: "Ready to begin implementation of [feature] using [chosen approach]?" Wait for confirmation before proceeding.

1. Read all relevant files:

Before making any changes, read the complete content of every file you will modify.

1. Implement the feature:
2. Follow the chosen architecture design
3. Match existing code patterns and conventions
4. Create new files as needed
5. Modify existing files with targeted edits
6. Add appropriate error handling
7. Include inline comments only where logic is not obvious

1. Test if applicable:
2. If the project has tests, add tests for the new functionality
3. Run existing tests to ensure nothing broke

1. Proceed immediately to Phase 6.

Phase 6: Quality Review

Goal: Review the implementation for issues.

1. Load skills for this phase:
2. Refer to the code-quality skill and apply its guidance.

1. Delegate to 3 independent review agents with different focuses (correctness, security, maintainability):

`` Agent 1: Review for correctness and edge cases Agent 2: Review for security and error handling Agent 3: Review for maintainability and code quality ``

Each agent should receive: ``` Review focus: [specific focus for this agent]

Files to review: [List of files modified/created]

Review the implementation and report:

• Issues found with confidence scores (0-100)
• Suggestions for improvement
• Positive observations

Only report issues with confidence >= 80. ```

1. Aggregate findings:
2. Collect results from all reviewers
3. Deduplicate similar issues
4. Prioritize by severity and confidence

1. Present findings:

Show the user:

• Critical issues (must fix)
• Moderate issues (should fix)
• Minor suggestions (nice to have)

1. User decides:

Prompt the user to choose:

• Fix all issues now
• Fix critical issues only
• Proceed without fixes
• I will fix manually later

1. If fixing: make the changes and re-review if needed.

1. Proceed immediately to Phase 7.

Phase 7: Summary

Goal: Document and celebrate accomplishments.

1. Summarize accomplishments:

Present to the user:

• What was built
• Key files created/modified
• Architecture decisions made
• Architecture diagram (Mermaid flowchart showing the implemented structure)
• Any known limitations or future work

1. Update CHANGELOG.md:
2. Use the changelog entry template below
3. Refer to the changelog-format skill for Keep a Changelog guidelines
4. Create an entry under the [Unreleased] section with:
5. Appropriate category (Added, Changed, Fixed, etc.)
6. Concise description of the feature
7. If CHANGELOG.md does not exist, create it with proper header
8. Add the entry to the appropriate section under [Unreleased]
9. Inform the user of the update

1. Final message:

Congratulate the user and offer next steps:

• Commit the changes
• Create a PR
• Additional testing suggestions

Error Handling

If any phase fails:

1. Explain what went wrong
2. Prompt the user to choose:
3. Retry the phase
4. Skip to next phase
5. Abort the workflow

Agent Coordination

When launching parallel agents (architecture agents, review agents):

• Give each agent a distinct focus area
• Wait for all agents to complete before proceeding
• Handle agent failures gracefully (continue with partial results)

ADR Template

Use this template when generating Architecture Decision Records in Phase 4.

Template

# ADR-NNNN: [Title]

**Date:** YYYY-MM-DD
**Status:** Accepted
**Feature:** [Feature name/description]

## Context

[Describe the situation that led to this decision. Include:]
- What problem are we solving?
- What constraints do we have?
- What are the driving forces?

## Decision

[State the decision clear