docs: use /speckit.-prefixed command names throughout (v0.1.1)#2
Merged
TortoiseWolfe merged 1 commit intomainfrom Apr 21, 2026
Merged
docs: use /speckit.-prefixed command names throughout (v0.1.1)#2TortoiseWolfe merged 1 commit intomainfrom
TortoiseWolfe merged 1 commit intomainfrom
Conversation
The unprefixed /plan, /tasks, /implement never existed in published Spec Kit releases — the actual commands are /speckit.plan, /speckit.tasks, /speckit.implement. Correct this in all three documentation surfaces: - extension.yml:7 — description field (shown by `specify extension info`) - README.md:10 — tagline paragraph - README.md:16 — how-it-works paragraph Bumps version to 0.1.1 and adds CHANGELOG entry. Resolves #1. Flagged during review of github/spec-kit#2262. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/plan,/tasks,/implement→/speckit.plan,/speckit.tasks,/speckit.implementacross all three documentation surfaces (extension.ymldescription,README.mdtagline,README.mdhow-it-works).versionto0.1.1inextension.yml.The unprefixed names never existed in published Spec Kit releases, so the prior text would have misled users. Flagged during review of github/spec-kit#2262.
Resolves #1.
Test plan
extension.ymlstill parses as valid YAML/plan,/tasks,/implementreferences anywhere in*.md/*.yml/*.yamlFollow-up
After merge + v0.1.1 release, a small PR against
github/spec-kitwill bump the catalog entry'sversionanddownload_urlto point at v0.1.1 (gated on github/spec-kit#2262 landing first).🤖 Generated with Claude Code