documentation
Installation
SKILL.md
Documentation & Requirements
Overview
Software specifications capture the "what" and "why" before implementation addresses the "how." Well-structured requirements documents, architecture decisions, and executable specs reduce ambiguity, align stakeholders, and create verifiable acceptance criteria.
Document Types
Requirements Documents
| Type | Audience | Focus |
|---|---|---|
| PRD (Product Requirements) | Product + Engineering | Features, user stories, success metrics |
| TRD (Technical Requirements) | Engineering | Architecture, APIs, data models, constraints |
| BRD (Business Requirements) | Business + Leadership | ROI, market need, business objectives |
Architecture Documents
| Type | Audience | Focus |
|---|---|---|
| ADR (Architecture Decision Record) | Engineering | Single decision with context and consequences |
| RFC (Request for Comments) | Engineering + Stakeholders | Proposed change seeking feedback |
Related skills