feature-design-doc

Draft, update, and fact-check Feature Design Docs against a fixed template.

18|3|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/buYoung/skills --skill feature-design-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-design-doc
Source: https://github.com/buYoung/skills/tree/main/skills/feature-design-doc
Command: npx skills add https://github.com/buYoung/skills --skill feature-design-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Feature Design Docs (FDD) provide a centralized source of truth for design decisions, their rationale, and constraints, ensuring design choices survive implementation and guiding code agents.

Core Features & Use Cases

  • Create, update, and fact-check a single Feature Design Doc against a fixed template.
  • Enforce separation of design decisions from implementation actions (through frontmatter and content structure).
  • Validate freshness, cross-cutting concerns, policy decisions, and risk questions using the canonical reference.
  • Facilitate collaboration by providing a consistent, reusable artifact for design governance and onboarding.

Quick Start

Draft a complete Feature Design Doc for a new feature and ensure it adheres to the canonical template in references/feature_design_doc_template.md.

Frequently Asked Questions about feature-design-doc

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

FAQPage Schema
How do I draft a feature design doc that captures design decisions and rationale?

To draft a feature design doc, apply a fixed template that enforces frontmatter metadata, section content, and cross-cutting concerns, recording design decisions and rationale in a single evergreen source.

What is the best way to maintain feature design docs for iterative improvements?

Maintain feature design docs for iterative improvements by updating and fact-checking the evergreen source against the canonical template, recording revision history and risks for future traceability.

How does a feature design doc template enforce separation of design decisions from implementation actions?

A feature design doc template enforces separation of design decisions from implementation actions through structured frontmatter metadata and content sections, keeping design choices distinct from code execution.

Can I use a feature design doc to validate policy decisions and cross-cutting concerns?

Yes, you can validate freshness, cross-cutting concerns, policy decisions, and risk questions by fact-checking the feature design doc against its canonical reference template.

When do I need a feature design doc for post-implementation reviews?

You need a feature design doc for post-implementation reviews to fact-check recorded design decisions, update revision history, and ensure traceability of constraints and rationale.

What should a feature design doc include to facilitate collaboration and onboarding?

A feature design doc should include frontmatter metadata, design decisions, rationale, cross-cutting concerns, policy decisions, revision history, and risks to provide a consistent artifact for collaboration and onboarding.