# Plan Product

> Turns a raw feature or project idea into a structured product plan document covering goals, audience, requirements, and constraints, with a maturity-tracking workflow.

- Skill: `nagarenegishi/plan-product` (Agent Skill)
- Install (CLI): `npx skillmds add nagarenegishi/plan-product`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nagarenegishi/plan-product/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning, PRDs & Specs
- Tags: Ears, Maturity Mark, Prd, Product Plan, Requirements
- Author: NagareNegishi (https://skillmd.com/u/nagarenegishi)
- Updated: 2026-08-22
- Page: https://skillmd.com/skills/nagarenegishi/plan-product

---


# Plan Product

Turn a raw idea into a product doc pinning down the "what and why". First skill
in the chain: `plan-product` → `plan-impl` → `plan-verify`.

## Output

Write to `docs/plans/<slug>/product.md` — always this path. Docs only: never
change code, run git, or make a network call.

### Choosing the slug

Derive a kebab-case `<slug>` from the idea (e.g. `bulk-export`). Propose it and
ask the user to accept or rename it **before** creating the directory.

## Two things this skill does

1. **Draft** — build `product.md` from the idea, one marked entry per field.
2. **Audit** — the only way entries clear the `plan-impl` gate. Defined under
   `## The maturity mark`.

## The maturity mark

Every entry carries exactly one maturity mark:

```
🌱 idea               raw, as the user dictated it
🤖 ai-audited(<model>) Claude reviewed and refined it; stamps the model id
👤 human-ok           the user reviewed it
✅ settled            the user locked it
```

- Fresh dictation is `🌱 idea`.
- Advance an entry to `🤖 ai-audited(<model>)` on your own. Stamp `👤 human-ok`
  or `✅ settled` only when the user explicitly instructs you to set that mark on
  a named entry: ask, wait for the instruction, then stamp — one entry per
  instruction. Never stamp either mark on your own initiative, and never reuse
  one entry's instruction for another.
- Stamp the running model's short id per entry, e.g. `🤖 ai-audited(opus-4.8)`.

An audit pass on an entry means: read it, tighten the wording, flag
contradictions, gaps, and unknowns, then stamp `🤖 ai-audited(<model>)` with a
one-line note on what changed or what remains open. Never silently promote an
entry you did not actually audit.

## File format — follow this exactly

`product.md` opens with a maturity summary header, then one section per field.

```markdown
# Product plan: <slug>

## Maturity
lowest: 🌱 idea
🌱 idea 6 · 🤖 ai-audited 3 · 👤 human-ok 0 · ✅ settled 0

## about
🌱 idea

<one or two sentences: what this is.>

## problem / motivation
🤖 ai-audited(opus-4.8) — tightened; still no numbers on how often this hurts

<why it's worth building.>

## goal
🌱 idea

<the outcome, not the mechanism.>

## audience
🌱 idea

<who uses it.>

## requirements
🌱 idea

- When <trigger>, the system shall <response>.   (EARS phrasing)
- ...

## stack
🌱 idea

<languages, frameworks, services. Leave empty if undecided.>

## target device / platform
🌱 idea

<web / mobile / CLI / etc.>

## constraints
🌱 idea

<hard limits: deadlines, budgets, must-use tech, compliance.>

## non-goals
🌱 idea

<what this explicitly will not do.>

## open questions
🌱 idea

<unresolved decisions blocking or shaping the work.>
```

## Rules

- **Fixed core, optional extras.** The fields above are always present, left
  empty (not deleted) when they don't apply. A project may append its own extra
  fields after `open questions`.
- **`non-goals` and `open questions`** — never leave them blank by default;
  press for at least one entry each.
- **Requirements use EARS phrasing** — "When \<trigger>, the system shall
  \<response>".
- **Header can't drift.** Whatever writes or updates an entry updates the header
  in the same pass. `lowest:` is the lowest mark present; the counts sum to the
  number of entries.
- Never invent facts to fill a field. An unknown belongs in `open questions`, not
  a confident-looking guess.

## human-writing

Follow the `human-writing` skill for the prose in every field.

## After writing

Do not render the doc in chat — the user reviews the file in their editor. Show
the path and offer:

1. **Audit** — run an audit pass to clear entries toward the `plan-impl` gate.
2. **Revise a field** — reword or re-scope, rewrite the file, update the header.
3. **Hand off to `plan-impl`** — only once every entry is `🤖 ai-audited` or
   above (`plan-impl` enforces this from the header).
4. **Stop** — the doc stays for later.