requirements-document

A requirements document consolidates user stories, data models, acceptance criteria, and system constraints into a single structured source of truth. This Skill automates the process through a 3-phase discovery workflow that guides you through capturing functional and technical requirements, business rules, quality attributes, and integration touchpoints, producing a versioned, testable document.

Requirements documents should capture role-based access control rules, user stories organized by stakeholder, business data entities with attributes and constraints, acceptance criteria tied to each capability, and integration points with external systems. This Skill structures those inputs across discovery phases to ensure security, compliance, and workflow clarity are documented alongside functional needs.

A data model isn't a prerequisite; this Skill guides discovery by first capturing main capabilities and stakeholders, then mapping business entities, attributes, and rules as part of the requirements process. You can start with feature scope and user roles, and the structured phases help you define the data model alongside functional requirements.

Requirements remain testable and traceable when structured with clear acceptance criteria, versioned sections, and cross-functional inputs tied to specific capabilities and user stories. This Skill organizes outputs to link each requirement to its phase, stakeholder source, and success criteria, enabling validation and change tracking throughout development.

User stories describe what a role needs to accomplish; acceptance criteria specify how to verify the story is complete and working correctly. This Skill structures both within the same document, tying acceptance criteria directly to each user story and business capability so requirements remain concrete and measurable.

Yes. This Skill includes quality attributes and constraints sections specifically for security, compliance, performance, and reliability requirements. The 3-phase discovery process guides capture of regulatory touchpoints, data-handling rules, and integration dependencies alongside functional needs, ensuring compliance and security are built into the requirements from the start.