From 516f07d3ec230abb58e5d3db7cfc174cf935d61f Mon Sep 17 00:00:00 2001 From: marcelsafin <179933638+marcelsafin@users.noreply.github.com> Date: Thu, 9 Jul 2026 01:01:18 +0200 Subject: [PATCH 1/5] fix(templates): point constitution sync checklist at installed command files MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The consistency-propagation checklist told the agent to read .specify/templates/commands/*.md, but specify init never creates that directory — command templates are rendered straight into the agent-specific directory (.github/prompts/, .claude/commands/, ...). The checklist step could therefore never run against real files. Point it at the installed speckit.* command files for the active agent instead. Fixes #660 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- templates/commands/constitution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/commands/constitution.md b/templates/commands/constitution.md index d003d5c9b2..18353d62cf 100644 --- a/templates/commands/constitution.md +++ b/templates/commands/constitution.md @@ -81,7 +81,7 @@ Follow this execution flow: - Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles. - Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints. - Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline). - - Read each command file in `.specify/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. + - Read each installed `speckit.*` command file for your agent (including this one) — e.g. in `.github/prompts/`, `.claude/commands/`, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed. 5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update): From d9a884bdd21eabec2faef5abcd59df2c642e79bc Mon Sep 17 00:00:00 2001 From: marcelsafin <179933638+marcelsafin@users.noreply.github.com> Date: Thu, 9 Jul 2026 01:13:45 +0200 Subject: [PATCH 2/5] fix(templates): cover hyphenated and skills-mode command filenames Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- templates/commands/constitution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/commands/constitution.md b/templates/commands/constitution.md index 18353d62cf..447dba6f59 100644 --- a/templates/commands/constitution.md +++ b/templates/commands/constitution.md @@ -81,7 +81,7 @@ Follow this execution flow: - Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles. - Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints. - Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline). - - Read each installed `speckit.*` command file for your agent (including this one) — e.g. in `.github/prompts/`, `.claude/commands/`, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. + - Read each installed Spec Kit command file for your agent (including this one) — named `speckit.*` or `speckit-*` depending on the agent, e.g. in `.github/prompts/`, `.claude/commands/`, a skills directory, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed. 5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update): From 7a9bfc31d85175d9fc90f46dc9857f81e6195825 Mon Sep 17 00:00:00 2001 From: marcelsafin <179933638+marcelsafin@users.noreply.github.com> Date: Thu, 9 Jul 2026 01:35:47 +0200 Subject: [PATCH 3/5] fix(templates): use actual integration output directories in examples Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- templates/commands/constitution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/commands/constitution.md b/templates/commands/constitution.md index 447dba6f59..76d9a15d04 100644 --- a/templates/commands/constitution.md +++ b/templates/commands/constitution.md @@ -81,7 +81,7 @@ Follow this execution flow: - Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles. - Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints. - Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline). - - Read each installed Spec Kit command file for your agent (including this one) — named `speckit.*` or `speckit-*` depending on the agent, e.g. in `.github/prompts/`, `.claude/commands/`, a skills directory, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. + - Read each installed Spec Kit command file for your agent (including this one) — named `speckit.*` or `speckit-*` depending on the agent, e.g. in `.github/agents/`, `.claude/skills/`, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed. 5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update): From 836844a8de41d868358e2fcdc077253a3fdfb5c6 Mon Sep 17 00:00:00 2001 From: marcelsafin <179933638+marcelsafin@users.noreply.github.com> Date: Thu, 9 Jul 2026 01:57:08 +0200 Subject: [PATCH 4/5] docs(templates): cover skills-based command layouts in sync checklist Copilot skills mode installs speckit-/SKILL.md under .github/skills/, not .github/agents/. Mention both directories and the SKILL.md layout. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- templates/commands/constitution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/commands/constitution.md b/templates/commands/constitution.md index 76d9a15d04..c8472c747b 100644 --- a/templates/commands/constitution.md +++ b/templates/commands/constitution.md @@ -81,7 +81,7 @@ Follow this execution flow: - Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles. - Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints. - Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline). - - Read each installed Spec Kit command file for your agent (including this one) — named `speckit.*` or `speckit-*` depending on the agent, e.g. in `.github/agents/`, `.claude/skills/`, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. + - Read each installed Spec Kit command file for your agent (including this one) — named `speckit.*`, or `speckit-/SKILL.md` for skills-based layouts, e.g. in `.github/agents/`, `.github/skills/`, `.claude/skills/`, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed. 5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update): From 7e2540329146d0bb763ed188532371f14c6638b1 Mon Sep 17 00:00:00 2001 From: marcelsafin <179933638+marcelsafin@users.noreply.github.com> Date: Thu, 9 Jul 2026 02:00:25 +0200 Subject: [PATCH 5/5] docs(templates): restore hyphenated speckit-* naming in sync checklist The previous commit dropped the speckit-* flat-file variant used by Cline and others while adding the SKILL.md layout. Name all three: speckit.*, speckit-*, and speckit-/SKILL.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- templates/commands/constitution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/commands/constitution.md b/templates/commands/constitution.md index c8472c747b..a0cccdbb97 100644 --- a/templates/commands/constitution.md +++ b/templates/commands/constitution.md @@ -81,7 +81,7 @@ Follow this execution flow: - Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles. - Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints. - Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline). - - Read each installed Spec Kit command file for your agent (including this one) — named `speckit.*`, or `speckit-/SKILL.md` for skills-based layouts, e.g. in `.github/agents/`, `.github/skills/`, `.claude/skills/`, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. + - Read each installed Spec Kit command file for your agent (including this one) — named `speckit.*` or `speckit-*` (dot or hyphen depending on the agent), or laid out as `speckit-/SKILL.md` for skills-based integrations, e.g. in `.github/agents/`, `.github/skills/`, `.claude/skills/`, or your agent's equivalent commands directory — to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed. 5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):