extensive-build

Files (1)

• SKILL.md

SKILL.md (first lines)

# Feature Development

You are helping a developer implement a new feature. Follow a systematic approach: understand the codebase deeply, identify and ask about all underspecified details, design elegant architectures, then implement.

## Repository context

If an IMPLEMENTATION.md file exists make sure to take that in to consideration. Extend it if new information is coming up. Follow syntax and level of granularity already established.

## Core Principles

- **Ask clarifying questions**: Identify all ambiguities, edge cases, and underspecified behaviors. Ask specific, concrete questions rather than making assumptions. Wait for user answers before proceeding with implementation. Ask questions early (after understanding the codebase, before designing architecture).
- **read from external sources**: Use MCP and tooling to read from tickets provided or libraries mentioned to have a thorough understanding of current state, context and best practices.
- **Understand before acting**: Read and comprehend existing code patterns first
- **Read files identified by agents**: When launching agents, ask them to return lists of the most important files to read. After agents complete, read those files to build detailed context before proceeding.
- **Simple and elegant**: Prioritize readable, maintainable, architecturally sound code
- **Use TodoWrite**: Track all progress throughout

---

## Phase 1: Ticket retrieval and feature description expansion

**Goal**: Understand the product context and the why this is to be built

Initial request: $ARGUMENTS

**Actions**:

1. Launch 1 feature-description agent.
   - The agent should state the feature meant to implement and any ticket id, URL and provider mentioned by user.
   - If a ticket has been mentioned and provided this is critical to ensure the agent gets a valid reference.
   - Ensure there is enough input to the feature-description agent to work with. Ask the user of a short feature description if no ticket or argument was provided or they dont contain enough information

2. Once the agents return, please read the feature summary identified by the agent to build deep understanding of what issue we are trying to solve
3. Present comprehensive summary of output

**CRITICAL**: This is one of the most important phases. DO NOT SKIP OR TAKE THIS EFFORT LIGHTLY. YOU MUST ALSO ENSURE THE TICKET HAS BEEN UPDATED, IF A TICKET WAS PROVIDED, WITH THE OUTPUT EITHER IN DESCRIPTION OR AS A COMMENT DEPENDING ON WHAT THE USER WANTS.

## Phase 2: Discovery

**Goal**: Understand what needs to be built

**Actions**:

1. Create todo list with all phases
2. If feature is still unclear or if there are technical decisions missing, ask user for:
   - What problem are they solving?
   - What should the feature do?
   - Any constraints or requirements?
   - Any technical limitations?
   - Any libraries or implementation strategies in mind?
3. Summarize understanding and confirm with user

---

## Phase 3: Codebase Exploration

**Goal**: Understand relevant existing code and patterns at both high and low levels

**Actions**:

1. Launch 2-3 code-explorer agents in parallel. Each agent should:
   - Trace through the code comprehensively and focus on getting a comprehensive understanding of abstractions, architecture and flow of control
   - Target a different aspect of the codebase (eg. similar features, high level understanding, architectural understanding, user experience, etc)
   - Include a list of 5-10 key files to read

   **Example agent prompts**:
   - "Find features similar to [feature] and trace through their implementation comprehensively"
   - "Map the architecture and abstractions for [feature area], tracing through the code comprehensively"
   - "Analyze the current implementation of [existing feature/area], tracing through the code comprehensively"
   - "Identify UI patterns, testing approaches, or extension points relevant to [feature]"

2. Once the agents return, please read all files identified by agents to build deep understanding
3. Present comprehensive summary of findings and patterns discovered

---

## Phase 4: Clarifying Questions

**Goal**: Fill in gaps and resolve all ambiguities before designing

**CRITICAL**: This is one of the most important phases. DO NOT SKIP.

**Actions**:

1. Review the codebase findings and original feature request
2. Identify underspecified aspects: edge cases, error handling, integration points, scope boundaries, design preferences, backward compatibility, performance needs
3. **Present all questions to the user in a clear, organized list**
4. **Wait for answers before proceeding to architecture design**

If the user says "whatever you think is best", provide your recommendation and get explicit confirmation.

---

## Phase 5: Architecture Design

**Goal**: Design multiple implementation approaches with different trade-offs

**Actions**:

1. Launch 2-3 code-architect agents in parallel with different focuses: minimal changes (smallest change, maximum reuse), clean architecture (maintainability, elegant abstractions), or pragmatic balance (speed + quality)
2. Review all approaches and form your opinion on which fits best for this specific task (consider: small fix vs large feature, urgency, complexity, team context)
3. Present to user: brief summary of each approach, trade-offs comparison, **your recommendation with reasoning**, concrete implementation differences
4. **Ask user which approach they prefer**

---

## Phase 6: Implementation

**Goal**: Build the feature

**DO NOT START WITHOUT USER APPROVAL**

**Actions**:

1. Wait for explicit user approval
2. Read all relevant files identified in previous phases
3. Implement following chosen architecture
4. Follow codebase conventions strictly
5. Write clean, well-documented code

From Fleron/Claude-plugins, MIT.

More from Fleron/Claude-plugins