project-phaselisted
Install: claude install-skill SRGSSR/agent-skills
# Project Phase
The right way to write code depends on where a project is in its life. A prototype needs speed and zero ceremony. A live product needs tests, compatibility and an eye on tech debt. A system in maintenance needs the smallest possible diff. AI agents tend to apply "large project best practices" everywhere: full scaffolding on day one, early generalization, improvement suggestions nobody asked for. Or the opposite: casual sweeping edits in code that must not regress.
This skill makes the phase explicit and gives the agent a behavior contract for it.
Commands:
- `/project-phase`: the [status](#status).
- `/project-phase setup`: set it up, or review the choices of a project already set up. See [Setup](#setup-first-use-in-a-project).
- `/project-phase on`, `/project-phase off`: turn it on or off for this project. See [On / off](#on--off).
- `/project-phase help`: this list, with the current phase (or off, or not set up) from the block in `AGENTS.md`. Read only the block; run nothing else.
Everything else works in words: change the phase ("this is live now"), review the debt, add an area override or a custom rule.
## How it works
Two pieces, both plain Markdown in the repo, readable by any agent or human:
1. **Contract block** - about 15 lines between `<!-- project-phase:start -->` and `<!-- project-phase:end -->` in `AGENTS.md` (and loaded from `CLAUDE.md`). Agent tools load these files on every task, so the phase shapes all work even when this skill is not