Add optional review and refine step to workflows:brainstorm and workflows:plan
that checks documents for clarity, completeness, user intent, and YAGNI.
- New document-review skill with review questions and evaluation criteria
- Brainstorm Phase 4 offers "Review and refine" option
- Plan post-generation offers "Review and refine" after technical review
- Includes YAGNI-based simplification guidance
- Max 2 iteration rounds before suggesting to proceed
Co-authored-by: Kieran Klaassen <kieranklaassen@users.noreply.github.com>
- Move plans from `plans/` to `docs/plans/` for consistency with other artifacts
- Add date prefix (YYYY-MM-DD) to both plans and brainstorms for chronological sorting
- Add self-documenting suffixes: `-plan` and `-brainstorm` to identify artifact type
- Update filename derivation to extract title from content, not filename
- Clarify deepened plan naming: append `-deepened` after `-plan` suffix
New conventions:
- Brainstorms: `docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md`
- Plans: `docs/plans/YYYY-MM-DD-<type>-<name>-plan.md`
- Deepened: `docs/plans/YYYY-MM-DD-<type>-<name>-plan-deepened.md`
* feat(workflows:plan): Add smart research decision logic
Previously, /workflows:plan always ran all 3 research agents (repo-research,
best-practices, framework-docs) regardless of task complexity. This wasted
tokens and time for simple tasks like UI tweaks or bug fixes with clear causes.
Now the workflow:
- Always runs repo research first (fast, local)
- Makes an informed decision about external research based on:
- Signals gathered during idea refinement (familiarity, intent, risk)
- Repo research findings (existing patterns, CLAUDE.md guidance)
- High-risk topics (security, payments, external APIs) always trigger research
- Strong local context allows skipping external research
- Announces the decision and proceeds, user can redirect if needed
This makes the planning workflow smarter about when web research adds value.
* feat: Add /workflows:brainstorm command and skill
Add brainstorming workflow to explore requirements and approaches
before planning implementation:
- New `/workflows:brainstorm` command for collaborative dialogue
- New `brainstorming` skill with process knowledge and techniques
- Update `/workflows:plan` to detect brainstorm output and skip
idea refinement when relevant brainstorm exists
- Add brainstorm to README workflow commands table
The brainstorm → plan flow enables:
- Phase 0: Assess requirement clarity
- Phase 1: Understand the idea via repo research + dialogue
- Phase 2: Explore 2-3 approaches with trade-offs
- Phase 3: Capture design to docs/brainstorms/
- Phase 4: Handoff to /workflows:plan
