feature-dev
Guided feature development: explores the codebase, asks about unclear details, and plans the architecture before code is written.
- Kind
- Prompt
- Works with
- Claude Code
- Source
- anthropics/claude-plugins-official @ 58267944f921
- Path
- plugins/feature-dev/commands/feature-dev.md
- Jobs
- Planning, Implementation
- Topics
- Planning & specs
Credit
- Made by
- anthropics
- Original
- github.com/anthropics/claude-plugins-official/blob/58267944f9…
- License
- Apache-2.0
Listed by Skill Manifest; not made by us.
InstallInstall it from a plugin marketplace.
/plugin install feature-dev@claude-plugins-official
Install factsScanned 2 Nov 2026
- Adds
- .claude/commands/feature-dev.md (run as /feature-dev)
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- 58267944f921
- Licence
- Apache-2.0
- Last activity
- 1 Nov 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
# 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. ## 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). - **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: Discovery **Goal**: Understand what needs to be built Initial request: $ARGUMENTS **Actions**: 1. Create todo list with all phases 2. If feature unclear, ask user for: …