feature-design

Produces a reviewed, decision-closed feature design document grounded in the codebase.

Updated May 26, 2026
One-click install
npx skills add https://github.com/cagriy/dev-skills --skill feature-design-cagriy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-design
Source: https://github.com/cagriy/dev-skills/tree/main/skills/feature-design
Command: npx skills add https://github.com/cagriy/dev-skills --skill feature-design-cagriy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a technical design often leaves open decisions, unverified assumptions, and scope ambiguity that surface mid-implementation. This Skill interviews the user until every material decision is closed, grounds the design in the actual codebase, and self-reviews the result before it ships. ## Core Features & Use Cases - Clarification interview: Iteratively asks questions covering scope, acceptance criteria, data models, interfaces, failure behavior, and cross-project contracts until no open decision remains. - Codebase grounding: Reads existing modules, prior designs, and storm documents, re-verifying inherited claims and path:line citations before designing against them. - Mockups and cross-project briefs: Renders a mockup for any unsettled user-visible surface and writes a self-contained design brief for each other project the feature spans. - Use Case: After brainstorming a reminders feature for a todo app, run the skill to produce a complete design document under features/feature-v<N>-<description>/ that /feature-plan can stage into a TDD implementation plan. ## Quick Start Ask the assistant to run /feature-design with a short description of the feature you want designed, or invoke it right after completing a /feature-storm brainstorm.

Frequently Asked Questions about feature-design

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

FAQPage Schema
How do I create a feature design document from a rough idea?

Run /feature-design with a free-form description of the feature. The skill grounds itself in your codebase, interviews you until every material decision is closed, and writes the design document into a versioned feature folder.

What is the difference between feature-design, feature-plan, and feature-implement?

feature-design produces the decision-closed design document, feature-plan stages it into a TDD implementation plan, and feature-implement builds it one commit per stage. Use feature-design first; it is not for planning, implementation, or bug work.

Can feature-design run without a prior brainstorm or feature-storm?

Yes, cold design is a supported path. If no storm document exists in the feature folder, the skill proceeds directly from your requirements text or asks what you want designed.

Does feature-design work when a feature spans multiple repositories?

Yes. The clarification loop closes the cross-project contract, and the skill writes one self-contained design brief per other project into the feature folder. It never writes into another repository directly.

Why does feature-design ask so many clarifying questions?

The interview runs until a readiness test passes: no hedge language, an empty open-questions section, and a two-engineer equivalence check. This prevents designs built on guesses that would stall the later planning stage.