Skip to content

docs(commands): fix stale path refs, phantom phase, duplicate numbering #2267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vsima wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −6
Open

docs(commands): fix stale path refs, phantom phase, duplicate numbering #2267

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion templates/commands/constitution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,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.
- Review each installed command file to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. Paths vary by integration — e.g. `.claude/skills/speckit-*/SKILL.md` (Claude Code), `.github/prompts/speckit.*.prompt.md` (Copilot), or `.specify/templates/commands/*.md` when a preset ships them. Consult the active integration's skills/commands directory rather than assuming a single location.
- 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):
Expand Down
2 changes: 1 addition & 1 deletion templates/commands/implement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,7 @@ You **MUST** consider the user input before proceeding (if not empty).
- **Kubernetes/k8s**: `*.secret.yaml`, `secrets/`, `.kube/`, `kubeconfig*`, `*.key`, `*.crt`

5. Parse tasks.md structure and extract:
- **Task phases**: Setup, Tests, Core, Integration, Polish
- **Task phases**: Setup, Foundational, User Stories (one phase per story, in priority order), Polish (matches the phase structure emitted by `/speckit.tasks`; see `templates/commands/tasks.md`)
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The inline reference to templates/commands/tasks.md is not a stable path in installed integrations (e.g., Copilot/Claude installs place command files under integration-specific directories). To keep this guidance accurate across integrations, refer to the /speckit.tasks output/phase headings generically, or describe the integration-specific locations (similar to constitution.md) rather than pointing to a repo-only template path.

Suggested change
- **Task phases**: Setup, Foundational, User Stories (one phase per story, in priority order), Polish (matches the phase structure emitted by `/speckit.tasks`; see `templates/commands/tasks.md`)
- **Task phases**: Setup, Foundational, User Stories (one phase per story, in priority order), Polish (matches the phase headings emitted by `/speckit.tasks`)

Copilot uses AI. Check for mistakes.
- **Task dependencies**: Sequential vs parallel execution rules
- **Task details**: ID, description, file paths, parallel markers [P]
- **Execution flow**: Order and dependency requirements
Expand Down
2 changes: 1 addition & 1 deletion templates/commands/plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ You **MUST** consider the user input before proceeding (if not empty).
- Phase 1: Update agent context by running the agent script
- Re-evaluate Constitution Check post-design

4. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
4. **Stop and report**: Command ends after Phase 1 (data-model & contracts). Report branch, IMPL_PLAN path, and generated artifacts.
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This parenthetical says Phase 1 is “data-model & contracts”, but in the preceding step Phase 1 also includes generating quickstart.md and updating agent context. Consider either expanding the parenthetical to cover all Phase 1 deliverables (data-model, contracts, quickstart, context update) or removing the parenthetical to avoid implying an incomplete Phase 1 scope.

Suggested change
4. **Stop and report**: Command ends after Phase 1 (data-model & contracts). Report branch, IMPL_PLAN path, and generated artifacts.
4. **Stop and report**: Command ends after Phase 1 (data-model, contracts, quickstart, and agent context update). Report branch, IMPL_PLAN path, and generated artifacts.

Copilot uses AI. Check for mistakes.

5. **Check for extension hooks**: After reporting, check if `.specify/extensions.yml` exists in the project root.
- If it exists, read it and look for entries under the `hooks.after_plan` key
Expand Down
6 changes: 3 additions & 3 deletions templates/commands/taskstoissues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,8 +51,8 @@ You **MUST** consider the user input before proceeding (if not empty).
## Outline

1. Run `{SCRIPT}` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
1. From the executed script, extract the path to **tasks**.
1. Get the Git remote by running:
2. From the executed script, extract the path to **tasks**.
3. Get the Git remote by running:

```bash
git config --get remote.origin.url
Expand All @@ -61,7 +61,7 @@ git config --get remote.origin.url
> [!CAUTION]
> ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL

1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
4. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.

> [!CAUTION]
> UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL
Expand Down