feature-dev

Guide engineers through multi-phase feature development from discovery to validation.

340|43|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/notedit/happy-skills --skill feature-dev-notedit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/notedit/happy-skills/tree/main/skills/feature-dev
Command: npx skills add https://github.com/notedit/happy-skills --skill feature-dev-notedit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers implement new features by guiding them through a structured, question-driven process that clarifies requirements, designs robust architectures, and coordinates end-to-end execution from discovery to review.

Core Features & Use Cases

  • Discovery-driven planning: defines scope, asks clarifying questions, and aligns with stakeholders before coding.
  • Multi-phase execution: guides exploration, architecture design, implementation, testing, and quality review in a repeatable workflow.
  • Risk-aware delivery: enforces guardrails, documentation, and test coverage to reduce rework and miscommunication.

Quick Start

Propose a feature draft, then run through the discovery and design phases to produce a complete implementation plan.

Frequently Asked Questions about feature-dev

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

FAQPage Schema
How do I structure feature development from idea to release?

Feature development is structured through a guided multi-phase process covering discovery, architecture design, implementation, testing, and quality review. This enforces documentation, traceability, and quality checks to reduce rework and miscommunication across teams.

What is discovery-driven planning in software engineering?

Discovery-driven planning defines project scope, asks clarifying questions, and aligns stakeholders before coding begins. It ensures product, design, and engineering teams share a clear understanding of requirements to mitigate risks early.

How do I create a feature implementation plan with risk mitigation?

Creating an implementation plan with risk mitigation involves enforcing guardrails, documentation, and test coverage throughout the workflow. This risk-aware delivery method coordinates end-to-end execution to reduce miscommunication and rework.

Can I use a question-driven workflow for small software projects?

Yes, a question-driven workflow is applicable to software projects of varying sizes needing repeatable workflows. It structures exploration and design to produce a complete implementation plan regardless of overall project scale.

Does guided feature development work for coordinating product and engineering teams?

Guided feature development explicitly supports collaboration across product, design, and engineering teams. It structures discovery and validation phases to ensure all stakeholders remain aligned throughout the end-to-end execution process.