Review functional requirements against CSP stability failure models.
npx skills add https://github.com/Foo-x/dotfiles --skill requirements-reviewer
Please help me install this Agent Skill. Skill: requirements-reviewer Source: https://github.com/Foo-x/dotfiles/tree/main/claude/skills/requirements-reviewer Command: npx skills add https://github.com/Foo-x/dotfiles --skill requirements-reviewer
This Skill addresses the challenge of ambiguous, incomplete, or poorly structured requirements by providing a systematic, theory-based review process. It ensures requirements are clear, testable, and align with theoretical best practices, preventing costly errors downstream.
Review the provided requirements document using the requirements-reviewer skill.
High-intent search queries and answers about installing and using this skill.
To review functional requirements for completeness and clarity, you can use a systematic process that evaluates specifications against theoretical models like CSP stability failure, checking for liveness, reachability, and safety properties to prevent downstream errors.
A CSP stability failure model in requirements validation is a theoretical framework used to evaluate whether functional specifications properly separate liveness, reachability, and safety properties, ensuring the requirements are robust and testable.
To check if your software requirements properly separate liveness and safety properties, apply a theoretical review process that assesses specification validation against established models, providing structured feedback on separation of concerns.
Yes, the requirements review process works for non-functional requirements as well, assessing them alongside liveness, reachability, and safety properties to ensure overall specification quality and alignment with theoretical best practices.
The best way to validate requirement specifications for ambiguous or incomplete logic is to use a theory-based review that applies frameworks like Michael Jackson's requirements theory and Meyer's Design by Contract to generate actionable improvement feedback.
You should reconsider using a theoretical model for requirements quality checks when your specifications lack defined functional behaviors, as the review process relies heavily on evaluating liveness, reachability, and safety properties within established frameworks.
HigorAlvesCreate technical documentation for system interfaces, data schemas, and failure risks.
magicpro97Transform high-level design documents into implementation-ready specifications with interfaces, schemas, and method signatures.
Foo-xGenerate acceptance and rejection test cases from specifications using CSP failure models.
AGIBuildReview business goals, PRDs, user journeys, and UX designs for completeness and logic.
