paw-ps-concept-to-product-plan · git:20261104.2ecd7cf · 2026-11-04 · sha256 be7de0b40276d8f0
paw-ps-concept-to-product-plan git:20261104.2ecd7cfA
Immutable. This exact content never changes and is served at /api/v1/blob/be7de0b40276d8f0.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jy4cgydstk5gya24/be7de0b40276d8f0df1b0bed5e95c1b5e14395a79d185b48e78da082916a006e.json
Then /plugin install paw-ps-concept-to-product-plan@markdownregistry-jy4cgydstk5gya24 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: paw-ps-concept-to-product-plan
description: "Transform an accepted product brief into an executor-ready product plan. Triggers: 'create product plan', 'product plan from brief', 'prepare for executor', 'plan for building', 'handoff to builder'."
---
# Concept to Product Plan
## Overview
Transforms an accepted product brief into a detailed, executor-ready product plan. This workflow bridges product decisions and execution by producing specific instructions for the correct builder type.
**Args:** Accepts `--headless` / `-H` for non-interactive execution.
**Output:** Product plan/spec package and executor handoff bundle.
## Inputs
- Product brief (from `product-decisions.md` or brief file)
- Chosen product family (knowledge, template, software, service)
- Scope and packaging decisions
## Outputs
| Output | Location |
|--------|----------|
| Product plan | `{suite-root}/{product-slug}/plan/plan.md` |
| Executor handoff | `{suite-root}/{product-slug}/plan/handoff.md` |
| Product context update | `{suite-root}/{product-slug}/product-context.md` |
## Pipeline
### Stage 1: Load Brief
Load `./references/01-load-brief.md`
**Inputs:** Product brief location or product-decisions.md
**Progression:** Brief is loaded and completeness verified. All required sections present.
### Stage 2: Identify Executor
Load `./references/02-identify-executor.md`
**Inputs:** Product family selection, product type
**Progression:** Executor type determined and validated against product requirements.
### Stage 3: Create Plan
Load `./references/03-create-plan.md`
**Inputs:** Brief, executor type, scope decisions
**Progression:** Detailed execution plan created with all sections populated.
### Stage 4: Prepare Handoff
Load `./references/04-prepare-handoff.md`
**Inputs:** Product plan, executor type
**Progression:** Executor handoff bundle formatted and saved. Product context updated with plan reference.
## On Activation
1. Load shared context from `{suite-root}/_memory/index.md`
2. Load product context: `{suite-root}/{product-slug}/product-context.md`
3. If no product slug provided, list available products for selection
## Path Resolution
- `{suite-root}` is `root` from `uv run {skill-root}/scripts/paw-paths.py detect` (`{skill-root}` is this skill's folder), normally `{project-root}/paw-suites/products`. All paths below are relative to it. A custom folder in config `ps.products_folder` (or `ps.memory_folder` for `_memory/`) wins (`detect` lists it under `overrides`; an old default is not one).
- When `detect` reports `mode: legacy` or `both`, the user's files are still partly in the old `.pawbytes/prodig-suites/` tree. Pass every path through `paw-paths.py locate <path>` (add `--write` for a new file) and use the path it returns. Once per session, tell the user that `paw-ps-setup` can move them to `paw-suites/products/`, and offer it. Keep working either way.
**Plans root:** `{suite-root}/{product-slug}/plan/`
**Product context:** `{suite-root}/{product-slug}/product-context.md`
**Handoff bundle:** `{suite-root}/{product-slug}/plan/handoff.md`
**Dashboard:** once the handoff is written, set `Status: planned` and `Next: <executor skill>` in `{suite-root}/{product-slug}/README.md`, link `plan/plan.md` and `plan/handoff.md`, then run `paw-paths.py index`.
## Executor Types
| Product Family | Executor | Plan Focus |
|----------------|----------|------------|
| Knowledge | Knowledge Builder | Content structure, research scope, deliverable format |
| Template | Template Builder | Component structure, customization points, usage patterns |
| Software | Software Builder | Technical specs, architecture, implementation phases |
| Service | Service Builder | Service definition, delivery process, quality criteria |
## Output Contract
Every product plan includes:
- **Plan type:** Which executor will use it
- **Source brief:** Reference to original decisions
- **Scope:** What is included and excluded
- **Deliverables:** Specific outputs expected
- **Success criteria:** Measurable completion conditions
- **File saved to:** Resolved path
## Non-Negotiables
1. Plan must be specific enough for executor to act without clarification
2. All scope decisions must be explicitly stated
3. Executor type must be clearly identified
4. Handoff bundle must be self-contained