planning-and-variants
Skill0 starsChanged 34 days agoMITView on GitHub
Turn an owner's request into an agreed plan before implementation. Use when the owner asks to brainstorm or plan, when a request adds a feature or changes behavior, and always when a change visibly alters the UI (rendered design variants first).
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- convergence-reviewSkill
- ecoSkill
- plan-executionSkill
- post-deploy-checkSkill
- provider-evidenceSkill
- receiving-code-reviewSkill
- security-lifecycleSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- convergence-reviewSkill
- ecoSkill
- plan-executionSkill
- planning-and-variantsSkill
- post-deploy-checkSkill
- provider-evidenceSkill
- receiving-code-reviewSkill
- security-lifecycleSkill
- systematic-debuggingSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the request, the affected code and tests, the relevant spec and decisions, and check whether the work already exists on main or in …
- Distinctive: line 14
Write back the intended outcome, constraints and success criteria in a few lines, separating what the owner said from your assumptions.
- Distinctive: line 43
When the change visibly alters the UI (layout, card structure, controls, copy placement):
- Distinctive: line 48
Put the variant choice in the same single question as any other open decisions.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
planning-and-variants
The repository's planning step (decision R-217). It replaces the superpowers brainstorming skill and follows AGENTS.md and CONTRIBUTING.md, which win wherever this text seems to differ.
1. Understand
- Read the request, the affected code and tests, the relevant spec and decisions, and check
whether the work already exists on
mainor in another worktree. - Write back the intended outcome, constraints and success criteria in a few lines, separating what the owner said from your assumptions. Skip questions the request already answers.
- A bug report (wrong behaviour, a regression against approved UI) is a diagnosis request, not a design question: use the systematic-debugging skill and fix it; no variants, no design gate.
2. Classify
Say the classification out loud so the owner can override it, and take the heavier one when unsure:
- Spike: a feasibility question. State the question and the cheapest probe, run it, and report a recommendation; anything built is throwaway.
- Change: pick the tier (T0-T3) from CONTRIBUTING, Risk tiers. The tier sets the records:
T0 has no spec; T1 and T2 get a one-page spec in
docs/specs/<T-NEW>-<slug>/; T2 with parallel workers also gets tasks.md (see the plan-execution skill); T3 adds a design note when there is a real choice.
Hidden complexity found later upgrades the tier; say so and continue.
3. Ask once
Collect every open question that the always-ask list in AGENTS.md covers and ask them in one batch, each with options and your recommendation first. When the owner asked to brainstorm, also offer 2-3 approaches for the main design choice, with trade-offs and your recommendation. Decide everything else yourself and record the reason. Never ask the owner to approve a spec, a plan or an execution mode separately: the owner's yes to the design covers the path to a verified merge.
4. Visible UI: rendered variants
When the change visibly alters the UI (layout, card structure, controls, copy placement):
- Show 2-3 short variants as rendered mockups, not prose: use the inline visual widget or a design tool when available, with states or animation when they matter. Mark your recommendation.
- Put the variant choice in the same single question as any other open decisions.
- Record the pick as one line in the spec ("Variant B, owner, date"); record a decision only if it binds future work.
5. Plan and go
- State one plan line: tier, intended result and acceptance checks.
- For T1-T3 write the spec (Problem, R-xx, AC-xx, Out of scope; a bug may use current, expected and unchanged behaviour) following docs/workflow/formats.md.
- Then implement without further approval gates. For multi-part work, use the plan-execution
skill. Nothing from this skill is written to
docs/superpowersor.superpowers.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

