Pm Planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
Install
npx skills add jeremybrasher/grokbot-skills --skill pm-planninggit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/pm-planning ~/.claude/skills/pm-planningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# PM planning — decompose ARCH into tasks The pm agent's job is to take the architect's ARCH document and produce 2 things: 1. A `PLAN-<feature>.md` for humans 2. A sequence of `bd create` tasks for senior-dev to claim The plan is good if a fresh senior-dev (no prior context) can pick up the bd tasks and ship without coming back for clarification. ## The decomposition rules ### Rule 1. Tasks ≤ 4 hours Anything bigger gets split. If the task is "build the auth system", split into: - Schema migration for user table - Signup endpoint with hashing - Login endpoint with JWT issuance - Logout / token revocation - Tests Each ≤ 4h. If you can't split, the task is unclear — go back to ARCH and clarify. ### Rule 2. Single output artefact per task Each task produces ONE of: - A code file (new or modified) - A database migration - A test file - A documentation update - A config change If a task produces multiple unrelated artefacts, split it. ### Rule 3. Explicit dependencies via `--blocks` When task B requires task A's output: ```bash bd create "Task A: schema migration" -p P1 # returns id: my-proj-001-abc bd create "Task B: signup endpoint" -p P1 \ --blocks-on my-proj-001-abc \ --label senior-dev ``` The pipeline orchestrator reads `bd ready --assignee senior-dev` to know what's claimable. Tasks blocked on incomplete predecessors don't appear. ### Rule 4. Acceptance criteria — what does "done" mean? Every task description ends with a bulleted "Done when:" section.
Details
- Skill name
pm-planning- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/pm-planning/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Pm Planning skill do?
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
How do I install the Pm Planning skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill pm-planning. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pm Planning popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Reproduce and Fix Issues
38jeremybrasher/grokbot-skills
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation. Observe required inputs first; HOLD when they are missing rather than guessing.
Great Cto
38jeremybrasher/grokbot-skills
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
Setup Benny
38jeremybrasher/grokbot-skills
Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings. Observe required inputs first; HOLD when they are missing rather than guessing.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.