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.
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation.
Install Productspec Authoring
$ npx skills add gokulrajaram/ProductSpec --skill productspec-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gokulrajaram/ProductSpec productspec-authoring --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/gokulrajaram/ProductSpec.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/productspec-authoring .claude/skills/productspec-authoring && 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 "productspec-authoring" agent skill from https://github.com/gokulrajaram/ProductSpec/tree/main/skills/productspec-authoring into .claude/skills/productspec-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "productspec-authoring", 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/gokulrajaram/ProductSpec/tree/main/skills/productspec-authoringType 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 gokulrajaram/ProductSpec --skill productspec-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gokulrajaram/ProductSpec productspec-authoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gokulrajaram/ProductSpec.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/productspec-authoring .agents/skills/productspec-authoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "productspec-authoring" agent skill from https://github.com/gokulrajaram/ProductSpec/tree/main/skills/productspec-authoring into .agents/skills/productspec-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "productspec-authoring", 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 gokulrajaram/ProductSpec --skill productspec-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gokulrajaram/ProductSpec productspec-authoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gokulrajaram/ProductSpec.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/productspec-authoring .cursor/skills/productspec-authoring && 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 "productspec-authoring" agent skill from https://github.com/gokulrajaram/ProductSpec/tree/main/skills/productspec-authoring into .cursor/skills/productspec-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "productspec-authoring", 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/gokulrajaram/ProductSpec.git --path skills/productspec-authoring--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 gokulrajaram/ProductSpec --skill productspec-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gokulrajaram/ProductSpec productspec-authoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gokulrajaram/ProductSpec.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/productspec-authoring .gemini/skills/productspec-authoring && 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 "productspec-authoring" agent skill from https://github.com/gokulrajaram/ProductSpec/tree/main/skills/productspec-authoring into .gemini/skills/productspec-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "productspec-authoring", 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 gokulrajaram/ProductSpec productspec-authoringInstalls 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 gokulrajaram/ProductSpec --skill productspec-authoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gokulrajaram/ProductSpec.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/productspec-authoring .github/skills/productspec-authoring && 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 "productspec-authoring" agent skill from https://github.com/gokulrajaram/ProductSpec/tree/main/skills/productspec-authoring into .github/skills/productspec-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "productspec-authoring", 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 gokulrajaram/ProductSpec --skill productspec-authoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gokulrajaram/ProductSpec productspec-authoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gokulrajaram/ProductSpec.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/productspec-authoring .opencode/skills/productspec-authoring && 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 "productspec-authoring" agent skill from https://github.com/gokulrajaram/ProductSpec/tree/main/skills/productspec-authoring into .opencode/skills/productspec-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "productspec-authoring", 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
productspec-authoring- GitHub stars
- 306
- Token cost
- ~929 tokens
- SKILL.md length
- 385 words
- Files
- 5 (incl. references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation.
- Authoring a new Product Spec
- SKILL.md covers Always true, Pick the task, read one… and Ground rules
- Calls npm
- Converting an existing PRD
What it does
Productspec Authoring is an agent skill from gokulrajaram/ProductSpec. Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over time in a Decision Trace. For implementing code against a Product Spec that already exists, use the productspec skill instead.
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/authoring.md`, `references/converting.md` and `references/decision-trace.md`).
It sits in Product & Project Management, covering PRD writing. The repository describes itself as: Open standard for software intent in the AI agent era. The licence is MIT.
When your agent uses it
- Authoring a new Product Spec
- Converting an existing PRD
- Feature doc into one
- Validating spec files locally
Example prompts
- “/productspec-authoring”
What it can do on your machine
Read from SKILL.md and the folder at commit 97b90b6. 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
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
Productspec Authoring loads about 929 tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 385 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 gokulrajaram/ProductSpec at commit 97b90b6, republished under its MIT licence (© gokulrajaram). 385 words, ~929 tokens.
Download SKILL.mdSave it as
.claude/skills/productspec-authoring/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- productspec-authoring
- description
- Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over time in a Decision Trace. For implementing code against a Product Spec that already exists, use the productspec skill instead.
- license
- MIT
- metadata.version
- 0.1
Authoring ProductSpec Files
ProductSpec is a Markdown format for the product decision that comes before tickets, engineering plans, and code. One file per feature holds the committed intent.
This skill covers producing that file. Reading a finished spec and building against it is a different job, and the productspec skill covers it. This skill ends when the file validates.
Always true
- Files use the extension
.product-spec.md: YAML frontmatter between---markers, then## Sectionheadings. - Six sections are mandatory, in order:
problem,hypothesis,product_summary,scope,acceptance_criteria,success_metrics. - Headings match case- and separator-insensitively.
## Acceptance Criteriaand## acceptance_criteriaare the same section. Title case is the convention. - Frontmatter requires
spec_format_version: "0.1",title,artifact_type(hypothesis|prd|openspec_proposal),author,created_at,updated_at. Optional:spec_revision,linked_github_repo,applies_to,custom_sections,tool_metadata. acceptance_criteriaandsuccess_metricseach carry a required fenced block. Prose alone fails validation. Structured scope, AI evals, and related artifacts are optional.- Structured items carry durable ids:
AC-<number>,SM-<number>,EVAL-<number>. Other documents cite them. - AI evals live inside
## Acceptance Criteria, never in a section of their own. Related artifacts live inside## Related Artifacts. - Validate any file with:
npm exec --yes --package @productspec/parser -- productspec validate <file>(--yessuppresses npm's interactive install prompt, which hangs CI and non-interactive agents). - The full normative definition is SPEC.md in the ProductSpec repository: https://github.com/gokulrajaram/ProductSpec/blob/main/SPEC.md. When this skill and SPEC.md disagree, SPEC.md wins.
Show full SKILL.md (168 more words)Show less
Pick the task, read one reference
| Task | Read |
|---|---|
| Write a new spec from scratch | references/authoring.md |
| Validate files and fix errors | references/validating.md |
| Convert an existing PRD or feature doc | references/converting.md |
| Record drift, revisions, and outcomes | references/decision-trace.md |
Read only the reference the task needs.
Ground rules
- Never renumber a durable id.
AC-2means the same criterion tomorrow as it does today, because a ticket, an engineering spec, or another agent may cite it. Add new ids at the end. - A success metric needs a target and a window, and the block is required. When the number depends on a baseline that only exists after launch, write
target: tbdwithtarget_status: provisionaland a namedtarget_owner. Never invent a number to clear the validator. - Preserve the author's Markdown inside sections. Tables, lists, and links survive the format. Do not flatten them.
- Write Scope items as complete sentences or imperative statements. Avoid terse tags like
searchorstorage. spec_revisionincrements only when product intent materially changes, never for typo or formatting edits.
© gokulrajaram, 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 skills/productspec-authoring of gokulrajaram/ProductSpec.
- SKILL.md
- references/authoring.md
- references/converting.md
- references/decision-trace.md
- references/validating.md
Open the folder on GitHubat commit 97b90b6
Compare with similar skills
Productspec Authoring 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 |
|---|---|---|---|---|---|---|
| Productspec Authoring this skillgokulrajaram/ProductSpec | 306 | — | ~929 | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
Prd Generator
jamesrochabrun/skills
Generate comprehensive Product Requirements Documents (PRDs) for product managers.
More from gokulrajaram/ProductSpec
Productspec
gokulrajaram/ProductSpec
A skill your agent uses when implementing, reviewing, planning, or changing work governed by a Product Spec.
Related
Categories
Questions about Productspec Authoring
What does Productspec Authoring do?
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Productspec Authoring is an agent skill from gokulrajaram/ProductSpec.md), the Markdown format for recording product intent before implementation.
When should I use Productspec Authoring?
Productspec Authoring fits situations like: authoring a new Product Spec; converting an existing PRD; feature doc into one; validating spec files locally.
How do I install Productspec Authoring in Claude Code?
Run `npx skills add gokulrajaram/ProductSpec --skill productspec-authoring -a claude-code`. Or copy the skill folder (skills/productspec-authoring in gokulrajaram/ProductSpec) into .claude/skills/productspec-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Productspec Authoring in Codex?
Run `npx skills add gokulrajaram/ProductSpec --skill productspec-authoring -a codex`. Or copy the skill folder (skills/productspec-authoring in gokulrajaram/ProductSpec) into .agents/skills/productspec-authoring in your project. Codex loads it when a task matches its description.
Can I use Productspec Authoring 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 gokulrajaram/ProductSpec --skill productspec-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/productspec-authoring, .gemini/skills/productspec-authoring, .github/skills/productspec-authoring and .opencode/skills/productspec-authoring in your project.
What does Productspec Authoring need to run?
Going by SKILL.md and its folder, Productspec Authoring needs the command-line tools its instructions call (npm).
Does Productspec Authoring access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Productspec Authoring 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 Productspec Authoring use?
Productspec Authoring is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Productspec Authoring use?
About 929 tokens (SKILL.md is roughly 3.7k 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 5.3k tokens, read only when the agent opens those files.
What are the alternatives to Productspec Authoring?
Skills that share tags, products or a category with Productspec Authoring: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Productspec Authoring?
gokulrajaram (a GitHub user) maintains it in gokulrajaram/ProductSpec, which has 306 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 19, 2026.
Source: gokulrajaram/ProductSpec on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.