القائمة
Use when scoping a new feature - produces problem statement, 3-5 candidate approaches, and a recommendation with explicit alternative
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
| name | brainstorming-a-feature |
| description | Use when scoping a new feature - produces problem statement, 3-5 candidate approaches, and a recommendation with explicit alternative |
| kind | workflow |
| audience | dev |
| ai-tools | any |
| complexity | guided |
| time | 30-90 min |
| version | 1.0.0 |
| source | bundled |
Turns a feature idea into a structured brainstorm: a sharp problem statement, the user it serves, the constraints that bound the solution, 3-5 candidate approaches with trade-offs, and a recommendation with an explicit alternative considered.
A brainstorm document: problem statement, user, constraints, 3-5 candidate approaches with trade-offs, recommendation, and the alternative considered.
This is a workflow.
Write the problem in one sentence. Format: "[User] needs to [do X] but [obstacle], which causes [pain]."
If you cannot complete that sentence, the problem isn't sharp enough yet. Interview a real user or revisit the source request.
Specifically. Not "users." Which segment, which role, which context. If multiple — pick the primary one for v1.
What MUST be true of any solution? Examples:
Constraints are not preferences — they're hard limits.
For each: 1-3 sentences describing what it is, what it requires, what it costs, what it forecloses.
If you can only think of one, you haven't brainstormed. Force at least 3, even if some are obviously bad — bad approaches sharpen the good ones.
For each approach against criteria like: time-to-ship, risk, fit with existing system, user experience, future flexibility. Pick a winner.
Explicitly: "I considered [runner-up] and rejected it because [reason]." This is non-negotiable. (See decisions-need-an-alternative.)
Each chosen approach rests on assumptions. List the top 3. Mark which are cheap to test and which are not.
Input: "Add SSO."
Output:
