Document product decisions with rationale, alternatives, and tradeoffs.
npx skills add https://github.com/pisithrps/yapzee --skill decision-doc-pisithrps
Please help me install this Agent Skill. Skill: decision-doc Source: https://github.com/pisithrps/yapzee/tree/main/.claude/skills/decision-doc Command: npx skills add https://github.com/pisithrps/yapzee --skill decision-doc-pisithrps
Many product decisions lack a concise record of rationale, tradeoffs, and stakeholder agreement, which causes repeated debates, misalignment, and lost institutional memory. This Skill structures decisions so teams can make timely choices, communicate why they were made, and revisit outcomes later.
Create a decision document recommending build versus partner for feature X with options, pros and cons, recommended choice, confidence level, key metrics, and next steps.
High-intent search queries and answers about installing and using this skill.
To document product decisions with rationale and tradeoffs, use a structured decision log that records options, pros, cons, and a clear recommendation. This ensures stakeholder alignment by providing a concise record of why choices were made.
The best way to structure a build vs buy decision document is using a templated format that includes side-by-side option breakdowns, cost assumptions, success criteria, and mitigation plans. This produces a shareable record for executive review.
Yes, you can use different decision framework templates for varying risk profiles. Standard, DACI, One-Way Door, and Lightweight formats fit different audiences and risk levels, ensuring the decision log matches the context's required depth.
To route stakeholder approvals and notifications after finalizing a recommendation, generate suggested stakeholder routing guidance and announcement copy. This directs approvals and communicates the decision rationale to relevant teams.
You need a formal decision log for cross-functional tradeoffs and architectural choices when repeated debates occur or institutional memory is at risk. Documenting assumptions and success metrics prevents misalignment and lost context.
dev-khoiDocument product decision rationale, options, and outcomes with structured criteria.
wme3Document final project decisions with rationale and traceable artifacts.
SoufianouassifGenerate PRDs, user stories, and roadmaps with acceptance criteria and DACI roles.
adolfoaranaes12Create Architecture Decision Records with context, alternatives, rationale, and consequences.
