菜单
Explore a rough idea with the user, clarify requirements, and draft a spec. Also decomposes large specs into smaller ones (e.g. /brainstorm "offline mode", /brainstorm <gest-id>).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Take an iteration and execute it: dispatch /implement agents per phase, always sequentially (e.g. /orchestrate <iteration-id>).
Take an iteration and execute it: dispatch /implement agents per phase with git worktree isolation for parallel work (e.g. /orchestrate <iteration-id>).
Take an iteration and execute it: dispatch /implement agents per phase with jj workspace isolation for parallel work (e.g. /orchestrate <iteration-id>).
Promote a gest task to a GitHub Issue (e.g. /promote-task <id>).
Implement a single issue: write code, verify, review, format, and commit (e.g. /implement <gest-id>).
Take a spec and create an implementation plan: tasks, ADRs for large features, and dependency ordering (e.g. /plan <gest-id>).
| name | brainstorm |
| description | Explore a rough idea with the user, clarify requirements, and draft a spec. Also decomposes large specs into smaller ones (e.g. /brainstorm "offline mode", /brainstorm <gest-id>). |
| args | <rough idea or gest artifact ID to decompose> |
Explore a problem space with the user and produce a spec.
Read the input provided by the user. Determine the mode:
For rough ideas, delegate to the brainstormer agent with the idea. The agent will research the codebase and return a structured context report covering existing patterns, constraints, complexity, and open questions. Use the research report to ground the conversation.
For existing specs, retrieve the spec via
cargo run -- artifact show <id> --json for structured parsing,
or without --json for human-readable output. Identify natural decomposition boundaries.
Ask clarifying questions one at a time. Do not front-load a list of questions. Wait for the user's answer before asking the next. Use the brainstormer's open questions as a starting point for rough ideas, or scope boundaries for decomposition.
Once the problem is well-understood, propose 2-3 approaches with trade-offs and complexity estimates. Ground each approach in the constraints and existing patterns surfaced by the brainstormer. Ask the user which approach to pursue.
Invoke /write-spec with the agreed-upon approach. The skill will output a gest artifact ID for the new spec.
For decomposition, invoke /write-spec for each sub-spec, linking them back to the parent.
Print next-step hint: invoke /plan <id> when you're ready for the next step (using the spec's gest ID).
