Spec Requirements

# Spec: Requirements

Define product requirements for: **$ARGUMENTS**

## What This Does

Invokes the **Product Manager** agent to:
- Brainstorm and clarify requirements with you
- Analyze competitor screenshots (if provided)
- Document user stories and acceptance criteria
- Identify edge cases and error states
- Create a complete PRD

## Output

internal-documentation/temp/prd/$ARGUMENTS/ ├── requirements.md # Full PRD └── acceptance-criteria.md # Testable criteria

## Workflow

1. **@agent-android-product-manager** will ask clarifying questions
2. Iterate until requirements are clear
3. PRD is written to the output location
4. **MANDATORY: Agent performs self-review audit**
5. Agent provides self-review verdict (PASS/PASS WITH NOTES/FAIL)
6. **If FAIL**: Resolve critical gaps before proceeding
7. **If PASS or PASS WITH NOTES**: Handoff statement confirms completion

## Self-Review Enforcement

The Product Manager agent MUST execute its Self-Review Protocol before handoff:

**Required Checks:**
- [ ] Requirements are testable (can QA write test cases?)
- [ ] Requirements are unambiguous (only ONE interpretation)
- [ ] Requirements cover happy path AND error cases
- [ ] Requirements are technically feasible
- [ ] Edge cases documented (empty, offline, error, scale, a11y)

**Expected Output:**

SELF-REVIEW VERDICT: PASS | PASS WITH NOTES | FAIL

Quality Score:

• Testable: ✅
• Unambiguous: ✅
• Complete: ⚠️ (3 open questions remain)
• Feasible: ✅

Open Questions: 3 items in open-questions.md

Downstream Ready:

• Designer can proceed: YES
• Data Scientist can define events: YES (after design)
• Developer can estimate: YES

**If FAIL verdict**: Stop workflow, ask user to address gaps, then re-run.

## Next Step

After this completes, run:

/spec-design $ARGUMENTS

## Tips

- Provide screenshots of competitor apps for analysis
- Be specific about what problem you're solving
- Don't skip edge cases - they cause bugs later