CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Create a product spec from a GitHub issue in this repository by applying the shared write-product-spec workflow with Oz-specific issue context and output paths.
Install Create Product Spec
$ npx skills add warpdotdev/oz-for-oss --skill create-product-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install warpdotdev/oz-for-oss create-product-spec --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/warpdotdev/oz-for-oss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-product-spec .claude/skills/create-product-spec && 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 "create-product-spec" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-product-spec into .claude/skills/create-product-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-product-spec", 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/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-product-specType 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 warpdotdev/oz-for-oss --skill create-product-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install warpdotdev/oz-for-oss create-product-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/create-product-spec .agents/skills/create-product-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-product-spec" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-product-spec into .agents/skills/create-product-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-product-spec", 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 warpdotdev/oz-for-oss --skill create-product-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install warpdotdev/oz-for-oss create-product-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/create-product-spec .cursor/skills/create-product-spec && 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 "create-product-spec" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-product-spec into .cursor/skills/create-product-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-product-spec", 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/warpdotdev/oz-for-oss.git --path .agents/skills/create-product-spec--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 warpdotdev/oz-for-oss --skill create-product-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install warpdotdev/oz-for-oss create-product-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/create-product-spec .gemini/skills/create-product-spec && 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 "create-product-spec" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-product-spec into .gemini/skills/create-product-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-product-spec", 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 warpdotdev/oz-for-oss create-product-specInstalls 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 warpdotdev/oz-for-oss --skill create-product-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/create-product-spec .github/skills/create-product-spec && 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 "create-product-spec" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-product-spec into .github/skills/create-product-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-product-spec", 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 warpdotdev/oz-for-oss --skill create-product-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install warpdotdev/oz-for-oss create-product-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/create-product-spec .opencode/skills/create-product-spec && 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 "create-product-spec" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-product-spec into .opencode/skills/create-product-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-product-spec", 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
create-product-spec- GitHub stars
- 313
- Token cost
- ~1.2k tokens
- SKILL.md length
- 615 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create a product spec from a GitHub issue in this repository by applying the shared write-product-spec workflow with Oz-specific issue context and output paths.
- Works in 12 steps: Start from the shared write-product-spec… → Read the issue details carefully. If… → Inspect the repository enough to… → …
- Without creating commits
- SKILL.md covers Overview, Inputs, Process and Outputs
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Create Product Spec is an agent skill from warpdotdev/oz-for-oss. Create a product spec from a GitHub issue in this repository by applying the shared write-product-spec workflow with Oz-specific issue context and output paths. Use when an issue should be turned into a product spec artifact stored under specs/GH<issue-number/product.md and the agent should prepare file changes only, without creating commits or pull requests itself unless a cloud workflow explicitly asks for it.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering PRD writing. It works with GitHub. The repository describes itself as: Workflows and skills to help people and agents collaborate on open-source software with the power of Oz! The licence is MIT.
When your agent uses it
- Without creating commits
- Pull requests itself unless a cloud workflow explicitly asks for it
Example prompts
- “/create-product-spec”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Start from the shared write-product-spec guidance and follow its structure and writing standards unless this wrapper says otherwise.
- Read the issue details carefully. If issue_comments.md exists, review it for clarifications, prior decisions, and issue-comment nuance…
- Inspect the repository enough to understand the current user workflow and likely scope before writing the spec.
- Create or update specs/GH/product.md.
- Keep the product spec focused on intended behavior and user-facing requirements. Use the shared skill's sections as the baseline, adapted…
- If design context such as a Figma link is present in the issue description or comments, include it. If no design context exists, make that…
- Do not include implementation details, file-level changes, or technical design. Those belong in the tech spec.
- Do not implement the feature or modify production code as part of this task. Limit changes to the product spec artifact. Treat temporary…
- Do not include issue number references (e.g. (#N), Refs #N) in commit messages. The issue is already linked in the PR.
- If the prompt asks for it, write pr-metadata.json at the repository root containing a JSON object with the fields branch_name, pr_title…
- Default behavior: do not stage files, create commits, push branches, open pull requests, or use the GitHub CLI. If the prompt explicitly…
- In your final response, provide a brief summary of the product spec and call out any assumptions or open questions so the workflow can…
What it can do on your machine
Read from SKILL.md and the folder at commit a2bb45f. 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
Create Product Spec loads about 1.2k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 615 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 warpdotdev/oz-for-oss at commit a2bb45f, republished under its MIT licence (© warpdotdev). 615 words, ~1,163 tokens.
Download SKILL.mdSave it as
.claude/skills/create-product-spec/SKILL.md (or your agent's skills folder).- name
- create-product-spec
- description
- Create a product spec from a GitHub issue in this repository by applying the shared `write-product-spec` workflow with Oz-specific issue context and output paths. Use when an issue should be turned into a product spec artifact stored under `specs/GH<issue-number>/product.md` and the agent should prepare file changes only, without creating commits or pull requests itself unless a cloud workflow explicitly asks for it.
create-product-spec
Create a product spec from a GitHub issue for this repository.
Overview
This skill is a thin Oz wrapper around the shared product-spec workflow:
write-product-spec
Use that shared skill as the base behavior and structure unless this wrapper overrides it. Keep the same emphasis on precise user-facing behavior, invariants, edge cases, validation, and open questions.
The Oz-specific differences are:
- the primary input is a GitHub issue, not a Linear issue
- the output path is
specs/GH<issue-number>/product.md issue_comments.mdand triggering-comment context are first-class inputs- a workflow may also request a structured PR metadata file in
pr-metadata.json - do not create or edit Linear issues as part of this workflow
Inputs
Expect issue details in the prompt, including the issue number, title, description, labels, assignees, and optional prior discussion captured in issue_comments.md.
If a triggering comment or other workflow-provided comment context is present, treat it as additional context, not as a silent override of the issue body. Resolved decisions from comments can refine the spec; unresolved disagreements should remain explicit open questions.
Process
- Start from the shared
write-product-specguidance and follow its structure and writing standards unless this wrapper says otherwise. - Read the issue details carefully. If
issue_comments.mdexists, review it for clarifications, prior decisions, and issue-comment nuance that should influence the spec. - Inspect the repository enough to understand the current user workflow and likely scope before writing the spec.
- Create or update
specs/GH<issue-number>/product.md. - Keep the product spec focused on intended behavior and user-facing requirements. Use the shared skill's sections as the baseline, adapted to this repository and issue format. At minimum, cover:
- summary
- problem
- goals
- non-goals or scope boundaries
- concrete user experience and behavior requirements
- success criteria
- validation
- open product questions
- If design context such as a Figma link is present in the issue description or comments, include it. If no design context exists, make that absence explicit rather than silently omitting it.
- Do not include implementation details, file-level changes, or technical design. Those belong in the tech spec.
- Do not implement the feature or modify production code as part of this task. Limit changes to the product spec artifact. Treat temporary context files such as
issue_comments.mdas scratch input only and do not commit them. - Do not include issue number references (e.g.
(#N),Refs #N) in commit messages. The issue is already linked in the PR. - If the prompt asks for it, write
pr-metadata.jsonat the repository root containing a JSON object with the fieldsbranch_name,pr_title, andpr_summary. Thepr_summaryshould summarize the product and technical planning clearly enough that reviewers can use it directly as the PR body. For spec-only PRs, include a non-closing reference to the source issue such asRelated issue: #<issue-number>rather than closing keywords likeClosesorFixes. - Default behavior: do not stage files, create commits, push branches, open pull requests, or use the GitHub CLI. If the prompt explicitly instructs you to publish a named branch, you may commit and push exactly the requested spec changes to that branch, but still do not open or update the pull request yourself unless the prompt explicitly asks for it.
- In your final response, provide a brief summary of the product spec and call out any assumptions or open questions so the workflow can reuse that summary when creating the PR.
Show full SKILL.md (59 more words)Show less
Outputs
- Leave the repository with the new or updated product spec file ready to be committed by the workflow.
- When requested by the prompt, leave a ready-to-use
pr-metadata.jsonwithbranch_name,pr_title, andpr_summary. - If the issue is underspecified, still produce the best possible product spec and clearly capture assumptions or open questions in the spec file and final response.
© warpdotdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/create-product-spec of warpdotdev/oz-for-oss.
Open the folder on GitHubat commit a2bb45f
Compare with similar skills
Create Product Spec 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 |
|---|---|---|---|---|---|---|
| Create Product Spec this skillwarpdotdev/oz-for-oss | 313 | — | ~1.2k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Write Update Tidb Docspingcap/docs | 616 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Create Product SpecTerry-Mao/AICodingFlow | 167 | — | ~1.3k | Automated safety check: Pass | MIT | |
| RalphTheCraigHewitt/skills | 156 | — | ~1k | Automated safety check: Pass | MIT | |
| Ouroboros PM InterviewQ00/ouroboros | 6.2k | — | ~5.7k | Automated safety check: Pass | MIT |
Similar skills
Write Update Tidb Docs
pingcap/docs
Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.
Create Product Spec
Terry-Mao/AICodingFlow
Create a product spec from a GitHub issue in this repository by applying the local shared write-product-spec workflow with issue context and output paths.
Ralph
TheCraigHewitt/skills
Autonomous PRD implementation loop — turns GitHub issues into shipped code using TDD, code review gates, and Docker sandbox isolation.
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
Setup Matt Pocock Skills
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
More from warpdotdev/oz-for-oss
All 17 skills in this repoUpdate Dedupe
warpdotdev/oz-for-oss
Update the repo-local dedupe-issue-local companion skill using closed-as-duplicate signals.
Update PR Review
warpdotdev/oz-for-oss
Update the repo-local review-pr-local and review-spec-local companion skills using human feedback left on pull request conversations.
Bootstrap Issue Config
warpdotdev/oz-for-oss
Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate .github/issue-triage/config.json and .github/STAKEHOLDERS.
Update Triage
warpdotdev/oz-for-oss
Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments).
Implement Issue
warpdotdev/oz-for-oss
Implement a GitHub issue in this repository by applying the shared implement-specs workflow with Oz-specific issue, spec-context, and summary-file handling.
Review Spec
warpdotdev/oz-for-oss
Review a spec/plan pull request diff and write structured feedback to review.json for the workflow to publish.
Related
Works with
Categories
Questions about Create Product Spec
What does Create Product Spec do?
Create a product spec from a GitHub issue in this repository by applying the shared write-product-spec workflow with Oz-specific issue context and output paths. Create Product Spec is an agent skill from warpdotdev/oz-for-oss. Create a product spec from a GitHub issue in this repository by applying the shared write-product-spec workflow with Oz-specific issue context and output paths.
When should I use Create Product Spec?
Create Product Spec fits situations like: without creating commits; pull requests itself unless a cloud workflow explicitly asks for it.
How do I install Create Product Spec in Claude Code?
Run `npx skills add warpdotdev/oz-for-oss --skill create-product-spec -a claude-code`. Or copy the skill folder (.agents/skills/create-product-spec in warpdotdev/oz-for-oss) into .claude/skills/create-product-spec in your project. Claude Code loads it when a task matches its description.
How do I install Create Product Spec in Codex?
Run `npx skills add warpdotdev/oz-for-oss --skill create-product-spec -a codex`. Or copy the skill folder (.agents/skills/create-product-spec in warpdotdev/oz-for-oss) into .agents/skills/create-product-spec in your project. Codex loads it when a task matches its description.
Can I use Create Product Spec 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 warpdotdev/oz-for-oss --skill create-product-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-product-spec, .gemini/skills/create-product-spec, .github/skills/create-product-spec and .opencode/skills/create-product-spec in your project.
What does Create Product Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: Create Product Spec is instructions for the agent only.
Does Create Product Spec 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 Create Product Spec 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 Create Product Spec use?
Create Product Spec 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 Create Product Spec use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Create Product Spec?
Skills that share tags, products or a category with Create Product Spec: CCPM Project Management (automazeio/ccpm, 8.4k stars), Write Update Tidb Docs (pingcap/docs, 616 stars), Create Product Spec (Terry-Mao/AICodingFlow, 167 stars) and Ralph (TheCraigHewitt/skills, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create Product Spec?
warpdotdev (a GitHub organization) maintains it in warpdotdev/oz-for-oss, which has 313 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 17, 2026.
Source: warpdotdev/oz-for-oss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.