feature-dev

Guides feature implementation through a seven-phase workflow with codebase exploration and review.

507|40|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/waybarrios/opencode-power-pack --skill feature-dev-waybarrios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/waybarrios/opencode-power-pack/tree/main/skills/feature-dev
Command: npx skills add https://github.com/waybarrios/opencode-power-pack --skill feature-dev-waybarrios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building new features without a structured process leads to misunderstood requirements, missed edge cases, and code that ignores existing conventions. This Skill enforces a methodical seven-phase workflow so features are understood, designed, implemented, and reviewed before shipping. ## Core Features & Use Cases - Structured Seven-Phase Workflow: Discovery, codebase exploration, clarifying questions, architecture design, implementation, quality review, and summary. - Parallel Sub-Task Orchestration: Dispatches code-explorer, code-architect, and code-reviewer sub-tasks with a strict assignment envelope, coverage ledger, and recovery order. - Untrusted Data Boundary: Treats repository files, PR metadata, and tool output as untrusted data, redacts secrets, and rejects scope-widening embedded instructions. - Use Case: When asked to add a new API endpoint, the Skill explores the codebase, asks clarifying questions about error handling and compatibility, presents three architecture options with trade-offs, implements after approval, and runs three parallel code reviews. ## Quick Start Ask the agent to implement a new feature using the feature-dev workflow and answer its clarifying questions before approving an architecture.

Frequently Asked Questions about feature-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a new feature with a structured workflow?▼

Invoke the feature-dev workflow and it walks through seven phases: discovery, codebase exploration, clarifying questions, architecture design, implementation, quality review, and summary. It waits for your answers and approval before writing code.

How does the skill explore an unfamiliar codebase before coding?▼

It dispatches 2-3 parallel code-explorer sub-tasks targeting different aspects such as architecture, similar features, and extension points. Each returns 5-10 key files, which the parent then reads directly to build detailed context.

Can it compare multiple architecture approaches before implementation?▼

Yes. It dispatches parallel code-architect sub-tasks covering minimal changes, clean architecture, and pragmatic balance. It presents trade-offs, gives a recommendation, and asks which approach you prefer before implementing.

Does the workflow start coding without user approval?▼

No. Implementation requires explicit user approval after the architecture phase. It also captures a Git baseline before editing and derives an implementation delta afterward for full change provenance.

What happens when a sub-task fails or returns incomplete output?▼

It follows a recovery order: retry transient failures once, resume the child once for malformed output, then fall back to performing the assignment in the parent. Uncovered scope stays non-valid and is disclosed in the final summary.