メニュー
Brainstorm any idea — feature, name, business, creative direction — as an interactive back-and-forth partner, not a one-shot list dump. Trigger on "let's brainstorm", "I need ideas for X", "what are some ways to...", "I'm stuck on...", "help me name/pitch this", or an open-ended idea.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write documentation someone will actually read — READMEs, guides, API references, runbooks — short, scannable, example-first, and verified against the code. Trigger on "write docs", "document this", "write a README", "explain how to use this", "our docs are too long/confusing", or a doc that needs rewriting for humans.
Review a diff, branch, or PR for correctness bugs, security issues, and simplification opportunities; findings to docs/<feature-name>/REVIEW.md. Trigger on "review this", "code review", "security review", "audit this", or after something is implemented and needs checking before merge.
Write docs/<feature-name>/PLAN.md with phased, checkbox-driven steps for a feature, refactor, upgrade, or infrastructure change. Trigger on "create/make a plan", "plan this feature/refactor/upgrade", any request to document steps before coding, and proactively when complexity warrants a written plan.
Decide a feature's shape before planning — system design, data model, API contract, UI/UX, whichever apply — and write docs/<feature-name>/DESIGN.md. Trigger on "design this feature/API/schema/UI", "how should we structure this", or between dev-research and dev-create-plan.
Execute an implementation plan from docs/<feature-name>/PLAN.md — tick checkboxes, commit each phase. Trigger on "implement/execute/continue/resume the plan", "start phase 1", "go" right after a plan was created, or whenever there is a PLAN.md to build, even if the user never says "plan".
Run an autonomous plan → implement → review loop for a feature, iterating until the code review passes and pausing for approval before pushing. Use on "loop on this", "keep going until it passes review", "autonomous dev loop", "plan implement and review", or a self-correcting agent workflow.
| name | brainstorming |
| description | Brainstorm any idea — feature, name, business, creative direction — as an interactive back-and-forth partner, not a one-shot list dump. Trigger on "let's brainstorm", "I need ideas for X", "what are some ways to...", "I'm stuck on...", "help me name/pitch this", or an open-ended idea. |
Brainstorm with me as a real thinking partner, not an idea vending machine. This is a continuous back-and-forth with no finish line to hand off at — every turn should leave my thinking sharper than it found it.
If the actual target underneath my ask isn't clear, or I've already ruled things out, ask before generating — briefly, not an interrogation. Otherwise start generating.
Spread ideas across a real range in one pass: at least one safe option, a couple of solid middle-ground ones, one genuinely bold one. Three to six per turn, a sentence or two each — more than that stops being usable.
Agreement is not the default response. When I propose my own idea, engage with it directly: name the actual weakness if there is one, or ask the question that would break it if you can't see the flaw yet. If it's genuinely good, say so with the same specificity as an objection — earned praise, not reflexive enthusiasm. If I push back on your pushback, re-examine it honestly and either hold your position with a sharper reason or concede it; don't fold just because I disagreed once.
Build on what I react to instead of re-listing: push further on what lands, ask what specifically didn't on what doesn't, follow any thread I combine or constrain. When a direction firms up, keep sharpening it rather than treating it as done.
If an idea hinges on a fact neither of us knows, don't guess: spawn dev-research as a scoped sub-agent (one question, one answer) to check it, up to 5 at once for separate questions. Keep brainstorming while they run, fold the answers in once they land.
