Produce cross-domain PRODUCT-SPEC.md files with scope, risks, and success criteria.
npx skills add https://github.com/kouko/monkey-skills --skill planning-team
Please help me install this Agent Skill. Skill: planning-team Source: https://github.com/kouko/monkey-skills/tree/main/domain-teams/skills/planning-team Command: npx skills add https://github.com/kouko/monkey-skills --skill planning-team
Helps teams turn ambiguous ideas into a cross-domain, actionable PRODUCT-SPEC.md that captures scope, validated assumptions, and measurable success criteria so downstream design, engineering, and research work can begin without guesswork or rework.
Create a PRODUCT-SPEC.md for a new project by running the planning-team intake, drafting a Job Story, tagging the top three assumptions with [ASSUMPTION] mapped to Value/Usability/Feasibility/Business Viability, naming MVP learning goals, and listing OKR-style success criteria.
High-intent search queries and answers about installing and using this skill.
To create a cross-domain product spec, run structured intake to elicit a Job Story, map top assumptions to the 4 Big Risks, and define MVP learning objectives with OKR-based success criteria in a PRODUCT-SPEC.md file.
Assumption mapping in product planning identifies top hypotheses and tags them to Value, Usability, Feasibility, and Business Viability risks, needed during new project kickoffs or major direction changes to prevent downstream rework.
Define measurable success criteria by establishing OKR-based metrics and MVP learning goals during the spec writing process, ensuring cross-domain teams have clear, validated targets before development begins.
Yes, you can ground a PRODUCT-SPEC.md in JTBD, Lean Startup, and Business Model Canvas frameworks by explicitly attributing authors and translating the frameworks into structured goals, non-goals, and UX directions.
The best way to handle cross-domain consistency is running checkpoint-based quality gates where an evaluator checks MUST and SHOULD compliance, applying retry rules and BLOCKED handling for any failed artifacts.
Skipping intake brainstorming risks missing critical spark context, Job Stories, and assumption mapping, leading to ambiguous scope and guesswork that forces rework across design, engineering, and research teams.
reez455GRefine raw ideas into actionable concepts through structured dialogue and markdown one-pagers.
kmshihab7878Generate company-to-team OKRs and strategic product roadmaps with alignment scores and JSON export.
koukoRoutes domain-specific tasks to the correct team based on intent and required deliverables.
dobachiDesign business models with Business Model Canvas and Lean Canvas frameworks.
