feature-dev

Guides structured feature implementation through seven phases from discovery to quality review.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill feature-dev-juanjo-zurich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/juanjo-zurich/juarvis-v4/tree/main/plugins/feature-dev/skills/feature-dev
Command: npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill feature-dev-juanjo-zurich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing new features without a structured process leads to misunderstood requirements, missed edge cases, and code that ignores existing codebase conventions. This Skill enforces a disciplined seven-phase workflow that ensures deep codebase understanding, explicit clarification of ambiguities, and architectural review before any code is written. ## Core Features & Use Cases - Codebase Exploration: Launches parallel exploration sub-agents to map architecture, abstractions, and similar existing features before designing anything. - Clarifying Questions Phase: Identifies unspecified behaviors, edge cases, and integration points, then waits for explicit user answers before proceeding. - Multi-Approach Architecture Design: Generates minimal-change, clean-architecture, and pragmatic design options with trade-off comparisons and a reasoned recommendation. - Parallel Quality Review: Runs three review sub-agents covering simplicity/DRY, functional correctness, and project conventions after implementation. - Use Case: A developer asks to add a new payment retry feature. The Skill explores existing payment code, asks about retry limits and error handling, presents two architecture options, implements the approved design, and reviews the result for bugs and convention violations. ## Quick Start Ask the agent to implement a new feature using the guided feature development workflow, for example: implement a user notification preferences feature following the structured development process.

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 development workflow with your feature request. It runs seven phases: discovery, codebase exploration via parallel sub-agents, clarifying questions, architecture design with multiple approaches, implementation after your approval, quality review, and a final summary.

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

It launches 2-3 parallel exploration sub-agents, each targeting a different aspect such as similar features, architecture, or UI patterns. Each returns 5-10 key files, which are then read to build deep context before any design work begins.

Does the workflow require user approval before writing code?▼

Yes. Implementation does not start without explicit user approval. The workflow also pauses after the clarifying questions phase and after presenting architecture options, waiting for answers and a chosen approach before proceeding.

What architecture options does the design phase produce?▼

It generates 2-3 approaches in parallel: minimal changes with maximum reuse, clean architecture with elegant abstractions, or a pragmatic balance of speed and quality. Each is presented with trade-offs, a reasoned recommendation, and concrete implementation differences.

When should I not use this guided feature workflow?▼

Avoid it for trivial fixes, typo corrections, or small one-line changes where seven phases add unnecessary overhead. It is designed for significant features or changes where requirements ambiguity and architectural decisions justify the structured process.