phase-trackerlisted

Use whenever the user starts non-trivial development work, says things like "let's start phase X", "start the phase", "let's begin a new feature", "next we're going to...", "phase X is done", "close the phase", "write up the phase log", or describes upcoming work that will involve multiple commits or files. Generates a phase plan file at the start of a phase and a phase log file at the end, both under development/phase_log/, following a strict phase-driven workflow. Every meaningful development effort is part of a numbered phase — if the user describes work that does not match a current plan, surface that and offer to draft a plan before coding. Trigger even when the user does not explicitly say "phase".
awjackson2/phase-skills · ★ 0 · AI & Automation · score 70

Install: claude install-skill awjackson2/phase-skills

# Phase Tracker This skill drives a phase-based development workflow. Every meaningful development effort is tracked as a numbered **phase**. Each phase has two markdown files under `development/phase_log/`: - `phase_<NUM>_plan.md` — written **before** the work, captures the plan to be used - `phase_<NUM>_log.md` — written **after** the work, captures what actually happened Two templates live alongside the phase files and define the required structure: - `development/phase_log/phase_plan_template.md` - `development/phase_log/phase_log_template.md` Always follow the template structure. Templates exist so future readers (and Claude in future sessions) can scan any phase quickly without learning a new layout each time. If the templates don't exist yet, run `phase-project-init` first (it scaffolds them). A chronological table of contents for every phase lives at `development/phase_log/phase_index.md`. Keep it in sync whenever a new phase log is written (see Mode 2, Step 3). ## Plans and logs are concepts `development/` is a **knowledge bundle**: every file in it is a concept, meaning it carries YAML front matter and ends with a `## OKF relationships` footer. A plan or log is not a loose note that happens to live in a folder — it is a node in the project's knowledge graph, and the templates already have the right shape. Fill them in; do not strip the front matter. Three rules bite in practice: - **`phase` must equal the number in the filename.** Renaming a file without