new-fdd

Conduct a structured interview to generate a Feature Design Doc.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lucas-ferrari-correa/ai-subagents --skill new-fdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-fdd
Source: https://github.com/lucas-ferrari-correa/ai-subagents/tree/main/.claude/skills/new-fdd
Command: npx skills add https://github.com/lucas-ferrari-correa/ai-subagents --skill new-fdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently uncover and document the technical design for a feature by guiding stakeholders through a focused interview, ensuring the resulting FDD is clear, verifiable, and aligned with system architecture.

Core Features & Use Cases

  • Structured interview workflow with prompts for context, objectives, scope, flows, contracts, errors, observability, dependencies, and risks.
  • Produces a standardized FDD document (text) and optionally a JSON representation for tooling and validation.
  • Suitable for software engineering teams defining new features in HLD-aligned projects.

Quick Start

Ask the user for the target directory to save the FDD, then generate the document in kebab-case in that directory and offer an optional JSON export.

Frequently Asked Questions about new-fdd

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

FAQPage Schema
How do I write a feature design document using a structured interview?

A structured interview guides stakeholders step-by-step to capture motivation, objectives, scope, flows, public contracts, errors, observability, dependencies, and risks, producing a standardized Feature Design Doc (FDD).

What is a Feature Design Doc and when do I need one for software engineering?

A Feature Design Doc (FDD) captures the technical design for a feature, including goals, constraints, and verification criteria. It is needed during feature design in HLD-aligned software engineering projects to ensure clarity and alignment.

How do I capture technical goals, constraints, and verification criteria for a new feature?

You can capture these elements by conducting a structured interview that systematically gathers motivation, objectives, scope, flows, public contracts, errors, observability, dependencies, and risks into an FDD.

Can I export a feature design document to JSON for tooling and validation?

Yes, after completing the interview to generate the FDD text document, you can optionally export a JSON representation. This allows integration with downstream tooling and automated validation of the design specs.

Does the feature design interview workflow support HLD-aligned projects?

Yes, the structured interview is explicitly suitable for software engineering teams defining new features in HLD-aligned projects. It ensures the resulting FDD aligns with the broader system architecture.