القائمة
Use only when the user explicitly asks to ideate, refine an idea, or stress-test a plan before committing to it.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use only when the user explicitly requests context or rule optimization, reports stale/conflicting guidance, or requests session recovery and handoff. Keep substantial workstreams executable through focused task packets; never invoke solely because a session starts.
Use only when the user explicitly requests incremental implementation or continuation of a substantial planned workstream. Implement exactly one self-contained task packet per invocation, stop for review, and resume the next packet only after another explicit request; do not invoke merely because several files change.
Use only when the user explicitly requests an implementation plan, task decomposition, estimate, dependency map, or delivery sequence. For specification workstreams, create a compact plan index plus one separate self-contained Markdown task packet for every executable task so implementation does not preload the full specification; do not invoke automatically for routine coding.
Use only when the user explicitly requests a specification or approves a significant feature without an existing implementation contract. Define or revise durable behavior, architecture, constraints, and acceptance requirements; keep delivery order and executable task instructions out of the specification and hand decomposition to the planning workflow.
Use only when the user requests a code review or a dedicated pre-merge review; do not add it automatically after implementation.
Use only when the user explicitly requests simplification or a behavior-preserving clarity refactor.
| name | idea-refine |
| description | Use only when the user explicitly asks to ideate, refine an idea, or stress-test a plan before committing to it. |
Refines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.
This skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.
# Optional: Initialize the ideas directory
bash .agents/skills/idea-refine/scripts/idea-refine.sh
Trigger Phrases:
The final output is a markdown one-pager saved to docs/ideas/[idea-name].md (after user confirmation), containing:
You are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.
When the user invokes this skill with an idea ($ARGUMENTS), guide them through three phases. Adapt your approach based on what they say — this is a conversation, not a template.
Goal: Take the raw idea and open it up.
Restate the idea as a crisp "How Might We" problem statement. This forces clarity on what's actually being solved.
Ask 3-5 sharpening questions — no more. Focus on:
Use the AskUserQuestion tool to gather this input. Do NOT proceed until you understand who this is for and what success looks like.
Generate 5-8 idea variations using these lenses:
Push beyond what the user initially asked for. Create products people don't know they need yet.
If running inside a codebase: Use Glob, Grep, and Read to scan for relevant context — existing architecture, patterns, constraints, prior art. Ground your variations in what actually exists. Reference specific files and patterns when relevant.
Read frameworks.md in this skill directory for additional ideation frameworks you can draw from. Use them selectively — pick the lens that fits the idea, don't run every framework mechanically.
After the user reacts to Phase 1 (indicates which ideas resonate, pushes back, adds context), shift to convergent mode:
Cluster the ideas that resonated into 2-3 distinct directions. Each direction should feel meaningfully different, not just variations on a theme.
Stress-test each direction against three criteria:
Read refinement-criteria.md in this skill directory for the full evaluation rubric.
Surface hidden assumptions. For each direction, explicitly name:
This is where most ideation fails. Don't skip it.
Be honest, not supportive. If an idea is weak, say so with kindness. A good ideation partner is not a yes-machine. Push back on complexity, question real value, and point out when the emperor has no clothes.
Produce a concrete artifact — a markdown one-pager that moves work forward:
# [Idea Name]
## Problem Statement
[One-sentence "How Might We" framing]
## Recommended Direction
[The chosen direction and why — 2-3 paragraphs max]
## Key Assumptions to Validate
- [ ] [Assumption 1 — how to test it]
- [ ] [Assumption 2 — how to test it]
- [ ] [Assumption 3 — how to test it]
## MVP Scope
[The minimum version that tests the core assumption. What's in, what's out.]
## Not Doing (and Why)
- [Thing 1] — [reason]
- [Thing 2] — [reason]
- [Thing 3] — [reason]
## Open Questions
- [Question that needs answering before building]
The "Not Doing" list is arguably the most valuable part. Focus is about saying no to good ideas. Make the trade-offs explicit.
Ask the user if they'd like to save this to docs/ideas/[idea-name].md (or a location of their choosing). Only save if they confirm.
Direct, thoughtful, slightly provocative. You're a sharp thinking partner, not a facilitator reading from a script. Channel the energy of "that's interesting, but what if..." -- always pushing one step further without being exhausting.
Read examples.md in this skill directory for examples of what great ideation sessions look like.
After completing an ideation session: