From claude-commands
Displays requirements gathering reminder for active session, showing phase, progress, rules, current state, and next action. Handles corrections for common deviations.
How this command is triggered — by the user, by Claude, or both
Slash command
/claude-commands:requirements-remindcommands/The summary Claude sees in its command listing — used to decide when to auto-load this command
## ⚡ EXECUTION INSTRUCTIONS FOR CLAUDE **When this command is invoked, YOU (Claude) must execute these steps immediately:** **This is NOT documentation - these are COMMANDS to execute right now.** **Use TodoWrite to track progress through multi-phase workflows.** ## 🚨 EXECUTION WORKFLOW ### Phase 1: Execute Documented Workflow **Action Steps:** 1. Review the reference documentation below and execute the detailed steps sequentially. ## 📋 REFERENCE DOCUMENTATION # Requirements Gathering Reminder *Taken from the excellent requirements gathering system by [rizethereum](https://github.co...
When this command is invoked, YOU (Claude) must execute these steps immediately: This is NOT documentation - these are COMMANDS to execute right now. Use TodoWrite to track progress through multi-phase workflows.
Action Steps:
Taken from the excellent requirements gathering system by rizethereum. Thank you for sharing this thoughtful approach!
Quick correction when deviating from requirements gathering rules.
Check requirements/.current-requirement
If no active requirement:
Display reminder based on current context:
🔔 Requirements Gathering Reminder
You are gathering requirements for: [active-requirement]
Current phase: [Initial Setup/Context Discovery/Targeted Context/Expert Requirements]
Progress: [X/Y questions]
📋 PHASE-SPECIFIC RULES:
Phase 2 - Context Discovery:
- ✅ Ask 5 yes/no questions about the problem space
- ✅ Questions for product managers (no code knowledge required)
- ✅ Focus on user workflows, not technical details
- ✅ Write ALL questions before asking any
- ✅ Record answers ONLY after all questions asked
Phase 3 - Targeted Context (Autonomous):
- ✅ Use RepoPrompt tools to search and read code
- ✅ Analyze similar features and patterns
- ✅ Document findings in context file
- ❌ No user interaction during this phase
Phase 4 - Expert Requirements:
- ✅ Ask 5 detailed yes/no questions
- ✅ Questions as if speaking to PM who knows no code
- ✅ Clarify expected system behavior
- ✅ Reference specific files when relevant
- ✅ Record answers ONLY after all questions asked
🚫 GENERAL RULES:
1. ❌ Don't start coding or implementing
2. ❌ Don't ask open-ended questions
3. ❌ Don't record answers until ALL questions in phase are asked
4. ❌ Don't exceed 5 questions per phase
📍 CURRENT STATE:
- Last question: [Show last question]
- User response: [pending/answered]
- Next action: [Continue with question X of 5]
Please continue with the current question or read the next one from the file.
"Let me rephrase as a yes/no question..."
"Let me ask one question at a time..."
"I apologize. Let me continue with requirements gathering..."
"Let me add a default for that question..."
npx claudepluginhub jleechanorg/claude-commands --plugin claude-commands/good-questionAsks adaptive, information-maximizing questions to systematically elicit and clarify software requirements until uncertainty is resolved.
/deep-interviewRuns a Socratic requirements interview that turns vague ideas into approval-gated specs. Also supports resume, status, and finalize subcommands.
/requirements-authoring-flowGuides AI through requirements authoring workflow (create/update/review/improve) with mandatory user approvals per phase, producing final requirements set, validation pack, and traceability matrix.
/interviewConducts interactive Socratic interview using provided user input to crystallize vague requirements into precise, actionable specifications.