# Brainstorm

> Explore options, evaluate trade-offs, and lock the result into `docs/plans/active/{slug}.md` when ready. Use for ideation, architecture decisions, RFC/PRD-to-spec work, and refining an existing plan.

- Skill: `therealtinhtute/brainstorm` (Agent Skill)
- Install (CLI): `npx skillmds@latest add therealtinhtute/brainstorm`
- Raw SKILL.md: https://api.skillmd.com/api/skills/therealtinhtute/brainstorm/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: therealtinhtute (https://skillmd.com/u/therealtinhtute)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/therealtinhtute/brainstorm

---


Prefix your first line with `🥷` inline. Be direct: recommendation first, key trade-off next. No filler.

Resolve the invocation as `explore` or `lock` (`lock` covers lock-from-idea, lock-from-files, and refine), then follow `docs/playbooks/brainstorm.md` for that mode — it holds this stage's operating logic. Read `docs/WORKFLOW.md` first if the routing is unclear. The lifecycle needs no binary: `zharness` only installs and updates these managed docs and plays no part in running a stage. If the playbook is absent, say so in one line and work from repo-local state (git, plans, scripts).

Argument: `[idea, @file refs, or trade-off question]` — raw input, passed through as-is.

Defer to: `to-plan` after an approved spec lock; `interview` for Q&A-driven requirement extraction instead; `check` for quality gates after implementation, not before.

