Feature Dev

This is the methodical approach to feature work: it forces you to explore the codebase first, ask clarifying questions before writing any code, compare architectural approaches, then implement with testing baked in. The structure is opinionated about sequence (discovery, exploration, questions, design, implementation, testing, review) and leans heavily on parallel agents for code exploration, architecture design, and review. It's built for when you're adding something substantial to an unfamiliar codebase and want guardrails against the usual mistakes like assuming requirements or skipping edge cases. The clarifying questions phase is explicitly non-skippable, which will either save you or annoy you depending on how well-specified your features usually are.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 10
skills.sh installs: 544
GitHub stars: 340
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add notedit/happy-skills --skill feature-dev --agent claude-code

Installs into .claude/skills of the current project.

Files

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, implement, test thoroughly, then review.

Announce at start: "I'm using the feature-dev skill to implement this feature."

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
Test thoroughly: Ensure all new code has appropriate test coverage
Use TodoWrite: Track all progress throughout