unknowns-tweakable-plan
Skill2 starsChanged 4 months agoMITView on GitHub
Write implementation plans sorted by the decisions the human is most likely to tweak, with mechanical work buried below. Use when the user asks for a tweakable plan, decision-first plan, plan review artifact, alternatives before sequencing, or wants judgment calls surfaced before implementation.
In this repository11 other files it gives its agents.
- know-your-unknownsSkill
- unknowns-blindspot-passSkill
- unknowns-buy-in-docSkill
- unknowns-design-directionsSkill
- unknowns-domain-bootstrapSkill
- unknowns-implementation-notesSkill
- unknowns-intervention-brainstormSkill
- unknowns-merge-quizSkill
- unknowns-mock-before-wireSkill
- unknowns-reference-mapSkill
- unknowns-spec-interviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 20
Stop condition: high-impact judgment calls are accepted or edited.
- Distinctive: line 24
Do not lead with routine step order.
- Distinctive: line 26
Use HTML when toggles or side-by-side alternatives make plan review easier.
≈ “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
Unknowns Tweakable Plan
Workflow
Optimize for review, not chronological execution.
Return:
- The top decisions likely to change the plan.
- For each decision: recommended choice, alternative, "choose this if", consequences, and evidence.
- Type/API/data/user-facing impacts.
- Execution sequence after the decisions.
- Mechanical work grouped last.
- Copyable tweaks the user can send back.
- Stop condition: high-impact judgment calls are accepted or edited.
Rules
Do not lead with routine step order. If a step is obvious plumbing, move it below the decisions. Surface irreversible or expensive-to-change choices early.
Use HTML when toggles or side-by-side alternatives make plan review easier.
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.