CLAUDE GITHUB PMS

GITHUB ISSUES AS PMS

Claude Github PMS

Plans are milestones, features and bugs are native issue types, status lives on a Projects v2 board. Open the Issues tab and you see exactly where the project is.

lifecycle · #42gate 2 / 5
  • in-progress → ready-for-testing
    passed
  • in-testing → ready-for-docs
    open
  • documented → in-review
    locked
/plugin marketplace add fadymondy/gh-pms
Read the docs
  • Projects v2 fields
  • Milestones for plans
  • Sub-issues & relationships
  • Evidence-gated lifecycle
  • Needs gh CLI + jq
  • MIT licensed

Features

Native primitives

Issue Types, Projects v2, Milestones and sub-issues — not a pile of labels pretending to be structure.

Five evidence gates

Each transition demands named sections: file paths, test results, self-review. No prose, no pass.

PR-driven review

Every feature ends in a PR carrying Closes #N, so merging closes the issue and the loop.

Guardrails

One in-progress issue per assignee, a cooldown between gates, and bugs auto-skip the docs gate.

All configuration, not code

01

Classify

  • severity scale
  • service taxonomy
02

Gate

  • gate evidence
03

Branch

  • branching policy

Get started

  1. 01

    Add the marketplace

    /plugin marketplace add fadymondy/gh-pms
  2. 02

    Bootstrap the repo

    /gh-pms:gh-init --with-project
  3. 03

    Then just talk — it classifies the prompt and files the issue itself

    "the login button is broken on mobile"

Configuration

Defaults live in workflows/default.yaml; drop a .github/gh-pms.yaml to override per repo. Severity scales, service taxonomy, gate evidence and the branching policy are all config, not code.

Community

GitHubmaintained