requirements-document

Generate a consolidated requirements document through a structured 3-phase discovery process.

35|1|Updated Nov 6, 2011

Search Tags:#requirements #RBAC #user-stories #acceptance-criteria #data-model

Ready to run

npx skills add https://github.com/steveclarke/dotfiles --skill requirements-document

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-document
Source: https://github.com/steveclarke/dotfiles/tree/main/ai/skills/requirements-document
Command: npx skills add https://github.com/steveclarke/dotfiles --skill requirements-document

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams capture all requirements in a single consolidated document, including user stories, data models, rules, security, performance, and integration needs.

Core Features & Use Cases

User Stories & Business Needs: Structured by role with core capabilities.
Business Data & Rules: Entities, attributes, constraints, and rules.
Quality Attributes & Constraints: Performance, security, reliability, scalability, compliance.
Integration & Success: Touchpoints, testing approaches, acceptance criteria.

Quick Start

Start by listing the main capabilities and stakeholders for the feature.

Frequently Asked Questions about requirements-document

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

FAQPage Schema

How do I create a consolidated requirements document for my project?▼

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.

What should a requirements document include for RBAC and user workflows?▼

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.

Do I need to start with a data model before writing requirements?▼

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.

How do I ensure requirements are testable and traceable?▼

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.

What's the difference between user stories and acceptance criteria in requirements?▼

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.

Can this approach work for projects with complex security and compliance needs?▼

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.