Agent skill
developing-features
This skill should be used when the user asks to "build a feature", "implement a feature", "add new functionality", "develop a feature", "create a new feature", or when embarking on a multi-phase feature development workflow that requires codebase understanding, architecture design, clarifying questions, implementation, and quality review.
Install this agent skill to your Project
npx add-skill https://github.com/jawhnycooke/claude-plugins/tree/main/plugins/feature-dev/skills/developing-features
SKILL.md
Feature Development Workflow
Guide feature development through a systematic multi-phase process: understand the codebase deeply, identify and ask about all underspecified details, design elegant architectures, implement, and review.
Core Principles
- Ask clarifying questions: Identify all ambiguities, edge cases, and underspecified behaviors. Ask specific, concrete questions rather than making assumptions. Wait for answers before proceeding.
- 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.
- Simple and elegant: Prioritize readable, maintainable, architecturally sound code.
- Use TodoWrite: Track all progress throughout.
Phase 1: Discovery
Goal: Understand what needs to be built.
- Create a todo list with all phases
- If feature is unclear, ask the user:
- What problem are they solving?
- What should the feature do?
- Any constraints or requirements?
- Summarize understanding and confirm with the user
Phase 2: Codebase Exploration
Goal: Understand relevant existing code and patterns at both high and low levels.
- Launch 2-3 code-explorer agents in parallel, each targeting a different aspect:
- Find features similar to the target feature and trace through their implementation
- Map the architecture and abstractions for the feature area
- Analyze the current implementation of related existing features
- Identify UI patterns, testing approaches, or extension points
- Each agent should include a list of 5-10 key files to read
- Read all files identified by agents to build deep understanding
- Present a comprehensive summary of findings and patterns
Phase 3: Clarifying Questions
Goal: Fill in gaps and resolve all ambiguities before designing.
CRITICAL: This is one of the most important phases. DO NOT SKIP.
- Review the codebase findings and original feature request
- Identify underspecified aspects: edge cases, error handling, integration points, scope boundaries, design preferences, backward compatibility, performance needs
- Present all questions to the user in a clear, organized list
- Wait for answers before proceeding to architecture design
If the user says "whatever you think is best", provide a recommendation and get explicit confirmation.
Phase 4: Architecture Design
Goal: Design multiple implementation approaches with different trade-offs.
- Launch 2-3 code-architect agents in parallel with different focuses:
- Minimal changes: smallest change, maximum reuse
- Clean architecture: maintainability, elegant abstractions
- Pragmatic balance: speed + quality
- Review all approaches and form an opinion on which fits best (consider: small fix vs large feature, urgency, complexity, team context)
- Present to the user: brief summary of each approach, trade-offs comparison, recommendation with reasoning, concrete implementation differences
- Ask the user which approach they prefer
Phase 5: Implementation
Goal: Build the feature.
DO NOT START WITHOUT USER APPROVAL.
- Wait for explicit user approval
- Read all relevant files identified in previous phases
- Implement following the chosen architecture
- Follow codebase conventions strictly
- Write clean, well-documented code
- Update todos as progress is made
Phase 6: Quality Review
Goal: Ensure code is simple, DRY, elegant, easy to read, and functionally correct.
- Launch 3 code-reviewer agents in parallel with different focuses:
- Simplicity, DRY, elegance
- Bugs, functional correctness
- Project conventions, abstractions
- Consolidate findings and identify highest severity issues
- Present findings to the user and ask what they want to do (fix now, fix later, or proceed as-is)
- Address issues based on user decision
Phase 7: Summary
Goal: Document what was accomplished.
- Mark all todos complete
- Summarize:
- What was built
- Key decisions made
- Files modified
- Suggested next steps
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
demonstrating-skill-format
Provides a reference template and structural guide for creating Claude Code plugin skills. Activates when the user asks about skill development patterns, requests a skill template, or wants to understand the SKILL.md format and frontmatter options.
coauthoring-documents
Guides collaborative creation of structured documents through a three-stage workflow of context gathering, iterative refinement, and reader testing. Activates when the user drafts documentation, proposals, technical specs, or decision documents that benefit from structured co-authoring.
processing-pdfs
Reads, creates, merges, splits, and edits PDF files, including text and table extraction, form filling, OCR on scanned documents, and watermarking. Activates when the user works with .pdf files or requests any PDF manipulation task.
editing-word-documents
Reads, creates, edits, and formats Word documents (.docx files), including tracked changes, comments, and template-based generation. Activates when the user works with .docx files or requests document authoring, redlining, or text extraction from Word documents.
analyzing-spreadsheets
Creates, edits, and analyzes Excel spreadsheets (.xlsx, .xlsm, .csv), including formula-based calculations, cell formatting, financial modeling, and data analysis with pandas and openpyxl. Activates when the user works with spreadsheet files or requests Excel-related tasks.
creating-presentations
Creates, edits, and analyzes PowerPoint presentations (.pptx files), including slide design, chart and table insertion, HTML-to-PPTX conversion, and template-based generation. Activates when the user works with .pptx files or requests presentation authoring.
Didn't find tool you were looking for?