skills.rest
dxiiren
dxiirenCOMMUNITY
Explore all skills by this author →
GitHub

define-requirements

Guides structured interrogation and research to produce five staged requirements documents from Discovery through TDD.

Updated Aug 1, 2026
Search Tags:#documentation#specification#requirements#discovery#prd#product planning#interrogation
One-click install
npx skills add https://github.com/dxiiren/project-skeleton --skill define-requirements-dxiiren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: define-requirements
Source: https://github.com/dxiiren/project-skeleton/tree/main/.claude/skills/define-requirements
Command: npx skills add https://github.com/dxiiren/project-skeleton --skill define-requirements-dxiiren

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a vague project idea into a build-ready specification is hard: unasked questions become wrong decisions made unsupervised later. This Skill runs a disciplined requirements pipeline that interrogates the developer in rounds, fans out background research agents in parallel, and writes five staged documents (Discovery, BRD, PRD, FSD, TDD) into .docs/00-requirements/ before any code is written. ## Core Features & Use Cases - Five-stage document pipeline: Produces Discovery, BRD, PRD, FSD, and TDD documents plus a tracker README, dated research appendices, and an audit trail, with strict rules that later stages may refine but never contradict earlier ones. - Parallel research agents: Launches competitor, data/API feasibility, domain knowledge, and integration research agents in one message while interrogation rounds proceed. - UI prototyping step: For products with screens, settles palette, theme modes, and per-page layout via clickable HTML prototypes recorded in DESIGN.md before the build. - Use Case: A developer says "I want to build a trading journal app" with no spec. The Skill asks themed question rounds, researches the market and APIs in the background, then delivers a complete, audited specification a fresh session can build from at 3am. ## Quick Start Ask the AI to run /define-requirements to turn your new project idea into a full Discovery-to-TDD specification.

Frequently Asked Questions about define-requirements

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

FAQPage Schema
How do I write a PRD or requirements spec for a new software project?▼

Run the define-requirements pipeline, which interrogates you in themed rounds of at most four questions while research agents work in parallel. It writes five staged documents (Discovery, BRD, PRD, FSD, TDD) into .docs/00-requirements/ with testable acceptance criteria.

What is the difference between BRD, PRD, FSD, and TDD documents?▼

Each answers one question: the BRD covers why the product exists with measurable success metrics, the PRD defines what gets built with user stories, the FSD specifies how it behaves including edge cases, and the TDD describes how it is built with architecture and schema.

How does the requirements pipeline handle UI and visual design decisions?▼

For products with screens, step D.5 settles design direction, theme modes, and per-page layout using clickable HTML prototypes before any code is written. The chosen palette and layouts are recorded in a root DESIGN.md file that the build treats as law.

When should I not use a full five-stage requirements pipeline?▼

The pipeline is designed for new projects or major capabilities where no spec exists and ambiguity is costly. For small bug fixes, minor features, or exploratory prototypes, a full Discovery-to-TDD pipeline with audits is heavier than the task warrants.

Why must every number in a spec have exactly one authoritative home?▼

Restating a threshold or formula in multiple documents creates two truths that drift apart when either changes. The pipeline requires each number to live in exactly one document, with all other documents citing it rather than copying it.

Related Skills

Explore More Product & Management Skills→
VertaKhanVertaKhan

office-hours

Runs YC-style office hours sessions that interrogate product ideas and produce design documents.

Community
Advanced
NeoLabHQNeoLabHQ
1.5k

analyze-issue

Analyzes a GitHub issue and generates a structured technical specification document.

Official
Intermediate
yckkkkyckkkk
1

design-review

Audit design visuals for inconsistencies and document fixes with screenshots.

Community
Advanced
asengardeonasengardeon

sdd-docs

Generates and updates technical documentation including READMEs, docs, and ADRs via the tech-writer agent.

Community
Basic