Slash Command

/review-requirements

Reviews feature requirements document against template for completeness, summarizes key elements and gaps, asks clarifications, brainstorms options, and iterates until resolved with next-step guidance.

documentation

developer-tools

npx claudepluginhub codeaholicguy/ai-devkit

Prompt Preview

Review `docs/ai/requirements/feature-{name}.md` and the project-level template `docs/ai/requirements/README.md` to ensure structure and content alignment.

1. **Use Memory for Context** — Search memory for related requirements/domain decisions before starting: `npx ai-devkit@latest memory search --query "<feature requirements>"`.
2. Summarize:
   - Core problem statement and affected users
   - Goals, non-goals, and success criteria
   - Primary user stories & critical flows
   - Constraints, assumptions, open questions
   - Any missing sections or deviations from the template
3. **Clarify ...

Command Content

Other plugins with /review-requirements

/requirements

Gathers non-technical requirements for a feature using EARS syntax from topic or description input, drafts spec file, iterates feedback until approved, saves pipeline state.

rpi

/interview

Conducts structured interview with 30-40 questions to extract requirements and generates REQ-*.md files from ideas, docs, or REQ IDs.

sonnet8 tools

spec-system

/requirements

Generates requirements spec for a feature with user stories, functional requirements, acceptance criteria, and constraints. Uses questionnaire if no <feature-name> provided; supports --auto flag.

sddw

Stats

Stars1178

Forks190

Last CommitMar 24, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Review `docs/ai/requirements/feature-{name}.md` and the project-level template `docs/ai/requirements/README.md` to ensure structure and content alignment. 1. **Use Memory for Context** — Search memory for related requirements/domain decisions before starting: `npx ai-devkit@latest memory search --query "<feature requirements>"`. 2. Summarize: - Core problem statement and affected users - Goals, non-goals, and success criteria - Primary user stories & critical flows - Constraints, assumptions, open questions - Any missing sections or deviations from the template 3. **Clarify ...

Review docs/ai/requirements/feature-{name}.md and the project-level template docs/ai/requirements/README.md to ensure structure and content alignment.

Use Memory for Context — Search memory for related requirements/domain decisions before starting: npx ai-devkit@latest memory search --query "<feature requirements>".
Summarize:
- Core problem statement and affected users
- Goals, non-goals, and success criteria
- Primary user stories & critical flows
- Constraints, assumptions, open questions
- Any missing sections or deviations from the template
Clarify and explore (loop until converged):
- Ask clarification questions for every gap, contradiction, or ambiguity. Do not just list issues — actively ask specific questions to resolve them.
- Brainstorm and explore options — For key decisions, trade-offs, or areas with multiple viable approaches, proactively brainstorm alternatives. Present options with pros/cons and trade-offs. Challenge assumptions and surface creative alternatives.
- Repeat — Continue looping until the user is satisfied with the chosen approach and no open questions remain.
Store Reusable Knowledge — If new reusable requirement conventions are agreed, store them with npx ai-devkit@latest memory store ....
Next Command Guidance — If fundamentals are missing, go back to /new-requirement; otherwise continue to /review-design.