unknowns-buy-in-doc
Skill2 starsChanged 4 months agoMITView on GitHub
Package completed work into a stakeholder buy-in/sign-off artifact. Use when the user asks for a pitch doc, sign-off doc, Slack-ready summary, rollout package, objection handling, or a review artifact that leads with demo/evidence and names who must approve what.
In this repository11 other files it gives its agents.
- know-your-unknownsSkill
- unknowns-blindspot-passSkill
- 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
- unknowns-tweakable-planSkill
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 21
Stop condition: stakeholders know what decision is required and what evidence supports it.
- Distinctive: line 25
Do not write a vague status update.
- Distinctive: line 27
Use HTML when a skimmable demo-first page, FAQ accordions, timeline, or sign-off checklist improves review.
≈ “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 Buy-In Doc
Workflow
Turn completed work into a decision package for other people.
Return:
- Demo or outcome first.
- Problem and why now.
- What changed, with evidence.
- Why this approach beats alternatives.
- Risks, mitigations, rollback, and rollout.
- Objections pre-answered.
- Named asks/sign-offs.
- Stop condition: stakeholders know what decision is required and what evidence supports it.
Rules
Do not write a vague status update. Aim at the objections reviewers would raise. Use implementation notes, prototype, spec, tests, and diff evidence.
Use HTML when a skimmable demo-first page, FAQ accordions, timeline, or sign-off checklist improves review.
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.