devdocs-requirements

You can generate a traceability matrix for user stories by expanding brief prompts into structured DevDocs, which automatically produces a ready-to-use matrix linking features, user stories, and acceptance criteria for your project.

Yes, you can append new user stories to existing DevDocs requirements. The Skill supports incremental updates, allowing you to add features and acceptance criteria while preserving existing content and numbering within the 01-requirements.md document.

The best way to structure non-functional requirements is to generate a dedicated 01-requirements-nfr.md document, capturing technical constraints and domain knowledge alongside the main PRD to establish a clear baseline for product development.

Yes, this requirements clarification tool supports retrofit projects. It applies to product development workflows and PRD creation, ensuring background information, technical constraints, and project domain knowledge are captured for legacy system updates.

To start generating DevDocs from a short requirement prompt, use the /devdocs-requirements command to create the initial 01-requirements.md file, then iteratively update the document with incremental changes and additional context.