AgentAlley
Connect your AISubmit
Submit

Brief-to-Plan Transformer

Concept to Product Plan

by pawbytes · MIT license · ★ 114 on GitHub

Concept to Product Plan cover

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'.

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

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.

What you get

  • Plan typeWhich executor will use it
  • Source briefReference to original decisions
  • ScopeWhat is included and excluded
  • DeliverablesSpecific outputs expected
  • Success criteriaMeasurable completion conditions
  • File saved toResolved path
Manual install (npx, ZIP)
Claude Codenpx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -g -a claude-code
Claude Code (degit)npx degit pawbytes/skill-suites/src/prodig/paw-ps-concept-to-product-plan#main ~/.claude/skills/paw-ps-concept-to-product-plan
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md3.5 KB
Read SKILL.md here
pawbytes/main1 file shown
SKILL.md
Show the full text102 lines
paw-ps-concept-to-product-plan/SKILL.md102 lines · 3.5 KB
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

  1. Load shared context from {project-root}/.pawbytes/prodig-suites/index.md
  2. Load product context: .pawbytes/prodig-suites/products/{product-slug}/product-context.md
  3. 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

  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
1---
2name: paw-ps-concept-to-product-plan
3description: "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 
10Transforms 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 
34Load `./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 
42Load `./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 
50Load `./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 
58Load `./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 
661. Load shared context from `{project-root}/.pawbytes/prodig-suites/index.md`
672. Load product context: `.pawbytes/prodig-suites/products/{product-slug}/product-context.md`
683. 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 
89Every 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 
991. Plan must be specific enough for executor to act without clarification
1002. All scope decisions must be explicitly stated
1013. Executor type must be clearly identified
1024. Handoff bundle must be self-contained
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 114
Checked
Source
pawbytes/skill-suites ↗
Creator
pawbytes · 60 listings
View creator

Similar skills

See all →
SkillCross-Platform Reverse Engineermorluto/rea · by morlutoReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.★ 316k GitHub starsSkillBrainstorm Ideasobra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub starsSkillCode Review Feedback Analyzerobra/superpowers · by obraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation★ 290k GitHub starsSkillBug Diagnosis Frameworkmattpocock/skills · by mattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.★ 267k GitHub starsSkillImplement Specmattpocock/skills · by mattpocockImplement the result of /to-spec and /to-tickets in code.★ 267k GitHub starsSkillPR Description Writermattpocock/skills · by mattpocockUse when writing a PR body.★ 267k GitHub stars

More from pawbytes

SkillCreative Campaign Directorpawbytes/skill-suites · by pawbytesCreative director and orchestrator for Pawbytes Creative Suites. Use when the user needs creative direction, campaign planning, brand setup, or help choosing the right creative specialist or workflow. Triggers: 'Aria', 'creative direction', 'campaign planning', 'brand setup', 'which creative agent should I use', 'creative suite'.★ 114 GitHub starsSkillCustomer Insights Analyzerpawbytes/skill-suites · by pawbytesCustomer insight specialist for audience understanding. Use when defining target audience, buyer personas, customer pains, value mapping, problem discovery, audience language. Triggers: 'who would buy this', 'target audience', 'buyer persona', 'customer pain points', 'ideal customer', 'user problems', 'value proposition', 'audience research'.★ 114 GitHub starsSkillBatch Design Producerpawbytes/skill-suites · by pawbytesBatch visual production workflow for campaigns. Accepts a content calendar or campaign brief, produces multiple platform-ready assets with organized bundle output and machine-readable manifest. Trigger for 'batch design', 'content calendar to assets', 'campaign batch', 'produce all campaign visuals', or 'bulk asset generation'.★ 114 GitHub starsSkillBrand Asset Designerpawbytes/skill-suites · by pawbytesBrand asset and flyer production pipeline. Use when user requests 'create logo', 'design brand asset', 'make flyer', 'generate icon', or 'create banner'.★ 114 GitHub starsSkillCampaign Orchestration Enginepawbytes/skill-suites · by pawbytesOrchestrates multi-deliverable campaigns by dispatching Designer and Video Producer workflows in parallel. Use when the user requests 'run campaign', 'execute campaign', 'launch campaign production', or 'orchestrate deliverables'.★ 114 GitHub starsSkillCommunity Platform Builderpawbytes/skill-suites · by pawbytesBuilds and manages owned community platforms. Use when the user requests 'Discord community', 'Slack community', 'community platform', 'community-led growth', 'forum', 'champions program', 'ambassador program', or 'community engagement strategy'.★ 114 GitHub stars

Browse more free Claude skills.