brainstormlisted

______________________________________________________________________ ## brainstorm **Skill metrics:** Emit a start event to the activity log: ```bash echo "{\"type\":\"skill\",\"event\":\"start\",\"skill\":\"brainstorm\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}" >> docs/sessions/.activity-log.jsonl ``` Brainstorming: **$ARGUMENTS** ## Plan Mode (Optional) For complex or high-stakes brainstorms, consider using Plan Mode for Phases 1-4. This adds an extra layer of safety by preventing premature implementation during design exploration. **When to use:** The idea is architecturally significant, affects multiple systems, or the user explicitly requests a careful exploration. **How:** Enter Plan Mode before Phase 1. Remain in Plan Mode through Phase 4 (risk identification). Exit Plan Mode before Phase 5 (design presentation) so you can interact with the user for approval. ## 1. Explore the Problem Space Understand the idea deeply before proposing solutions: - What problem does this solve? Who benefits? - What are the constraints (technical, business, time)? - What similar functionality already exists in the codebase? - What are the non-negotiable requirements vs nice-to-haves? **Product requirements context:** Read `docs/reference/PRD_SUMMARY.md` if it exists. Use Section 3 (success criteria) as evaluation criteria for approaches in Phase 3. Use Section 7 (scope boundaries) to ensure no approach violates stated non-goals or implementation boundaries. Use Section 6 (N