agentsclimarketplace

Buy in

Skill ajitta/know-your-unknowns/skills/buy-in

The buy-in doc — after implementation, produce a ship-readiness pitch that leads with a working demo, pre-answers likely reviewer objections with evidence, states known limitations, and names the stakeholders who must sign off. This skill should be used when the user says "buy-in doc", "buy-in 문서", "prep me for review", "prepare for merge approval", "설득 문서 만들어줘", "리뷰 준비", "머지 승인 준비해줘", "pitch this work", or before requesting review/approval/merge of significant work.From its SKILL.md

Install
npx -y skills add ajitta/know-your-unknowns --skill buy-in

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, as published. Nobody here has run it

Buy-in — Reviewer Persuasion Doc (The Buy-In Doc)

Implementation done, but others' approval remains an unknown. Know what reviewers will ask in advance — it becomes known. Original "The Buy-In Doc": show working demo first, preempt reviewer objections with evidence, name who must sign off. /unknowns:quiz validates my understanding; buy-in prepares others' trust.

Procedure

  1. From $ARGUMENTS, identify target work and audience (reviewers, team, decision-makers).
  2. Demo first: working result at top of doc — execution output, screenshot/GIF, interactive demo operable inside the doc if possible.
  3. Preempt objections: anticipate ~5 questions/objections reviewers would raise, answer each with evidence (test results, benchmark numbers, code locations, design rationale). No unsupported rebuttals — no evidence, move it to limitations.
  4. Known limitations and unresolved unknowns: if IMPLEMENTATION_NOTES.md exists, pull recorded deviations and unresolved risks here. Not hiding is the basis of trust.
  5. Sign-off list: name people/teams needing to approve, with roles, and assign what each must check.
  6. Rollback plan: one paragraph on how to revert if things break.

Output Format (HTML first)

Single-file interactive HTML: top demo (animation, execution example), expandable card per objection (objection → evidence), limitations section, sign-off checklist (check each item → assembles into review-comment draft). Inline CSS/JS, no external dependencies. No viewer available, or target is a PR body — fall back to markdown with same structure.

Integration

  • Run /unknowns:quiz before writing — work the user can't explain can't be defended in a buy-in doc either.
  • independent-reviewer agent's verification results (including "verified" list) are the strongest evidence for objection responses.

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.