Skill Claude CodeCodex
Build a Software Requirements Specification using a structured template with labeled requirements, data dictionary, and external interfaces. Use when a project requires a formal, baselined requirements document.
Skill Claude CodeCodex
Identify and classify stakeholders, user classes, and their requirements influence. Use when starting a project to ensure all perspectives are represented and no critical voices are missed.
Skill Claude CodeCodex
Create state-transition diagrams and state tables to model object lifecycle behavior. Use when requirements involve objects that change state based on events and where valid transitions must be constrained.
Skill Claude CodeCodex
Write structured use case specifications with triggers, flows, and exceptions. Use when documenting user-system interactions that require detailed behavioral specification beyond what user stories provide.
Skill Claude CodeCodex
Write requirements-focused user stories with INVEST criteria and structured acceptance criteria. Use when capturing user needs in agile RE contexts where traceability and testability matter.
Skill Claude CodeCodex
Prioritize requirements using a multi-factor value/cost/risk model with relative scoring. Use when stakeholders disagree on priority or when simple ranking fails to capture trade-offs.
Skill Claude CodeCodex
Create a vision and scope document that captures business requirements, project scope, and stakeholder context. Use when launching a new project or product to align all parties on objectives and boundaries.
Skill Claude CodeCodex
Write individual requirements that are clear, testable, and unambiguous using EARS templates and quality checklists. Use when drafting or improving shall-statements and functional requirements.