New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Pm Planning

by avelikiy in avelikiy/great_cto

Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria.

MITAuto-check passedProduct & Project Management

Install Pm Planning

skills CLI
$ npx skills add avelikiy/great_cto --skill pm-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install avelikiy/great_cto pm-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pm-planning .claude/skills/pm-planning && rm -rf skills-src

Use ~/.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/

Facts

Skill name
pm-planning
GitHub stars
102
Token cost
~1.3k tokens
SKILL.md length
428 words
Files
1
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria.

  • Works in 2 steps: A PLAN-.md for humans → A sequence of bd create tasks for…
  • Tasks that involve User stories
  • SKILL.md covers The decomposition rules, The PLAN-*.md template, When pm should push back… and Anti-patterns
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pm Planning is an agent skill from avelikiy/great_cto. 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.

Its SKILL.md is about 1.3k 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 User stories and Task breakdown. The repository describes itself as: You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next… The licence is MIT.

When your agent uses it

  • Tasks that involve User stories
  • Tasks that involve Task breakdown

Example prompts

  • “seeable work”
  • “/pm-planning”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Bash(bd:*)

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. A PLAN-.md for humans
  2. A sequence of bd create tasks for senior-dev to claim

What it can do on your machine

Read from SKILL.md and the folder at commit 97dd037. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Bash(bd:*)

    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 bash and 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

Pm Planning loads about 1.3k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 428 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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 avelikiy/great_cto at commit 97dd037, republished under its MIT licence (© avelikiy). 428 words, ~1,260 tokens.

Download SKILL.mdSave it as .claude/skills/pm-planning/SKILL.md (or your agent's skills folder).
name
pm-planning
description
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.
allowed-tools
Read, Write, Bash(bd:*)
when_to_use
Apply when: - pm agent receives an approved ARCH-*.md from architect - pm needs to write PLAN-*.md - pm creates Beads tasks for senior-dev to claim Do NOT…
effort
medium
paths
docs/architecture/**, docs/plans/**

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.

markdown
## Done when:
- [ ] POST /signup returns 201 with user_id on success
- [ ] Bad email returns 400 with "invalid_email"
- [ ] Duplicate email returns 409 with "email_taken"
- [ ] Password is hashed with argon2 (no plaintext in DB)
- [ ] Unit test in `tests/<area>/<feature>.test.ts` covers all 4 cases
- [ ] `npm test` passes

Senior-dev knows EXACTLY what to ship and when to stop.

Rule 5. Owners and parallelism

If 3 tasks can run in parallel, mark each with the agent it goes to. Don't bundle them.

bash
bd create "..." --label senior-dev
bd create "..." --label senior-dev   # parallel
bd create "..." --label devops       # parallel, different agent

The PLAN-*.md template

markdown
# PLAN — <feature>

Date: <ISO>
Architect ARCH: docs/architecture/ARCH-<feature>.md
Owner: pm

## Summary

2-3 sentences. What problem, what solution. Reference ARCH for detail.

## Cost estimate

(Follow skill: cost-model)

## Tasks

1. **<title>** [P1, ≤2h, senior-dev]
   - Goal: <one-sentence>
   - Done when: <bulleted criteria>
   - bd id: <ID after create>

2. **<title>** [P1, ≤4h, senior-dev]
   - Blocked on: 1
   - Goal: ...
   - Done when: ...

3. **<title>** [P2, ≤1h, qa-engineer]
   - Blocked on: 1, 2

## Pre-mortem

(Follow skill: pre-mortem)

## Gates

(Follow GATES_BY_ARCHETYPE for this archetype + project_size)
- [ ] gate:plan — after pm finishes, before senior-dev starts
- [ ] gate:qa — after qa-engineer, before ship
- [ ] gate:ship — after security-officer, before devops
Show full SKILL.md (186 more words)Show less

When pm should push back instead of plan

The pm agent is allowed — and EXPECTED — to refuse a plan if the ARCH is incomplete. Specifically:

❌ ARCH is missing acceptance criteria for the feature itself. Push back: "ARCH says 'build webhook handler' but doesn't specify what counts as success. Re-architect with explicit success criteria."

❌ ARCH doesn't specify the failure mode. Push back: "ARCH says 'handle errors gracefully' but doesn't say what 'graceful' means. Define: log + ack? log + retry? log + alert?"

❌ ARCH conflicts with existing ADRs. Push back: "ARCH proposes Postgres but ADR-005 mandated DynamoDB. Resolve before plan."

Push-back goes to the architect with bd update + label re-arch. The plan is BLOCKED until ARCH is refined.

Anti-patterns

❌ Tasks named after components, not goals. "Build UserService" is ambiguous. "Add POST /signup endpoint that hashes password with argon2" is clear.

❌ No dependencies declared. Two tasks editing the same file with no --blocks-on will conflict. Always declare.

❌ Estimating without doing one task. If you genuinely don't know how long task 1 takes, ask senior-dev to do task 1 first and report back. THEN estimate 2–N.

❌ Tasks > 8 hours. Split. No exceptions.

© avelikiy, 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 skills/pm-planning of avelikiy/great_cto.

Open the folder on GitHubat commit 97dd037

Compare with similar skills

Pm Planning 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.

Pm Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pm Planning this skillavelikiy/great_cto102—~1.3kAutomated safety check: PassMIT
Project Planneradrianpuiu/claude-skills-marketplace1001 repos~6kAutomated safety check: PassNone
Spec Workflowhashgraph-online/awesome-codex-plugins1.3k—~2.1kAutomated safety check: PassApache-2.0
Analyze And Planadobe/skills197—~1.5kAutomated safety check: PassApache-2.0
Backlog Builderopen-mercato/skills231—~3kAutomated safety check: NotesMIT
New FeaturePolymathWizard/BHIL-AI-First-Development-Toolkit132—~1.1kAutomated safety check: PassNone

Similar skills

  • Project Planner

    adrianpuiu/claude-skills-marketplace

    Comprehensive project planning and documentation generator for software projects.

    100 GitHub starsUsed in 1 repo~6k tokens
    Product & Project ManagementAuto-check passed

  • Spec Workflow

    hashgraph-online/awesome-codex-plugins

    This skill should be used when the user asks to "create a spec", "write requirements", "design a feature", "plan implementation", "use EARS notation", "create user stories", "break down tasks"…

    1.3k GitHub stars~2.1k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Analyze And Plan

    adobe/skills

    Use this when you need to define acceptance criteria, write requirements, scope work, or create a definition of done for AEM Edge Delivery Services (EDS) tasks such as new blocks, variants, behavior…

    197 GitHub stars~1.5k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Backlog Builder

    open-mercato/skills

    Turns a product brief or a spec's phasing into a tracker backlog of epics, stories and tasks with stable ids, acceptance criteria and epic checklists.

    231 GitHub stars~3k tokensUpdated 5 days ago
    Product & Project ManagementAuto-check: notes

  • New Feature

    PolymathWizard/BHIL-AI-First-Development-Toolkit

    Create a complete feature artifact scaffold — PRD slice, technical spec, and task breakdown.

    132 GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Epic Breakdown Advisor

    deanpeters/Product-Manager-Skills

    Splits a too-large epic into user stories using Richard Lawrence's nine Humanizing Work splitting patterns while keeping each story a vertical slice of user value.

    7.2k GitHub starsUsed in 1 repo~6k tokens
    Product & Project ManagementAuto-check passed

More from avelikiy/great_cto

All 27 skills in this repo

  • AnyDesign Design Analyzer

    avelikiy/great_cto

    Analyzes a screenshot, website or Figma file and writes a `design.md` with its token system, component inventory and reconstruction notes, or an `element.md` for one element.

    102 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed

  • Opportunity Solution Tree

    avelikiy/great_cto

    Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.

    102 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Outcome-Focused Roadmap Rewriter

    avelikiy/great_cto

    Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.

    102 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Exposed Secret Rotation

    avelikiy/great_cto

    Turns a leaked key, token or password into one tracked rotation task the moment it's spotted, instead of a reminder repeated every session.

    102 GitHub stars~884 tokensUpdated yesterday
    Auto-check: notes

  • Skeptical Triage

    avelikiy/great_cto

    Runs a three-round self-challenge plus an arbiter over high-stakes findings, so false positives from reviews, audits and flaky-test verdicts do not become blockers.

    102 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check: notes

  • Aesthetic Instrument

    avelikiy/great_cto

    greatcto's own committed aesthetic — the instrument panel. An agent skill from avelikiy/great_cto.

    102 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Pm Planning

What does Pm Planning do?

Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. Pm Planning is an agent skill from avelikiy/great_cto. Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria.

When should I use Pm Planning?

Pm Planning fits situations like: tasks that involve User stories; tasks that involve Task breakdown.

How do I install Pm Planning in Claude Code?

Run `npx skills add avelikiy/great_cto --skill pm-planning -a claude-code`. Or copy the skill folder (skills/pm-planning in avelikiy/great_cto) into .claude/skills/pm-planning in your project. Claude Code loads it when a task matches its description.

How do I install Pm Planning in Codex?

Run `npx skills add avelikiy/great_cto --skill pm-planning -a codex`. Or copy the skill folder (skills/pm-planning in avelikiy/great_cto) into .agents/skills/pm-planning in your project. Codex loads it when a task matches its description.

Can I use Pm Planning 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 avelikiy/great_cto --skill pm-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pm-planning, .gemini/skills/pm-planning, .github/skills/pm-planning and .opencode/skills/pm-planning in your project.

What does Pm Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Pm Planning is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Bash(bd:*).

Does Pm Planning 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 Pm Planning 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 Pm Planning use?

Pm Planning 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 Pm Planning use?

About 1.3k tokens (SKILL.md is roughly 5k 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 Pm Planning?

Skills that share tags, products or a category with Pm Planning: Project Planner (adrianpuiu/claude-skills-marketplace, 100 stars), Spec Workflow (hashgraph-online/awesome-codex-plugins, 1.3k stars), Analyze And Plan (adobe/skills, 197 stars) and Backlog Builder (open-mercato/skills, 231 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pm Planning?

avelikiy (a GitHub user) maintains it in avelikiy/great_cto, which has 102 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 9, 2026.

Source: avelikiy/great_cto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.