shape-it
Skill2 starsChanged 53 days agoMITView on GitHub
Shape an unsettled idea with the user before planning or building.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mikeleg/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mikeleg/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ask-barbara-liskovSkill
- ask-donald-knuthSkill
- ask-john-ousterhoutSkill
- ask-kent-beckSkill
- ask-linus-torvaldsSkill
- ask-martin-fowlerSkill
- ask-rich-hickeySkill
- aureliusSkill
- conventional-commitSkill
- craft-itSkill
- create-pull-requestSkill
- define-goalSkill
- drive-itSkill
- nextjs-feature-architectureSkill
- own-itSkill
- plan-itSkill
- pr-review-loopSkill
- review-itSkill
- scaffold-itSkill
- summarize-itSkill
- to-issuesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
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
Before asking questions, form your own opinion about the idea.
- Distinctive: line 14
Consider both the technical and business perspective.
- Distinctive: line 20
Ask no more than three focused questions per round.
- Distinctive: line 23
Treat the challenge as a decision tree.
- Distinctive: line 24
Every answer may reveal new decisions, make existing questions irrelevant, or invalidate previous assumptions.
- Distinctive: line 27
Only ask questions whose prerequisites have already been clarified.
- Distinctive: line 28
If a question depends on a decision or assumption that is still open, defer it to a later round.
- Distinctive: line 35
Do not ask the user for information you can find yourself through research, code, documentation, or available tools.
- Distinctive: line 40
Do not rely on guesses for relevant details.
- Distinctive: line 43
Before asking a question, thoroughly think through the possible answers and their consequences.
- Distinctive: line 47
If multiple reasonable approaches exist, compare them and give a clear recommendation.
- Distinctive: line 63
Only include options you genuinely consider reasonable.
- Distinctive: line 64
Prefer a few clear alternatives over a complete list of every conceivable option.
- Distinctive: line 67
Use your experience, research, and judgment to shape the direction together with the user.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Shape It
Your task is to understand and challenge the user's idea until you are both confident that you are solving the right problem with the right approach.
Before asking questions, form your own opinion about the idea. Challenge its value, the underlying assumptions, and the proposed approach. Consider both the technical and business perspective.
Methodology
The challenge runs in rounds.
Ask no more than three focused questions per round. One good question is better than three superficial ones.
Treat the challenge as a decision tree. Every answer may reveal new decisions, make existing questions irrelevant, or invalidate previous assumptions.
Only ask questions whose prerequisites have already been clarified. If a question depends on a decision or assumption that is still open, defer it to a later round.
Challenge the scope as well. Clarify what actually contributes to the goal and what can deliberately remain out of scope.
Gather facts yourself. Do not ask the user for information you can find yourself through research, code, documentation, or available tools.
Research especially when you lack knowledge, need to verify assumptions, or when it could reveal better approaches. Do not rely on guesses for relevant details. However, only research as deeply as necessary to make a difference to the current decision.
Before asking a question, thoroughly think through the possible answers and their consequences. Weigh value, effort, risks, and trade-offs against each other and prefer the simplest approach that reliably achieves the goal.
If multiple reasonable approaches exist, compare them and give a clear recommendation. The user should not have to perform analysis that you can do yourself.
Present each question using this format:
### 1. <short decision title>
<one-sentence question>
**Recommendation: A — <one-sentence reason>**
- **A — <option>:** <consequence>
- **B — <option>:** <consequence>Only include options you genuinely consider reasonable. Prefer a few clear alternatives over a complete list of every conceivable option.
You are not an interviewer. Use your experience, research, and judgment to shape the direction together with the user.
Conclusion
The challenge ends when no relevant question remains open and the shared understanding is concrete enough that the goal, scope, approach, and all decision-relevant details are clearly established.
Then summarize this shared understanding in a few sentences, reduced to what matters most, and have the user confirm or correct it.
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.

