Skill: generate-checklist

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.

Triggers

Russian: «чек-лист запуска», «чек-лист технической готовности», «чек-лист передачи», «подготовь чеклист», «проверка готовности к запуску», «список для передачи в эксплуатацию» English: "launch checklist", "tech readiness checklist", "handover checklist", "generate checklist", "readiness checklist", "deployment checklist", "closure checklist"

Language Detection

• Request in Russian → templates with -ru suffix, responses in Russian
• Otherwise → templates with -en suffix, responses in English

Input

Output

File structure is defined in the corresponding template from templates/.

Instructions

Step 1 — Determine Checklist Type

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:

If type cannot be determined unambiguously → ask: "Which checklist do you need?

1. Launch checklist (#22) — confirming overall product/project readiness for launch.
2. Technical readiness checklist (#24) — verifying technical and infrastructure readiness.
3. Operations handover checklist (#32) — documenting project transfer to the support/operations team."

Do not proceed to Step 2 without an answer.

Step 2 — Gather Context Data

Read project-state.md to obtain:

• Project name
• Current phase and launch date (if specified)

If 02-planning/project-plan.md is available — read and extract:

• Planned launch / handover date
• Key milestones of Phase 5 or Phase 6
• Task list and owners for the phase (for auto-populating checklist items)
• Team composition (PM, tech lead, business owner)

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

Step 3 — Build the Checklist

Load the corresponding template:

Populate template placeholders:

1. Project name, date, responsible — from project-state.md or PM's data
2. Checklist items — base items from template (PMBoK Best Practice) + specifics from project-plan.md
3. Owners per item — from project plan if available; otherwise [PM] as placeholder
4. Due dates — from project plan if available; otherwise [date] as placeholder

Enrichment rule: if project-plan.md contains specific Phase tasks, add them as additional items under the matching template section, marked [from plan].

Step 4 — Show Draft to PM

Output to chat:

• Brief summary: checklist type, number of sections, number of items
• First 2 sections as preview (markdown)

Ask: "Draft checklist is ready. Would you like to:

1. Save as is → I will generate the file.
2. Add / remove items → describe your changes.
3. Update owners or dates → specify."

Do not create the file until PM confirms.

Step 5 — Create File and Save

1. Create file per the table in the Output section.
2. Save to the corresponding project folder.
3. Update project-state.md: add/update artifact record → status draft.
4. Write to logs/log.md: date, skill, checklist type, file path.
5. Output to chat:

• "File saved: {path}"
• Next orchestration step (see table below)

Post-creation orchestration:

Templates

Dependencies

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 phase
• 04-closure/handover-checklist.md → generate-closure-report (#31)

Constraints

• Mode B: draft for PM; PM reviews and approves
• One checklist type per invocation; for multiple types — separate skill calls
• Without project-plan.md — base template items only; placeholders for project-specific data
• Does not modify project-plan.md or other artifacts
• Does not create Jira tasks — use coordinate-executors for that
• Base items follow PMBoK 8 and Agile best practice; PM adapts to project specifics