# Why I Built Claude GitHub PMS: Project Management Where the Code Lives

> I let Claude Code work on my repos all day, so I wanted project management to live where the code lives. Here is why Claude GitHub PMS exists and the choices behind it.

*2026-10-19T12:49:02Z*

# Why I Built Claude GitHub PMS: Project Management Where the Code Lives

I let Claude Code work on my repos all day. At some point the question stopped being "can it write the change?" and became "where does the work get tracked, and who decides it's done?"

Claude GitHub PMS (gh-pms) is my answer: GitHub Issues project management, run from Claude Code. This is the short story of why it looks the way it does.

## The itch

I wanted project management to live where the code lives, not in yet another tool. If the agent opens branches and pull requests in GitHub, then the plan, the issue, the status and the review should be in GitHub too, where anyone on the team can open the Issues, Milestones or Projects tab and see the same thing.

## The choices

The first commit landed on 29 April 2026 as a Claude Code plugin marketplace. The README says it was inspired by Orchestra MCP and Studio PMS, and the idea was to build that kind of lifecycle on top of GitHub instead of beside it. A few choices followed from that.

- **Use GitHub's own primitives.** Plans are milestones, features and bugs use native Issue Types, status lives on a Projects v2 board, and breakdowns are real sub-issues. Labels stay as a fallback when an account doesn't have the native feature. The effect: nothing is hidden in a side database, and your team adopts nothing new.
- **Make "done" cost something.** An issue can't advance until the required sections, with file paths where they matter, are in an evidence comment. There are five gates, and only a human can pass the last one. The effect: a status change carries a record of what changed and how it was checked.
- **Add friction on purpose.** One in-progress issue per assignee, a 30-second cooldown between gated moves, and no feature work on `main`. The effect: it's harder to fake progress by batch-advancing issues.
- **Keep it configurable.** The defaults live in one workflow file and a repo can override them in `.github/gh-pms.yaml`. The effect: the gates are a starting point, not a rule imposed on you.

It grew release by release from there. The changelog goes from the first gates to severity on every issue kind, an optional AI reviewer on Gate 4, triage for deferred requests, metrics and bulk actions. Today the plugin has 22 skills and 4 hooks.

## What it doesn't do

- It only works with GitHub.
- The gate checks that evidence exists and has the right shape. It can't prove the tests passed, so the final approval stays with a person.
- I don't know yet whether the default gates are too strict or too loose for how other teams work. That's the feedback I'm asking for.

## Try it

```bash
/plugin marketplace add fadymondy/gh-pms
/plugin install gh-pms@gh-pms
/gh-pms:gh-init --with-project
```

It's open source under the MIT license. The full walkthrough, with the gate table and the FAQ, is in [GitHub Issues project management with Claude Code](https://gh-pms.fadymondy.com/en/blog/github-issues-project-management-claude-code).

## FAQ

**Is Claude GitHub PMS free?** It's open source under the MIT license.

**Who is it for?** Teams and solo developers who use Claude Code and already live in GitHub.

**Do I need a GitHub organization?** No. Native Issue Types need one, but the plugin falls back to labels on a personal account.

## Next steps

- Read the product walkthrough: [gh-pms.fadymondy.com](https://gh-pms.fadymondy.com/en/blog/github-issues-project-management-claude-code).
- Source: [github.com/fadymondy/gh-pms](https://github.com/fadymondy/gh-pms).
- Tell me whether the gate is too strict, too loose or about right on [Product Hunt](https://www.producthunt.com/products/claude-github-pms) (launching 20 October).

---

Source: https://fadymondy.com/en/blog/why-i-built-claude-github-pms
