Workflow Planning & Development Skills

Use to retrofit the phase workflow into an EXISTING project that already has code and git history. Trigger when the user says "adopt the phase workflow here", "set up phases in this existing repo", "start using phases on this project", "retrofit the workflow", or drops these skills into a project that already has commits. Unlike phase-project-init (which bootstraps an empty repo), this works with an established, possibly-shared default branch: it adds development/phaselog/ via a docs-lane PR, optionally backfills a light phase history reconstructed from git, settles where the first new phase number starts, then hands off to phase-decompose/phase-loop or phase-tracker.

Use this skill in the phase-skills authoring repo whenever the user wants to change a rule, convention, terminology, or format of the phase workflow and have it stay consistent across the whole suite. Trigger on "change the phase rule", "update the numbering convention", "phases should now...", "update the phase skills to...", "propagate this convention", "add/rename a response banner", "the index should...", "make the skills consistent", or any edit to a shared phase convention — even if the user names only one file. A single convention is duplicated across the canonical docs, all the phase- skills' embedded copies, the template assets, the portable charter, CLAUDE.md, and a memory; editing one by hand silently drifts the rest. This skill maps every place the convention lives, applies the change everywhere, verifies no drift remains, and overrides the installed .claude/skills copies. Prefer it over hand-editing whenever a change touches a shared rule rather than one skill's private wording.

Use to turn a large goal into a well-chunked umbrella roadmap before any phase work starts. Trigger when the user hands over a big feature or project and says "break this down", "decompose this", "chunk this into phases", "plan out this whole thing", "make a roadmap", or when phase-loop needs an umbrella to drive. Produces the MAJOR.0.0 umbrella plan — the ordered roadmap of Minors and Patches — applying a quality bar (tiny independently-testable steps, dependency ordering, risk tags, right-sizing) and leaving numbering room so future work can append near its theme. Hands off to phase-loop (multi-phase) or phase-tracker (single Minor).

Use to drive a large multi-step effort to completion by running phase cycles continuously. Trigger when the user hands over a big plan and wants it chunked into phases and executed end-to-end ("loop through this plan", "build this whole thing", "run phase cycles until done", "phase loop"), OR when the user wants to CONTINUE a half-finished effort and complete all remaining phases ("pick up where we left off", "finish the rest of this", "continue from 8.5.1"). Orchestrates phase-tracker and phase-recap: it builds (or recovers) an umbrella plan that chunks the work into Minors and Patches, then loops the phase cycle — recap, plan, implement, log, commit, PR — until every phase ships. Uses Claude's /loop to self-pace across turns and sessions.

Use to bootstrap a fresh project for the phase-driven workflow. Trigger when the user is starting a brand-new project, says "initialize the project", "set up the project", "bootstrap this repo", "set up the phase workflow here", "phase init", or otherwise wants the scaffolding (git, development directories, phase-log templates) in place before any phase work begins. Sets up git, the development/phaselog/ structure, the plan/log/index templates, and the conventions the phase-tracker and phase-recap skills expect, then hands off to phase-tracker or phase-loop for the first phase.

Use this skill to load context about the project's state from its phase logs before answering or acting on anything substantial. Runs in two modes — an ambient session recap that silently loads general state into working memory, and an explicit scoped recap that prints a clean report of the phases preceding the current one within the current phase's scope. Trigger when the agent lacks current state — start of a session, "catch me up", "what's the state", "summarize the project", "what's in progress / deferred / placeholder" — or when the user asks for a recap at a phase level ("phase recap Major 5", "recap 5.4", "catch me up on 5.3.2"), and BEFORE proposing scope or drafting a phase plan. Reads only from development/phaselog/, never the codebase.