feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than diving straight to code.
npx skills add waybarrios/opencode-power-pack --skill feature-dev --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Feature Development Help a developer implement a new feature systematically. Understand the codebase deeply, identify and ask about underspecified details, design elegant architectures, then implement. ## Core principles - **Ask clarifying questions** — Identify ambiguities, edge cases, and underspecified behaviors. Ask specific, concrete questions rather than making assumptions. Wait for user answers before proceeding. - **Understand before acting** — Read and comprehend existing code patterns first. - **Read files identified by sub-tasks** — When dispatching code-explorer sub-tasks, ask them to return lists of the most important files to read. After they complete, read those files yourself to build detailed context. - **Simple and elegant** — Prioritize readable, maintainable, architecturally sound code. - **Track progress** — Use a todo list throughout. ## Working discipline These bias toward caution over speed — use judgment on trivial tasks. - **Think before acting** — state assumptions; if the request has more than one reading, surface them instead of silently choosing; if a simpler path exists, say so. - **Simplicity first** — the minimum that solves the problem; no specul
- Core principles
- Working discipline
- Untrusted data boundary
- Orchestration contract
- Phase 1: Discovery
- Phase 2: Codebase exploration
- Phase 3: Clarifying questions
- Phase 4: Architecture design
- Phase 5: Implementation
- Phase 6: Quality review
- Phase 7: Summary
git rev-parse HEAD git status --short git diff git diff --cached git ls-files --others --exclude-standard
What does the feature-dev skill do?
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than diving straight to code.
How do I install it?
Run `npx skills add waybarrios/opencode-power-pack --skill feature-dev --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From waybarrios/opencode-power-pack, a repository with 443 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.