agile-re
01Command Claude Code
Run requirements engineering in an agile context — vision, backlog seeding, just-in-time elaboration, and sprint validation.
Command Claude Code
Run requirements engineering in an agile context — vision, backlog seeding, just-in-time elaboration, and sprint validation.
Command Claude Code
Process a requirements change request — classify, analyze impact, and recommend a CCB decision.
Command Claude Code
Model and refine requirements using the right analysis techniques — use cases, data models, state diagrams, and more.
Command Claude Code
Run the complete requirements development lifecycle from vision through validated, baselined requirements.
Command Claude Code
Plan and execute requirements elicitation — select techniques, prepare sessions, and capture stakeholder needs.
Command Claude Code
Set up and run requirements management for baselined requirements — change control, traceability, and status tracking.
Command Claude Code
Select the right prioritization method and rank requirements by value, cost, and risk.
Command Claude Code
Review and validate requirements using the right level of formality — walkthroughs, inspections, testing, or prototypes.
Command Claude Code
Create a structured SRS document with well-written requirements, data dictionary, and acceptance criteria.
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.
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: