Planning Artifacts
dralgorhythm/claude-agentic-framework
Produces this framework's planning artifacts — PR-FAQ (working-backwards vision), PRD (requirements), and execution roadmap — from their bundled templates.
Writes (or rewrites) a spec, PRD, PR-FAQ or shaped pitch and grades it against what the best product teams actually do.
Install Spec
$ npx skills add menkesu/awesome-pm-skills --skill spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install menkesu/awesome-pm-skills 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/menkesu/awesome-pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spec .claude/skills/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 "spec" agent skill from https://github.com/menkesu/awesome-pm-skills/tree/main/skills/spec into .claude/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/menkesu/awesome-pm-skills/tree/main/skills/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 menkesu/awesome-pm-skills --skill spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install menkesu/awesome-pm-skills spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/menkesu/awesome-pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/spec .agents/skills/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 "spec" agent skill from https://github.com/menkesu/awesome-pm-skills/tree/main/skills/spec into .agents/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 menkesu/awesome-pm-skills --skill spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install menkesu/awesome-pm-skills spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/menkesu/awesome-pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/spec .cursor/skills/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 "spec" agent skill from https://github.com/menkesu/awesome-pm-skills/tree/main/skills/spec into .cursor/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/menkesu/awesome-pm-skills.git --path skills/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 menkesu/awesome-pm-skills --skill spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install menkesu/awesome-pm-skills spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/menkesu/awesome-pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/spec .gemini/skills/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 "spec" agent skill from https://github.com/menkesu/awesome-pm-skills/tree/main/skills/spec into .gemini/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 menkesu/awesome-pm-skills 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 menkesu/awesome-pm-skills --skill spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/menkesu/awesome-pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/spec .github/skills/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 "spec" agent skill from https://github.com/menkesu/awesome-pm-skills/tree/main/skills/spec into .github/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 menkesu/awesome-pm-skills --skill 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 menkesu/awesome-pm-skills spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/menkesu/awesome-pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/spec .opencode/skills/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 "spec" agent skill from https://github.com/menkesu/awesome-pm-skills/tree/main/skills/spec into .opencode/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
spec- GitHub stars
- 433
- Token cost
- ~4.2k tokens
- SKILL.md length
- 2,273 words
- Files
- 4 (incl. references, assets)
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Writes (or rewrites) a spec, PRD, PR-FAQ or shaped pitch and grades it against what the best product teams actually do.
- Works in 3 steps: Diagnose (ask before answering) → Pick the play → Run it
- You ask write a PRD
- SKILL.md covers When to use, Step 1: Diagnose (ask before…, Step 2: Pick the play and Step 3: Run it, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Spec is an agent skill from menkesu/awesome-pm-skills. Writes (or rewrites) a spec, PRD, PR-FAQ or shaped pitch and grades it against what the best product teams actually do. Use when you ask 'write a PRD', 'how do I spec this', 'PR/FAQ', 'working backwards doc', 'shape this project', 'do we even need a PRD', or 'engineering says the spec isn't detailed enough'. Draws on 56 insights from 38 Lenny's Podcast guests incl. Ryan Singer, Bill Carr and Lane Shackleton.
Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `references/frameworks.md` and `references/quotes.md`).
It sits in Product & Project Management, covering PRD writing, Help center and FAQ content and Podcasting. The repository describes itself as: Product management workflows grounded in Lenny's Podcast, for Claude Code, Codex, and Cursor.
When your agent uses it
- You ask write a PRD
- How do I spec this
- Working backwards doc
- Shape this project
Example prompts
- “write a PRD”
- “how do I spec this”
- “PR/FAQ”
- “/spec”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Diagnose (ask before answering)
- Pick the play
- Run it
What it can do on your machine
Read from SKILL.md and the folder at commit c1b6e2d. 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 (its code samples are markdown).
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
Spec loads about 4.2k tokens when it runs, and up to ~9.2k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 2,273 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,273 words (~4,175 tokens).
“Turn a vague request into a spec an engineer can build from, or a PR/FAQ that decides whether to build at all, then grade it and return the top 3 fixes. Built from 56 insights from 38 Lenny's Podcast guests…”
- name
- spec
Files
SKILL.md and 3 other files (references, assets) in skills/spec of menkesu/awesome-pm-skills.
- SKILL.md
- assets/card.png
- references/frameworks.md
- references/quotes.md
Open the folder on GitHubat commit c1b6e2d
Compare with similar skills
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 |
|---|---|---|---|---|---|---|
| Spec this skillmenkesu/awesome-pm-skills | 433 | — | ~4.2k | Automated safety check: Pass | Custom licence | |
| Planning Artifactsdralgorhythm/claude-agentic-framework | 125 | — | ~765 | Automated safety check: Pass | None | |
| Tdoctornado-doc/tdoc | 103 | — | ~18k | Automated safety check: Notes | AGPL-3.0 | |
| Status Update Writeraakashg/pm-claude-skills | 112 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Prd V03 Pricing Modelmattgierhart/PRD-driven-context-engineering | 180 | — | ~3k | Automated safety check: Pass | MIT | |
| Proposal Reviewer ChorusChorus-AIDLC/Chorus | 1.2k | — | ~3.9k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Tdoc
tornado-doc/tdoc
Use tdoc by default to create, edit, publish, or share any document, even when tdoc is not mentioned.
Status Update Writer
aakashg/pm-claude-skills
A skill your agent uses when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR.
Prd V03 Pricing Model
mattgierhart/PRD-driven-context-engineering
Select and validate pricing model for PRD v0.3 Commercial Model.
Proposal Reviewer Chorus
Chorus-AIDLC/Chorus
Read-only adversarial Chorus proposal reviewer — audits PRD/task drafts against the originating Idea and posts a single structured VERDICT comment.
Feature Launch Playbook
gooseworks-ai/goose-skills
Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales…
More from menkesu/awesome-pm-skills
All 25 skills in this repoCraft Review
menkesu/awesome-pm-skills
Runs a product quality review on a journey, feature, landing page, onboarding flow, or AI/agent surface and returns a friction log, a scored critical-journey review, and a taste bar your team can…
Customer Interviews
menkesu/awesome-pm-skills
Designs customer interviews and turns the transcripts into decisions.
Decide
menkesu/awesome-pm-skills
Turns a hard product or career decision into a one-page decision memo with the eigenquestion, options, pre-mortem with kill criteria, reversibility rating, a named decider and a review date.
Eval Plan
menkesu/awesome-pm-skills
Builds an eval plan for an AI feature - error analysis on real traces, failure-mode ranking, code checks and binary LLM judges validated against human labels, CI tests, production monitoring, and a…
Exec Comms
menkesu/awesome-pm-skills
Rewrite an exec update, memo, strategy doc, deck outline, Slack post or talk so it lands with senior people, and get a graded score plus the top 3 fixes.
Hard Conversations
menkesu/awesome-pm-skills
Writes you a ready-to-use script for a feedback or hard conversation, then rehearses the pushback.
Related
Questions about Spec
What does Spec do?
Writes (or rewrites) a spec, PRD, PR-FAQ or shaped pitch and grades it against what the best product teams actually do. Spec is an agent skill from menkesu/awesome-pm-skills. Writes (or rewrites) a spec, PRD, PR-FAQ or shaped pitch and grades it against what the best product teams actually do.
When should I use Spec?
Spec fits situations like: you ask write a PRD; how do I spec this; working backwards doc; shape this project.
How do I install Spec in Claude Code?
Run `npx skills add menkesu/awesome-pm-skills --skill spec -a claude-code`. Or copy the skill folder (skills/spec in menkesu/awesome-pm-skills) into .claude/skills/spec in your project. Claude Code loads it when a task matches its description.
How do I install Spec in Codex?
Run `npx skills add menkesu/awesome-pm-skills --skill spec -a codex`. Or copy the skill folder (skills/spec in menkesu/awesome-pm-skills) into .agents/skills/spec in your project. Codex loads it when a task matches its description.
Can I use 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 menkesu/awesome-pm-skills --skill 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/spec, .gemini/skills/spec, .github/skills/spec and .opencode/skills/spec in your project.
What does Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: Spec is instructions for the agent only.
Does 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 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 Spec use?
Spec has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Spec use?
About 4.2k tokens (SKILL.md is roughly 17k 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 5k tokens, read only when the agent opens those files.
What are the alternatives to Spec?
Skills that share tags, products or a category with Spec: Planning Artifacts (dralgorhythm/claude-agentic-framework, 125 stars), Tdoc (tornado-doc/tdoc, 103 stars), Status Update Writer (aakashg/pm-claude-skills, 112 stars) and Prd V03 Pricing Model (mattgierhart/PRD-driven-context-engineering, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Spec?
menkesu (a GitHub user) maintains it in menkesu/awesome-pm-skills, which has 433 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 6, 2026.
Source: menkesu/awesome-pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.