# Claude Github PMS

> GITHUB ISSUES AS 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.

```bash
/plugin marketplace add fadymondy/gh-pms
```

## 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

- **Classify**: severity scale, service taxonomy
- **Gate**: gate evidence
- **Branch**: branching policy

## Get started

1. Add the marketplace

```bash
/plugin marketplace add fadymondy/gh-pms
```

2. Bootstrap the repo

```bash
/gh-pms:gh-init --with-project
```

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

```bash
"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.

Source: https://github.com/fadymondy/gh-pms