From project-manager
Generates project management checklists for Phase 5 (Launch) and Phase 6 (Closure): launch readiness checklist (launch-checklist.md), technical readiness checklist (tech-readiness-checklist.md), and handover-to-operations checklist (handover-checklist.md). Covers tasks #22, #24, and #32 of the project management agent. Mode B: agent pre-populates base items from PMBoK-aligned templates and enriches with data from project-plan.md if available; PM reviews and finalizes. Checklist type is inferred from context; if ambiguous, agent asks. Triggers EN: 'launch checklist', 'tech readiness checklist', 'handover checklist'.
npx claudepluginhub kirkruglov/claude-project-managerThis skill uses the workspace's default tool permissions.
Generates three types of project checklists for the Launch (Phase 5) and Closure (Phase 6) phases.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Generates three types of project checklists for the Launch (Phase 5) and Closure (Phase 6) phases. Populates base items from PMBoK-aligned templates; enriches with project-plan.md data when available. Mode B: agent prepares a draft, PM reviews and finalizes.
Russian: «чек-лист запуска», «чек-лист технической готовности», «чек-лист передачи», «подготовь чеклист», «проверка готовности к запуску», «список для передачи в эксплуатацию» English: "launch checklist", "tech readiness checklist", "handover checklist", "generate checklist", "readiness checklist", "deployment checklist", "closure checklist"
-ru suffix, responses in Russian-en suffix, responses in English| Data | Required | Source |
|---|---|---|
| Checklist type (launch / tech readiness / handover) | no | Inferred from context or PM question |
| Project name | no | project-state.md or PM in chat |
| Responsible person | no | PM specifies or left blank |
| Task and milestone data | no | 02-planning/project-plan.md — for auto-population |
| Launch / handover date | no | PM specifies or from project-plan.md |
| File | Project path | Type | Task |
|---|---|---|---|
launch-checklist.md | 03-execution/ | Launch checklist | #22 |
tech-readiness-checklist.md | 03-execution/ | Tech readiness checklist | #24 |
handover-checklist.md | 04-closure/ | Handover checklist | #32 |
File structure is defined in the corresponding template from templates/.
Guard-rail — verify request type. If the request concerns checklist methodology in general, not a specific project checklist → respond: "generate-checklist creates three types of project checklists: launch (#22, Phase 5), technical readiness (#24, Phase 5), and operations handover (#32, Phase 6). Specify which checklist you need or describe the context." Do not start the workflow.
Infer type from request context:
| Context / keywords | Checklist type |
|---|---|
| "launch", "go-live", "market release", task #22 | launch-checklist |
| "tech readiness", "deploy", "infrastructure", task #24 | tech-readiness-checklist |
| "handover", "operations", "closure", task #32 | handover-checklist |
If type cannot be determined unambiguously → ask: "Which checklist do you need?
Read project-state.md to obtain:
If 02-planning/project-plan.md is available — read and extract:
If files are unavailable: continue with template base items. Output to chat: "project-plan.md not found — generating checklist from PMBoK template. Add specific tasks, dates, and owners manually."
Load the corresponding template:
| Type | Template (RU) | Template (EN) |
|---|---|---|
| launch-checklist | templates/launch-checklist-ru.md | templates/launch-checklist-en.md |
| tech-readiness-checklist | templates/tech-readiness-checklist-ru.md | templates/tech-readiness-checklist-en.md |
| handover-checklist | templates/handover-checklist-ru.md | templates/handover-checklist-en.md |
Populate template placeholders:
[PM] as placeholder[date] as placeholderEnrichment rule: if project-plan.md contains specific Phase tasks, add them as additional items under the matching template section, marked [from plan].
Output to chat:
Ask: "Draft checklist is ready. Would you like to:
Do not create the file until PM confirms.
project-state.md: add/update artifact record → status draft.logs/log.md: date, skill, checklist type, file path.Post-creation orchestration:
| Checklist type | Next step |
|---|---|
| launch-checklist (#22) | Run tech-readiness-checklist (#24) in parallel; after both → coordinate-executors (#23) |
| tech-readiness-checklist (#24) | Run in parallel with launch-checklist (#22); both complete → launch phase active |
| handover-checklist (#32) | After completion → generate-closure-report (#31) |
| File | Checklist type |
|---|---|
templates/launch-checklist-ru.md | Launch checklist (RU) |
templates/launch-checklist-en.md | Launch checklist (EN) |
templates/tech-readiness-checklist-ru.md | Tech readiness checklist (RU) |
templates/tech-readiness-checklist-en.md | Tech readiness checklist (EN) |
templates/handover-checklist-ru.md | Handover checklist (RU) |
templates/handover-checklist-en.md | Handover checklist (EN) |
Reads:
project-state.md — project name, phase (optional)02-planning/project-plan.md — tasks, milestones, owners (optional)Feeds data to:
03-execution/launch-checklist.md → coordinate-executors (#23)03-execution/tech-readiness-checklist.md → activates launch phase04-closure/handover-checklist.md → generate-closure-report (#31)