Concept to Product Plan skill

Transform an accepted product brief into an executor-ready product plan.

by pawbytes·MIT license·★ 114 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words

# 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…

**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

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

pawbytes/main1 file shown

SKILL.md3.5 KB

Browse every file on GitHub↗

SKILL.md

Show the full text102 lines

paw-ps-concept-to-product-plan/SKILL.md102 lines · 3.5 KB

PreviewCode

Outline

RawView on GitHub

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	`.pawbytes/prodig-suites/plans/{product-slug}/plan.md`
Executor handoff	`.pawbytes/prodig-suites/plans/{product-slug}/handoff.md`
Product context update	`.pawbytes/prodig-suites/products/{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

Load shared context from {project-root}/.pawbytes/prodig-suites/index.md
Load product context: .pawbytes/prodig-suites/products/{product-slug}/product-context.md
If no product slug provided, list available products for selection

Path Resolution

Plans root: {project-root}/.pawbytes/prodig-suites/plans/{product-slug}/

Product context: {project-root}/.pawbytes/prodig-suites/products/{product-slug}/product-context.md

Handoff bundle: {project-root}/.pawbytes/prodig-suites/plans/{product-slug}/handoff.md

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

Plan must be specific enough for executor to act without clarification
All scope decisions must be explicitly stated
Executor type must be clearly identified
Handoff bundle must be self-contained

1	---
2	name: paw-ps-concept-to-product-plan
3	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'."
4	---
5
6	# Concept to Product Plan
7
8	## Overview
9
10	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.
11
12	Args: Accepts `--headless` / `-H` for non-interactive execution.
13
14	Output: Product plan/spec package and executor handoff bundle.
15
16	## Inputs
17
18	- Product brief (from `product-decisions.md` or brief file)
19	- Chosen product family (knowledge, template, software, service)
20	- Scope and packaging decisions
21
22	## Outputs
23
24	\| Output \| Location \|
25	\|--------\|----------\|
26	\| Product plan \| `.pawbytes/prodig-suites/plans/{product-slug}/plan.md` \|
27	\| Executor handoff \| `.pawbytes/prodig-suites/plans/{product-slug}/handoff.md` \|
28	\| Product context update \| `.pawbytes/prodig-suites/products/{product-slug}/product-context.md` \|
29
30	## Pipeline
31
32	### Stage 1: Load Brief
33
34	Load `./references/01-load-brief.md`
35
36	Inputs: Product brief location or product-decisions.md
37
38	Progression: Brief is loaded and completeness verified. All required sections present.
39
40	### Stage 2: Identify Executor
41
42	Load `./references/02-identify-executor.md`
43
44	Inputs: Product family selection, product type
45
46	Progression: Executor type determined and validated against product requirements.
47
48	### Stage 3: Create Plan
49
50	Load `./references/03-create-plan.md`
51
52	Inputs: Brief, executor type, scope decisions
53
54	Progression: Detailed execution plan created with all sections populated.
55
56	### Stage 4: Prepare Handoff
57
58	Load `./references/04-prepare-handoff.md`
59
60	Inputs: Product plan, executor type
61
62	Progression: Executor handoff bundle formatted and saved. Product context updated with plan reference.
63
64	## On Activation
65
66	1. Load shared context from `{project-root}/.pawbytes/prodig-suites/index.md`
67	2. Load product context: `.pawbytes/prodig-suites/products/{product-slug}/product-context.md`
68	3. If no product slug provided, list available products for selection
69
70	## Path Resolution
71
72	Plans root: `{project-root}/.pawbytes/prodig-suites/plans/{product-slug}/`
73
74	Product context: `{project-root}/.pawbytes/prodig-suites/products/{product-slug}/product-context.md`
75
76	Handoff bundle: `{project-root}/.pawbytes/prodig-suites/plans/{product-slug}/handoff.md`
77
78	## Executor Types
79
80	\| Product Family \| Executor \| Plan Focus \|
81	\|----------------\|----------\|------------\|
82	\| Knowledge \| Knowledge Builder \| Content structure, research scope, deliverable format \|
83	\| Template \| Template Builder \| Component structure, customization points, usage patterns \|
84	\| Software \| Software Builder \| Technical specs, architecture, implementation phases \|
85	\| Service \| Service Builder \| Service definition, delivery process, quality criteria \|
86
87	## Output Contract
88
89	Every product plan includes:
90	- Plan type: Which executor will use it
91	- Source brief: Reference to original decisions
92	- Scope: What is included and excluded
93	- Deliverables: Specific outputs expected
94	- Success criteria: Measurable completion conditions
95	- File saved to: Resolved path
96
97	## Non-Negotiables
98
99	1. Plan must be specific enough for executor to act without clarification
100	2. All scope decisions must be explicitly stated
101	3. Executor type must be clearly identified
102	4. Handoff bundle must be self-contained

Discussion

Browse more free Claude skills.

Files of Concept to Product Plan