Jirapan Tunpita

You can write requirement specifications (SRS) with testable business rules and non-functional requirements, build product backlogs with epics, user stories, MoSCoW prioritization and sprint plans, and generate Requirements Traceability Matrices linking requirements to test cases.

These skills target business analysts, product owners, and development teams maintaining a structured docs vault. They suit anyone asked to write requirements, split user stories, plan sprints, prioritize features, or verify requirement coverage before delivery.

The requirement-spec skill applies to docs/01-requirements/01-spec/, while product-backlog covers docs/01-requirements/02-plan/ and 03-task/. The traceability-matrix skill runs across these artifacts, typically before closing a sprint or handing off documents.

It builds and audits an RTM chaining business rule to functional requirement, user story, task, and test case. This reveals requirements with no implementation or testing, plus stories or tasks that appeared without any originating requirement.

You need a docs vault organized under docs/01-requirements/ with spec, plan, and task subfolders. No external dependencies are stated; the skills provide templates and rules for writing requirements, backlogs, and traceability matrices directly in that structure.