| name | gen-idea |
| description | Clarify a loose product or engineering idea through focused user discovery, repository research, and distinct design options, then write a concise spec. Use for brainstorming, requirement discovery, 头脑风暴, 需求澄清, or before gen-plan. |
Gen Idea
Turn an incomplete idea into an approved, repo-grounded spec. Do not implement it.
Input
Accept idea text or one readable Markdown file, plus:
--n <2..6>: design directions; default 3.--output <path>: spec path; default <PROJECT_ROOT>/spec.md.
Run inside a Git repository. Reject invalid options, a missing path-like input, an input/output
collision, or an overwrite the user has not confirmed.
Workflow
- Preserve the input verbatim. Read applicable repo instructions, the root README, and the code
needed to avoid asking questions the repository can answer.
- Interview the user one question at a time. Ask only questions whose answers can change the
design. Cover the goal, users, success state, scope, constraints, tradeoffs, and important edge
cases. Offer concrete choices and a recommendation when useful.
- Keep asking while material uncertainty remains; do not stop at an arbitrary question count.
Record nonblocking unknowns instead of forcing false certainty.
- Develop
n genuinely different directions. Use independent read-only agents when available.
Verify cited paths; write exploratory, no concrete precedent when evidence is absent.
- Compare the directions, recommend one, and get the user's explicit approval or correction.
- Read
assets/spec-template.md, fill it concisely, and write only the approved output file.
Quality Bar
- Preserve the user's goal; do not quietly expand it.
- Separate required outcomes from possible implementation choices.
- Include rejected alternatives and why they lost.
- Leave no blocking decision hidden in prose.
Report the spec path and suggest gen-plan <spec-path> as the next step.
