<phase-or-classification-skill-name>
I don't have the actual content filled in for this Claude Code skill template. The item you've shared contains placeholder text in angle brackets (like `<phase-or-classification-skill-name>` and `<Skill Title>`) rather than specific details about what the skill does. To write an accurate, factual description for ClaudeWave, I would need the template completed with the actual skill name, purpose, instructions, and use cases. Please provide the filled-in version of this skill definition.
git clone --depth 1 https://github.com/product-on-purpose/pm-skills /tmp/-phase-or-classification-skill-name- && cp -r /tmp/-phase-or-classification-skill-name-/docs/templates/skill-template ~/.claude/skills/-phase-or-classification-skill-name-SKILL.md
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # <Skill Title> <One paragraph overview of what this skill produces and why it matters.> ## When to Use - <Situation 1> - <Situation 2> - <Situation 3> ## When NOT to Use (Optional) - <Common misuse to avoid> - <When another skill is a better fit> ## Instructions When asked to <create artifact>, follow these steps: 1. **<Step 1 Title>** <What to do and why> 2. **<Step 2 Title>** <What to do and why> 3. **<Step 3 Title>** <What to do and why> 4. **<Step 4 Title>** <What to do and why> ## Output Contract Use `references/TEMPLATE.md` as the output format. A complete response should: - <Required element 1> - <Required element 2> - <Required element 3> ## Quality Checklist Before finalizing, verify: - [ ] <Quality criterion 1> - [ ] <Quality criterion 2> - [ ] <Quality criterion 3> ## Examples See `references/EXAMPLE.md` for a completed example.
Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.
Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.
Creates 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.
Generates 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.
Documents 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.