AI导哈

其他

tool-foundation-sprint-basics

product-on-purpose/pm-skills

Day 1 morning move of a Foundation Sprint. Forces explicit team choices on target customer, important problem, team advantage, and competitors and alternatives. Produces a single coherent strategic frame that becomes the input to Day 1 afternoon Differentiation. Use after the sprint brief is signed and Day 1 morning is scheduled. Bundled artifact, not four separate decisions.

  • 631 次安装
  • 770 星标
  • 收录于

安装命令

npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-foundation-sprint-basics

SKILL.md

Foundation Sprint Basics

Day 1 morning of a Foundation Sprint. The team makes four foundational choices explicit: who the product is for, what important problem it solves, why this team has a right to win, and what customers do today instead. The output is one coherent strategic frame, not four separable decisions.

Family contract: docs/reference/skill-families/foundation-sprint-skills-contract.md. This skill is a member of foundation-sprint-skills.

When to Use

  • Day 1 morning of a Foundation Sprint, after the brief is signed.
  • The team has sufficient customer and market knowledge (per readiness verdict) to make informed choices.
  • Each of the four sub-decisions is open or contested; the team has not pre-aligned on any of them.
  • The Decider is in the room and ready to sign off on the bundled output before lunch.

When NOT to Use

相关 Skills

deliver-acceptance-criteriaproduct-on-purpose/pm-skillsGenerates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.测试与安全1076deliver-prdproduct-on-purpose/pm-skillsCreates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.其他1027deliver-user-storiesproduct-on-purpose/pm-skillsGenerates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.智能体工作流905deliver-edge-casesproduct-on-purpose/pm-skillsDocuments edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.测试与安全885discover-competitive-analysisproduct-on-purpose/pm-skillsCreates a structured competitive analysis comparing features, pricing, and positioning across 3-5 direct and indirect competitors, with a 2x2 map and actionable strategic recommendations. Use before entering a market, planning differentiation, or after losing deals. For market size rather than competitor positioning, use discover-market-sizing instead.数据与研究845define-problem-statementproduct-on-purpose/pm-skillsCreates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.其他834