<skill-name>
Scannednpx machina-cli add skill product-on-purpose/pm-skills/skill-template --openclaw<Skill Title>
<One paragraph overview of what this skill produces and why it matters.>When to Use
- <Situation 1>
- <Situation 2>
- <Situation 3>
Instructions
When asked to <create artifact>, follow these steps:
-
<Step 1 Title> <What to do and why>
-
<Step 2 Title> <What to do and why>
-
<Step 3 Title> <What to do and why>
-
<Step 4 Title> <What to do and why>
Output Format
Use the template in references/TEMPLATE.md to structure the output.
Quality Checklist
Before finalizing, verify:
- <Quality criterion 1>
- <Quality criterion 2>
- <Quality criterion 3>
Examples
See references/EXAMPLE.md for a completed example.
Source
git clone https://github.com/product-on-purpose/pm-skills/blob/main/docs/templates/skill-template/SKILL.mdView on GitHub Overview
<Skill Title> enables teams to produce structured outputs by following a repeatable process rooted in design thinking, triple-diamond, and lean-startup. It reduces ambiguity, aligns stakeholders, and yields actionable artifacts that accelerate decision-making.
How This Skill Works
The skill defines a four-step workflow (Step 1–Step 4) and requires using a standard output template (per references/TEMPLATE.md) to ensure consistency. It weaves together design-thinking, triple-diamond, and lean-startup principles to move from problem framing to validated solution concepts, with clear checkpoints for stakeholder review.
When to Use It
- Starting a new product concept or feature idea when requirements are unclear
- Clarifying complex problems or ambiguous goals with cross-functional teams
- Aligning stakeholders around a single artifact before invest/exec decisions
- Validating assumptions and hypotheses with quick, concrete outputs
- Documenting decisions and handoffs to engineers, researchers, or designers
Quick Start
- Step 1: Define the artifact you will create and the trigger keywords
- Step 2: Gather inputs from stakeholders and align on the four-step workflow
- Step 3: Fill the artifact template (per TEMPLATE.md) and review against quality criteria
Best Practices
- Define the artifact objective upfront and bind it to a decision you need to support
- Use the standard output template consistently across projects
- Involve diverse stakeholders early to reduce rework later
- Iterate in short cycles with explicit feedback checkpoints
- Tag artifacts with frameworks used (design-thinking, triple-diamond, lean-startup) for traceability
Example Use Cases
- A product concept brief for a mobile app feature developed with design thinking to validate user value
- A problem-framing artifact that aligns engineering and product on scope and success metrics
- A requirements artifact that clarifies APIs and data flows for a new service
- An ideation artifact that surfaces MVP topics and prioritization criteria
- A validation artifact that records user feedback and pivots for a new offering
