Requirements Engineering Skills for Claude Code, Cowork, Codex, and AI agents.
This repository also configures its own agents. See what RE-Skills tells them →
Skill Claude CodeCodex
Write testable acceptance criteria and acceptance tests for requirements using Given/When/Then, checklist, and rule-based formats. Use when defining the conditions that prove a requirement is correctly implemented.
Skill Claude CodeCodex
Orchestrate requirements engineering for agile projects using just-in-time elaboration and continuous validation. Use when adopting agile and need to adapt RE practices without losing rigor.
Skill Claude CodeCodex
Select the right analysis and modeling techniques based on requirement type, system complexity, and team experience. Use when deciding which visual models and analysis methods to apply during requirements analysis.
Skill Claude CodeCodex
Document business rules as structured, traceable specifications separate from functional requirements. Use when capturing organizational policies, regulations, calculations, or constraints that govern system behavior.
Skill Claude CodeCodex
Evaluate change requests, perform impact analysis, and manage the change control process. Use when requirements changes are proposed and you need a structured approach to assess, approve, and track them.
Skill Claude CodeCodex
Establish and operate a change control process for requirements changes. Use when projects lack a structured way to evaluate, approve, and track requirement modifications after baselining.
Skill Claude CodeCodex
Assess the implications, affected work products, and effort for a proposed requirements change. Use when a change request arrives and you need to determine whether to approve, defer, or reject it.
Skill Claude CodeCodex
Create system context diagrams that define the boundary between the system and its external entities. Use when establishing scope, identifying interfaces, and ensuring all external interactions are captured in requirements.
Skill Claude CodeCodex
Define data elements, structures, and compositions using formal data dictionary notation. Use when documenting the data model to eliminate ambiguity about what each data item means, contains, and how it relates to other data.
Skill Claude CodeCodex
Create entity-relationship diagrams (ERDs) to model data entities, attributes, and relationships. Use when requirements involve structured data and you need to visualize how entities relate to each other.
Skill Claude CodeCodex
Create decision tables and decision trees to specify complex business logic with multiple conditions and outcomes. Use when requirements involve combinatorial logic that is error-prone to express in prose.
Skill Claude CodeCodex
Create dialog maps to model user-system navigation flows, screen inventories, and transition rules. Use when requirements involve user interfaces and you need to specify how users move between screens.
Skill Claude CodeCodex
Plan and conduct stakeholder interviews that uncover real requirements using structured question progressions. Use when you need to elicit requirements directly from users, sponsors, or domain experts.
Skill Claude CodeCodex
Choose the right requirements elicitation technique based on project context, stakeholder access, and information needs. Use when deciding between interviews, workshops, observations, surveys, and other elicitation methods.
Skill Claude CodeCodex
Categorize requirements into Must/Should/Could/Won't buckets with allocation guidelines. Use when timeboxed delivery requires clear scope boundaries and stakeholder alignment on what is in vs. out.
Skill Claude CodeCodex
Plan and conduct observation sessions to discover unstated requirements by watching users work. Use when interviews alone miss tacit knowledge, workarounds, or workflow inefficiencies.
Skill Claude CodeCodex
Choose a requirements prioritization method based on stakeholder count, requirement volume, and decision context. Use when deciding between MoSCoW, value/cost/risk, pairwise comparison, and other prioritization approaches.
Skill Claude CodeCodex
Create activity diagrams and swim-lane diagrams that model cross-functional processes and derive requirements. Use when you need to visualize workflows, identify handoffs, and find missing requirements.
Skill Claude CodeCodex
Select the right prototyping approach based on project risks, requirements uncertainty, and stakeholder needs. Use when deciding what to prototype, at what fidelity, and how to evaluate the results.
Skill Claude CodeCodex
Specify non-functional requirements using Planguage notation with measurable scales, meters, goals, and trade-off analysis. Use when quality attributes like performance, security, or usability need quantified, testable specifications.
Skill Claude CodeCodex
Design requirements questionnaires with effective question types, scales, and bias-resistant ordering. Use when you need to gather requirements data from many stakeholders simultaneously.
Skill Claude CodeCodex
Assess, plan, pilot, and measure improvements to your requirements engineering processes using a 4-phase improvement cycle. Use when requirements defects, rework, or stakeholder dissatisfaction signal that current RE practices need upgrading.
Skill Claude CodeCodex
Select and evaluate requirements engineering tools based on project context, current maturity, and integration needs. Use when choosing between RM tools, deciding to upgrade from spreadsheets, or evaluating commercial RE tool suites.
Skill Claude CodeCodex
Transform raw elicitation outputs into analyzed, modeled, and structured requirements. Use when moving from "what stakeholders said" to "what the system shall do" through visual modeling, data analysis, and requirements decomposition.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: