feature-dev

Guides end-to-end feature implementation through exploration, architecture comparison, and code review phases.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill feature-dev-alessioscarfone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/AlessioScarfone/aine-copilot-plugins/tree/main/src/aine-misc/skills/feature-dev
Command: npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill feature-dev-alessioscarfone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Adding a new feature to an existing codebase often fails due to missed context, unasked questions, and inconsistent architecture choices. This Skill structures the entire feature development lifecycle so nothing is skipped: codebase exploration, clarifying questions, architecture comparison, implementation, and quality review. ## Core Features & Use Cases - Parallel Codebase Exploration: Launches multiple code-explorer subagents to map similar features, architecture, and testing patterns, then reads the key files they identify. - Structured Clarifying Questions: Surfaces underspecified aspects like edge cases, error handling, and integration points before any design work begins. - Architecture Comparison: Generates minimal, clean, and pragmatic design options via code-architect subagents and presents them in a comparison table with a recommendation. - Multi-Agent Quality Review: Runs three code-reviewer subagents focused on simplicity, correctness, and project conventions after implementation. - Use Case: When asked to add a new API endpoint to an existing service, the Skill explores how similar endpoints are built, asks about auth and error handling requirements, compares design approaches, implements the chosen one, and reviews the result. ## Quick Start Ask the agent to implement a new feature or user story in your codebase, for example: implement a password reset endpoint following the feature-dev workflow.

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 in an existing codebase with AI?▼

Use a phased workflow: explore the codebase with parallel explorer agents, ask clarifying questions about scope and edge cases, compare architecture options, then implement after approval. This Skill automates that sequence and tracks progress with todos.

How to compare architecture approaches before writing code?▼

Launch multiple architect subagents with different focuses — minimal changes, clean architecture, and pragmatic balance — then present the options in a comparison table covering files changed, reuse, risk, and maintainability with a recommendation.

When should I not use a feature development workflow?▼

Avoid it for bug fixes, refactoring existing code, quick one-off edits, or tasks that only need a spec or plan without implementation. The full explore-question-design-implement-review cycle is designed for net-new functionality.

Does this workflow require user approval before implementation?▼

Yes. The workflow waits for explicit user approval after the architecture design phase before writing any code, and also asks the user how to handle review findings — fix now, fix later, or proceed as-is.

How does automated code review work after implementation?▼

Three code-reviewer subagents run in parallel with different focuses: simplicity and DRY, bugs and functional correctness, and project conventions. Findings are consolidated by severity and presented to the user for a decision.