Skip to content

docs: point the upgrade guide's Copilot checks at .github/skills #5010

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
yxshee wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −5
Open

docs: point the upgrade guide's Copilot checks at .github/skills #5010

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
10 changes: 5 additions & 5 deletions docs/upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ When Spec Kit releases new features (like new slash commands, updated templates,

For existing Spec Kit projects, use the manifest-aware upgrade path first:

- ✅ **Integration command/skill files** (`.claude/skills/`, `.github/prompts/`, `.agents/skills/`, etc.)
- ✅ **Integration command/skill files** (`.claude/skills/`, `.github/skills/`, `.agents/skills/`, etc.)
- ✅ **Managed shared scripts and templates** (`.specify/scripts/`, `.specify/templates/`) when they are unchanged from the previous managed copy
- ✅ **Installed extensions** when you run `specify extension update`

Expand Down Expand Up @@ -420,7 +420,7 @@ This warning appears when you run `specify init --here` (or `specify init .`) in

Only Spec Kit infrastructure files:

- Agent command/skill files (`.claude/skills/`, `.github/prompts/`, etc.)
- Agent command/skill files (`.claude/skills/`, `.github/skills/`, etc.)
- Scripts in `.specify/scripts/`
- Templates in `.specify/templates/`
- Missing memory files such as `.specify/memory/constitution.md` may be created from templates; an existing constitution is preserved
Expand Down Expand Up @@ -498,15 +498,15 @@ The `specify` CLI tool is used for:
- **Fallback recovery:** `specify init --here --force` when integration metadata is missing or the manifest-aware path cannot be used
- **Diagnostics:** `specify check` to verify tool installation

Once you've run `specify init`, the slash commands (like `/speckit.specify`, `/speckit.plan`, etc.) are **permanently installed** in your project's agent folder (`.claude/`, `.github/prompts/`, `.pi/prompts/`, `.omp/commands/`, etc.). Your AI coding agent reads these command files directly—no need to run `specify` again.
Once you've run `specify init`, the slash commands (like `/speckit.specify`, `/speckit.plan`, etc.) are **permanently installed** in your project's agent folder (`.claude/`, `.github/skills/`, `.pi/prompts/`, `.omp/commands/`, etc.). Your AI coding agent reads these command files directly—no need to run `specify` again.

**If your agent isn't recognizing slash commands:**

1. **Verify command files exist:**

```bash
# For GitHub Copilot
ls -la .github/prompts/
# For GitHub Copilot (.github/agents/ and .github/prompts/ with --integration-options="--commands")
ls -la .github/skills/

# For Claude
ls -la .claude/skills/
Expand Down