pm-project-improve
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".
What this skill does
# 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
1. **Repo context** — files/modules likely involved (CODEOWNERS lookup; recent commits touching paths mentioned in the description; existing tests that cover the area).
2. **Related projects / prior art** — other projects (and recently-closed issues) with overlapping keywords or shared teams.
3. **Best-practice references** — internal docs, ADRs, runbooks, registered SME repos that bear on the work.
4. **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").
5. **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 `<!-- pm-project-improve: v0.25.0 -->` 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.
## Related
- `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.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.