name	pm-project-improve
description	Enrich a project (a Linear Project / GitHub Milestone) with repo context (owning modules, related code, recent commits), related projects + prior art, best-practice references, risk surfacing, and clarifying Q&A. Pipelined after pm-project-review or standalone. --apply posts as comment (Linear) or marked description block (GitHub). Operates on a project, not an individual issue — issue improvement lives in pm-improve. Trigger phrases — "improve this project", "enrich this project", "add context to the project", "research the project", "/pm-project-improve".
version	0.44.4

PM Project Improve

Enrichment pass for tracker projects. Mirrors pm-improve one tier up.

Usage

/pm-project-improve <project> [--apply]

<project> (project slug/name, required) — the Linear Project or GitHub Milestone to enrich.
--apply (flag, optional) — post the enrichment (Linear comment / marked GitHub milestone-description block) instead of emitting a draft only.

What it adds

Repo context — files/modules likely involved (CODEOWNERS lookup; recent commits touching paths mentioned in the description; existing tests that cover the area).
Related projects / prior art — other projects (and recently-closed issues) with overlapping keywords or shared teams.
Best-practice references — internal docs, ADRs, runbooks, registered SME repos that bear on the work.
Risk surfacing — risks the author may not have considered, drawn from related prior art ("last migration we did took 3x the estimate because of X").
Clarifying Q&A — questions the author should resolve before kickoff. Each Q numbered, with a recommended answer when one is obvious.

Pipelining with `pm-project-review`

When invoked right after review, improve reads the findings block from the project's most recent review and prioritizes enrichment that closes structural gaps first (e.g., if review flagged "Risks section is one line," improve surfaces specific risks for the author to consider).

`--apply`

Same mechanic as pm-project-review: Linear posts a comment with  markers; GitHub appends a marked block to the milestone description via appendApplyBlock. The marker is replaced (not stacked) on re-runs.

Safe to re-run after time has passed — repo state drifts, related-projects set evolves, and the marker mechanic replaces rather than accumulates.

pm-improve — the issue-tier equivalent.
pm-project-review — natural upstream; improve is the "now fix it" follow-up.
pm-conventions — consulted for project-improvement style rules if ## Project review heading is present.

PM Project Improve

Enrichment pass for tracker projects. Mirrors pm-improve one tier up.

Usage

/pm-project-improve <project> [--apply]

<project> (project slug/name, required) — the Linear Project or GitHub Milestone to enrich.

--apply (flag, optional) — post the enrichment (Linear comment / marked GitHub milestone-description block) instead of emitting a draft only.

What it adds

Repo context — files/modules likely involved (CODEOWNERS lookup; recent commits touching paths mentioned in the description; existing tests that cover the area).

Related projects / prior art — other projects (and recently-closed issues) with overlapping keywords or shared teams.

Best-practice references — internal docs, ADRs, runbooks, registered SME repos that bear on the work.

Risk surfacing — risks the author may not have considered, drawn from related prior art ("last migration we did took 3x the estimate because of X").

Clarifying Q&A — questions the author should resolve before kickoff. Each Q numbered, with a recommended answer when one is obvious.

Pipelining with pm-project-review

--apply

Safe to re-run after time has passed — repo state drifts, related-projects set evolves, and the marker mechanic replaces rather than accumulates.

pm-improve — the issue-tier equivalent.

pm-project-review — natural upstream; improve is the "now fix it" follow-up.

pm-conventions — consulted for project-improvement style rules if ## Project review heading is present.

pm-project-improve