claude-skills
A complete project management pipeline for Claude Code — from product idea to structured GitHub project, powered by Notion and GitHub.
How the Pipeline Works
Idea → PRD → TRD → Bootstrap → GitHub → Build
Everything runs through a single command: /pm. It detects your environment (Claude Code vs Claude.ai/Desktop) and routes to the right action.
-
Create a PRD (/pm create) — A guided interview captures product requirements: what you're building, why, for whom, and how you'll measure success. The PRD is saved to your Notion PRDs database with a Project Status dashboard and Project Board.
-
Create a TRD (/pm trd) — A technical interview builds the implementation plan: architecture, tool decisions, milestones, stories, and dependencies. The TRD is saved as a child page of the PRD in Notion.
-
Mark as Ready (/pm ready) — Validates the PRD and sets GitHub Ready = true in Notion. This is the gate between planning and execution.
-
Bootstrap the Project (/pm bootstrap) — Populates the Notion Project Board, creates GitHub milestones and issues with TDD checklists, builds a dependency map, cross-links everything, and generates a CLAUDE.md file. One atomic operation.
-
Build — Use /pm next to find what to work on, /pm bug and /pm enhancement to track issues as they arise, /pm bughunt to investigate problems, and /pm status for project health checks.
Environment Modes
| Full Mode (Claude Code) | Light Mode (Claude.ai / Desktop) |
|---|
| Available actions | All 9 actions | create, trd, ready, status, bug, enhancement |
| GitHub integration | Yes (gh CLI) | No — Notion board only |
| File system | Yes | No |
Configuration
Skills read Notion database IDs from your project's CLAUDE.md (generated by /pm bootstrap). On first run, if no CLAUDE.md exists, the skill will ask for your Notion PRD database ID. No hardcoded IDs are stored in the skills themselves.
Installation
As a Claude Code Plugin (recommended)
Inside any Claude Code session:
/plugin marketplace add paulmona/claude
Then run /plugin, find pm under the paulmona-claude marketplace, and install it.
To update after new releases:
/plugin update pm
Manual Install
cp commands/* ~/.claude/commands/
cp -r commands/pm-actions ~/.claude/commands/
Usage
/pm — Show menu (filtered by environment)
/pm create — Create PRD via guided interview
/pm trd [PRD ref] — Create TRD from PRD
/pm ready [PRD ref] — Mark PRD as GitHub Ready
/pm bootstrap [PRD ref] — Populate Notion board + GitHub milestones/issues
/pm status — Project health summary
/pm next — Recommend what to work on next
/pm bug ["description"] — File a bug
/pm enhancement ["desc"]— File an enhancement
/pm bughunt [#N or desc]— Investigate and root-cause a bug
After each action, /pm suggests the logical next step in the pipeline.
Actions Reference
/pm create
Guides you through a structured interview to create a Product Requirements Document and saves it to Notion.
What it does:
- Walks through 9 interview topics one at a time: name, problem, goals, non-goals, user stories, success metrics, stakeholders, open questions, and priority
- Coaches you to keep product and technical concerns separate — technical details are redirected to the TRD
- Probes thin answers with follow-up questions to get depth
- Flags production-only metrics that will need instrumentation
- Auto-numbers the PRD by scanning existing entries in Notion
- Drafts the full PRD in Markdown for review before saving
- Creates the page in your Notion PRDs database with Status: Draft
- Creates a Project Status dashboard and inline Project Board database as child pages
Output: A Notion page titled PRD-{NNN}: {Feature Name} with dashboard and board.
/pm trd
Guides you through a technical interview to create a Technical Requirements Document, then saves it as a child page of the PRD in Notion.
Usage: /pm trd PRD-009 or /pm trd "Feature name"
What it does:
- Locates the PRD in Notion and pulls its content for context
- Walks through 9 technical topics: architecture, tool decisions, interface mapping, observability, milestones, stories per milestone, dependencies, risks, and open questions
- Ensures observability is a dedicated milestone, not an afterthought
- Keeps stories atomic — if a story has "and" in it, it's probably two stories
- Can auto-generate interface mappings from OpenAPI specs or API docs
- Story IDs are sequential (S1, S2, S3...) with explicit dependency declarations
- Drafts the full TRD in Markdown for review before saving
- Creates the TRD as a child page of the PRD in Notion
- Updates the dashboard Quick Links with TRD reference
Output: A Notion page titled TRD: {Feature Name} nested under the PRD.
/pm ready
el-feo
mintuz
ccplugins
opensesh
wshobson
Lucklyric