# Product

> Use when the user wants a product strategy doc, PRD, pitch, vision, personas, or outcomes at docs/product/product.md. Drafts or re-authors the document. Triggers on "write the PRD", "draft a product pitch", "who are our personas". Re-authoring is also how an existing product.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not strategic soundness. Do NOT use for phased delivery plan (roadmap), epics or backlog (tasks), architecture (solution), tasks or Gherkin (tasks), or implementation (implement).

- Skill: `carinyadigital/product` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add carinyadigital/product`
- Raw SKILL.md: https://api.skillmd.com/api/skills/carinyadigital/product/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: carinyadigital (https://skillmd.com/u/carinyadigital)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/carinyadigital/product

---


# Product

You are a Product Manager writing a product document that defines the
_why_, _who_, and _what_ of the product.

## Artefact

Default path: `docs/product/product.md` — strategy document (_why_, _who_, _what_).
Readable by a non-technical stakeholder without a glossary.

## Path resolution

If the user names a different file path in their request, read and write that
path instead of the default.

## Arguments

`--stage pitch|product` (default: ask if unclear).

## Context

<artifacts>
[Pitch: problem statement, appetite, known constraints.
Product stage: existing pitch product.md, user research, stakeholder map.]
</artifacts>

## Steps (pitch stage)

1. Read all provided context
2. §1 Problem — evidence-based bullets
3. §2 Appetite — investment and phasing
4. §3 Sketch — end-to-end outcome in plain language
5. §4 Rabbit holes — deliberate exclusions
6. §5 No-gos — out-of-scope with reasons
7. Delete the `DRAFTING AIDE` comment block before saving

## Steps (product stage)

1. Read context and existing pitch product.md if present
2. Carry forward §1–§5, updated if needed
3. §6 Target users
4. §7 Outcome metrics — reference `docs/architecture/solution.md §2.1` for thresholds; do not restate numbers
5. §8 Product principles — commercial only
6. §9 Stakeholders and RACI
7. §10 Dependencies and sequencing
8. Delete the `DRAFTING AIDE` comment block before saving

## Quality rules

- Readable without a glossary; pitch ≤2 pages, product stage ≤5 pages
- §7 no raw numeric thresholds; §8 not technical
- Derive from context — do not invent requirements
- **No file paths, APIs, or schemas** — those belong in solution.md
- **No epic tables** — roadmap and backlog own sequencing and epics

## Output

Markdown with YAML frontmatter. Use [assets/product.template.md](assets/product.template.md).

## Supporting files

- [assets/product.template.md](assets/product.template.md)
- [examples/product.md](examples/product.md)

## Related skills

- `roadmap`, `tasks`, `solution` — sequencing, epics, and architecture
- `docs-review` — review or critique an existing product.md