phase-amendlisted

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.
awjackson2/phase-skills · ★ 0 · AI & Automation · score 70

Install: claude install-skill awjackson2/phase-skills

# Phase Amend This is a **maintenance skill for the phase-skills authoring repo itself** — not one of the seven workflow skills that ship into other projects. Its job: apply a change to a shared phase-workflow convention *consistently everywhere it is expressed*. ## Why this exists The conventions are deliberately **duplicated**. The canonical docs (`TERMINOLOGY.md`, `templates/`, `phase_project.md`) are the source of truth, but every skill also **embeds** the conventions it needs so it stays self-contained when dropped into a project alone. That duplication is a feature — and a liability: change the phase-number grammar in `phase-tracker` only, and `phase-recap`, the charter, `CLAUDE.md`, and the memory now disagree. Nothing at runtime catches that drift; a human reading one skill months later just gets a wrong rule. So the value of this skill is **not** editing — it's knowing the full *sync surface* for a given convention and hitting all of it in one pass, then proving nothing was missed. ## The sync surface Where each shared convention lives. Grep to confirm before editing (files shift as the suite grows) — treat this as the starting map, not gospel. | Convention | Lives in | |---|---| | **Phase-number grammar** (`MAJOR.MINOR.PATCH`, digits-only, branch=Minor, Patch=commit) | `TERMINOLOGY.md` (hierarchy), `phase-tracker` (Terminology, Step 1, File-naming, Git rules), `phase-recap` (numbering-signal nuance), `phase-decompose`, `phase-adopt` (numbering origin), `phase