pm-project-templates
Tag-keyed template registry for project types (feature-epic, migration, research-track, integration). Mirrors pm-templates one tier up — the registry is consulted by pm-projects create (to scaffold a project body) and by pm-project-review (to lint required sections). Operates on a project (a Linear Project / GitHub Milestone), not an individual issue. Trigger phrases — "project template", "template for an epic", "template for a migration project", "list project templates", "add a project template", "register a project type", "/pm-project-templates".
What this skill does
# PM Project Templates
Tag-keyed registry of project-type templates. One template per type, two-layer resolution: `<repo>/.claude/pm/project-templates/` overrides the plugin default if present.
## Registry layout
```
<repo>/.claude/pm/project-templates/
├── _manifest.json
└── <type>.md
```
Plugin defaults ship at `skills/pm-project-templates/templates/`.
## Manifest schema
`_manifest.json`:
```json
{
"types": {
"<type-key>": {
"required_sections": ["..."],
"optional_sections": ["..."],
"labels": { "linear": ["..."], "github": ["..."] }
}
}
}
```
`required_sections` drive the `pm-project-review` linter; `optional_sections` are recommended but not enforced; `labels` are applied at create time per-tracker.
## Default types shipped
| Type | Required sections |
|---|---|
| `feature-epic` | Goal / Success Metrics / Milestones / Risks / Out of Scope |
| `migration` | Goal / Scope / Rollback Plan / Cutover Steps / Risks |
| `research-track` | Question / Hypotheses / Time Box / Deliverable / Decision Criteria |
| `integration` | Goal / Systems Involved / Contract / Risks / Acceptance |
## Resolution order
1. `<repo>/.claude/pm/project-templates/_manifest.json` — fully replaces plugin defaults if present (in-repo manifest is authoritative).
2. `plugins/project-manager/skills/pm-project-templates/templates/_manifest.json` — plugin default.
Body resolution (per type) follows the same two-layer rule.
## Operations
| Task | How |
|---|---|
| List registered types | Read the resolved manifest's `types` keys |
| Show a type body | Read `<type>.md` (in-repo first, then plugin) |
| Register a new type | Author `<repo>/.claude/pm/project-templates/<type>.md` + add an entry to the in-repo `_manifest.json` |
| Drop a default type | Author the in-repo manifest with the trimmed `types` map |
## Related
- `pm-projects` — uses the template body + required sections to scaffold and validate creates.
- `pm-project-review` — lints an existing project against its type's `required_sections`.
- `pm-templates` — the **issue-tier** equivalent. Distinct registry, identical mechanic.
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.