Brief
alirezarezvani/claude-skills
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
Transform an accepted product brief into an executor-ready product plan.
MITAuto-check passed
Install Paw Ps Concept To Product Plan
$ npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-concept-to-product-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/prodig/paw-ps-concept-to-product-plan .claude/skills/paw-ps-concept-to-product-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "paw-ps-concept-to-product-plan" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-concept-to-product-plan into .claude/skills/paw-ps-concept-to-product-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-concept-to-product-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-concept-to-product-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-concept-to-product-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/prodig/paw-ps-concept-to-product-plan .agents/skills/paw-ps-concept-to-product-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "paw-ps-concept-to-product-plan" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-concept-to-product-plan into .agents/skills/paw-ps-concept-to-product-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-concept-to-product-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-concept-to-product-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/prodig/paw-ps-concept-to-product-plan .cursor/skills/paw-ps-concept-to-product-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "paw-ps-concept-to-product-plan" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-concept-to-product-plan into .cursor/skills/paw-ps-concept-to-product-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-concept-to-product-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pawbytes/skill-suites.git --path src/prodig/paw-ps-concept-to-product-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-concept-to-product-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/prodig/paw-ps-concept-to-product-plan .gemini/skills/paw-ps-concept-to-product-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "paw-ps-concept-to-product-plan" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-concept-to-product-plan into .gemini/skills/paw-ps-concept-to-product-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-concept-to-product-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pawbytes/skill-suites paw-ps-concept-to-product-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/prodig/paw-ps-concept-to-product-plan .github/skills/paw-ps-concept-to-product-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "paw-ps-concept-to-product-plan" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-concept-to-product-plan into .github/skills/paw-ps-concept-to-product-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-concept-to-product-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-concept-to-product-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/prodig/paw-ps-concept-to-product-plan .opencode/skills/paw-ps-concept-to-product-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "paw-ps-concept-to-product-plan" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-concept-to-product-plan into .opencode/skills/paw-ps-concept-to-product-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-concept-to-product-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
paw-ps-concept-to-product-plan- GitHub stars
- 113
- Token cost
- ~890 tokens
- SKILL.md length
- 319 words
- Files
- 5 (incl. references)
- Skills in repo
- 71
- Repo updated
- First seen
- Licence
- MIT
At a glance
Transform an accepted product brief into an executor-ready product plan.
- Works in 4 steps: Load Brief → Identify Executor → Create Plan → …
- SKILL.md covers Overview, Inputs, Outputs and Pipeline, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Paw Ps Concept To Product Plan is an agent skill from pawbytes/skill-suites. 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'.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/01-load-brief.md`, `references/02-identify-executor.md` and `references/03-create-plan.md`).
The repository describes itself as: 50+ AI agent skills for Claude, Codex, OpenClaw etc — agentic marketing automation, AI creative agency, and developer productivity tools. The licence is MIT.
Example prompts
- “create product plan”
- “product plan from brief”
- “prepare for executor”
- “/paw-ps-concept-to-product-plan”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 547a6df. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Paw Ps Concept To Product Plan loads about 890 tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 319 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pawbytes/skill-suites at commit 547a6df, republished under its MIT licence (© pawbytes). 319 words, ~890 tokens.
Download SKILL.mdSave it as
.claude/skills/paw-ps-concept-to-product-plan/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- 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.mdor 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
© pawbytes, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in src/prodig/paw-ps-concept-to-product-plan of pawbytes/skill-suites.
- SKILL.md
- references/01-load-brief.md
- references/02-identify-executor.md
- references/03-create-plan.md
- references/04-prepare-handoff.md
Open the folder on GitHubat commit 547a6df
Compare with similar skills
Paw Ps Concept To Product Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Paw Ps Concept To Product Plan this skillpawbytes/skill-suites | 113 | — | ~890 | Automated safety check: Pass | MIT | |
| Briefalirezarezvani/claude-skills | 28k | — | ~967 | Automated safety check: Pass | MIT | |
| TransformersK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~2.8k | Automated safety check: Notes | Apache-2.0 | |
| Briefdavepoon/buildwithclaude | 3.6k | — | ~1.3k | Automated safety check: Notes | MIT | |
| QA Acceptancepaperclipai/paperclip | 100k | — | ~964 | Automated safety check: Pass | MIT | |
| Hugging Face Transformers Usagedavila7/claude-code-templates | 33k | 11 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Transformers
K-Dense-AI/scientific-agent-skills
Hugging Face Transformers for loading Hub models, running pipeline inference, text generation, and Trainer fine-tuning on NLP, vision, audio, and multimodal tasks.
Brief
davepoon/buildwithclaude
Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude.
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Hugging Face Transformers Usage
davila7/claude-code-templates
Loads pre-trained Hugging Face Transformers models for text, vision and audio tasks, runs inference with pipelines and fine-tunes on custom datasets.
Transformers JS
sickn33/agentic-awesome-skills
Use Transformers.js to run state-of-the-art machine learning models directly in JavaScript/TypeScript.
More from pawbytes/skill-suites
All 71 skills in this repoProdig Suites Setup
pawbytes/skill-suites
Installs the Prodig Suites product-creation module into a project, scaffolding its workspace folders and writing the shared and personal config files.
Video Clip Repurposing
pawbytes/skill-suites
Cuts long-form video into short platform-ready clips: finds strong moments, reframes for vertical, adds subtitles and brand overlays, and writes a clip manifest.
Paw Pa Generation
pawbytes/skill-suites
Assembles branded, export-ready proposals from brief, research, and pricing artifacts — type-adaptive for pitch, RFP, or scoping.
Proposal Brief Intake
pawbytes/skill-suites
Turns pasted text, audio, video or URLs from a client into a structured, completeness-checked brief.md for the first stage of a proposal pipeline.
Proposal Library Indexer
pawbytes/skill-suites
Turns case studies, past proposals and boilerplate dropped into a library inbox into structured, source-linked indexes for later proposal work.
Proposal Research Dossier Builder
pawbytes/skill-suites
Turns a structured sales brief into an evidence-backed HTML research dossier, matching indexed case studies locally and gathering client, tech-stack and pricing evidence from the web.
Questions about Paw Ps Concept To Product Plan
What does Paw Ps Concept To Product Plan do?
Transform an accepted product brief into an executor-ready product plan. Paw Ps Concept To Product Plan is an agent skill from pawbytes/skill-suites. Transform an accepted product brief into an executor-ready product plan.
How do I install Paw Ps Concept To Product Plan in Claude Code?
Run `npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a claude-code`. Or copy the skill folder (src/prodig/paw-ps-concept-to-product-plan in pawbytes/skill-suites) into .claude/skills/paw-ps-concept-to-product-plan in your project. Claude Code loads it when a task matches its description.
How do I install Paw Ps Concept To Product Plan in Codex?
Run `npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a codex`. Or copy the skill folder (src/prodig/paw-ps-concept-to-product-plan in pawbytes/skill-suites) into .agents/skills/paw-ps-concept-to-product-plan in your project. Codex loads it when a task matches its description.
Can I use Paw Ps Concept To Product Plan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pawbytes/skill-suites --skill paw-ps-concept-to-product-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paw-ps-concept-to-product-plan, .gemini/skills/paw-ps-concept-to-product-plan, .github/skills/paw-ps-concept-to-product-plan and .opencode/skills/paw-ps-concept-to-product-plan in your project.
What does Paw Ps Concept To Product Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Paw Ps Concept To Product Plan is instructions for the agent only.
Does Paw Ps Concept To Product Plan access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Paw Ps Concept To Product Plan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Paw Ps Concept To Product Plan use?
Paw Ps Concept To Product Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Paw Ps Concept To Product Plan use?
About 890 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.3k tokens, read only when the agent opens those files.
What are the alternatives to Paw Ps Concept To Product Plan?
Skills that share tags, products or a category with Paw Ps Concept To Product Plan: Brief (alirezarezvani/claude-skills, 28k stars), Transformers (K-Dense-AI/scientific-agent-skills, 48k stars), Brief (davepoon/buildwithclaude, 3.6k stars) and QA Acceptance (paperclipai/paperclip, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Paw Ps Concept To Product Plan?
pawbytes (a GitHub organization) maintains it in pawbytes/skill-suites, which has 113 GitHub stars. The repository holds 71 skills in this directory. The repository was last updated on October 3, 2026.
Source: pawbytes/skill-suites on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.