implementation-checklist-generation

name	Implementation Checklist Generation
description	Read specifications from docs/plan/<feature>/ and generate a phased implementation checklist.
user_invocable	true

Overview

A skill that reads specification documents generated by /plan-feature and produces a bottom-up implementation checklist (CHECKLIST.md).

Execution Steps

Step 1: Read Specifications

1. Confirm the target feature name (docs/plan/<feature>/ directory name) with the user
2. Read all .md files in docs/plan/<feature>/
3. Verify specification consistency (no undefined references or contradictions)

Step 2: Generate Checklist

Generate docs/plan/<feature>/CHECKLIST.md following the checklist structure template in docs/plan/README.md.

• Concretize each phase's checklist based on the specification content
• Omit phases for layers not covered in the specification (e.g., skip Phase 5 for backend-only features)
• If the specification contains TBD items, annotate the corresponding tasks with [TBD]

Step 3: Present Implementation Guide

After generation, present the following:

1. Overview of all phases and estimated task count
2. The first phase to start (Phase 1: Domain Model)
3. Dependencies between phases
4. Reminder: If spec changes are needed, update the specification documents first before modifying code

Rules

• Implementation order must be bottom-up: Domain -> Data Access -> UseCase -> API -> Frontend
• Include test commands in each phase
• Generate Session Notes in an empty state (to be filled in during implementation)
• Session Notes must always contain three items: Done / Next / Risks & TODO

Reference Documents

• docs/plan/README.md
• docs/plan/<feature>/ all specification files
• docs/testing/README.md
• docs/backend/server-architecture.md
• docs/web-frontend/architecture.md