chore: bump version to 0.12.7

.github/CODEOWNERS

@@ -5,3 +5,4 @@
 /extensions/catalog.community.json @mnriem
 /integrations/catalog.community.json @mnriem
 /presets/catalog.community.json @mnriem
+

.github/ISSUE_TEMPLATE/agent_request.yml

@@ -7,8 +7,8 @@ body:
     attributes:
       value: |
         Thanks for requesting a new agent! Before submitting, please check if the agent is already supported.
-
-        **Currently supported agents**: Amp, Antigravity, Auggie CLI, Claude Code, Cline, CodeBuddy, Codex CLI, Cursor, Devin for Terminal, Firebender, Forge, Gemini CLI, GitHub Copilot, Goose, Grok Build, Hermes Agent, IBM Bob, Junie, Kilo Code, Kimi Code, Kiro CLI, Lingma, Mistral Vibe, Oh My Pi, opencode, Pi Coding Agent, Qoder CLI, Qwen Code, RovoDev ACLI, SHAI, Tabnine CLI, Trae, ZCode, Zed
+        
+        **Currently supported agents**: Amp, Antigravity, Auggie CLI, Claude Code, Cline, CodeBuddy, Codex CLI, Cursor, Devin for Terminal, Firebender, Forge, Gemini CLI, GitHub Copilot, Goose, Hermes Agent, IBM Bob, Junie, Kilo Code, Kimi Code, Kiro CLI, Lingma, Mistral Vibe, Oh My Pi, opencode, Pi Coding Agent, Qoder CLI, Qwen Code, RovoDev ACLI, SHAI, Tabnine CLI, Trae, ZCode, Zed
 
   - type: input
     id: agent-name

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -76,7 +76,6 @@ body:
         - Gemini CLI
         - GitHub Copilot
         - Goose
-        - Grok Build
         - Hermes Agent
         - IBM Bob
         - Junie

.github/ISSUE_TEMPLATE/extension_submission.yml

@@ -7,7 +7,7 @@ body:
     attributes:
       value: |
         Thanks for contributing an extension! This template helps you submit your extension to the community catalog.
-
+        
         **Before submitting:**
         - Review the [Extension Publishing Guide](https://github.com/github/spec-kit/blob/main/extensions/EXTENSION-PUBLISHING-GUIDE.md)
         - Ensure your extension has a valid `extension.yml` manifest
@@ -209,9 +209,9 @@ body:
         **Tested on:**
         - macOS 14.0 with Spec Kit v0.1.0
         - Linux Ubuntu 22.04 with Spec Kit v0.1.0
-
+        
         **Test project:** [Link or description]
-
+        
         **Test scenarios:**
         1. Installed extension
         2. Configured settings
@@ -230,7 +230,7 @@ body:
         ```bash
         # Install extension
         specify extension add <extension-name> --from https://github.com/your-org/spec-kit-your-extension/archive/refs/tags/v1.0.0.zip
-
+        
         # Use a command
         /speckit.your-extension.command-name arg1 arg2
         ```

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -70,7 +70,6 @@ body:
         - Gemini CLI
         - GitHub Copilot
         - Goose
-        - Grok Build
         - Hermes Agent
         - IBM Bob
         - Junie

.github/ISSUE_TEMPLATE/preset_submission.yml

@@ -7,7 +7,7 @@ body:
     attributes:
       value: |
         Thanks for contributing a preset! This template helps you submit your preset to the community catalog.
-
+        
         **Before submitting:**
         - Review the [Preset Publishing Guide](https://github.com/github/spec-kit/blob/main/presets/PUBLISHING.md)
         - Ensure your preset has a valid `preset.yml` manifest

.github/PULL_REQUEST_TEMPLATE.md

@@ -19,3 +19,4 @@
 - [ ] I **did** use AI assistance (describe below)
 
 <!-- If you used AI, briefly describe how (e.g., "Code generated by Copilot", "Consulted ChatGPT for approach"): -->
+

.github/workflows/add-community-extension.lock.yml

@@ -36,7 +36,7 @@
 #   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
-#   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+#   - actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
 #   - actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
 #   - github/gh-aw-actions/setup@c0338fef4749d08c21f8f975fb0e37efa17dda47 # v0.79.8
 #
@@ -1399,7 +1399,7 @@ jobs:
           mkdir -p /tmp/gh-aw/threat-detection
           touch /tmp/gh-aw/threat-detection/detection.log
       - name: Setup Node.js
-        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: '24'
           package-manager-cache: false

.github/workflows/add-community-preset.lock.yml

@@ -36,7 +36,7 @@
 #   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
-#   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+#   - actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
 #   - actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
 #   - github/gh-aw-actions/setup@c0338fef4749d08c21f8f975fb0e37efa17dda47 # v0.79.8
 #
@@ -1399,7 +1399,7 @@ jobs:
           mkdir -p /tmp/gh-aw/threat-detection
           touch /tmp/gh-aw/threat-detection/detection.log
       - name: Setup Node.js
-        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: '24'
           package-manager-cache: false

.github/workflows/bug-assess.lock.yml

@@ -35,7 +35,7 @@
 #   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
-#   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+#   - actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
 #   - actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
 #   - github/gh-aw-actions/setup@c0338fef4749d08c21f8f975fb0e37efa17dda47 # v0.79.8
 #
@@ -1344,7 +1344,7 @@ jobs:
           mkdir -p /tmp/gh-aw/threat-detection
           touch /tmp/gh-aw/threat-detection/detection.log
       - name: Setup Node.js
-        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: '24'
           package-manager-cache: false

.github/workflows/bug-fix.lock.yml

@@ -36,7 +36,7 @@
 #   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
-#   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+#   - actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
 #   - actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
 #   - github/gh-aw-actions/setup@c0338fef4749d08c21f8f975fb0e37efa17dda47 # v0.79.8
 #
@@ -1405,7 +1405,7 @@ jobs:
           mkdir -p /tmp/gh-aw/threat-detection
           touch /tmp/gh-aw/threat-detection/detection.log
       - name: Setup Node.js
-        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: '24'
           package-manager-cache: false

.github/workflows/bug-test.lock.yml

@@ -35,7 +35,7 @@
 #   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
-#   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+#   - actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
 #   - actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
 #   - github/gh-aw-actions/setup@c0338fef4749d08c21f8f975fb0e37efa17dda47 # v0.79.8
 #
@@ -1366,7 +1366,7 @@ jobs:
           mkdir -p /tmp/gh-aw/threat-detection
           touch /tmp/gh-aw/threat-detection/detection.log
       - name: Setup Node.js
-        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: '24'
           package-manager-cache: false

.github/workflows/docs.yml

@@ -35,7 +35,7 @@ jobs:
           fetch-depth: 0 # Fetch all history for git info
 
       - name: Setup .NET
-        uses: actions/setup-dotnet@a98b56852c35b8e3190ac28c8c2271da59106c68 # v6.0.0
+        uses: actions/setup-dotnet@26b0ec14cb23fa6904739307f278c14f94c95bf1 # v5.4.0
         with:
           dotnet-version: '8.x'
 

.github/workflows/lint.yml

@@ -37,7 +37,7 @@ jobs:
           fi
 
       - name: Run markdownlint-cli2
-        uses: DavidAnson/markdownlint-cli2-action@8de2aa07cae85fd17c0b35642db70cf5495f1d25 # v24.0.0
+        uses: DavidAnson/markdownlint-cli2-action@ded1f9488f68a970bc66ea5619e13e9b52e601cd # v23
         with:
           globs: |
             '**/*.md'

.github/workflows/publish-pypi.yml

@@ -32,7 +32,7 @@ jobs:
           ref: refs/tags/${{ inputs.tag }}
 
       - name: Install uv
-        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
 
       - name: Set up Python
         uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6
@@ -74,7 +74,7 @@ jobs:
           path: dist/
 
       - name: Install uv
-        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
 
       - name: Publish to PyPI
         run: uv publish

.github/workflows/stale.yml

@@ -14,30 +14,30 @@ jobs:
   stale:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@1e223db275d687790206a7acac4d1a11bd6fe629 # v10
+      - uses: actions/stale@eb5cf3af3ac0a1aa4c9c45633dd1ae542a27a899 # v10
         with:
           # Days of inactivity before an issue or PR becomes stale
           days-before-stale: 150
           # Days of inactivity before a stale issue or PR is closed (after being marked stale)
           days-before-close: 30
-
+          
           # Stale issue settings
           stale-issue-message: 'This issue has been automatically marked as stale because it has not had any activity for 150 days. It will be closed in 30 days if no further activity occurs.'
           close-issue-message: 'This issue has been automatically closed due to inactivity (180 days total). If you believe this issue is still relevant, please reopen it or create a new issue.'
           stale-issue-label: 'stale'
-
+          
           # Stale PR settings
           stale-pr-message: 'This pull request has been automatically marked as stale because it has not had any activity for 150 days. It will be closed in 30 days if no further activity occurs.'
           close-pr-message: 'This pull request has been automatically closed due to inactivity (180 days total). If you believe this PR is still relevant, please reopen it or create a new PR.'
           stale-pr-label: 'stale'
-
+          
           # Exempt issues and PRs with these labels from being marked as stale
           exempt-issue-labels: 'pinned,security'
           exempt-pr-labels: 'pinned,security'
-
+          
           # Only issues or PRs with all of these labels are checked
           # Leave empty to check all issues and PRs
           any-of-labels: ''
-
+          
           # Operations per run (helps avoid rate limits)
           operations-per-run: 250

.github/workflows/test.yml

@@ -16,7 +16,7 @@ jobs:
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 
       - name: Install uv
-        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
 
       - name: Set up Python
         uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6
@@ -37,7 +37,7 @@ jobs:
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 
       - name: Install uv
-        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 # v8.2.0
 
       - name: Set up Python ${{ matrix.python-version }}
         uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6

.gitignore

@@ -53,10 +53,9 @@ docs/dev
 
 # The following directories/file are intentionally ignored so that they are not accidentally
 # committed to the repository. They contain the scaffolding `specify init --integration copilot`
-# (or other agents) does and they are meant for dogfooding Spec Kit during its own feature development.
+# does and they are meant for dogfooding Spec Kit during its own feature development.
 .github/agents/
 .github/prompts/
 .github/copilot-instructions.md
-.grok/
 .specify/
 specs/

.markdownlint-cli2.jsonc

@@ -26,4 +26,4 @@
   "ignores": [
     ".genreleases/"
   ]
-}
+}

.pre-commit-config.yaml

@@ -1,12 +0,0 @@
----
-repos:
-  - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v6.0.0
-    hooks:
-      - id: check-executables-have-shebangs
-      - id: check-yaml
-        exclude: \.lock\.yml$
-      - id: end-of-file-fixer
-        exclude: \.lock\.yml$
-      - id: trailing-whitespace
-        exclude: \.lock\.yml$

CHANGELOG.md

@@ -2,172 +2,6 @@
 
 <!-- insert new changelog below this comment -->
 
-## [0.12.18] - 2026-07-17
-
-### Changed
-
-- chore(deps): bump actions/setup-dotnet from 5.4.0 to 6.0.0 (#3574)
-- chore(deps): bump actions/stale from 10.3.0 to 10.4.0 (#3572)
-- chore(deps): bump actions/setup-node from 6.4.0 to 7.0.0 (#3570)
-- docs: weave harness/SDLC framing into landing page (#3567)
-- docs: reframe SDD positioning, modernize install, and de-duplicate walkthroughs (#3565)
-- docs: document extensions.yml hook configuration (#3563)
-- docs: refresh landing page ecosystem stats (#3561)
-- [extension] Add Dotdog extension to community catalog (#3558)
-- Update DocGuard — CDD Enforcement to v0.33.0 (#3559)
-- chore: release 0.12.17, begin 0.12.18.dev0 development (#3560)
-
-## [0.12.17] - 2026-07-16
-
-### Changed
-
-- fix(extensions): resolve __SPECKIT_COMMAND tokens in auto-registered skills (#3544)
-- fix(workflows): fail if/switch steps on non-list branch instead of crashing (#3515)
-- feat(integrations): add Grok Build skills-based integration (#3535)
-- fix(extensions/git): reject negative -Number in create-new-feature-branch.ps1 (#3538)
-- test: cover preset constitution seeding through init CLI (#3297)
-- fix(integration): preserve ai_skills on `use` for skills-mode Copilot (#3550) (#3551)
-- [extension] Add Figma Starter extension to community catalog (#3547)
-- [extension] Add Spec-Kit BDD extension to community catalog (#3548)
-- [extension] Update Quality Gates (Enforcement Layer) extension to v0.3.2 (#3542)
-- chore: release 0.12.16, begin 0.12.17.dev0 development (#3549)
-
-## [0.12.16] - 2026-07-15
-
-### Changed
-
-- fix(workflows): raise a clear error, not a cryptic crash, on non-string filter args (#3522)
-- feat(workflows): expose workflow source directory to steps (#3469)
-- fix(workflows): fan-out max_concurrency .inf falls back to sequential, not crash (#3521)
-- Update Coding Standards Drift Control extension to v0.4.0 (#3540)
-- fix(presets): seed constitution from preset constitution-template (#3272) (#3276)
-- docs: add PyPI as second supported install route (#3425) (#3516)
-- fix(workflows): fail while/do-while steps on non-list steps instead of crashing (#3519)
-- Add PatchWarden Evidence Pack extension to community catalog (#3514)
-- feat(extensions): port git extension scripts to Python (#3400)
-- chore: release 0.12.15, begin 0.12.16.dev0 development (#3513)
-
-## [0.12.15] - 2026-07-14
-
-### Changed
-
-- Update Autonomous Run Governance preset to v0.1.4 (#3511)
-- fix(workflows): raise catalog error, not raw ValueError, on a malformed catalog URL (#3484)
-- fix(workflows): evaluate 'in'/'not in' safely on a non-iterable right operand (#3447) (#3468)
-- fix: add trailing newline to init-options.json output (#3509)
-- feat(workflows): align workflow CLI with extension command surface (#3419)
-- fix(extensions): stop env-var config leaking across prefix-colliding extension IDs (#3497)
-- fix(integrations): escape control characters in goose recipe YAML renderer (#3384)
-- [extension] Update DocGuard — CDD Enforcement extension to v0.32.0 (#3489)
-- [extension] Add Multi-Repo Branch Sync extension to community catalog (#3411)
-- chore: release 0.12.14, begin 0.12.15.dev0 development (#3506)
-
-## [0.12.14] - 2026-07-13
-
-### Changed
-
-- [extension] Add Spec Kit Memory extension to community catalog (#3455)
-- Add Test-First Governance preset to community catalog (#3504)
-- Add Autonomous Run Governance preset to community catalog (#3501)
-- fix(workflows): validate command step input/options are mappings (#3262)
-- fix(presets): resolve() honors manifest-declared file: for installed presets (#3351)
-- fix(init): don't block on confirmation for 'init --here' without a TTY (#3236)
-- [extension] Add Quality Gates (Enforcement Layer) extension to community catalog (#3431)
-- fix(integrations): exit cleanly on unbalanced quote in --integration-options (#3457) (#3466)
-- fix(integrations): declare kiro-cli multi-install safe (#3471) (#3485)
-- fix(workflows): fail fan-in step on non-list wait_for instead of crashing (#3482)
-- chore: release 0.12.13, begin 0.12.14.dev0 development (#3498)
-
-## [0.12.13] - 2026-07-13
-
-### Changed
-
-- fix(workflows): fail switch step on non-mapping cases instead of crashing (#3481)
-- Cleanup agent-file-template.md (#2579)
-- fix: mark Kiro integration as multi-install safe (#3472)
-- fix: rewrite extension-relative subdir paths in generated command bodies (#3444)
-- fix(templates): point constitution sync checklist at installed command files (#3418)
-- feat(workflows): make shell step timeout configurable (#3327) (#3328)
-- docs: clarify that release tags keep the leading v prefix (#3463)
-- fix(workflows): don't crash on membership test against a non-iterable (#3448)
-- fix(workflows): if-step validate accepts falsy non-list else (#3264)
-- chore: release 0.12.12, begin 0.12.13.dev0 development (#3490)
-
-## [0.12.12] - 2026-07-13
-
-### Changed
-
-- fix(extensions): set-priority repairs corrupted boolean priority (#3268)
-- fix(presets): set-priority repairs corrupted boolean priority (#3269)
-- fix(workflows): engine loop cap ignores bool max_iterations (#3270)
-- docs(bundles): document --integration on 'bundle update' (#3271)
-- fix(workflows): harden catalog.py against mis-shaped registry & non-string fields (#3375)
-- Add Verify Review Ship extension to community catalog (#3450)
-- fix(bundle): reject file:// / local download_url — catalog URLs are HTTPS-only (#3344)
-- fix(extensions): handle prefix-colliding env vars in _get_env_config (#3350)
-- docs: document copilot skills mode (--skills) and markdown deprecation (#3313)
-- chore: release 0.12.11, begin 0.12.12.dev0 development (#3460)
-
-## [0.12.11] - 2026-07-10
-
-### Changed
-
-- fix(agent-context): discover nested plan.md in scoped layouts (#3024) (#3301)
-- fix(auth): return no matches, not raw ValueError, for a malformed URL (#3437)
-- fix(catalogs): raise catalog error, not raw ValueError, on a malformed URL (#3435)
-- fix(bundler): raise BundlerError, not raw ValueError, on a malformed catalog URL (#3433)
-- chore: add pre-commit config and fix trailing whitespace/end-of-file (#3430)
-- Add EARS Requirements Syntax extension to community catalog (#3407)
-- Add Spec Kit Figma extension to community catalog (#3408)
-- fix(workflows): report validation errors instead of crashing on non-string workflow.yml scalars (#3421)
-- fix(templates): remove self-referencing path in plan-template.md note (#3417)
-- chore: release 0.12.10, begin 0.12.11.dev0 development (#3453)
-
-## [0.12.10] - 2026-07-10
-
-### Changed
-
-- chore(deps): bump astral-sh/setup-uv from 8.2.0 to 8.3.2 (#3439)
-- chore(deps): bump DavidAnson/markdownlint-cli2-action (#3438)
-- fix(templates): correct phase numbering in plan.md (#3416)
-- fix(git-ext): honor explicit -Number 0 in PowerShell branch creation (#3412)
-- docs: add 'spectatui' entry to friends.md (#3362)
-- test: pin interpreter probe so py-template render test passes on Windows (#3428)
-- feat(workflows): make shell step timeout configurable (#3404)
-- fix: find plans in nested spec directories (#3405)
-- feat(templates): add py: lines to command templates' scripts frontmatter (#3403)
-- chore: release 0.12.9, begin 0.12.10.dev0 development (#3426)
-
-## [0.12.9] - 2026-07-09
-
-### Changed
-
-- fix(integrations): skip Windows Store python3 alias stub in resolve_python_interpreter (#3385)
-- fix(integrations): escape control characters in SKILL.md frontmatter (#3399)
-- fix(workflows): apply chained expression filters left-to-right (#3339)
-- fix(scripts): resolve invoke_separator by parse success, not python3 availability (#3304) (#3320)
-- fix(shared-infra): refresh_shared_templates preserves recovered user files (#3378)
-- fix(agents): resolve skill placeholders in Goose (yaml) command output (#3374)
-- fix(bundler): enforce version pin on bundled preset/extension installs (#3377)
-- Update Golden Demo extension to v0.3.0 (#3394)
-- test: isolate integration test home (#3144)
-- chore: release 0.12.8, begin 0.12.9.dev0 development (#3410)
-
-## [0.12.8] - 2026-07-08
-
-### Changed
-
-- [extension] Add LLM Wiki extension to community catalog (#3361)
-- Docs: Document missing CLI flags and integrations (#3182)
-- Docs: Remove Cursor from CLI check list in README (#3184)
-- feat(extensions): port update-agent-context to Python (#3387)
-- fix(scripts): fall through to grep/sed when python3 is a broken stub in feature.json parser (#3312)
-- fix(toml): escape control characters so generated command files parse (#3341)
-- fix(cli): exit cleanly on malformed IPv6 URLs in `extension`/`preset`/`workflow add` (#3369)
-- fix(github-http): return None on malformed GHES port instead of raising (#3379)
-- fix(integrations): guard _sha256 against unreadable managed files (#3376)
-- chore: release 0.12.7, begin 0.12.8.dev0 development (#3398)
-
 ## [0.12.7] - 2026-07-07
 
 ### Changed

LICENSE

@@ -19,3 +19,4 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
+

README.md

@@ -32,6 +32,7 @@
 - [🎯 Experimental Goals](#-experimental-goals)
 - [🔧 Prerequisites](#-prerequisites)
 - [📖 Learn More](#-learn-more)
+- [📋 Detailed Process](#-detailed-process)
 - [💬 Support](#-support)
 - [🙏 Acknowledgements](#-acknowledgements)
 - [📄 License](#-license)
@@ -44,18 +45,12 @@ Spec-Driven Development **flips the script** on traditional software development
 
 ### 1. Install Specify CLI
 
-Requires **[uv](https://docs.astral.sh/uv/)** ([install uv](./docs/install/uv.md)). Replace `vX.Y.Z` with the latest release tag from [Releases](https://github.com/github/spec-kit/releases) — keep the leading `v` (for example, `v0.12.11`, not `0.12.11`):
+Requires **[uv](https://docs.astral.sh/uv/)** ([install uv](./docs/install/uv.md)). Replace `vX.Y.Z` with the latest tag from [Releases](https://github.com/github/spec-kit/releases):
 
 ```bash
 uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@vX.Y.Z
 ```
 
-Prefer installing from PyPI? The `specify-cli` package is also published there:
-
-```bash
-uv tool install specify-cli
-```
-
 See the [Installation Guide](./docs/installation.md) for alternative methods, verification, upgrade, and troubleshooting.
 
 ### 2. Initialize a project
@@ -360,7 +355,294 @@ If you encounter issues with an agent, please open an issue so we can refine the
 ## 📖 Learn More
 
 - **[Complete Spec-Driven Development Methodology](./spec-driven.md)** - Deep dive into the full process
-- **[Quick Start Guide](https://github.github.io/spec-kit/quickstart.html)** - Step-by-step implementation walkthrough
+- **[Detailed Walkthrough](#-detailed-process)** - Step-by-step implementation guide
+
+---
+
+## 📋 Detailed Process
+
+<details>
+<summary>Click to expand the detailed step-by-step walkthrough</summary>
+
+You can use the Specify CLI to bootstrap your project, which will bring in the required artifacts in your environment. Run:
+
+```bash
+specify init <project_name>
+```
+
+Or initialize in the current directory:
+
+```bash
+specify init .
+# or use the --here flag
+specify init --here
+# Skip confirmation when the directory already has files
+specify init . --force
+# or
+specify init --here --force
+```
+
+![Specify CLI bootstrapping a new project in the terminal](./media/specify_cli.gif)
+
+In an interactive terminal, you will be prompted to select the coding agent integration you are using. In non-interactive sessions, such as CI or piped runs, `specify init` defaults to GitHub Copilot unless you pass `--integration`. You can also proactively specify the integration directly in the terminal:
+
+```bash
+specify init <project_name> --integration copilot
+specify init <project_name> --integration gemini
+specify init <project_name> --integration codex
+
+# Or in current directory:
+specify init . --integration copilot
+specify init . --integration codex --integration-options="--skills"
+
+# or use --here flag
+specify init --here --integration copilot
+specify init --here --integration codex --integration-options="--skills"
+
+# Force merge into a non-empty current directory
+specify init . --force --integration copilot
+
+# or
+specify init --here --force --integration copilot
+```
+
+The CLI will check that your selected agent's CLI tool is installed (for integrations that require a CLI), such as Claude Code, Gemini CLI, Qwen Code, opencode, Codex CLI, Qoder CLI, Tabnine CLI, Kiro CLI, Pi Coding Agent, Oh My Pi, Forge, Goose, Mistral Vibe, or ZCode. If you don't have the required tool installed, or you prefer to get the templates without checking for the right tools, use `--ignore-agent-tools` with your command:
+
+```bash
+specify init <project_name> --integration copilot --ignore-agent-tools
+```
+
+### **STEP 1:** Establish project principles
+
+Go to the project folder and run your coding agent. In our example, we're using `claude`.
+
+![Bootstrapping Claude Code environment](./media/bootstrap-claude-code.gif)
+
+You will know that things are configured correctly if you see the `/speckit.constitution`, `/speckit.specify`, `/speckit.plan`, `/speckit.tasks`, and `/speckit.implement` commands available.
+
+The first step should be establishing your project's governing principles using the `/speckit.constitution` command. This helps ensure consistent decision-making throughout all subsequent development phases:
+
+```text
+/speckit.constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements. Include governance for how these principles should guide technical decisions and implementation choices.
+```
+
+This step creates or updates the `.specify/memory/constitution.md` file with your project's foundational guidelines that the coding agent will reference during specification, planning, and implementation phases.
+
+### **STEP 2:** Create project specifications
+
+With your project principles established, you can now create the functional specifications. Use the `/speckit.specify` command and then provide the concrete requirements for the project you want to develop.
+
+> [!IMPORTANT]
+> Be as explicit as possible about *what* you are trying to build and *why*. **Do not focus on the tech stack at this point**.
+
+An example prompt:
+
+```text
+Develop Taskify, a team productivity platform. It should allow users to create projects, add team members,
+assign tasks, comment and move tasks between boards in Kanban style. In this initial phase for this feature,
+let's call it "Create Taskify," let's have multiple users but the users will be declared ahead of time, predefined.
+I want five users in two different categories, one product manager and four engineers. Let's create three
+different sample projects. Let's have the standard Kanban columns for the status of each task, such as "To Do,"
+"In Progress," "In Review," and "Done." There will be no login for this application as this is just the very
+first testing thing to ensure that our basic features are set up. For each task in the UI for a task card,
+you should be able to change the current status of the task between the different columns in the Kanban work board.
+You should be able to leave an unlimited number of comments for a particular card. You should be able to, from that task
+card, assign one of the valid users. When you first launch Taskify, it's going to give you a list of the five users to pick
+from. There will be no password required. When you click on a user, you go into the main view, which displays the list of
+projects. When you click on a project, you open the Kanban board for that project. You're going to see the columns.
+You'll be able to drag and drop cards back and forth between different columns. You will see any cards that are
+assigned to you, the currently logged in user, in a different color from all the other ones, so you can quickly
+see yours. You can edit any comments that you make, but you can't edit comments that other people made. You can
+delete any comments that you made, but you can't delete comments anybody else made.
+```
+
+After this prompt is entered, you should see Claude Code kick off the planning and spec drafting process. Claude Code will also trigger some of the built-in scripts to set up the repository.
+
+Once this step is completed, you should have a new branch created (e.g., `001-create-taskify`), as well as a new specification in the `specs/001-create-taskify` directory.
+
+The produced specification should contain a set of user stories and functional requirements, as defined in the template.
+
+At this stage, your project folder contents should resemble the following:
+
+```text
+.
+├── .specify
+│   ├── memory
+│   │   └── constitution.md
+│   ├── scripts
+│   │   └── bash
+│   │       ├── check-prerequisites.sh
+│   │       ├── common.sh
+│   │       ├── create-new-feature.sh
+│   │       ├── setup-plan.sh
+│   │       └── setup-tasks.sh
+│   └── templates
+│       ├── plan-template.md
+│       ├── spec-template.md
+│       └── tasks-template.md
+└── specs
+    └── 001-create-taskify
+        └── spec.md
+```
+
+### **STEP 3:** Functional specification clarification (required before planning)
+
+With the baseline specification created, you can go ahead and clarify any of the requirements that were not captured properly within the first shot attempt.
+
+You should run the structured clarification workflow **before** creating a technical plan to reduce rework downstream.
+
+Preferred order:
+
+1. Use `/speckit.clarify` (structured) – sequential, coverage-based questioning that records answers in a Clarifications section.
+2. Optionally follow up with ad-hoc free-form refinement if something still feels vague.
+
+If you intentionally want to skip clarification (e.g., spike or exploratory prototype), explicitly state that so the agent doesn't block on missing clarifications.
+
+Example free-form refinement prompt (after `/speckit.clarify` if still needed):
+
+```text
+For each sample project or project that you create there should be a variable number of tasks between 5 and 15
+tasks for each one randomly distributed into different states of completion. Make sure that there's at least
+one task in each stage of completion.
+```
+
+You should also ask Claude Code to validate the **Review & Acceptance Checklist**, checking off the things that are validated/pass the requirements, and leave the ones that are not unchecked. The following prompt can be used:
+
+```text
+Read the review and acceptance checklist, and check off each item in the checklist if the feature spec meets the criteria. Leave it empty if it does not.
+```
+
+It's important to use the interaction with Claude Code as an opportunity to clarify and ask questions around the specification - **do not treat its first attempt as final**.
+
+### **STEP 4:** Generate a plan
+
+You can now be specific about the tech stack and other technical requirements. You can use the `/speckit.plan` command that is built into the project template with a prompt like this:
+
+```text
+We are going to generate this using .NET Aspire, using Postgres as the database. The frontend should use
+Blazor server with drag-and-drop task boards, real-time updates. There should be a REST API created with a projects API,
+tasks API, and a notifications API.
+```
+
+The output of this step will include a number of implementation detail documents, with your directory tree resembling this:
+
+```text
+.
+├── CLAUDE.md
+├── .specify
+│   ├── memory
+│   │   └── constitution.md
+│   ├── scripts
+│   │   └── bash
+│   │       ├── check-prerequisites.sh
+│   │       ├── common.sh
+│   │       ├── create-new-feature.sh
+│   │       ├── setup-plan.sh
+│   │       └── setup-tasks.sh
+│   └── templates
+│       ├── CLAUDE-template.md
+│       ├── plan-template.md
+│       ├── spec-template.md
+│       └── tasks-template.md
+└── specs
+    └── 001-create-taskify
+        ├── contracts
+        │   ├── api-spec.json
+        │   └── signalr-spec.md
+        ├── data-model.md
+        ├── plan.md
+        ├── quickstart.md
+        ├── research.md
+        └── spec.md
+```
+
+Check the `research.md` document to ensure that the right tech stack is used, based on your instructions. You can ask Claude Code to refine it if any of the components stand out, or even have it check the locally-installed version of the platform/framework you want to use (e.g., .NET).
+
+Additionally, you might want to ask Claude Code to research details about the chosen tech stack if it's something that is rapidly changing (e.g., .NET Aspire, JS frameworks), with a prompt like this:
+
+```text
+I want you to go through the implementation plan and implementation details, looking for areas that could
+benefit from additional research as .NET Aspire is a rapidly changing library. For those areas that you identify that
+require further research, I want you to update the research document with additional details about the specific
+versions that we are going to be using in this Taskify application and spawn parallel research tasks to clarify
+any details using research from the web.
+```
+
+During this process, you might find that Claude Code gets stuck researching the wrong thing - you can help nudge it in the right direction with a prompt like this:
+
+```text
+I think we need to break this down into a series of steps. First, identify a list of tasks
+that you would need to do during implementation that you're not sure of or would benefit
+from further research. Write down a list of those tasks. And then for each one of these tasks,
+I want you to spin up a separate research task so that the net results is we are researching
+all of those very specific tasks in parallel. What I saw you doing was it looks like you were
+researching .NET Aspire in general and I don't think that's gonna do much for us in this case.
+That's way too untargeted research. The research needs to help you solve a specific targeted question.
+```
+
+> [!NOTE]
+> Claude Code might be over-eager and add components that you did not ask for. Ask it to clarify the rationale and the source of the change.
+
+### **STEP 5:** Have Claude Code validate the plan
+
+With the plan in place, you should have Claude Code run through it to make sure that there are no missing pieces. You can use a prompt like this:
+
+```text
+Now I want you to go and audit the implementation plan and the implementation detail files.
+Read through it with an eye on determining whether or not there is a sequence of tasks that you need
+to be doing that are obvious from reading this. Because I don't know if there's enough here. For example,
+when I look at the core implementation, it would be useful to reference the appropriate places in the implementation
+details where it can find the information as it walks through each step in the core implementation or in the refinement.
+```
+
+This helps refine the implementation plan and helps you avoid potential blind spots that Claude Code missed in its planning cycle. Once the initial refinement pass is complete, ask Claude Code to go through the checklist once more before you can get to the implementation.
+
+You can also ask Claude Code (if you have the [GitHub CLI](https://docs.github.com/en/github-cli/github-cli) installed) to go ahead and create a pull request from your current branch to `main` with a detailed description, to make sure that the effort is properly tracked.
+
+> [!NOTE]
+> Before you have the agent implement it, it's also worth prompting Claude Code to cross-check the details to see if there are any over-engineered pieces (remember - it can be over-eager). If over-engineered components or decisions exist, you can ask Claude Code to resolve them. Ensure that Claude Code follows the constitution in `.specify/memory/constitution.md` as the foundational piece that it must adhere to when establishing the plan.
+
+### **STEP 6:** Generate task breakdown with /speckit.tasks
+
+With the implementation plan validated, you can now break down the plan into specific, actionable tasks that can be executed in the correct order. Use the `/speckit.tasks` command to automatically generate a detailed task breakdown from your implementation plan:
+
+```text
+/speckit.tasks
+```
+
+This step creates a `tasks.md` file in your feature specification directory that contains:
+
+- **Task breakdown organized by user story** - Each user story becomes a separate implementation phase with its own set of tasks
+- **Dependency management** - Tasks are ordered to respect dependencies between components (e.g., models before services, services before endpoints)
+- **Parallel execution markers** - Tasks that can run in parallel are marked with `[P]` to optimize development workflow
+- **File path specifications** - Each task includes the exact file paths where implementation should occur
+- **Test-driven development structure** - If tests are requested, test tasks are included and ordered to be written before implementation
+- **Checkpoint validation** - Each user story phase includes checkpoints to validate independent functionality
+
+The generated tasks.md provides a clear roadmap for the `/speckit.implement` command, ensuring systematic implementation that maintains code quality and allows for incremental delivery of user stories.
+
+### **STEP 7:** Implementation
+
+Once ready, use the `/speckit.implement` command to execute your implementation plan:
+
+```text
+/speckit.implement
+```
+
+The `/speckit.implement` command will:
+
+- Validate that all prerequisites are in place (constitution, spec, plan, and tasks)
+- Parse the task breakdown from `tasks.md`
+- Execute tasks in the correct order, respecting dependencies and parallel execution markers
+- Follow the TDD approach defined in your task plan
+- Provide progress updates and handle errors appropriately
+
+> [!IMPORTANT]
+> The coding agent will execute local CLI commands (such as `dotnet`, `npm`, etc.) - make sure you have the required tools installed on your machine.
+
+Once the implementation is complete, test the application and resolve any runtime errors that may not be visible in CLI logs (e.g., browser console errors). You can copy and paste such errors back to your coding agent for resolution.
+
+</details>
 
 ---
 

docs/.gitignore

@@ -6,3 +6,4 @@ obj/
 # Temporary files
 *.tmp
 *.log
+

docs/community/extensions.md

@@ -51,17 +51,14 @@ The following community-contributed extensions are available in [`catalog.commun
 | Confluence Extension | Create a doc in Confluence summarizing the specifications and planning files | `integration` | Read+Write | [spec-kit-confluence](https://github.com/aaronrsun/spec-kit-confluence) |
 | Cost Tracker | Track real LLM dollar cost across SDD workflows — per-feature budgets, per-integration comparison, and finance-ready exports | `visibility` | Read+Write | [spec-kit-cost](https://github.com/Quratulain-bilal/spec-kit-cost) |
 | Data Model Diagram | Generates Mermaid ER diagrams from Spec Kit data models after planning | `docs` | Read+Write | [spec-kit-data-model-diagram](https://github.com/benizzio/spec-kit-data-model-diagram) |
-| DocGuard — CDD Enforcement | The only doc-integrity engine with an MCP server, SARIF/JUnit output, and a deterministic zero-LLM core. Validates, scores, and traces documentation against code — 27 validators, stable finding codes, adoption baseline for legacy repos, compliance-evidence reports, GitHub Action with PR annotations, spec-kit hooks. Pure Node.js, one pinned dep. | `docs` | Read+Write | [spec-kit-docguard](https://github.com/raccioly/docguard) |
-| Dotdog | Import GitHub Spec Kit artifacts into local knowledge graphs for validation, analysis, search, and MCP queries. | `docs` | Read+Write | [dotdog](https://github.com/specdog/dotdog) |
-| EARS Requirements Syntax | Author, lint, and convert requirements using EARS - the five industry-standard sentence patterns for unambiguous, testable requirements | `docs` | Read+Write | [spec-kit-ears](https://github.com/dhruv-15-03/spec-kit-ears) |
+| DocGuard — CDD Enforcement | The only doc-integrity engine with an MCP server, SARIF output, and a deterministic zero-LLM core. Validates, scores, and traces documentation against code — 24 validators, stable finding codes, GitHub Action with PR annotations, spec-kit hooks. Pure Node.js, one pinned dep. | `docs` | Read+Write | [spec-kit-docguard](https://github.com/raccioly/docguard) |
 | Extensify | Create and validate extensions and extension catalogs | `process` | Read+Write | [extensify](https://github.com/mnriem/spec-kit-extensions/tree/main/extensify) |
-| Figma Starter | Turns a Figma section's screens into per-screen spec.md files, an app-level user-stories.md, and a build-order.md, then hands off to /speckit.specify | `integration` | Read+Write | [spec-kit-figma-starter](https://github.com/wavemaker/spec-kit-figma-starter) |
 | Fix Findings | Automated analyze-fix-reanalyze loop that resolves spec findings until clean | `code` | Read+Write | [spec-kit-fix-findings](https://github.com/Quratulain-bilal/spec-kit-fix-findings) |
 | FixIt Extension | Spec-aware bug fixing — maps bugs to spec artifacts, proposes a plan, applies minimal changes | `code` | Read+Write | [spec-kit-fixit](https://github.com/speckit-community/spec-kit-fixit) |
 | Fleet Orchestrator | Orchestrate a full feature lifecycle with human-in-the-loop gates across all SpecKit phases | `process` | Read+Write | [spec-kit-fleet](https://github.com/sharathsatish/spec-kit-fleet) |
 | GitHub Issues Integration 1 | Generate spec artifacts from GitHub Issues - import issues, sync updates, and maintain bidirectional traceability | `integration` | Read+Write | [spec-kit-github-issues](https://github.com/Fatima367/spec-kit-github-issues) |
 | GitHub Issues Integration 2 | Creates and syncs local specs from an existing GitHub issue | `integration` | Read+Write | [spec-kit-issue](https://github.com/aaronrsun/spec-kit-issue) |
-| Golden Demo | Deterministic behavioral drift oracle. Extracts acceptance criteria, generates fuzz test vectors (seed=42), compares golden Python implementations against real code in any language. CI/CD gatekeeper with warn/strict modes. | `docs` | Read+Write | [spec-kit-golden-demo](https://github.com/jasstt/spec-kit-golden-demo) |
+| Golden Demo | Extracts acceptance criteria from specs, builds test vectors, and produces a behavioral drift report — complementary to Architecture Guard and CDD | `docs` | Read+Write | [spec-kit-golden-demo](https://github.com/jasstt/spec-kit-golden-demo) |
 | Improve Extension | Audits any codebase as a senior advisor and writes prioritized, self-contained spec prompts under specs/ that the spec-kit lifecycle can process | `process` | Read+Write | [spec-kit-improve](https://github.com/d0whc3r/spec-kit-improve) |
 | Intake | Normalize PRD, design, HTML SSOT, and test-case evidence into SDD-ready intake artifacts. | `docs` | Read+Write | [spec-kit-intake](https://github.com/bigsmartben/spec-kit-intake) |
 | Intelligent Agent Orchestrator | Cross-catalog agent discovery and intelligent prompt-to-command routing | `process` | Read+Write | [spec-kit-orchestrator](https://github.com/pragya247/spec-kit-orchestrator) |
@@ -70,7 +67,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Jira Integration (Sync Engine) | Idempotent, drift-aware, fail-closed reconcile engine mirroring spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase) | `integration` | Read+Write | [spec-kit-jira-sync](https://github.com/ashbrener/spec-kit-jira-sync) |
 | Learning Extension | Generate educational guides from implementations and enhance clarifications with mentoring context | `docs` | Read+Write | [spec-kit-learn](https://github.com/imviancagrace/spec-kit-learn) |
 | Linear Integration | Mirror spec-kit feature directories into Linear (filesystem → Linear, reconcile-based, unidirectional). | `integration` | Read+Write | [spec-kit-linear-sync](https://github.com/ashbrener/spec-kit-linear-sync) |
-| LLM Wiki | LLM-maintained compounding project wiki: source ingestion, cited answers, and consistency linting | `docs` | Read+Write | [spec-kit-wiki](https://github.com/formin/spec-kit-wiki) |
 | Loop Engineering | Engineer safe autonomous agent loops for spec-driven development: a maker/checker split, externalized loop state, and stay-the-engineer guardrails against comprehension debt and cognitive surrender | `process` | Read+Write | [spec-kit-loop](https://github.com/formin/spec-kit-loop) |
 | MAQA — Multi-Agent & Quality Assurance | Coordinator → feature → QA agent workflow with parallel worktree-based implementation. Language-agnostic. Auto-detects installed board plugins. Optional CI gate. | `process` | Read+Write | [spec-kit-maqa-ext](https://github.com/GenieRobot/spec-kit-maqa-ext) |
 | MAQA Azure DevOps Integration | Azure DevOps Boards integration for MAQA — syncs User Stories and Task children as features progress | `integration` | Read+Write | [spec-kit-maqa-azure-devops](https://github.com/GenieRobot/spec-kit-maqa-azure-devops) |
@@ -86,14 +82,12 @@ The following community-contributed extensions are available in [`catalog.commun
 | MemoryLint | Evidence-driven instruction drift checker: audits agent memory files for boundary, reality, conflict, and redundancy drift. | `process` | Read+Write | [memorylint](https://github.com/RbBtSn0w/spec-kit-extensions/tree/main/memorylint) |
 | Microsoft 365 Integration | Fetch Teams messages, meeting transcripts, and SharePoint/OneDrive files as local Markdown for spec generation | `integration` | Read+Write | [spec-kit-m365](https://github.com/BenBtg/spec-kit-m365) |
 | Multi-Model Review | Cross-model Spec Kit handoffs for spec authoring, implementation routing, and review. | `process` | Read+Write | [multi-model-review](https://github.com/formin/multi-model-review) |
-| Multi-Repo Branch Sync | Creates the feature branch in affected sub-repositories and git submodules via plan/tasks hooks | `process` | Read+Write | [multi-repo-sync](https://github.com/fyloss/spec-kit-multi-repo-sync) |
 | Multi-Sites Spec Kit | Multi-site aware specify command with per-site spec folders, auto-increment, and Drupal support | `process` | Read+Write | [spec-kit-multi-sites](https://github.com/teeyo/spec-kit-multi-sites) |
 | .NET Framework to Modern .NET Migration | Orchestrate end-to-end .NET Framework to modern .NET migration across 7 phases, with SDD lifecycle integration | `process` | Read+Write | [spec-kit-fx-to-net](https://github.com/RogerBestMsft/spec-kit-FxToNet) |
 | Onboard | Contextual onboarding and progressive growth for developers new to spec-kit projects. Explains specs, maps dependencies, validates understanding, and guides the next step | `process` | Read+Write | [spec-kit-onboard](https://github.com/dmux/spec-kit-onboard) |
 | Optimize | Audit and optimize AI governance for context efficiency — token budgets, rule health, interpretability, compression, coherence, and echo detection | `process` | Read+Write | [spec-kit-optimize](https://github.com/sakitA/spec-kit-optimize) |
 | Orchestration Task Context Management | Adds subagent work-unit orchestration to generated Spec Kit task files | `process` | Read+Write | [spec-kit-orchestration-task-context-management](https://github.com/benizzio/spec-kit-orchestration-task-context-management) |
 | OWASP LLM Threat Model | OWASP Top 10 for LLM Applications 2025 threat analysis on agent artifacts | `code` | Read-only | [spec-kit-threatmodel](https://github.com/NaviaSamal/spec-kit-threatmodel) |
-| PatchWarden Evidence Pack | Map Spec Kit tasks into a guarded PatchWarden Goal and export bounded, traceable evidence for an accepted lineage. | `process` | Read+Write | [spec-kit-patchwarden](https://github.com/jiezeng2004-design/spec-kit-patchwarden) |
 | Plan Review Gate | Require spec.md and plan.md to be merged via MR/PR before allowing task generation | `process` | Read-only | [spec-kit-plan-review-gate](https://github.com/luno/spec-kit-plan-review-gate) |
 | PR Bridge | Auto-generate pull request descriptions, checklists, and summaries from spec artifacts | `process` | Read-only | [spec-kit-pr-bridge-](https://github.com/Quratulain-bilal/spec-kit-pr-bridge-) |
 | Presetify | Create and validate presets and preset catalogs | `process` | Read+Write | [presetify](https://github.com/mnriem/spec-kit-extensions/tree/main/presetify) |
@@ -102,7 +96,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Project Health Check | Diagnose a Spec Kit project and report health issues across structure, agents, features, scripts, extensions, and git | `visibility` | Read-only | [spec-kit-doctor](https://github.com/KhawarHabibKhan/spec-kit-doctor) |
 | Project Status | Show current SDD workflow progress — active feature, artifact status, task completion, workflow phase, and extensions summary | `visibility` | Read-only | [spec-kit-status](https://github.com/KhawarHabibKhan/spec-kit-status) |
 | QA Testing Extension | Systematic QA testing with browser-driven or CLI-based validation of acceptance criteria from spec | `code` | Read-only | [spec-kit-qa](https://github.com/arunt14/spec-kit-qa) |
-| Quality Gates (Enforcement Layer) | Deterministic quality enforcement for Spec Kit across agent hooks, git checks, and CI pipelines with one policy file and one verify entrypoint for identical results at every boundary. | `process` | Read+Write | [spec-gates](https://github.com/schwichtgit/spec-gates) |
 | RAG Azure Builder | Spec Kit extension for onboarding and operating an Azure RAG stack with guided workflows. | `process` | Read+Write | [spec-kit-extension-rag-azure-builder](https://github.com/Sertxito/spec-kit-extension-rag-azure-builder) |
 | Ralph Loop | Autonomous implementation loop using AI agent CLI | `code` | Read+Write | [spec-kit-ralph](https://github.com/Rubiss-Projects/spec-kit-ralph) |
 | Reconcile Extension | Reconcile implementation drift by surgically updating feature artifacts. | `docs` | Read+Write | [spec-kit-reconcile](https://github.com/stn1slv/spec-kit-reconcile) |
@@ -123,8 +116,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Spec Critique Extension | Dual-lens critical review of spec and plan from product strategy and engineering risk perspectives | `docs` | Read-only | [spec-kit-critique](https://github.com/arunt14/spec-kit-critique) |
 | Spec Diagram | Auto-generate Mermaid diagrams of SDD workflow state, feature progress, and task dependencies | `visibility` | Read-only | [spec-kit-diagram-](https://github.com/Quratulain-bilal/spec-kit-diagram-) |
 | Spec Kit Discovery Extension | Run technical discovery commands for feasibility, technology selection, scenario-specific technical decisions, legacy codebase assessment, implementation understanding, and proof-of-concept validation | `process` | Read+Write | [spec-kit-discovery](https://github.com/bigsmartben/spec-kit-discovery) |
-| Spec Kit Figma | Agent-agnostic SpecKit extension that grounds spec, plan & task generation in Figma design context — REST + optional MCP, single/mono/multi-repo, macOS/Linux/Windows. | `integration` | Read+Write | [spec-kit-figma](https://github.com/Fyloss/spec-kit-figma) |
-| Spec Kit Memory | Recalls prior specs and decisions from configurable memory tools (e.g. memsearch) before SDLC stages, so planning and specification start from what the project already knows | `docs` | Read+Write | [spec-kit-memory](https://github.com/zaytsevand/spec-kit-memory) |
 | Spec Kit Preview | Generate evidence-backed low, mid, or high fidelity previews from Spec Kit artifacts as Markdown or self-contained HTML | `docs` | Read+Write | [spec-kit-preview](https://github.com/bigsmartben/spec-kit-preview) |
 | Spec Kit Schedule | Optimal multi-agent task scheduling via CP-SAT — DAG precedence, hallucination-aware caps, file-conflict avoidance, stochastic durations, replanning, and interactive HTML output | `process` | Read+Write | [spec-kit-schedule](https://github.com/jfranc38/spec-kit-schedule) |
 | Spec Kit TLDR | Render a feature's spec.md / plan.md into a review-oriented TLDR (self-contained HTML dashboard + PR-native Markdown) that surfaces risks for faster PR review. | `visibility` | Read+Write | [speckit-tldr](https://github.com/qurore/speckit-tldr) |
@@ -136,7 +127,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Spec Sync | Detect and resolve drift between specs and implementation. AI-assisted resolution with human approval | `docs` | Read+Write | [spec-kit-sync](https://github.com/bgervin/spec-kit-sync) |
 | Spec Trace | Build a requirement → test traceability matrix from spec.md and the test suite — surface untested requirements and orphan tests | `code` | Read+Write | [spec-kit-trace](https://github.com/Quratulain-bilal/spec-kit-trace) |
 | Spec Validate | Comprehension validation, review gating, and approval state for spec-kit artifacts — staged quizzes, peer review SLA, and a hard gate before /speckit.implement | `process` | Read+Write | [spec-kit-spec-validate](https://github.com/aeltayeb/spec-kit-spec-validate) |
-| Spec-Kit BDD | ATDD/BDD extension: convert specs to Gherkin scenarios, scaffold step definitions, and verify acceptance test coverage | `process` | Read+Write | [spec-kit-bdd](https://github.com/RSginer/spec-kit-bdd) |
 | Spec2Cloud | Spec-driven workflow tuned for shipping to Azure | `process` | Read+Write | [spec2cloud](https://github.com/Azure-Samples/Spec2Cloud) |
 | SpecKit Companion | Live spec-driven progress — lifecycle capture, status, resume, and a turbo pipeline profile | `visibility` | Read+Write | [speckit-companion](https://github.com/alfredoperez/speckit-companion) |
 | SpecTest | Auto-generate test scaffolds from spec criteria, map coverage, and find untested requirements | `code` | Read+Write | [spec-kit-spectest](https://github.com/Quratulain-bilal/spec-kit-spectest) |
@@ -155,7 +145,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Token Economy | Token routing, measured savings, and context audit workflows | `process` | Read+Write | [spec-kit-token-economy](https://github.com/formin/spec-kit-token-economy) |
 | V-Model Extension Pack | Enforces V-Model paired generation of development specs and test specs with full traceability | `docs` | Read+Write | [spec-kit-v-model](https://github.com/leocamello/spec-kit-v-model) |
 | Verify Extension | Post-implementation quality gate that validates implemented code against specification artifacts | `code` | Read-only | [spec-kit-verify](https://github.com/ismaelJimenez/spec-kit-verify) |
-| Verify Review Ship | Adds post-implementation verify, review, and ship readiness gates to Spec Kit workflows | `process` | Read-only | [spec-kit-verify-review-ship](https://github.com/cadugevaerd/spec-kit-verify-review-ship) |
 | Verify Tasks Extension | Detect phantom completions: tasks marked [X] in tasks.md with no real implementation | `code` | Read-only | [spec-kit-verify-tasks](https://github.com/datastone-inc/spec-kit-verify-tasks) |
 | Version Guard | Verify tech stack versions against live npm registries before planning and implementation | `process` | Read-only | [spec-kit-version-guard](https://github.com/KevinBrown5280/spec-kit-version-guard) |
 | What-if Analysis | Preview the downstream impact (complexity, effort, tasks, risks) of requirement changes before committing to them | `visibility` | Read-only | [spec-kit-whatif](https://github.com/DevAbdullah90/spec-kit-whatif) |

docs/community/friends.md

@@ -14,5 +14,3 @@ Community projects that extend, visualize, or build on Spec Kit:
 - **[SpecKit Companion](https://marketplace.visualstudio.com/items?itemName=alfredoperez.speckit-companion)** — A VS Code extension that brings a visual GUI to Spec Kit. Browse specs in a rich markdown viewer with clickable file references, create specifications with image attachments, comment and refine each step inline (GitHub-style review), track your progress through the SDD workflow with a visual phase stepper, and manage steering documents like constitutions and templates.
 
 - **[cc-spec-kit](https://github.com/speckit-community/cc-spec-kit)** — Community-maintained plugin for Claude Code and GitHub Copilot CLI that installs Spec Kit skills via the plugin marketplace.
-
-- **[spectatui](https://github.com/tinesoft/spectatui)** — A terminal UI (TUI) dashboard for Spec Kit that lets you track features, manage specifications, integrations, presets, workflows, and extensions, and monitor AI agent workflows. Attach to existing AI sessions or launch new ones from your terminal. Keyboard and mouse support. Light/dark theme support. Customizable and performance-oriented. Requires the `specify` CLI in your PATH.

docs/community/overview.md

@@ -4,7 +4,7 @@ The Spec Kit community builds extensions, presets, bundles, walkthroughs, and co
 
 ## Extensions
 
-Extensions add new capabilities to Spec Kit — domain-specific commands, external tool integrations, quality gates, and more. Over 130 community extensions are available from 70+ authors, covering everything from accessibility governance to multi-agent orchestration.
+Extensions add new capabilities to Spec Kit — domain-specific commands, external tool integrations, quality gates, and more. Over 90 community extensions are available from 50+ authors, covering everything from accessibility governance to multi-agent orchestration.
 
 [Browse community extensions →](extensions.md)
 

docs/community/presets.md

@@ -11,7 +11,6 @@ The following community-contributed presets customize how Spec Kit behaves — o
 | Agent Parity Governance | Adds shared-guidance parity, audit-ready Spec-Kit run evidence, and agent-neutral model-routing guidance across a project's declared AI-agent instruction surfaces so agent guidance does not drift. | 6 templates, 3 commands | — | [spec-kit-preset-agent-parity-governance](https://github.com/hindermath/spec-kit-preset-agent-parity-governance) |
 | AIDE In-Place Migration | Adapts the AIDE extension workflow for in-place technology migrations (X → Y pattern) — adds migration objectives, verification gates, knowledge documents, and behavioral equivalence criteria | 2 templates, 8 commands | AIDE extension | [spec-kit-presets](https://github.com/mnriem/spec-kit-presets) |
 | Architecture Governance | Adds secure software architecture, STRIDE+CAPEC threat modeling, arc42 security cross-cutting concepts, S-ADRs, Zero Trust applicability, OWASP SAMM governance, BSI C3A cloud autonomy, BSI C5 cloud compliance assurance, and audit-ready Spec Kit run evidence | 13 templates, 3 commands | — | [spec-kit-preset-architecture-governance](https://github.com/hindermath/spec-kit-preset-architecture-governance) |
-| Autonomous Run Governance | Adds permission-bounded, evidence-first governance for autonomous Spec Kit delivery, convergence, resume, closeout, and retrospective learning. | 12 templates, 2 commands, 2 scripts | — | [spec-kit-preset-autonomous-run-governance](https://github.com/hindermath/spec-kit-preset-autonomous-run-governance) |
 | Canon Core | Adapts original Spec Kit workflow to work together with Canon extension | 2 templates, 8 commands | — | [spec-kit-canon](https://github.com/maximiliamus/spec-kit-canon) |
 | Claude AskUserQuestion | Upgrades `/speckit.clarify` and `/speckit.checklist` on Claude Code from Markdown-table prompts to the native AskUserQuestion picker, with a recommended option and reasoning on every question | 2 commands | — | [spec-kit-preset-claude-ask-questions](https://github.com/0xrafasec/spec-kit-preset-claude-ask-questions) |
 | Command Density | Compacts the nine core Spec Kit command prompts while preserving scripts, handoffs, placeholders, hook output blocks, and rule structure | 9 commands | — | [spec-kit-preset-command-density](https://github.com/Xopoko/spec-kit-preset-command-density) |
@@ -29,7 +28,6 @@ The following community-contributed presets customize how Spec Kit behaves — o
 | SicarioSpec Core | Baseline secure-by-default Spec Kit governance profile. | 5 templates | — | [sicario-spec](https://github.com/dfirs1car1o/sicario-spec) |
 | Spec2Cloud | Spec-driven workflow tuned for shipping to Azure: spec → plan → tasks → implement → deploy | 5 templates, 8 commands | — | [spec2cloud](https://github.com/Azure-Samples/Spec2Cloud) |
 | Table of Contents Navigation | Adds a navigable Table of Contents to generated spec.md, plan.md, and tasks.md documents | 3 templates, 3 commands | — | [spec-kit-preset-toc-navigation](https://github.com/Quratulain-bilal/spec-kit-preset-toc-navigation) |
-| Test-First Governance | Governs TDD with coverage-complete BDD/ATDD Gherkin scenarios, explicit suite ownership, professional test reports, traceability, and risk-based quality gates. | 10 templates, 8 commands | — | [spec-kit-preset-test-first-governance](https://github.com/ka-zo/spec-kit-preset-test-first-governance) |
 | VS Code Ask Questions | Enhances the clarify command to use `vscode/askQuestions` for batched interactive questioning. | 1 command | — | [spec-kit-presets](https://github.com/fdcastel/spec-kit-presets) |
 | Workflow Preset | Behavior-first specification, design artifacts, and agent-native handoff orchestration — adds requirement-phase behavior drafts, formal BDD/UIF/behavior contracts, optional design artifacts, and scoped implementation handoffs with Core Agent, Vertical Planner Agent, and Worker Agent modes | 22 templates, 8 commands | — | [spec-kit-workflow-preset](https://github.com/bigsmartben/spec-kit-workflow-preset) |
 

docs/index.md

@@ -2,9 +2,9 @@
 
 # GitHub Spec Kit
 
-**Spec-Driven Development or your own process — step by step or as an automated workflow.**
+**Define what to build before building it — with any AI coding agent.**
 
-Spec Kit is an extensible, intent-driven harness that pushes any coding agent beyond code, guiding it across your SDLC or any business process. Use it for [Spec-Driven Development](concepts/sdd.md) (SDD), where you describe _what_ to build and refine it through structured phases. Run it step by step, automate it end to end, or shape a process of your own, keeping intent at the center.
+Spec Kit is a toolkit for [Spec-Driven Development](concepts/sdd.md) (SDD), a methodology that puts specifications at the center of AI-assisted software development. Instead of jumping straight to code, you describe _what_ to build, refine it through structured phases, and let your AI coding agent implement it.
 
 <a href="installation.md" class="btn btn-primary btn-lg">Install Spec Kit</a>&nbsp;
 <a href="quickstart.md" class="btn btn-outline-primary btn-lg">Quick Start</a>
@@ -31,9 +31,9 @@ Define what to build before building it. Rich templates, quality checklists, and
 
 ### Use any coding agent
 
-<span class="pillar-stat">35 integrations</span> — Copilot, Gemini, Codex, Kilo Code, Zed, Claude, Forge, Kiro, and more. Switch freely between agents with a single command. No lock-in.
+<span class="pillar-stat">30+ integrations</span> — Copilot, Gemini, Codex, Kilo Code, Zed, Claude, Forge, Kiro, and more. Switch freely between agents with a single command. No lock-in.
 
-Run `specify init` with your agent of choice and Spec Kit sets up the right command files and directory structures automatically. If your agent isn't listed, the `generic` integration is an escape hatch for any tool.
+Run `specify init` with your agent of choice and Spec Kit sets up the right command files, context rules, and directory structures automatically. If your agent isn't listed, the `generic` integration is an escape hatch for any tool.
 
 <a href="reference/integrations.md" class="pillar-link">See all integrations →</a>
 
@@ -43,21 +43,17 @@ Run `specify init` with your agent of choice and Spec Kit sets up the right comm
 
 ### Make it your own
 
-<span class="pillar-stat">138 community extensions</span> (70+ authors), <span class="pillar-stat">25 presets</span>, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, and package it all up as bundles you can share — or replace the process entirely. The process itself lives in these building blocks, so you're never locked to SDD, or even to software.
+<span class="pillar-stat">105 community extensions</span> (60+ authors), <span class="pillar-stat">22 presets</span>, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, or replace it entirely. Build and publish your own.
 
-Including entirely different processes:
+Including entirely different SDD processes:
 
 - **AIDE** — 7-step AI-driven engineering lifecycle
 - **Canon** — baseline-driven workflows (spec-first, code-first, spec-drift)
 - **Product Forge** — product-management-oriented SDD
 - **FX→.NET** — end-to-end .NET Framework migration across 7 phases
 - **MAQA** — multi-agent orchestration with quality assurance gates
-- **Fiction Book Writing** — novels and long-form fiction, from story bible to submission
 
-<a href="reference/presets.md" class="pillar-link">Presets →</a>&nbsp;&nbsp;
-<a href="reference/extensions.md" class="pillar-link">Extensions →</a>&nbsp;&nbsp;
-<a href="reference/workflows.md" class="pillar-link">Workflows →</a>&nbsp;&nbsp;
-<a href="reference/bundles.md" class="pillar-link">Bundles →</a>
+<a href="community/presets.md" class="pillar-link">Browse community presets →</a>
 
 </div>
 
@@ -65,12 +61,12 @@ Including entirely different processes:
 
 ### Integrate into your organization
 
-Works offline, behind firewalls, and on **Windows, macOS, and Linux**. Host your own catalogs to curate what integrations, extensions, presets, workflows, and bundles your organization discovers and recommends.
+Works offline, behind firewalls, and on **Windows, macOS, and Linux**. Host your own extension and preset catalogs so your organization controls what gets installed.
 
 Community extensions like CI Guard and Architecture Guard add compliance gates and governance that fit the way your team already works.
 
-<a href="install/air-gapped.md" class="pillar-link">Enterprise / Air-Gapped →</a>&nbsp;&nbsp;
-<a href="reference/overview.md" class="pillar-link">Reference →</a>
+<a href="installation.md" class="pillar-link">Installation guide →</a>&nbsp;&nbsp;
+<a href="reference/extensions.md" class="pillar-link">Extensions reference →</a>
 
 </div>
 
@@ -82,31 +78,31 @@ Community extensions like CI Guard and Architecture Guard add compliance gates a
 
 ## Built by the community
 
-**240+ contributors** power the Spec Kit ecosystem — from core integrations to entirely new processes. Anyone can create and publish an extension, preset, or workflow.
+**200+ contributors** power the Spec Kit ecosystem — from core integrations to entirely new development processes. Anyone can create and publish an extension, preset, or workflow.
 
 <div class="stats-grid">
   <div class="stat-item">
-    <span class="stat-number">121K+</span>
+    <span class="stat-number">106K+</span>
     <span class="stat-label">GitHub stars</span>
   </div>
   <div class="stat-item">
-    <span class="stat-number">240+</span>
+    <span class="stat-number">200+</span>
     <span class="stat-label">Contributors</span>
   </div>
   <div class="stat-item">
-    <span class="stat-number">35</span>
+    <span class="stat-number">30+</span>
     <span class="stat-label">Integrations</span>
   </div>
   <div class="stat-item">
-    <span class="stat-number">138</span>
+    <span class="stat-number">105</span>
     <span class="stat-label">Extensions</span>
   </div>
   <div class="stat-item">
-    <span class="stat-number">25</span>
+    <span class="stat-number">22</span>
     <span class="stat-label">Presets</span>
   </div>
   <div class="stat-item">
-    <span class="stat-number">6</span>
+    <span class="stat-number">4</span>
     <span class="stat-label">Friends projects</span>
   </div>
 </div>
@@ -147,7 +143,7 @@ Community extensions like CI Guard and Architecture Guard add compliance gates a
 <div class="footer-cta">
 
 ```bash
-uv tool install specify-cli
+uvx --from git+https://github.com/github/spec-kit.git
 specify init my-project --integration copilot
 ```
 
@@ -155,4 +151,4 @@ Ready to start? Follow the [Quick Start Guide](quickstart.md).
 
 </div>
 
-<p class="text-end small text-body-secondary">Last updated: July 16, 2026</p>
+<p class="text-end small text-body-secondary">Last updated: May 27, 2026</p>

docs/install/one-time.md

@@ -11,8 +11,7 @@ If you want to try Spec Kit without installing it permanently, use `uvx` to run
 # Create a new project (latest from main)
 uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME>
 
-# Or target a specific release (replace vX.Y.Z with a tag from Releases;
-# keep the leading v, e.g. v0.12.11 not 0.12.11)
+# Or target a specific release (replace vX.Y.Z with a tag from Releases)
 uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <PROJECT_NAME>
 
 # Initialize in the current directory

docs/install/pipx.md

@@ -7,8 +7,7 @@
 Pin a specific release tag for stability (check [Releases](https://github.com/github/spec-kit/releases) for the latest):
 
 ```bash
-# Install a specific stable release (recommended — replace vX.Y.Z with the
-# latest tag, keeping the leading v, e.g. v0.12.11 not 0.12.11)
+# Install a specific stable release (recommended — replace vX.Y.Z with the latest tag)
 pipx install git+https://github.com/github/spec-kit.git@vX.Y.Z
 
 # Or install latest from main (may include unreleased changes)

docs/install/pypi.md

@@ -1,83 +0,0 @@
-# Installing from PyPI
-
-Spec Kit is published to PyPI as [`specify-cli`](https://pypi.org/project/specify-cli/), maintained by the Spec Kit maintainers. Installing from PyPI is the second supported install route alongside installing from the [GitHub source](../installation.md#install-from-source--persistent-installation-recommended). Use whichever fits your workflow — both provide the same `specify` CLI.
-
-> [!NOTE]
-> The PyPI release version tracks the GitHub release tags (for example, PyPI `0.12.11` corresponds to the `v0.12.11` tag). `specify version` is only a local version/runtime sanity check — it reports the installed version but not where the `specify` executable came from, so it cannot distinguish a PyPI install from a Git install. To confirm the install source, inspect the source metadata your package manager records: `pipx list --json` reports the exact install specification for each tool, and for uv/pip installs you can check the package's [PEP 610](https://peps.python.org/pep-0610/) `direct_url.json` inside its `*.dist-info` directory (a Git or URL install records the repository/archive URL there, while a plain PyPI index install does not create that file). Note that `pip show specify-cli` only prints package metadata and will not see uv/pipx-managed environments from the host interpreter.
-
-## Install Specify CLI
-
-Use whichever Python tool you already have:
-
-```bash
-# Using uv (recommended)
-uv tool install specify-cli
-
-# Or using pipx
-pipx install specify-cli
-
-# Or using pip
-pip install specify-cli
-```
-
-### Install a specific release
-
-Pin an exact version for reproducible installs (check [PyPI](https://pypi.org/project/specify-cli/#history) or [Releases](https://github.com/github/spec-kit/releases) for available versions):
-
-```bash
-# Using uv
-uv tool install specify-cli==0.12.11
-
-# Or using pipx
-pipx install specify-cli==0.12.11
-
-# Or using pip
-pip install specify-cli==0.12.11
-```
-
-## Verify
-
-```bash
-specify version
-```
-
-## Initialize a project
-
-```bash
-specify init <PROJECT_NAME> --integration copilot
-```
-
-## Upgrade
-
-Upgrade by reinstalling the package through the same tool you used for the original install. If you originally pinned a version, note that `uv tool upgrade` preserves that pin; to move to the newest PyPI release, use an unpinned install command so you do not keep the existing version pin:
-
-```bash
-# Using uv
-uv tool install --force specify-cli
-
-# Or using pipx
-pipx install --force specify-cli
-
-# Or using pip
-pip install --upgrade specify-cli
-```
-
-> [!NOTE]
-> `specify self upgrade` currently rebuilds `uv tool` and `pipx` installs from the GitHub source release URL rather than preserving a PyPI-based installation. If you want to stay on the PyPI route, use the package-manager commands above. A plain `pip install specify-cli` is treated as an unmanaged install — upgrade it with `pip install --upgrade specify-cli`. See the [Upgrade Guide](../upgrade.md) for details.
-
-## Uninstall
-
-```bash
-# Using uv
-uv tool uninstall specify-cli
-
-# Or using pipx
-pipx uninstall specify-cli
-
-# Or using pip
-pip uninstall specify-cli
-```
-
-## Next steps
-
-Head to the [Quick Start](../quickstart.md) to initialize your first project.

docs/installation.md

@@ -11,16 +11,11 @@
 ## Installation
 
 > [!IMPORTANT]
-> Spec Kit is distributed through two official channels, both published and maintained by the Spec Kit maintainers: the [github/spec-kit](https://github.com/github/spec-kit) GitHub repository (source installs) and the [`specify-cli`](https://pypi.org/project/specify-cli/) package on [PyPI](https://pypi.org/project/specify-cli/). Either route is supported for normal installs — use the commands shown below. After installing, run `specify version` as a local version/runtime sanity check. It confirms that the `specify` command is available and reports its version, but it does not prove whether the executable came from PyPI or GitHub. For offline or air-gapped environments, locally built wheels created from this repository are also valid.
+> The only official, maintained packages for Spec Kit come from the [github/spec-kit](https://github.com/github/spec-kit) GitHub repository. Any packages with the same name available on PyPI (e.g. `specify-cli` on pypi.org) are **not** affiliated with this project and are not maintained by the Spec Kit maintainers. For normal installs, use the GitHub-based commands shown below. For offline or air-gapped environments, locally built wheels created from this repository are also valid.
 
-Spec Kit supports two install routes:
+### Persistent Installation (Recommended)
 
-1. **Install from source (GitHub)** — the recommended route, pinned to a release tag.
-2. **Install from PyPI** — install the published `specify-cli` package with your usual Python tooling.
-
-### Install from Source — Persistent Installation (Recommended)
-
-Install once and use everywhere. Replace `vX.Y.Z` with a release tag from [Releases](https://github.com/github/spec-kit/releases) — keep the leading `v` (for example, `v0.12.11`, not `0.12.11`):
+Install once and use everywhere. Replace `vX.Y.Z` with a tag from [Releases](https://github.com/github/spec-kit/releases):
 
 > [!NOTE]
 > The command below requires **[uv](https://docs.astral.sh/uv/)**. If you see `command not found: uv`, [install uv first](./install/uv.md).
@@ -35,30 +30,12 @@ Then initialize a project:
 specify init <PROJECT_NAME> --integration copilot
 ```
 
-### Install from PyPI
-
-Spec Kit is also published to PyPI as [`specify-cli`](https://pypi.org/project/specify-cli/), so you can install it with your preferred Python package manager without referencing the Git URL:
-
-```bash
-# Using uv (recommended)
-uv tool install specify-cli
-
-# Or using pipx
-pipx install specify-cli
-
-# Or using pip
-pip install specify-cli
-```
-
-To install a specific release, pin the version — for example `uv tool install specify-cli==0.12.11`. See the [PyPI installation guide](install/pypi.md) for details, including how to upgrade.
-
 ### One-time Usage
 
 Run directly without installing — see the [One-time usage (uvx)](install/one-time.md) guide.
 
 ### Alternative Package Managers
 
-- **PyPI** — see the [PyPI installation guide](install/pypi.md)
 - **pipx** — see the [pipx installation guide](install/pipx.md)
 - **Enterprise / Air-Gapped** — see the [air-gapped installation guide](install/air-gapped.md)
 
@@ -104,13 +81,13 @@ specify init <project_name> --integration claude --ignore-agent-tools
 
 ## Verification
 
-After installation, run the following command as a local version/runtime check:
+After installation, run the following command to confirm the correct version is installed:
 
 ```bash
 specify version
 ```
 
-This confirms that the `specify` command is available and reporting the expected version. It does not prove whether that executable came from PyPI or GitHub.
+This helps verify you are running the official Spec Kit build from GitHub, not an unrelated package with the same name.
 
 **Stay current:** Run `specify self check` periodically to learn whether a newer release is available — it is read-only and never modifies your installation. When you are ready to upgrade, follow the [Upgrade Guide](./upgrade.md).
 

docs/quickstart.md

@@ -1,128 +1,203 @@
 # Quick Start Guide
 
-This guide will help you get started with Spec-Driven Development using Spec Kit. Throughout, we illustrate each step with a running example: **Taskify**, a small team productivity platform.
+This guide will help you get started with Spec-Driven Development using Spec Kit.
 
 > [!NOTE]
-> Automation scripts are provided as both Bash (`.sh`) and PowerShell (`.ps1`) variants. The `specify` CLI auto-selects based on your OS unless you pass `--script sh|ps`.
+> All automation scripts now provide both Bash (`.sh`) and PowerShell (`.ps1`) variants. The `specify` CLI auto-selects based on OS unless you pass `--script sh|ps`.
 
-> [!NOTE]
-> Commands are shown here in `/speckit.*` form, but the exact invocation depends on your agent. Some skills-based agents use `$speckit-*` (e.g. Codex, ZCode) or `/skill:speckit-*` (e.g. Kimi). Use whichever form your agent exposes — the steps are otherwise identical.
-
-## Recommended Process
+## Recommended Workflow
 
 > [!TIP]
-> **Context Awareness**: Spec Kit tracks the active feature by the feature directory recorded in `.specify/feature.json` (overridable with the `SPECIFY_FEATURE_DIRECTORY` environment variable). Commands resolve the feature from that state, **not** from the checked-out Git branch — no Git required. The opt-in **git** extension adds numbered feature branches (e.g. `001-feature-name`) for organizing work in version control, but the active feature is still whichever directory that state points to; `git checkout` alone does not change it. To point commands at a different feature, update `.specify/feature.json` (or set `SPECIFY_FEATURE_DIRECTORY`).
+> **Context Awareness**: Spec Kit commands automatically detect the active feature based on your current Git branch (e.g., `001-feature-name`). To switch between different specifications, simply switch Git branches.
 
-After installing Spec Kit, each command below is a step in the process. Two paths are common:
+After installing Spec Kit and defining your project constitution, quick experiments can use the lean feature path: `/speckit.specify` -> `/speckit.plan` -> `/speckit.tasks` -> `/speckit.implement`. For production features or any work with meaningful ambiguity, treat `/speckit.clarify`, `/speckit.checklist`, and `/speckit.analyze` as regular quality gates:
 
-**Shorter path** — for smaller features:
+```text
+/speckit.constitution -> /speckit.specify -> /speckit.clarify -> /speckit.plan -> /speckit.checklist -> /speckit.tasks -> /speckit.analyze -> /speckit.implement -> /speckit.converge
+```
 
-1. `/speckit.specify`
-2. `/speckit.plan`
-3. `/speckit.tasks`
-4. `/speckit.implement`
-5. `/speckit.converge`
+Use `/speckit.clarify` to reduce requirement ambiguity before planning, `/speckit.checklist` (after `/speckit.plan`) to generate quality checklists that validate requirements completeness, clarity, and consistency, and `/speckit.analyze` to check spec/plan/task consistency before implementation starts. You can repeat `/speckit.analyze` after implementation as an extra review, but keep the first analysis before `/speckit.implement` so gaps are caught while the plan and tasks can still be adjusted. Finally, run `/speckit.converge` after implementation to verify all planned work is complete and generate tasks for any remaining gaps. If `/speckit.converge` appends new tasks, run `/speckit.implement` again (and converge again) until it reports that the feature has converged.
 
-**Full path** — for production features, adding `/speckit.clarify`, `/speckit.checklist`, and `/speckit.analyze` as quality gates:
+### Step 1: Install Specify
 
-1. `/speckit.constitution`
-2. `/speckit.specify`
-3. `/speckit.clarify`
-4. `/speckit.plan`
-5. `/speckit.checklist`
-6. `/speckit.tasks`
-7. `/speckit.analyze`
-8. `/speckit.implement`
-9. `/speckit.converge`
-
-### Install Specify
-
-**In your terminal**, install the CLI from PyPI (requires [uv](install/uv.md)), then initialize your project:
+**In your terminal**, run the `specify` CLI command to initialize your project:
 
 ```bash
-uv tool install specify-cli
-specify init taskify   # or: specify init .   to use the current directory
-```
+# Create a new project directory
+uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME>
 
-`init` lets you pick your coding agent interactively, or pass it explicitly with `--integration` (e.g. `--integration copilot`).
+# OR initialize in the current directory
+uvx --from git+https://github.com/github/spec-kit.git specify init .
+```
 
 > [!NOTE]
-> Prefer `pipx`, one-time `uvx` runs, a pinned release, or an offline/air-gapped setup? See the [Installation Guide](installation.md) for all supported methods.
+> You can also install the CLI persistently with `pipx`:
+>
+> ```bash
+> pipx install git+https://github.com/github/spec-kit.git
+> ```
+>
+> After installing with `pipx`, run `specify` directly instead of `uvx --from ... specify`, for example:
+>
+> ```bash
+> specify init <PROJECT_NAME>
+> specify init .
+> ```
 
-### Step 1: `/speckit.constitution` — set the ground rules
+Pick script type explicitly (optional):
 
-Establishes the project's guiding principles, which every later step is evaluated against. Run it once up front, passing your principles as arguments.
-
-```text
-/speckit.constitution Taskify is a "Security-First" application. All user inputs must be validated. We use a microservices architecture. Code must be fully documented.
+```bash
+uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME> --script ps  # Force PowerShell
+uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME> --script sh  # Force POSIX shell
 ```
 
-### Step 2: `/speckit.specify` — describe what to build
+### Step 2: Define Your Constitution
 
-Creates the feature specification from a natural-language description. Focus on the **what** and **why**, not the tech stack.
+**In your coding agent's chat interface**, use the `/speckit.constitution` slash command to establish the core rules and principles for your project. You should provide your project's specific principles as arguments.
 
-```text
-/speckit.specify Develop Taskify, a team productivity platform where predefined users create projects, assign tasks, comment, and move tasks across Kanban columns (To Do, In Progress, In Review, Done). Five users (one product manager, four engineers), three sample projects, no login for this first phase.
+```markdown
+/speckit.constitution This project follows a "Library-First" approach. All features must be implemented as standalone libraries first. We use TDD strictly. We prefer functional programming patterns.
 ```
 
-### Step 3: `/speckit.clarify` — resolve ambiguities
+### Step 3: Create the Spec
 
-Asks targeted questions about anything underspecified and folds your answers back into the spec, so you're not planning on top of ambiguity. Run it before planning, optionally with a focus area.
+**In the chat**, use the `/speckit.specify` slash command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
 
-```text
-/speckit.clarify Focus on task card behavior — status changes, comment permissions, and user assignment.
+```markdown
+/speckit.specify Build an application that can help me organize my photos in separate photo albums. Albums are grouped by date and can be re-organized by dragging and dropping on the main page. Albums are never in other nested albums. Within each album, photos are previewed in a tile-like interface.
 ```
 
-### Step 4: `/speckit.plan` — choose the tech stack
+### Step 4: Refine and Validate the Spec
 
-Generates the design artifacts from the spec. This is where implementation detail belongs — provide your tech stack and architecture.
+**In the chat**, use the `/speckit.clarify` slash command to identify and resolve ambiguities in your specification. You can provide specific focus areas as arguments.
 
-```text
-/speckit.plan Use .NET Aspire with Postgres. The frontend is Blazor Server with drag-and-drop boards and real-time updates. Expose REST APIs for projects, tasks, and notifications.
+```bash
+/speckit.clarify Focus on security and performance requirements.
 ```
 
-### Step 5: `/speckit.checklist` — validate the spec
+### Step 5: Create a Technical Implementation Plan
 
-Generates a quality checklist — "unit tests for your requirements" — to confirm the spec is complete, clear, and consistent before you break the work down.
+**In the chat**, use the `/speckit.plan` slash command to provide your tech stack and architecture choices.
 
-```text
+```markdown
+/speckit.plan The application uses Vite with minimal number of libraries. Use vanilla HTML, CSS, and JavaScript as much as possible. Images are not uploaded anywhere and metadata is stored in a local SQLite database.
+```
+
+Then generate quality checklists with `/speckit.checklist` once the plan exists:
+
+```bash
 /speckit.checklist
 ```
 
-### Step 6: `/speckit.tasks` — break the work down
+### Step 6: Break Down, Analyze, and Implement
 
-Generates an actionable, dependency-ordered `tasks.md` from the design artifacts.
+**In the chat**, use the `/speckit.tasks` slash command to create an actionable task list.
 
-```text
+```markdown
 /speckit.tasks
 ```
 
-### Step 7: `/speckit.analyze` — check consistency
+Validate cross-artifact consistency with `/speckit.analyze` before implementation:
 
-Reports conflicts, gaps, and ambiguities across `spec.md`, `plan.md`, and `tasks.md`. It's read-only — if it flags issues, fix them at the source and re-run before implementing.
-
-```text
+```markdown
 /speckit.analyze
 ```
 
-### Step 8: `/speckit.implement` — build it
+Use the `/speckit.implement` slash command to execute the plan.
 
-Executes the tasks in `tasks.md` in dependency order. Run it once to build everything, or scope it to one phase at a time for large features.
-
-```text
+```markdown
 /speckit.implement
 ```
 
-### Step 9: `/speckit.converge` — verify completeness
+> [!TIP]
+> **Phased Implementation**: For complex projects, implement in phases to avoid overwhelming the agent's context. Start with core functionality, validate it works, then add features incrementally.
 
-Checks the codebase against the spec, plan, and tasks. If it finds gaps, it appends new tasks to `tasks.md`; run `/speckit.implement` and converge again until it reports converged. Otherwise you're done — proceed to review or open a PR.
+## Detailed Example: Building Taskify
+
+Here's a complete example of building a team productivity platform:
+
+### Step 1: Define Constitution
+
+Initialize the project's constitution to set ground rules:
+
+```markdown
+/speckit.constitution Taskify is a "Security-First" application. All user inputs must be validated. We use a microservices architecture. Code must be fully documented.
+```
+
+### Step 2: Define Requirements with `/speckit.specify`
 
 ```text
+/speckit.specify Develop Taskify, a team productivity platform. It should allow users to create projects, add team members,
+assign tasks, comment and move tasks between boards in Kanban style. In this initial phase for this feature,
+let's call it "Create Taskify," let's have multiple users but the users will be declared ahead of time, predefined.
+I want five users in two different categories, one product manager and four engineers. Let's create three
+different sample projects. Let's have the standard Kanban columns for the status of each task, such as "To Do,"
+"In Progress," "In Review," and "Done." There will be no login for this application as this is just the very
+first testing thing to ensure that our basic features are set up.
+```
+
+### Step 3: Refine the Specification
+
+Use the `/speckit.clarify` command to interactively resolve any ambiguities in your specification. You can also provide specific details you want to ensure are included.
+
+```bash
+/speckit.clarify I want to clarify the task card details. For each task in the UI for a task card, you should be able to change the current status of the task between the different columns in the Kanban work board. You should be able to leave an unlimited number of comments for a particular card. You should be able to, from that task card, assign one of the valid users.
+```
+
+You can continue to refine the spec with more details using `/speckit.clarify`:
+
+```bash
+/speckit.clarify When you first launch Taskify, it's going to give you a list of the five users to pick from. There will be no password required. When you click on a user, you go into the main view, which displays the list of projects. When you click on a project, you open the Kanban board for that project. You're going to see the columns. You'll be able to drag and drop cards back and forth between different columns. You will see any cards that are assigned to you, the currently logged in user, in a different color from all the other ones, so you can quickly see yours. You can edit any comments that you make, but you can't edit comments that other people made. You can delete any comments that you made, but you can't delete comments anybody else made.
+```
+
+### Step 4: Generate Technical Plan with `/speckit.plan`
+
+Be specific about your tech stack and technical requirements:
+
+```bash
+/speckit.plan We are going to generate this using .NET Aspire, using Postgres as the database. The frontend should use Blazor server with drag-and-drop task boards, real-time updates. There should be a REST API created with a projects API, tasks API, and a notifications API.
+```
+
+### Step 5: Validate the Spec
+
+Generate quality checklists to validate the specification using the `/speckit.checklist` command:
+
+```bash
+/speckit.checklist
+```
+
+### Step 6: Define Tasks
+
+Generate an actionable task list using the `/speckit.tasks` command:
+
+```bash
+/speckit.tasks
+```
+
+### Step 7: Validate and Implement
+
+Have your coding agent audit the spec, plan, and tasks with `/speckit.analyze` before implementation:
+
+```bash
+/speckit.analyze
+```
+
+Finally, implement the solution:
+
+```bash
+/speckit.implement
+```
+
+### Step 8: Converge
+
+Run the `/speckit.converge` command after implementation to assess the current codebase against the feature's artifacts and append any remaining unbuilt work as new tasks to `tasks.md`. If the command appends new tasks, run `/speckit.implement` again to complete them, and repeat the converge step until the feature is fully complete.
+
+```bash
 /speckit.converge
 ```
 
 > [!TIP]
-> For a full reference on each command — arguments, output, phased implementation, and how they interact — see [Agentic SDD](reference/agentic-sdd.md).
+> **Phased Implementation**: For large projects like Taskify, consider implementing in phases (e.g., Phase 1: Basic project/task structure, Phase 2: Kanban functionality, Phase 3: Comments and assignments). This prevents context saturation and allows for validation at each stage.
 
 ## Key Principles
 
@@ -134,7 +209,6 @@ Checks the codebase against the spec, plan, and tasks. If it finds gaps, it appe
 
 ## Next Steps
 
-- See the [Agentic SDD](reference/agentic-sdd.md) reference for full detail on every command
 - Read the [complete methodology](https://github.com/github/spec-kit/blob/main/spec-driven.md) for in-depth guidance
 - Check out [more examples](https://github.com/github/spec-kit/tree/main/templates) in the repository
 - Explore the [source code on GitHub](https://github.com/github/spec-kit)

docs/reference/agentic-bugfix.md

@@ -1,52 +0,0 @@
-# Agentic Bug Fix
-
-The **bug** extension adds a three-step bug triage process — assess, fix, and validate — that your coding agent runs alongside the core [Agentic SDD](agentic-sdd.md) process. Each bug lives in its own directory under `.specify/bugs/<slug>/`, with one Markdown report per stage.
-
-> [!NOTE]
-> Commands are written in `/speckit.bug.*` form throughout this page. The exact invocation depends on your agent — some skills-based agents use `$speckit-bug-*` (e.g. Codex, ZCode) or `/skill:speckit-bug-*` (e.g. Kimi). Substitute the form your agent exposes.
-
-The bug extension is a bundled, opt-in extension. Install it before using these commands:
-
-```bash
-specify extension add bug
-```
-
-The three commands share a single handle — the **slug**, the per-bug directory name under `.specify/bugs/`. Supply it with `slug=<name>`; if omitted, `/speckit.bug.assess` asks for one (or generates a unique one in automated mode). Slugs are normalized to lowercase kebab-case. If an assessment already exists for a slug, an interactive run asks before overwriting it, while an automated run refuses and picks a new unique slug instead.
-
-```text
-/speckit.bug.assess -> /speckit.bug.fix -> /speckit.bug.test
-```
-
-## `/speckit.bug.assess`
-
-Triages a bug report — pasted text (such as a stack trace) or a URL (such as a GitHub issue) — against the codebase: it judges whether the report is a real bug, locates the suspected code paths, and proposes a remediation. This command is **read-only**: it writes only `assessment.md` and never modifies source code.
-
-```text
-/speckit.bug.assess "TypeError: cannot read properties of undefined (reading 'token') at /auth/callback"
-```
-
-```text
-/speckit.bug.assess https://github.com/example/repo/issues/1234 slug=callback-token
-```
-
-Output: `.specify/bugs/<slug>/assessment.md`.
-
-## `/speckit.bug.fix`
-
-Applies the remediation described in the assessment and records exactly what changed. This is the **only** bug command that edits source code, and it stays within the files listed in the assessment unless new evidence requires expanding scope (logged under **Deviations from Assessment**).
-
-```text
-/speckit.bug.fix slug=callback-token
-```
-
-Output: `.specify/bugs/<slug>/fix.md`.
-
-## `/speckit.bug.test`
-
-Validates the fix by re-running the reproduction and any added tests, then records the verification result — one of `verified`, `partial`, or `failed`. Like `assess`, it is **read-only** with respect to source code. Verdicts are never over-claimed: if the assessment listed a reproduction that wasn't actually exercised, the overall result is downgraded to `partial` rather than reported as `verified`.
-
-```text
-/speckit.bug.test slug=callback-token
-```
-
-Output: `.specify/bugs/<slug>/test.md`.

docs/reference/agentic-sdd.md

@@ -1,115 +0,0 @@
-# Agentic SDD
-
-The `/speckit.*` slash commands drive the core Spec-Driven Development (SDD) process — an **agentic process** your coding agent runs step by step. For a guided, end-to-end run see the [Quick Start Guide](../quickstart.md); this page is the detailed reference for each command — including arguments, output, and how they interact. For the philosophy behind the process, see [What is SDD?](../concepts/sdd.md). For bug triage, see [Agentic Bug Fix](agentic-bugfix.md).
-
-The commands are designed to run in order, but only `/speckit.specify` is strictly required before `/speckit.plan`. The clarify, checklist, and analyze commands are quality gates you add for anything with meaningful ambiguity.
-
-> [!NOTE]
-> Commands are written in `/speckit.*` form throughout this page. The exact invocation depends on your agent — some skills-based agents use `$speckit-*` (e.g. Codex, ZCode) or `/skill:speckit-*` (e.g. Kimi). Substitute the form your agent exposes.
-
-```text
-/speckit.constitution -> /speckit.specify -> /speckit.clarify -> /speckit.plan -> /speckit.checklist -> /speckit.tasks -> /speckit.analyze -> /speckit.implement -> /speckit.converge
-```
-
-## `/speckit.constitution`
-
-Creates or updates the project **constitution** — the guiding principles that every later phase is evaluated against — and keeps dependent templates in sync. Run it once up front and update it whenever your principles change. Pass the principles as arguments.
-
-```text
-/speckit.constitution This project follows a "Library-First" approach. All features must be implemented as standalone libraries first. We use TDD strictly. We prefer functional programming patterns.
-```
-
-## `/speckit.specify`
-
-Creates or updates the feature **specification** from a natural-language description. Focus on the **what** and **why** — the user-facing behavior and goals — not the tech stack, which belongs in `/speckit.plan`.
-
-```text
-/speckit.specify Build an application that helps me organize photos into albums grouped by date, re-orderable by drag-and-drop on the main page, with a tile preview inside each album.
-```
-
-## `/speckit.clarify`
-
-Asks up to five targeted questions about underspecified areas of the current spec and encodes your answers back into `spec.md`. Run it as many times as needed before planning, each time tackling a different area. Optionally pass a focus area as an argument.
-
-```text
-/speckit.clarify Focus on the task card behavior: status changes, comment limits, and who can be assigned.
-```
-
-Clarifying before planning keeps you from designing on top of ambiguity. If `/speckit.analyze` later surfaces requirement gaps, come back and run `/speckit.clarify` (or `/speckit.specify`) again.
-
-## `/speckit.plan`
-
-Runs the planning process to generate design artifacts from the spec. This is where implementation detail belongs — provide your tech stack, architecture, and technical constraints as arguments.
-
-```text
-/speckit.plan Use .NET Aspire with Postgres. The frontend is Blazor Server with drag-and-drop boards and real-time updates. Expose REST APIs for projects, tasks, and notifications.
-```
-
-## `/speckit.checklist`
-
-Generates a quality checklist for the feature — think of it as **"unit tests for your requirements."** Rather than testing code, it checks whether the spec itself is complete, clear, unambiguous, and consistent (for example: "Are the drag-and-drop rules defined for every column?", "Is behavior specified for a deleted assigned user?").
-
-Run it with no arguments for a broad pass, or pass a focus area to target one aspect:
-
-```text
-/speckit.checklist
-```
-
-```text
-/speckit.checklist Focus on the Kanban board interactions and comment permissions.
-```
-
-Review the generated checklist. If it surfaces gaps, loop back to `/speckit.clarify` or `/speckit.specify` to tighten the spec before breaking the work down.
-
-## `/speckit.tasks`
-
-Generates an actionable, dependency-ordered `tasks.md` from the design artifacts. Tasks are organized into phases: **Setup**, **Foundational** (blocking prerequisites), then **one phase per user story** in priority order, and a final **Polish** phase for cross-cutting concerns. Tests are generated within a user story's phase when requested rather than as a separate phase, and tasks are marked for parallel execution where possible.
-
-```text
-/speckit.tasks
-```
-
-## `/speckit.analyze`
-
-Performs a **read-only** cross-artifact consistency and quality analysis across `spec.md`, `plan.md`, and `tasks.md`, reporting conflicts, gaps, and ambiguities (for example a task with no matching requirement, or a plan choice that contradicts the spec). It never edits files — it produces a report and can optionally suggest remediations for you to approve.
-
-```text
-/speckit.analyze
-```
-
-Run it before implementing, while the artifacts can still be adjusted cheaply. If it surfaces issues, **return to the earlier step that owns them** and fix them at the source — `/speckit.specify` or `/speckit.clarify` for requirement problems, `/speckit.plan` for design problems, `/speckit.tasks` to regenerate the task list — then re-run `/speckit.analyze` until it comes back clean. You can also run `/speckit.analyze` again after implementation as an extra review.
-
-## `/speckit.implement`
-
-Executes the tasks in `tasks.md`, running each phase in dependency order and respecting parallel markers.
-
-For a small feature, run it once to build everything:
-
-```text
-/speckit.implement
-```
-
-For a large feature, work in stages to avoid overwhelming the agent's context — scope each run with an argument, validate the result, then continue:
-
-```text
-/speckit.implement Implement only the Setup and Foundational phases: project scaffolding and the project/task data model with basic CRUD. Stop before the user-story features.
-```
-
-```text
-/speckit.implement Now implement the Kanban board user story: drag-and-drop between columns.
-```
-
-Verify each stage works before moving to the next.
-
-## `/speckit.converge`
-
-Assesses the codebase against the feature's spec, plan, and tasks to confirm nothing was missed. It is **append-only**: it never edits or deletes code, and its only possible write is adding tasks to `tasks.md`. Run it only after `/speckit.implement` has run on the current `tasks.md`.
-
-```text
-/speckit.converge
-```
-
-It first prints a severity-graded findings summary, then resolves to one of two outcomes:
-
-- **Converged** — no gaps found. `tasks.md` is left byte-for-byte unchanged and you'll see a clean result like `✅ Converged — the implementation satisfies the spec, plan, and tasks.` You're done; proceed to review or open a PR.
-- **Tasks appended** — gaps found. Converge appends them as new tasks under a Convergence section in `tasks.md` and tells you how many. Run `/speckit.implement` again to complete them, then `/speckit.converge` once more. Each pass finds fewer items; repeat until it reports converged.

docs/reference/bundles.md

@@ -51,11 +51,10 @@ If the current directory is not yet a Spec Kit project, `install` initializes on
 specify bundle update [<bundle_id>]
 ```
 
-| Option           | Description                                                                                                            |
-| ---------------- | --------------------------------------------------------------------------------------------------------------------- |
-| `--all`          | Update every installed bundle                                                                                         |
-| `--integration`  | Override the integration used when refreshing components; applied only when the project's active integration can't be determined |
-| `--offline`      | Do not access the network                                                                                             |
+| Option       | Description                          |
+| ------------ | ------------------------------------ |
+| `--all`      | Update every installed bundle        |
+| `--offline`  | Do not access the network            |
 
 Re-resolves a bundle and **refreshes** its components through each primitive's update path, bringing already-installed components up to the bundle's newly pinned versions while preserving primitive-level overrides (such as preset priority). Provide a bundle id, or use `--all` to update everything installed.
 

docs/reference/extensions.md

@@ -26,7 +26,7 @@ specify extension add <name>
 | --------------- | -------------------------------------------------------- |
 | `--dev`         | Install from a local directory (for development)         |
 | `--from <url>`  | Install from a custom URL instead of the catalog         |
-| `--force`       | Overwrite if the extension is already installed          |
+| `--force`       | Overwrite if already installed                           |
 | `--priority <N>`| Resolution priority (default: 10; lower = higher precedence) |
 
 Installs an extension from the catalog, a URL, or a local directory. Extension commands are automatically registered with the currently installed AI coding agent integration.
@@ -171,63 +171,6 @@ To set up configuration for a newly installed extension, copy the template:
 cp .specify/extensions/<ext>/<ext>-config.template.yml \
    .specify/extensions/<ext>/<ext>-config.yml
 ```
-## Project Extension and Hook Configuration
-
-Spec Kit stores project-level extension registration and hook configuration in:
-
-```text
-.specify/extensions.yml
-```
-The file contains installed extensions, global settings, and hooks that are surfaced before or after Spec Kit commands.
-
-```yaml
-installed:
-  - git
-  - my-extension
-
-settings:
-  auto_execute_hooks: true
-
-hooks:
-  before_implement:
-    - extension: git
-      command: speckit.git.commit
-      enabled: true
-      optional: true
-      priority: 10
-      prompt: "Commit outstanding changes before implementation?"
-      description: "Auto-commit before implementation"
-
-  after_implement:
-    - extension: my-extension
-      command: speckit.my-extension.verify
-      enabled: true
-      optional: false
-      priority: 5
-      description: "Run verification after implementation"
-```
-
-### Configuration fields
-
-The top-level `installed` list records extensions installed in the project. The `settings` mapping stores project-wide extension settings, and `hooks` groups hook registrations by event.
-
-`auto_execute_hooks` defaults to `true`, but is currently reserved and is not consulted when hooks are surfaced or invoked.
-
-Each hook entry supports the following fields:
-
-| Field | Description |
-| --- | --- |
-| `extension` | ID of the extension that registered the hook. |
-| `command` | Extension command associated with the hook. |
-| `enabled` | Whether the hook is active. Hooks with `enabled: false` are skipped. |
-| `optional` | Whether the hook is optional. If `true`, the hook is presented with its `prompt` and can be skipped; if `false`, the hook is emitted as an automatic hook (includes `EXECUTE_COMMAND` markers). |
-| `priority` | Priority metadata for the hook. Values must be integers >= 1; invalid values fall back to the default priority `10`. Current command templates surface hooks in their configured YAML order and do not sort them by `priority`. |
-| `prompt` | Message shown when asking whether to run an optional hook. |
-| `description` | Human-readable explanation of what the hook does. |
-| `condition` | Optional expression evaluated by `HookExecutor` (using `config.<path>` or `env.<VAR>` with `is set`, `==`, or `!=`). Current command templates do not evaluate conditions and skip hooks with a non-empty condition. |
-Hook event names identify when a hook is invoked. They generally use `before_<command>` or `after_<command>`, such as `before_implement`, `after_implement`, `before_tasks`, and `after_tasks`.
-
-`HookExecutor.get_hooks_for_event()` returns hooks ordered by `priority`, with lower values first. However, current command templates read hook lists directly and surface them in their configured YAML order rather than using priority ordering.
 
 ## FAQ
 

docs/reference/integrations.md

@@ -1,6 +1,6 @@
 # Supported AI Coding Agent Integrations
 
-The Specify CLI supports a wide range of AI coding agents. When you run `specify init`, the CLI sets up the appropriate command files and directory structures for your chosen AI coding agent — so you can start using Spec-Driven Development immediately, regardless of which tool you prefer.
+The Specify CLI supports a wide range of AI coding agents. When you run `specify init`, the CLI sets up the appropriate command files, context rules, and directory structures for your chosen AI coding agent — so you can start using Spec-Driven Development immediately, regardless of which tool you prefer.
 
 ## Supported AI Coding Agents
 
@@ -18,9 +18,8 @@ The Specify CLI supports a wide range of AI coding agents. When you run `specify
 | [Firebender](https://firebender.com/)                                                | `firebender`     | IDE-based agent for Android Studio / IntelliJ                                                                                             |
 | [Forge](https://forgecode.dev/)                                                      | `forge`          |                                                                                                                                           |
 | [Gemini CLI](https://github.com/google-gemini/gemini-cli)                            | `gemini`         |                                                                                                                                           |
-| [GitHub Copilot](https://code.visualstudio.com/)                                     | `copilot`        | Defaults to legacy markdown mode: `.agent.md` command files under `.github/agents/`, companion `.prompt.md` files under `.github/prompts/`, and a `.vscode/settings.json` merge. Pass `--integration-options="--skills"` to scaffold skills as `speckit-<command>/SKILL.md` under `.github/skills/` instead. Legacy markdown mode is deprecated and will stop being the default in a future release. |
+| [GitHub Copilot](https://code.visualstudio.com/)                                     | `copilot`        |                                                                                                                                           |
 | [Goose](https://goose-docs.ai/)                                                      | `goose`          | Uses YAML recipe format in `.goose/recipes/`                                                                                              |
-| [Grok Build](https://docs.x.ai/build/overview)                                       | `grok`           | Skills-based integration; installs skills into `.grok/skills` and invokes them as `/speckit-<command>`                                    |
 | [Hermes](https://github.com/NousResearch/hermes-agent)                               | `hermes`         | Skills-based integration; installs skills globally into `~/.hermes/skills/`                                                                |
 | [IBM Bob](https://www.ibm.com/products/bob)                                          | `bob`            | IDE-based agent                                                                                                                           |
 | [Junie](https://junie.jetbrains.com/)                                                | `junie`          |                                                                                                                                           |
@@ -220,7 +219,6 @@ Some integrations accept additional options via `--integration-options`:
 | ----------- | ------------------- | -------------------------------------------------------------- |
 | `generic`   | `--commands-dir`    | Required. Directory for command files                          |
 | `kimi`      | `--migrate-legacy`  | Migrate legacy `.kimi/skills/` installs to `.kimi-code/skills/` (including dotted→hyphenated skill naming, e.g. `speckit.xxx` → `speckit-xxx`) |
-| `copilot`   | `--skills`          | Scaffold commands as agent skills (`speckit-<command>/SKILL.md` under `.github/skills/`, invoked as `/speckit-<command>`) instead of the default legacy markdown mode (`.github/agents/*.agent.md` plus `.github/prompts/*.prompt.md` and a `.vscode/settings.json` merge). Without this flag, install warns that legacy markdown mode is deprecated. |
 
 Example:
 
@@ -250,11 +248,7 @@ Spec Kit tracks one default integration in `.specify/integration.json` with `def
 
 ### Which integrations are multi-install safe?
 
-An integration is multi-install safe when it uses a static, unique agent root and command directory, stable command invocation settings, and a separate install manifest whose managed files do not overlap another safe integration. Registry tests enforce those path and manifest invariants. Shared Spec Kit templates remain aligned to the single default integration.
-
-The Isolation column below lists paths Spec Kit manages for that integration (skills/commands roots and any integration-owned rule files). It is not a full inventory of every file an agent may read.
-
-**Agent-context defaults are separate.** The optional agent-context extension maps each integration to a default context file in `extensions/agent-context/agent-context-defaults.json`. Those defaults are independent of multi-install safety: several agents may share a root file such as `AGENTS.md` when the extension is enabled. Multi-install safety does not require a unique context file per safe integration.
+An integration is multi-install safe when it uses isolated agent directories, a dedicated context file that does not collide with another safe integration, stable command invocation settings, and a separate install manifest. Shared Spec Kit templates remain aligned to the single default integration.
 
 The currently declared multi-install safe integrations are:
 
@@ -268,7 +262,6 @@ The currently declared multi-install safe integrations are:
 | `cursor-agent` | `.cursor/skills`, `.cursor/rules/specify-rules.mdc` |
 | `firebender` | `.firebender/commands`, `.firebender/rules/specify-rules.mdc` |
 | `gemini` | `.gemini/commands`, `GEMINI.md` |
-| `grok` | `.grok/skills` |
 | `junie` | `.junie/commands`, `.junie/AGENTS.md` |
 | `kilocode` | `.kilocode/workflows`, `.kilocode/rules/specify-rules.md` |
 | `qodercli` | `.qoder/commands`, `QODER.md` |
@@ -278,7 +271,7 @@ The currently declared multi-install safe integrations are:
 | `trae` | `.trae/skills`, `.trae/rules/project_rules.md` |
 | `zcode` | `.zcode/skills`, `ZCODE.md` |
 
-Integrations that share a command directory with another integration, require dynamic install paths such as `--commands-dir`, or merge shared tool settings are not declared safe by default. They can still be installed alongside another integration with `--force`.
+Integrations that share a context file or command directory with another integration, require dynamic install paths such as `--commands-dir`, or merge shared tool settings are not declared safe by default. They can still be installed alongside another integration with `--force`.
 
 ### What happens to my changes when I uninstall or switch?
 

docs/reference/overview.md

@@ -1,6 +1,6 @@
-# Reference
+# CLI Reference
 
-The Specify CLI (`specify`) manages the full lifecycle of Spec-Driven Development — from project initialization to workflow automation. This section is the detailed reference for the CLI's commands and primitives, plus the agentic `/speckit.*` processes your coding agent runs.
+The Specify CLI (`specify`) manages the full lifecycle of Spec-Driven Development — from project initialization to workflow automation.
 
 ## Core Commands
 
@@ -10,7 +10,7 @@ The foundational commands for creating and managing Spec Kit projects. Initializ
 
 ## Integrations
 
-Integrations connect Spec Kit to your AI coding agent. Each integration sets up the appropriate command files and directory structures for a specific agent. Only one integration is active per project at a time, and you can switch between them at any point.
+Integrations connect Spec Kit to your AI coding agent. Each integration sets up the appropriate command files, context rules, and directory structures for a specific agent. Only one integration is active per project at a time, and you can switch between them at any point.
 
 [Integrations reference →](integrations.md)
 
@@ -37,19 +37,3 @@ Workflows automate multi-step Spec-Driven Development processes into repeatable
 Bundles compose existing extensions, presets, workflows, and steps into a single, versioned, installable unit. Rather than adding new behavior, a bundle curates a stack of primitives — everything a team or role needs — and installs it in one step through each component's own machinery, with version pinning, conflict checks, and provenance tracking for clean updates and removal.
 
 [Bundles reference →](bundles.md)
-
-## Agentic Commands
-
-The sections above cover primitives managed by the `specify` CLI. The following are the `/speckit.*` slash commands your coding agent runs step by step inside the editor — the agentic processes built on top of that foundation.
-
-### Agentic SDD
-
-The `/speckit.*` slash commands that drive the core Spec-Driven Development process your coding agent runs step by step: constitution, specify, clarify, plan, checklist, tasks, analyze, implement, and converge. Run them in order, adding the clarify/checklist/analyze quality gates for anything with meaningful ambiguity.
-
-[Agentic SDD reference →](agentic-sdd.md)
-
-### Agentic Bug Fix
-
-The bundled **bug** extension adds a three-step bug triage process — assess, fix, and validate — with each bug tracked in its own directory under `.specify/bugs/`. Install it with `specify extension add bug`.
-
-[Agentic Bug Fix reference →](agentic-bugfix.md)

docs/reference/workflows.md

@@ -86,30 +86,8 @@ Lists workflows installed in the current project.
 specify workflow add <source>
 ```
 
-| Option          | Description                                            |
-| --------------- | ------------------------------------------------------ |
-| `--dev`         | Install from a local workflow YAML file or directory   |
-| `--from <url>`  | Install from a custom URL (`<source>` names the expected workflow ID) |
-
 Installs a workflow from the catalog, a URL (HTTPS required), or a local file path.
 
-## Update Workflows
-
-```bash
-specify workflow update [workflow_id]
-```
-
-Updates one installed catalog workflow — or all of them when no ID is given — to the latest catalog version. Prompts for confirmation and keeps the installed copy if a download or validation fails.
-
-## Enable or Disable a Workflow
-
-```bash
-specify workflow enable <workflow_id>
-specify workflow disable <workflow_id>
-```
-
-Disabled workflows stay installed and listed (marked `[disabled]`) but refuse to run until re-enabled.
-
 ## Remove a Workflow
 
 ```bash
@@ -124,10 +102,9 @@ Removes an installed workflow from the project.
 specify workflow search [query]
 ```
 
-| Option     | Description       |
-| ---------- | ----------------- |
-| `--tag`    | Filter by tag     |
-| `--author` | Filter by author  |
+| Option  | Description     |
+| ------- | --------------- |
+| `--tag` | Filter by tag   |
 
 Searches all active catalogs for workflows matching the query.
 
@@ -305,8 +282,6 @@ Steps can reference inputs and previous step outputs using `{{ expression }}` sy
 | `inputs.spec`                  | Workflow input values                |
 | `steps.specify.output.file`    | Output from a previous step          |
 | `item`                         | Current item in a fan-out iteration  |
-| `context.run_id`               | Current workflow run ID              |
-| `context.workflow_dir`         | Resolved absolute path to the workflow source directory. Empty string for string-loaded workflows. |
 
 Available filters: `default`, `join`, `contains`, `map`, `from_json`.
 
@@ -318,14 +293,6 @@ args: "{{ inputs.spec }}"
 message: "{{ status | default('pending') }}"
 ```
 
-## Shell Step Environment Variables
-
-Shell steps automatically receive the following environment variables:
-
-| Variable | Description |
-| -------- | ----------- |
-| `SPECKIT_WORKFLOW_DIR` | Resolved absolute path to the workflow source directory (same value as `{{ context.workflow_dir }}`). Not set when the workflow has no source path. |
-
 ## Input Types
 
 | Type      | Coercion                                          |

docs/toc.yml

@@ -13,8 +13,6 @@
       href: upgrade.md
     - name: Install uv
       href: install/uv.md
-    - name: Install from PyPI
-      href: install/pypi.md
     - name: Install with pipx
       href: install/pipx.md
     - name: One-time Usage (uvx)
@@ -39,10 +37,6 @@
       href: reference/workflows.md
     - name: Bundles
       href: reference/bundles.md
-    - name: Agentic SDD
-      href: reference/agentic-sdd.md
-    - name: Agentic Bug Fix
-      href: reference/agentic-bugfix.md
     - name: Authentication
       href: reference/authentication.md
 

extensions/agent-context/agent-context-defaults.json

@@ -17,7 +17,6 @@
     "gemini": "GEMINI.md",
     "generic": "AGENTS.md",
     "goose": "AGENTS.md",
-    "grok": "AGENTS.md",
     "hermes": "AGENTS.md",
     "junie": ".junie/AGENTS.md",
     "kilocode": ".kilocode/rules/specify-rules.md",

extensions/agent-context/commands/speckit.agent-context.update.md

@@ -15,7 +15,7 @@ The script reads the agent-context extension config at
 - `context_files` — optional project-relative paths for multiple coding agent context files. When non-empty, the script updates each listed file and the list takes precedence over `context_file`.
 - `context_markers.start` / `.end` — the delimiters surrounding the managed section. Defaults to `<!-- SPECKIT START -->` and `<!-- SPECKIT END -->` when the field is missing.
 
-It then creates, replaces, or appends the managed block so that the section points at the most recent plan path when one can be discovered (any `plan.md` under `specs/`, including nested scoped layouts such as `specs/<scope>/<feature>/plan.md`).
+It then creates, replaces, or appends the managed block so that the section points at the most recent plan path when one can be discovered (`specs/<feature>/plan.md`).
 
 If `context_files` and `context_file` are empty, the command reports nothing to do and exits successfully. Context file paths must stay project-relative; absolute paths, Windows drive paths, backslash separators, and `..` path segments are rejected.
 
@@ -24,4 +24,4 @@ If `context_files` and `context_file` are empty, the command reports nothing to
 - **Bash**: `.specify/extensions/agent-context/scripts/bash/update-agent-context.sh [plan_path]`
 - **PowerShell**: `.specify/extensions/agent-context/scripts/powershell/update-agent-context.ps1 [plan_path]`
 
-When `plan_path` is omitted, the script auto-detects the most recently modified `specs/**/plan.md` (searched recursively, so nested scoped layouts are discovered).
+When `plan_path` is omitted, the script auto-detects the most recently modified `specs/*/plan.md`.

extensions/agent-context/scripts/bash/update-agent-context.sh

@@ -12,7 +12,7 @@
 #
 # When `plan_path` is omitted, the script derives it from `.specify/feature.json`
 # (written by /speckit-specify). Falls back to the most recently modified
-# `specs/**/plan.md` only when feature.json is absent or its plan does not exist yet.
+# `specs/*/plan.md` only when feature.json is absent or its plan does not exist yet.
 
 set -euo pipefail
 
@@ -307,28 +307,16 @@ import sys
 from pathlib import Path
 root = Path(sys.argv[1]).resolve()
 specs = root / "specs"
-
-def _resolved_rel(p):
-    # Resolve symlinks before checking containment: relative_to() is lexical
-    # and would otherwise accept a plan reached through a specs/ symlink that
-    # points outside the project, emitting an in-project-looking path for an
-    # out-of-project file (or picking it as "most recent").
+plans = sorted(
+    specs.glob("*/plan.md"),
+    key=lambda p: p.stat().st_mtime,
+    reverse=True,
+)
+if plans:
     try:
-        return p.resolve().relative_to(root)
-    except (OSError, ValueError):
-        return None
-
-# Recurse (rather than the old one-level specs/*/plan.md glob) so scoped layouts
-# created via SPECIFY_FEATURE_DIRECTORY, e.g. specs/<scope>/<feature>/plan.md,
-# are still discovered when feature.json is absent (#3024).
-candidates = []
-for p in specs.rglob("plan.md"):
-    rel = _resolved_rel(p)
-    if rel:
-        candidates.append((p, rel))
-candidates.sort(key=lambda pr: pr[0].stat().st_mtime, reverse=True)
-if candidates:
-    print(candidates[0][1].as_posix())
+        print(plans[0].relative_to(root).as_posix())
+    except ValueError:
+        print("")
 else:
     print("")
 PY

extensions/agent-context/scripts/powershell/update-agent-context.ps1

@@ -12,7 +12,7 @@
 #
 # When `plan_path` is omitted, the script derives it from `.specify/feature.json`
 # (written by /speckit-specify). Falls back to the most recently modified
-# `specs/**/plan.md` only when feature.json is absent or its plan does not exist yet.
+# `specs/*/plan.md` only when feature.json is absent or its plan does not exist yet.
 
 [CmdletBinding()]
 param(
@@ -426,11 +426,9 @@ if (-not $PlanPath) {
     if (-not $PlanPath) {
         try {
             $specsDir = Join-Path $ProjectRoot 'specs'
-            # Recurse (rather than the old one-level specs/*/plan.md scan) so scoped
-            # layouts created via SPECIFY_FEATURE_DIRECTORY, e.g.
-            # specs/<scope>/<feature>/plan.md, are still discovered when
-            # feature.json is absent (#3024).
-            $candidate = Get-ChildItem -Path $specsDir -Filter 'plan.md' -File -Recurse -ErrorAction SilentlyContinue |
+            $candidate = Get-ChildItem -Path $specsDir -Directory -ErrorAction SilentlyContinue |
+                ForEach-Object { Get-Item -LiteralPath (Join-Path $_.FullName 'plan.md') -ErrorAction SilentlyContinue } |
+                Where-Object { $_ } |
                 Sort-Object LastWriteTime -Descending |
                 Select-Object -First 1
             if ($candidate) {

extensions/agent-context/scripts/python/update_agent_context.py

@@ -1,352 +0,0 @@
-#!/usr/bin/env python3
-"""Refresh the managed Spec Kit section in the coding agent's context file(s).
-
-Python port of ``update-agent-context.sh`` / ``update-agent-context.ps1``.
-
-Reads ``context_files`` or ``context_file``, plus ``context_markers.{start,end}``,
-from the agent-context extension config:
-    .specify/extensions/agent-context/agent-context-config.yml
-
-Usage: update_agent_context.py [plan_path]
-
-When ``plan_path`` is omitted, the script derives it from
-``.specify/feature.json`` (written by /speckit-specify). Falls back to the most
-recently modified ``specs/*/plan.md`` only when feature.json is absent or its
-plan does not exist yet.
-"""
-
-from __future__ import annotations
-
-import json
-import os
-import re
-import sys
-from pathlib import Path
-
-DEFAULT_START = "<!-- SPECKIT START -->"
-DEFAULT_END = "<!-- SPECKIT END -->"
-
-
-def _err(message: str) -> None:
-    print(message, file=sys.stderr)
-
-
-def _get_str(obj: object, *keys: str) -> str:
-    node = obj
-    for key in keys:
-        if isinstance(node, dict) and key in node:
-            node = node[key]
-        else:
-            return ""
-    return node if isinstance(node, str) else ""
-
-
-def _collect_context_files(data: dict, project_root: str) -> list[str]:
-    """Resolve the managed context files from config, mirroring the bash logic."""
-    context_files: list[str] = []
-    seen: set[str] = set()
-    case_insensitive = sys.platform.startswith(("win32", "cygwin", "msys"))
-
-    def add(value: object) -> None:
-        if not isinstance(value, str):
-            return
-        candidate = value.strip()
-        if not candidate:
-            return
-        key = candidate.casefold() if case_insensitive else candidate
-        if key in seen:
-            return
-        context_files.append(candidate)
-        seen.add(key)
-
-    raw_files = data.get("context_files")
-    if isinstance(raw_files, list):
-        for value in raw_files:
-            add(value)
-    if not context_files:
-        add(_get_str(data, "context_file"))
-    if not context_files:
-        # Self-seed: when the config declares no target, derive one from the
-        # active integration recorded in init-options.json, mapped through the
-        # bundled agent-context-defaults.json file. Independent of the Specify
-        # CLI by design.
-        integration_key = ""
-        try:
-            with open(
-                f"{project_root}/.specify/init-options.json", "r", encoding="utf-8"
-            ) as fh:
-                opts = json.load(fh)
-            if isinstance(opts, dict):
-                value = opts.get("integration") or opts.get("ai") or ""
-                integration_key = value if isinstance(value, str) else ""
-        except Exception:
-            integration_key = ""
-        if integration_key:
-            defaults_path = (
-                f"{project_root}/.specify/extensions/agent-context/"
-                "agent-context-defaults.json"
-            )
-            mapping = {}
-            try:
-                with open(defaults_path, "r", encoding="utf-8") as fh:
-                    loaded = json.load(fh)
-                agents = loaded.get("agents", {}) if isinstance(loaded, dict) else {}
-                mapping = agents if isinstance(agents, dict) else {}
-            except Exception:
-                _err(
-                    "agent-context: unable to read %s; cannot self-seed the context "
-                    "file. Set context_file in the extension config." % defaults_path
-                )
-                mapping = {}
-            add(mapping.get(integration_key, "") or "")
-            if not context_files:
-                _err(
-                    "agent-context: no default context file is known for integration "
-                    "%s. Set context_file in the extension config to choose one."
-                    % integration_key
-                )
-    return context_files
-
-
-def _validate_context_file(project_root: str, context_file: str) -> str | None:
-    """Return an error message when the path escapes the project root."""
-    if context_file.startswith("/") or re.match(r"^[A-Za-z]:", context_file):
-        return (
-            "agent-context: context files must be project-relative paths; "
-            f"got '{context_file}'."
-        )
-    if "\\" in context_file:
-        return (
-            "agent-context: context files must not contain backslash separators; "
-            f"got '{context_file}'."
-        )
-    if ".." in context_file.split("/"):
-        return (
-            "agent-context: context files must not contain '..' path segments; "
-            f"got '{context_file}'."
-        )
-    root = Path(project_root).resolve()
-    target = (root / context_file).resolve()
-    try:
-        target.relative_to(root)
-    except ValueError:
-        return (
-            "agent-context: context file path resolves outside the project root; "
-            f"got '{context_file}'."
-        )
-    return None
-
-
-def _resolve_plan_path(project_root: str) -> str:
-    """Derive the plan path: feature.json first, then the mtime fallback."""
-    plan_path = ""
-    feature_json = Path(project_root) / ".specify" / "feature.json"
-    if feature_json.is_file():
-        feature_dir = ""
-        try:
-            with open(feature_json, "r", encoding="utf-8") as fh:
-                data = json.load(fh)
-            value = data.get("feature_directory", "")
-            feature_dir = value if isinstance(value, str) else ""
-        except Exception:
-            feature_dir = ""
-        # Normalize backslashes (written by PS on Windows) before path ops.
-        feature_dir = feature_dir.replace("\\", "/").rstrip("/")
-        if feature_dir:
-            # feature_directory may be relative or absolute (absolute paths
-            # outside the project root are preserved as-is), including
-            # drive-qualified paths (C:/...) written by PowerShell on Windows.
-            if feature_dir.startswith("/") or re.match(r"^[A-Za-z]:/", feature_dir):
-                candidate = Path(feature_dir) / "plan.md"
-            else:
-                candidate = Path(project_root) / feature_dir / "plan.md"
-            if candidate.is_file():
-                # Resolve symlinks before comparing so paths like /var/… vs
-                # /private/var/… (macOS) are treated as equivalent.
-                root = Path(project_root).resolve()
-                resolved = candidate.resolve()
-                try:
-                    plan_path = resolved.relative_to(root).as_posix()
-                except ValueError:
-                    plan_path = resolved.as_posix()
-
-    if not plan_path:
-        root = Path(project_root).resolve()
-        plans = sorted(
-            (root / "specs").glob("*/plan.md"),
-            key=lambda p: p.stat().st_mtime,
-            reverse=True,
-        )
-        if plans:
-            try:
-                plan_path = plans[0].relative_to(root).as_posix()
-            except ValueError:
-                plan_path = ""
-    return plan_path
-
-
-def _build_section(marker_start: str, marker_end: str, plan_path: str) -> str:
-    lines = [
-        marker_start,
-        "For additional context about technologies to be used, project structure,",
-        "shell commands, and other important information, read the current plan",
-    ]
-    if plan_path:
-        lines.append(f"at {plan_path}")
-    lines.append(marker_end)
-    return "\n".join(lines) + "\n"
-
-
-def ensure_mdc_frontmatter(content: str) -> str:
-    """Ensure ``.mdc`` content has YAML frontmatter with ``alwaysApply: true``.
-
-    Cursor only auto-loads ``.mdc`` rule files that carry frontmatter with
-    ``alwaysApply: true``. Prepend it when missing, or repair the value while
-    preserving any existing frontmatter comments/formatting.
-    """
-    leading_ws = len(content) - len(content.lstrip())
-    leading = content[:leading_ws]
-    stripped = content[leading_ws:]
-
-    if not stripped.startswith("---"):
-        return "---\nalwaysApply: true\n---\n\n" + content
-
-    match = re.match(
-        r"^(---[ \t]*\r?\n)(.*?)(\r?\n---[ \t]*)(\r?\n|$)(.*)",
-        stripped,
-        re.DOTALL,
-    )
-    if not match:
-        return "---\nalwaysApply: true\n---\n\n" + content
-
-    opening, fm_text, closing, sep, rest = match.groups()
-    newline = "\r\n" if "\r\n" in opening else "\n"
-
-    if re.search(r"(?m)^[ \t]*alwaysApply[ \t]*:[ \t]*true[ \t]*(?:#.*)?$", fm_text):
-        return content
-
-    if re.search(r"(?m)^[ \t]*alwaysApply[ \t]*:", fm_text):
-        fm_text = re.sub(
-            r"(?m)^([ \t]*)alwaysApply[ \t]*:.*?([ \t]*(?:#.*)?)$",
-            r"\1alwaysApply: true\2",
-            fm_text,
-            count=1,
-        )
-    elif fm_text.strip():
-        fm_text = fm_text + newline + "alwaysApply: true"
-    else:
-        fm_text = "alwaysApply: true"
-
-    return f"{leading}{opening}{fm_text}{closing}{sep}{rest}"
-
-
-def _upsert_section(
-    ctx_path: str, marker_start: str, marker_end: str, section: str
-) -> None:
-    """Insert or replace the managed section, then normalize and write."""
-    if os.path.exists(ctx_path):
-        with open(ctx_path, "r", encoding="utf-8-sig") as fh:
-            content = fh.read()
-        s = content.find(marker_start)
-        e = content.find(marker_end, s if s != -1 else 0)
-        if s != -1 and e != -1 and e > s:
-            end_of_marker = e + len(marker_end)
-            if end_of_marker < len(content) and content[end_of_marker] == "\r":
-                end_of_marker += 1
-            if end_of_marker < len(content) and content[end_of_marker] == "\n":
-                end_of_marker += 1
-            new_content = content[:s] + section + content[end_of_marker:]
-        elif s != -1:
-            new_content = content[:s] + section
-        elif e != -1:
-            end_of_marker = e + len(marker_end)
-            if end_of_marker < len(content) and content[end_of_marker] == "\r":
-                end_of_marker += 1
-            if end_of_marker < len(content) and content[end_of_marker] == "\n":
-                end_of_marker += 1
-            new_content = section + content[end_of_marker:]
-        else:
-            if content and not content.endswith("\n"):
-                content += "\n"
-            new_content = (content + "\n" + section) if content else section
-    else:
-        new_content = section
-
-    new_content = new_content.replace("\r\n", "\n").replace("\r", "\n")
-    if ctx_path.casefold().endswith(".mdc"):
-        new_content = ensure_mdc_frontmatter(new_content)
-    with open(ctx_path, "wb") as fh:
-        fh.write(new_content.encode("utf-8"))
-
-
-def main(argv: list[str] | None = None) -> int:
-    args = sys.argv[1:] if argv is None else argv
-    project_root = os.getcwd()
-    ext_config = (
-        f"{project_root}/.specify/extensions/agent-context/agent-context-config.yml"
-    )
-
-    if not os.path.isfile(ext_config):
-        _err(f"agent-context: {ext_config} not found; nothing to do.")
-        return 0
-
-    try:
-        import yaml
-    except ImportError:
-        _err(
-            "agent-context: PyYAML is required to parse extension config but is "
-            "not available in the current Python environment.\n"
-            "  To resolve: pip install pyyaml (or install it into the environment "
-            "used by python3).\n"
-            "  Context file will not be updated until PyYAML is importable."
-        )
-        _err("agent-context: skipping update (see above for details).")
-        return 0
-
-    try:
-        with open(ext_config, "r", encoding="utf-8") as fh:
-            data = yaml.safe_load(fh)
-    except Exception as exc:
-        _err(
-            f"agent-context: unable to parse {ext_config} ({exc}); "
-            "cannot update context."
-        )
-        _err("agent-context: skipping update (see above for details).")
-        return 0
-    if not isinstance(data, dict):
-        data = {}
-
-    context_files = _collect_context_files(data, project_root)
-    if not context_files:
-        _err(
-            "agent-context: context_files/context_file not set in extension config; "
-            "nothing to do."
-        )
-        return 0
-
-    for context_file in context_files:
-        error = _validate_context_file(project_root, context_file)
-        if error:
-            _err(error)
-            return 1
-
-    marker_start = _get_str(data, "context_markers", "start") or DEFAULT_START
-    marker_end = _get_str(data, "context_markers", "end") or DEFAULT_END
-
-    plan_path = args[0] if args else ""
-    if not plan_path:
-        plan_path = _resolve_plan_path(project_root)
-
-    section = _build_section(marker_start, marker_end, plan_path)
-
-    for context_file in context_files:
-        ctx_path = os.path.join(project_root, context_file)
-        os.makedirs(os.path.dirname(ctx_path) or ".", exist_ok=True)
-        _upsert_section(ctx_path, marker_start, marker_end, section)
-        print(f"agent-context: updated {context_file}")
-
-    return 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())

extensions/catalog.community.json

@@ -1,6 +1,6 @@
 {
   "schema_version": "1.0",
-  "updated_at": "2026-07-16T00:00:00Z",
+  "updated_at": "2026-07-06T00:00:00Z",
   "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.community.json",
   "extensions": {
     "aide": {
@@ -395,66 +395,6 @@
       "created_at": "2026-03-03T00:00:00Z",
       "updated_at": "2026-03-03T00:00:00Z"
     },
-    "bdd": {
-      "name": "Spec-Kit BDD",
-      "id": "bdd",
-      "description": "ATDD/BDD extension: convert specs to Gherkin scenarios, scaffold step definitions, and verify acceptance test coverage.",
-      "author": "RSginer",
-      "version": "1.0.2",
-      "download_url": "https://github.com/RSginer/spec-kit-bdd/archive/refs/tags/v1.0.2.zip",
-      "repository": "https://github.com/RSginer/spec-kit-bdd",
-      "homepage": "https://github.com/RSginer/spec-kit-bdd",
-      "documentation": "https://github.com/RSginer/spec-kit-bdd/blob/main/docs/usage.md",
-      "changelog": "https://github.com/RSginer/spec-kit-bdd/releases",
-      "license": "MIT",
-      "category": "process",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.2.0",
-        "tools": [
-          {
-            "name": "pytest-bdd",
-            "required": false
-          },
-          {
-            "name": "behave",
-            "required": false
-          },
-          {
-            "name": "@cucumber/cucumber",
-            "required": false
-          },
-          {
-            "name": "cucumber",
-            "required": false
-          },
-          {
-            "name": "io.cucumber",
-            "required": false
-          },
-          {
-            "name": "SpecFlow",
-            "required": false
-          }
-        ]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 2
-      },
-      "tags": [
-        "bdd",
-        "gherkin",
-        "atdd",
-        "acceptance-testing",
-        "tdd"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-15T00:00:00Z",
-      "updated_at": "2026-07-15T00:00:00Z"
-    },
     "blueprint": {
       "name": "Blueprint",
       "id": "blueprint",
@@ -869,8 +809,8 @@
       "id": "coding-standards-drift-control",
       "description": "Generate coding-standards drift reports and remediation tasks for active Spec Kit features",
       "author": "Igor Benicio de Mesquita",
-      "version": "0.4.0",
-      "download_url": "https://github.com/benizzio/spec-kit-coding-standards-drift-control/archive/refs/tags/v0.4.0.zip",
+      "version": "0.3.1",
+      "download_url": "https://github.com/benizzio/spec-kit-coding-standards-drift-control/archive/refs/tags/v0.3.1.zip",
       "repository": "https://github.com/benizzio/spec-kit-coding-standards-drift-control",
       "homepage": "https://github.com/benizzio/spec-kit-coding-standards-drift-control",
       "documentation": "https://github.com/benizzio/spec-kit-coding-standards-drift-control#readme",
@@ -895,7 +835,7 @@
       "downloads": 0,
       "stars": 0,
       "created_at": "2026-06-11T00:00:00Z",
-      "updated_at": "2026-07-15T00:00:00Z"
+      "updated_at": "2026-06-11T00:00:00Z"
     },
     "companion": {
       "name": "SpecKit Companion",
@@ -1166,10 +1106,10 @@
     "docguard": {
       "name": "DocGuard — CDD Enforcement",
       "id": "docguard",
-      "description": "The only doc-integrity engine with an MCP server, SARIF/JUnit output, and a deterministic zero-LLM core. Validates, scores, and traces documentation against code — 27 validators, stable finding codes, adoption baseline for legacy repos, compliance-evidence reports, GitHub Action with PR annotations, spec-kit hooks. Pure Node.js, one pinned dep.",
+      "description": "The only doc-integrity engine with an MCP server, SARIF output, and a deterministic zero-LLM core. Validates, scores, and traces documentation against code — 24 validators, stable finding codes, GitHub Action with PR annotations, spec-kit hooks. Pure Node.js, one pinned dep.",
       "author": "raccioly",
-      "version": "0.33.0",
-      "download_url": "https://github.com/raccioly/docguard/releases/download/v0.33.0/spec-kit-docguard-v0.33.0.zip",
+      "version": "0.30.0",
+      "download_url": "https://github.com/raccioly/docguard/releases/download/v0.30.0/spec-kit-docguard-v0.30.0.zip",
       "repository": "https://github.com/raccioly/docguard",
       "homepage": "https://www.npmjs.com/package/docguard-cli",
       "documentation": "https://github.com/raccioly/docguard/blob/main/extensions/spec-kit-docguard/README.md",
@@ -1184,14 +1124,6 @@
             "name": "node",
             "version": ">=18.0.0",
             "required": true
-          },
-          {
-            "name": "npx",
-            "required": true
-          },
-          {
-            "name": "specify",
-            "required": false
           }
         ]
       },
@@ -1213,7 +1145,7 @@
       "downloads": 0,
       "stars": 0,
       "created_at": "2026-03-13T00:00:00Z",
-      "updated_at": "2026-07-16T00:00:00Z"
+      "updated_at": "2026-07-06T00:00:00Z"
     },
     "doctor": {
       "name": "Project Health Check",
@@ -1248,80 +1180,6 @@
       "created_at": "2026-03-13T00:00:00Z",
       "updated_at": "2026-03-13T00:00:00Z"
     },
-    "dotdog": {
-      "name": "Dotdog",
-      "id": "dotdog",
-      "description": "Import GitHub Spec Kit artifacts into local knowledge graphs for validation, analysis, search, and MCP queries.",
-      "author": "specdog",
-      "version": "0.9.0",
-      "download_url": "https://github.com/specdog/dotdog/releases/download/v0.9.0/dotdog-spec-kit-extension-v0.9.0.zip",
-      "repository": "https://github.com/specdog/dotdog",
-      "homepage": "https://specdog.github.io/dotdog",
-      "documentation": "https://github.com/specdog/dotdog/blob/main/docs/spec-kit-extension.md",
-      "changelog": "https://github.com/specdog/dotdog/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "docs",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.12.0",
-        "tools": [
-          {
-            "name": "dotdog",
-            "version": ">=0.9.0",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 0
-      },
-      "tags": [
-        "specification",
-        "knowledge-graph",
-        "validation",
-        "mcp",
-        "local-first"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-16T00:00:00Z",
-      "updated_at": "2026-07-16T00:00:00Z"
-    },
-    "ears": {
-      "name": "EARS Requirements Syntax",
-      "id": "ears",
-      "description": "Author, lint, and convert requirements using EARS (Easy Approach to Requirements Syntax) - the five industry-standard sentence patterns for unambiguous, testable requirements.",
-      "author": "dhruv-15-03",
-      "version": "1.0.0",
-      "download_url": "https://github.com/dhruv-15-03/spec-kit-ears/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/dhruv-15-03/spec-kit-ears",
-      "homepage": "https://github.com/dhruv-15-03/spec-kit-ears",
-      "documentation": "https://github.com/dhruv-15-03/spec-kit-ears/blob/main/README.md",
-      "changelog": "https://github.com/dhruv-15-03/spec-kit-ears/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "docs",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.9.0"
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 0
-      },
-      "tags": [
-        "ears",
-        "requirements",
-        "specification",
-        "quality"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-08T00:00:00Z",
-      "updated_at": "2026-07-08T00:00:00Z"
-    },
     "extensify": {
       "name": "Extensify",
       "id": "extensify",
@@ -1355,84 +1213,6 @@
       "created_at": "2026-03-18T00:00:00Z",
       "updated_at": "2026-04-23T00:00:00Z"
     },
-    "figma": {
-      "name": "Spec Kit Figma",
-      "id": "figma",
-      "description": "Agent-agnostic SpecKit extension that grounds spec, plan & task generation in Figma design context — REST + optional MCP, single/mono/multi-repo, macOS/Linux/Windows.",
-      "author": "Fyloss",
-      "version": "1.6.0",
-      "download_url": "https://github.com/Fyloss/spec-kit-figma/archive/refs/tags/v1.6.0.zip",
-      "repository": "https://github.com/Fyloss/spec-kit-figma",
-      "homepage": "https://github.com/Fyloss/spec-kit-figma",
-      "documentation": "https://github.com/Fyloss/spec-kit-figma/blob/main/docs/INSTALL.md",
-      "changelog": "https://github.com/Fyloss/spec-kit-figma/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "integration",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          { "name": "git", "required": true },
-          { "name": "bash", "required": false },
-          { "name": "curl", "required": false },
-          { "name": "jq", "required": false },
-          { "name": "pwsh", "required": false }
-        ]
-      },
-      "provides": {
-        "commands": 5,
-        "hooks": 6
-      },
-      "tags": [
-        "figma",
-        "design",
-        "frontend",
-        "ui",
-        "design-system"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-08T00:00:00Z",
-      "updated_at": "2026-07-08T00:00:00Z"
-    },
-    "figma-starter": {
-      "name": "Figma Starter",
-      "id": "figma-starter",
-      "description": "Turns a Figma section's screens into per-screen spec.md files, an app-level user-stories.md, and a build-order.md, then hands off to /speckit.specify.",
-      "author": "WaveMaker",
-      "version": "1.0.0",
-      "download_url": "https://github.com/wavemaker/spec-kit-figma-starter/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/wavemaker/spec-kit-figma-starter",
-      "homepage": "https://github.com/wavemaker/spec-kit-figma-starter",
-      "documentation": "https://github.com/wavemaker/spec-kit-figma-starter/blob/main/README.md",
-      "changelog": "https://github.com/wavemaker/spec-kit-figma-starter/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "integration",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          { "name": "python3", "version": ">=3.8", "required": true }
-        ]
-      },
-      "provides": {
-        "commands": 1,
-        "hooks": 1
-      },
-      "tags": [
-        "figma",
-        "design",
-        "design-to-spec",
-        "ui",
-        "frontend"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-15T00:00:00Z",
-      "updated_at": "2026-07-15T00:00:00Z"
-    },
     "fix-findings": {
       "name": "Fix Findings",
       "id": "fix-findings",
@@ -1573,58 +1353,6 @@
       "created_at": "2026-05-06T00:00:00Z",
       "updated_at": "2026-05-06T00:00:00Z"
     },
-    "gates": {
-      "name": "Quality Gates (Enforcement Layer)",
-      "id": "gates",
-      "description": "Deterministic quality enforcement for Spec Kit across agent hooks, git checks, and CI pipelines with one policy file and one verify entrypoint for identical results at every boundary.",
-      "author": "schwichtgit",
-      "version": "0.3.2",
-      "download_url": "https://github.com/schwichtgit/spec-gates/releases/download/v0.3.2/gates-0.3.2.zip",
-      "repository": "https://github.com/schwichtgit/spec-gates",
-      "homepage": "https://github.com/schwichtgit/spec-gates",
-      "documentation": "https://github.com/schwichtgit/spec-gates/blob/main/docs/how-it-works.md",
-      "changelog": "https://github.com/schwichtgit/spec-gates/releases",
-      "license": "MIT",
-      "category": "process",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.12.0",
-        "tools": [
-          {
-            "name": "jq",
-            "required": true
-          },
-          {
-            "name": "git",
-            "required": false
-          },
-          {
-            "name": "node",
-            "required": false
-          },
-          {
-            "name": "shellcheck",
-            "required": false
-          }
-        ]
-      },
-      "provides": {
-        "commands": 8,
-        "hooks": 2
-      },
-      "tags": [
-        "quality",
-        "enforcement",
-        "hooks",
-        "ci",
-        "governance"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-09T00:00:00Z",
-      "updated_at": "2026-07-15T00:00:00Z"
-    },
     "github-issues": {
       "name": "GitHub Issues Integration 1",
       "id": "github-issues",
@@ -1670,10 +1398,10 @@
     "golden-demo": {
       "name": "Golden Demo",
       "id": "golden-demo",
-      "description": "Deterministic behavioral drift oracle. Extracts acceptance criteria, generates fuzz test vectors (seed=42), compares golden Python implementations against real code in any language. CI/CD gatekeeper with warn/strict modes.",
+      "description": "Extracts acceptance criteria from specs, builds test vectors, and produces a behavioral drift report — complementary to Architecture Guard and CDD.",
       "author": "jasstt",
-      "version": "0.3.0",
-      "download_url": "https://github.com/jasstt/spec-kit-golden-demo/archive/refs/tags/v0.3.0.zip",
+      "version": "0.1.1",
+      "download_url": "https://github.com/jasstt/spec-kit-golden-demo/archive/refs/tags/v0.1.1.zip",
       "repository": "https://github.com/jasstt/spec-kit-golden-demo",
       "homepage": "https://github.com/jasstt/spec-kit-golden-demo",
       "documentation": "https://github.com/jasstt/spec-kit-golden-demo",
@@ -1684,16 +1412,13 @@
         "speckit_version": ">=0.1.0"
       },
       "provides": {
-        "commands": 3,
+        "commands": 2,
         "hooks": 2
       },
       "tags": [
         "testing",
         "drift-detection",
         "behavioral-oracle",
-        "fuzzing",
-        "ci-cd",
-        "cross-language",
         "tdd",
         "quality"
       ],
@@ -1701,7 +1426,7 @@
       "downloads": 0,
       "stars": 0,
       "created_at": "2026-06-24T00:00:00Z",
-      "updated_at": "2026-07-07T00:00:00Z"
+      "updated_at": "2026-06-24T00:00:00Z"
     },
     "harness": {
       "name": "Research Harness",
@@ -2415,42 +2140,6 @@
       "created_at": "2026-05-08T00:00:00Z",
       "updated_at": "2026-05-08T00:00:00Z"
     },
-    "memory": {
-      "name": "Spec Kit Memory",
-      "id": "memory",
-      "description": "Recalls prior specs and decisions from configurable memory tools (e.g. memsearch) before SDLC stages, so planning and specification start from what the project already knows.",
-      "author": "Andrey Zaytsev",
-      "version": "0.3.0",
-      "download_url": "https://github.com/zaytsevand/spec-kit-memory/archive/refs/tags/v0.3.0.zip",
-      "repository": "https://github.com/zaytsevand/spec-kit-memory",
-      "homepage": "https://github.com/zaytsevand/spec-kit-memory",
-      "documentation": "https://github.com/zaytsevand/spec-kit-memory/blob/main/README.md",
-      "changelog": "",
-      "license": "MIT",
-      "category": "docs",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.2.0",
-        "tools": [
-          { "name": "memsearch", "required": false }
-        ]
-      },
-      "provides": {
-        "commands": 2,
-        "hooks": 3
-      },
-      "tags": [
-        "memory",
-        "recall",
-        "research",
-        "memsearch"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-10T00:00:00Z",
-      "updated_at": "2026-07-10T00:00:00Z"
-    },
     "memory-loader": {
       "name": "Memory Loader",
       "id": "memory-loader",
@@ -2605,48 +2294,6 @@
       "created_at": "2026-05-04T02:51:52Z",
       "updated_at": "2026-06-18T00:00:00Z"
     },
-    "multi-repo-sync": {
-      "name": "Multi-Repo Branch Sync",
-      "id": "multi-repo-sync",
-      "description": "Creates the feature branch in affected sub-repositories and git submodules via plan/tasks hooks",
-      "author": "Fyloss",
-      "version": "1.0.0",
-      "download_url": "https://github.com/fyloss/spec-kit-multi-repo-sync/releases/download/v1.0.0/spec-kit-multi-repo-sync.zip",
-      "sha256": "12a5c7392145b4424b20715aaa3d8b6a8218c143dea596873e344146c1a76ba0",
-      "repository": "https://github.com/fyloss/spec-kit-multi-repo-sync",
-      "homepage": "https://github.com/fyloss/spec-kit-multi-repo-sync",
-      "documentation": "https://github.com/fyloss/spec-kit-multi-repo-sync/blob/main/README.md",
-      "changelog": "https://github.com/fyloss/spec-kit-multi-repo-sync/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "process",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.2.0",
-        "tools": [
-          {
-            "name": "git",
-            "version": ">=2.31",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 2
-      },
-      "tags": [
-        "git",
-        "branching",
-        "multi-repo",
-        "submodules",
-        "workflow"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-13T00:00:00Z",
-      "updated_at": "2026-07-13T00:00:00Z"
-    },
     "multi-sites": {
       "name": "Multi-Sites Spec Kit",
       "id": "multi-sites",
@@ -2816,46 +2463,6 @@
       "created_at": "2026-04-24T14:00:00Z",
       "updated_at": "2026-04-24T14:00:00Z"
     },
-    "patchwarden-evidence": {
-      "name": "PatchWarden Evidence Pack",
-      "id": "patchwarden-evidence",
-      "description": "Map Spec Kit tasks into a guarded PatchWarden Goal and export bounded, traceable evidence for an accepted lineage.",
-      "author": "Zengjie",
-      "version": "1.0.1",
-      "download_url": "https://github.com/jiezeng2004-design/spec-kit-patchwarden/archive/refs/tags/v1.0.1.zip",
-      "repository": "https://github.com/jiezeng2004-design/spec-kit-patchwarden",
-      "homepage": "https://github.com/jiezeng2004-design/spec-kit-patchwarden",
-      "documentation": "https://github.com/jiezeng2004-design/spec-kit-patchwarden/blob/main/README.md",
-      "changelog": "https://github.com/jiezeng2004-design/spec-kit-patchwarden/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "process",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          {
-            "name": "patchwarden",
-            "version": ">=1.5.1",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 2,
-        "hooks": 2
-      },
-      "tags": [
-        "verification",
-        "evidence",
-        "traceability",
-        "security"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-14T00:00:00Z",
-      "updated_at": "2026-07-14T00:00:00Z"
-    },
     "plan-review-gate": {
       "name": "Plan Review Gate",
       "id": "plan-review-gate",
@@ -4672,40 +4279,6 @@
       "created_at": "2026-03-03T00:00:00Z",
       "updated_at": "2026-04-09T00:00:00Z"
     },
-    "verify-review-ship": {
-      "name": "Verify Review Ship",
-      "id": "verify-review-ship",
-      "description": "Adds post-implementation verify, review, and ship readiness gates to Spec Kit workflows.",
-      "author": "Carlos Eduardo Gevaerd Araujo",
-      "version": "0.1.0",
-      "download_url": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/archive/refs/tags/v0.1.0.zip",
-      "repository": "https://github.com/cadugevaerd/spec-kit-verify-review-ship",
-      "homepage": "https://github.com/cadugevaerd/spec-kit-verify-review-ship",
-      "documentation": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/blob/main/README.md",
-      "changelog": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "process",
-      "effect": "read-only",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 1
-      },
-      "tags": [
-        "quality",
-        "review",
-        "shipping",
-        "workflow",
-        "testing"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-10T00:00:00Z",
-      "updated_at": "2026-07-10T00:00:00Z"
-    },
     "verify-tasks": {
       "name": "Verify Tasks Extension",
       "id": "verify-tasks",
@@ -4802,40 +4375,6 @@
       "created_at": "2026-04-13T00:00:00Z",
       "updated_at": "2026-04-13T00:00:00Z"
     },
-    "wiki": {
-      "name": "LLM Wiki",
-      "id": "wiki",
-      "description": "LLM-maintained compounding project wiki: source ingestion, cited answers, and consistency linting",
-      "author": "formin",
-      "version": "1.0.0",
-      "download_url": "https://github.com/formin/spec-kit-wiki/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/formin/spec-kit-wiki",
-      "homepage": "https://github.com/formin/spec-kit-wiki",
-      "documentation": "https://github.com/formin/spec-kit-wiki/blob/main/README.md",
-      "changelog": "https://github.com/formin/spec-kit-wiki/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "docs",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.2.0"
-      },
-      "provides": {
-        "commands": 5,
-        "hooks": 2
-      },
-      "tags": [
-        "wiki",
-        "knowledge-base",
-        "docs",
-        "memory",
-        "context-management"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-06T00:00:00Z",
-      "updated_at": "2026-07-06T00:00:00Z"
-    },
     "wireframe": {
       "name": "Wireframe Visual Feedback Loop",
       "id": "wireframe",

extensions/catalog.json

@@ -48,4 +48,4 @@
       ]
     }
   }
-}
+}

extensions/git/scripts/powershell/create-new-feature-branch.ps1

@@ -41,16 +41,6 @@ if ($Help) {
     exit 0
 }
 
-# -Number is [long], so PowerShell binds "-5" as -5 rather than rejecting it
-# the way the bash/Python twins do (`^[0-9]+$`). A negative value would format
-# via '{0:000}' to e.g. "-005" and produce a branch name starting with "-",
-# which git refuses (refs cannot begin with a dash). Reject it here, before the
-# description check, matching the bash twin's parse-time validation order.
-if ($Number -lt 0) {
-    Write-Error 'Error: --number must be a non-negative integer'
-    exit 1
-}
-
 if (-not $FeatureDescription -or $FeatureDescription.Count -eq 0) {
     Write-Error "Usage: ./create-new-feature-branch.ps1 [-Json] [-DryRun] [-AllowExistingBranch] [-ShortName <name>] [-Number N] [-Timestamp] <feature description>"
     exit 1
@@ -456,10 +446,7 @@ if ($env:GIT_BRANCH_NAME) {
         $branchSuffix = Get-BranchName -Description $featureDesc
     }
 
-    # Warn if -Number and -Timestamp are both specified. Use ContainsKey (not
-    # `-ne 0`) so an explicit `-Number 0` is also detected, matching the bash twin's
-    # `[ -n "$BRANCH_NUMBER" ]` check.
-    if ($Timestamp -and $PSBoundParameters.ContainsKey('Number')) {
+    if ($Timestamp -and $Number -ne 0) {
         Write-Warning "[specify] Warning: -Number is ignored when -Timestamp is used"
         $Number = 0
     }
@@ -469,10 +456,7 @@ if ($env:GIT_BRANCH_NAME) {
         $branchName = New-BranchName -FeatureNum $featureNum -BranchSuffix $branchSuffix
     } else {
         $branchScopePrefix = Get-BranchScopePrefix -Template $branchTemplate -BranchSuffix $branchSuffix
-        # Auto-detect the next number only when -Number was not supplied; an
-        # explicit value (including 0) is honored, matching the bash twin's
-        # `[ -z "$BRANCH_NUMBER" ]` check.
-        if (-not $PSBoundParameters.ContainsKey('Number')) {
+        if ($Number -eq 0) {
             if ($DryRun -and $hasGit) {
                 $Number = Get-NextBranchNumber -SpecsDir $specsDir -SkipFetch -ScopePrefix $branchScopePrefix
             } elseif ($DryRun) {

extensions/git/scripts/python/auto_commit.py

@@ -1,187 +0,0 @@
-#!/usr/bin/env python3
-"""Git extension: auto_commit.py
-
-Automatically commit changes after a Spec Kit command completes.
-Python port of ``auto-commit.sh`` / ``auto-commit.ps1``.
-Checks per-command config keys in git-config.yml before committing.
-
-Usage: auto_commit.py <event_name>
-  e.g.: auto_commit.py after_specify
-"""
-
-from __future__ import annotations
-
-import re
-import shutil
-import subprocess
-import sys
-from pathlib import Path
-
-
-def _find_project_root(start: Path) -> Path | None:
-    current = start
-    while True:
-        if (current / ".specify").is_dir() or (current / ".git").exists():
-            return current
-        if current.parent == current:
-            return None
-        current = current.parent
-
-
-def _value_after_colon(line: str) -> str:
-    return re.sub(r"^[^:]*:\s*", "", line)
-
-
-def _strip_quotes(value: str) -> str:
-    """Strip one leading quote and all trailing quotes, mirroring the bash sed."""
-    value = re.sub(r"^[\"']", "", value)
-    return re.sub(r"[\"']*$", "", value)
-
-
-def _parse_auto_commit_config(
-    config_file: Path, event_name: str
-) -> tuple[bool, str]:
-    """Parse the auto_commit section for this event, mirroring the bash line parser.
-
-    Returns (enabled, commit_msg). Looks for auto_commit.<event_name>.enabled
-    and .message, with auto_commit.default as fallback.
-    """
-    enabled = False
-    commit_msg = ""
-    default_enabled = False
-    in_auto_commit = False
-    in_event = False
-
-    try:
-        content = config_file.read_text(encoding="utf-8")
-    except (OSError, UnicodeDecodeError):
-        # Unreadable or non-UTF-8 config is treated like a missing one:
-        # auto-commit stays disabled instead of crashing with a traceback.
-        return False, ""
-    for record in content.splitlines(keepends=True):
-        if not record.endswith("\n"):
-            break
-        line = record[:-1]
-        if line.startswith("auto_commit:"):
-            in_auto_commit = True
-            in_event = False
-            continue
-
-        # Exit auto_commit section on next top-level key
-        if in_auto_commit and re.match(r"^[a-z]", line):
-            break
-
-        if not in_auto_commit:
-            continue
-
-        if re.match(r"^\s+default:\s", line):
-            value = re.sub(r"\s", "", _value_after_colon(line)).lower()
-            if value == "true":
-                default_enabled = True
-
-        if re.match(rf"^\s+{re.escape(event_name)}:", line):
-            in_event = True
-            continue
-
-        if in_event:
-            # Exit on next sibling key (same indent level as event name)
-            if re.match(r"^\s{2}[a-z]", line) and not re.match(r"^\s{4}", line):
-                in_event = False
-                continue
-            if re.search(r"\s+enabled:", line):
-                value = re.sub(r"\s", "", _value_after_colon(line)).lower()
-                if value == "true":
-                    enabled = True
-                elif value == "false":
-                    enabled = False
-            if re.search(r"\s+message:", line):
-                commit_msg = _strip_quotes(_value_after_colon(line))
-
-    # If event-specific key not found, use default — but only if the event
-    # section didn't exist at all (an explicit false must win).
-    if not enabled and default_enabled:
-        if not re.search(rf"^\s*{re.escape(event_name)}:", content, re.MULTILINE):
-            enabled = True
-
-    return enabled, commit_msg
-
-
-def main(argv: list[str]) -> int:
-    event_name = argv[0] if argv else ""
-    if not event_name:
-        print(f"Usage: {Path(sys.argv[0]).name} <event_name>", file=sys.stderr)
-        return 1
-
-    script_dir = Path(__file__).resolve().parent
-    repo_root = _find_project_root(script_dir) or Path.cwd()
-
-    if shutil.which("git") is None:
-        print("[specify] Warning: Git not found; skipped auto-commit", file=sys.stderr)
-        return 0
-
-    probe = subprocess.run(
-        ["git", "rev-parse", "--is-inside-work-tree"],
-        cwd=repo_root,
-        capture_output=True,
-        text=True,
-    )
-    if probe.returncode != 0:
-        print(
-            "[specify] Warning: Not a Git repository; skipped auto-commit",
-            file=sys.stderr,
-        )
-        return 0
-
-    config_file = repo_root / ".specify" / "extensions" / "git" / "git-config.yml"
-    if not config_file.is_file():
-        # No config file — auto-commit disabled by default
-        return 0
-
-    enabled, commit_msg = _parse_auto_commit_config(config_file, event_name)
-    if not enabled:
-        return 0
-
-    # Check if there are changes to commit
-    def _quiet(*args: str) -> bool:
-        return (
-            subprocess.run(
-                ["git", *args], cwd=repo_root, capture_output=True, text=True
-            ).returncode
-            == 0
-        )
-
-    untracked = subprocess.run(
-        ["git", "ls-files", "--others", "--exclude-standard"],
-        cwd=repo_root,
-        capture_output=True,
-        text=True,
-    ).stdout.strip()
-    if _quiet("diff", "--quiet", "HEAD") and _quiet("diff", "--cached", "--quiet") and not untracked:
-        print(f"[specify] No changes to commit after {event_name}", file=sys.stderr)
-        return 0
-
-    # Derive a human-readable command name from the event
-    # e.g., after_specify -> specify, before_plan -> plan
-    command_name = re.sub(r"^(after_|before_)", "", event_name)
-    phase = "before" if event_name.startswith("before_") else "after"
-
-    if not commit_msg:
-        commit_msg = f"[Spec Kit] Auto-commit {phase} {command_name}"
-
-    steps = [
-        (["git", "add", "."], "git add"),
-        (["git", "commit", "-q", "-m", commit_msg], "git commit"),
-    ]
-    for cmd, label in steps:
-        result = subprocess.run(cmd, cwd=repo_root, capture_output=True, text=True)
-        if result.returncode != 0:
-            output = (result.stdout + result.stderr).strip()
-            print(f"[specify] Error: {label} failed: {output}", file=sys.stderr)
-            return 1
-
-    print(f"[OK] Changes committed {phase} {command_name}", file=sys.stderr)
-    return 0
-
-
-if __name__ == "__main__":
-    raise SystemExit(main(sys.argv[1:]))

extensions/git/scripts/python/create_new_feature_branch.py

@@ -1,634 +0,0 @@
-#!/usr/bin/env python3
-"""Git extension: create_new_feature_branch.py
-
-Creates a git feature branch only. The feature directory and spec file are
-created by the core create-new-feature script. Python port of
-``create-new-feature-branch.sh`` / ``create-new-feature-branch.ps1``.
-
-Loads the core Python helpers from the project's installed scripts when
-available, falling back to the minimal git helpers next to this script.
-"""
-
-from __future__ import annotations
-
-import importlib.util
-import json
-import os
-import re
-import shutil
-import subprocess
-import sys
-from dataclasses import dataclass, field
-from datetime import datetime
-from pathlib import Path
-
-SCRIPT_DIR = Path(__file__).resolve().parent
-MAX_BRANCH_LENGTH = 244  # GitHub enforces a 244-byte limit on branch names
-
-USAGE = (
-    "Usage: create_new_feature_branch.py [--json] [--dry-run] "
-    "[--allow-existing-branch] [--short-name <name>] [--number N] "
-    "[--timestamp] <feature_description>"
-)
-
-HELP_TEXT = f"""{USAGE}
-
-Options:
-  --json              Output in JSON format
-  --dry-run           Compute branch name without creating the branch
-  --allow-existing-branch  Switch to branch if it already exists instead of failing
-  --short-name <name> Provide a custom short name (2-4 words) for the branch
-  --number N          Specify branch number manually (overrides auto-detection)
-  --timestamp         Use timestamp prefix (YYYYMMDD-HHMMSS) instead of sequential numbering
-  --help, -h          Show this help message
-
-Environment variables:
-  GIT_BRANCH_NAME     Use this exact branch name, bypassing all prefix/suffix generation
-
-Configuration:
-  branch_template     Optional git-config.yml template with {{author}}, {{app}}, {{number}}, {{slug}}
-  branch_prefix       Optional shorthand namespace expanded before {{number}}-{{slug}}
-
-Examples:
-  create_new_feature_branch.py 'Add user authentication system' --short-name 'user-auth'
-  create_new_feature_branch.py 'Implement OAuth2 integration for API' --number 5
-  create_new_feature_branch.py --timestamp --short-name 'user-auth' 'Add user authentication'
-  GIT_BRANCH_NAME=my-branch create_new_feature_branch.py 'feature description'
-"""
-
-STOP_WORDS = frozenset(
-    "i a an the to for of in on at by with from is are was were be been being "
-    "have has had do does did will would should could can may might must shall "
-    "this that these those my your our their want need add get set".split()
-)
-
-
-def _err(message: str) -> None:
-    print(message, file=sys.stderr)
-
-
-def _persist_hint(var_name: str, value: str) -> str:
-    """Shell-appropriate guidance for persisting an env var in the caller's shell."""
-    if os.name == "nt":
-        escaped_value = value.replace("'", "''")
-        return f"$env:{var_name} = '{escaped_value}'"
-    escaped_value = re.sub(r"([^\w@%+=:,./-])", r"\\\1", value)
-    return f"export {var_name}={escaped_value}"
-
-
-@dataclass
-class Args:
-    json_mode: bool = False
-    dry_run: bool = False
-    allow_existing: bool = False
-    short_name: str = ""
-    branch_number: str = ""
-    use_timestamp: bool = False
-    description_parts: list[str] = field(default_factory=list)
-
-
-def parse_args(argv: list[str]) -> Args:
-    args = Args()
-    i = 0
-    while i < len(argv):
-        arg = argv[i]
-        if arg == "--json":
-            args.json_mode = True
-        elif arg == "--dry-run":
-            args.dry_run = True
-        elif arg == "--allow-existing-branch":
-            args.allow_existing = True
-        elif arg == "--short-name":
-            if i + 1 >= len(argv) or argv[i + 1].startswith("--"):
-                _err("Error: --short-name requires a value")
-                raise SystemExit(1)
-            i += 1
-            args.short_name = argv[i]
-        elif arg == "--number":
-            if i + 1 >= len(argv) or argv[i + 1].startswith("--"):
-                _err("Error: --number requires a value")
-                raise SystemExit(1)
-            i += 1
-            args.branch_number = argv[i]
-            if not re.fullmatch(r"[0-9]+", args.branch_number):
-                _err("Error: --number must be a non-negative integer")
-                raise SystemExit(1)
-        elif arg == "--timestamp":
-            args.use_timestamp = True
-        elif arg in ("--help", "-h"):
-            print(HELP_TEXT)
-            raise SystemExit(0)
-        else:
-            args.description_parts.append(arg)
-        i += 1
-    return args
-
-
-# ── Core helpers loading ─────────────────────────────────────────────────────
-
-
-def _find_project_root(start: Path) -> Path | None:
-    current = start
-    while True:
-        if (current / ".specify").is_dir() or (current / ".git").exists():
-            return current
-        if current.parent == current:
-            return None
-        current = current.parent
-
-
-def _load_core_common(project_root: Path | None):
-    """Load the core common.py from the project's installed scripts.
-
-    Search locations in priority order, mirroring the bash script:
-     1. .specify/scripts/python/common.py (installed project)
-     2. scripts/python/common.py (source checkout fallback)
-    Returns the loaded module or None.
-    """
-    if project_root is None:
-        return None
-    for relative in (".specify/scripts/python/common.py", "scripts/python/common.py"):
-        candidate = project_root / relative
-        if candidate.is_file():
-            spec = importlib.util.spec_from_file_location("speckit_core_common", candidate)
-            if spec is None or spec.loader is None:
-                continue
-            module = importlib.util.module_from_spec(spec)
-            sys.modules[spec.name] = module
-            spec.loader.exec_module(module)
-            return module
-    return None
-
-
-def _local_has_git(repo_root: Path) -> bool:
-    git_marker = repo_root / ".git"
-    if not (git_marker.is_dir() or git_marker.is_file()):
-        return False
-    if shutil.which("git") is None:
-        return False
-    return (
-        subprocess.run(
-            ["git", "-C", str(repo_root), "rev-parse", "--is-inside-work-tree"],
-            capture_output=True,
-            text=True,
-        ).returncode
-        == 0
-    )
-
-
-# ── Numbering ────────────────────────────────────────────────────────────────
-
-
-def get_highest_from_specs(specs_dir: Path) -> int:
-    highest = 0
-    if specs_dir.is_dir():
-        for entry in specs_dir.iterdir():
-            if not entry.is_dir():
-                continue
-            name = entry.name
-            # Match sequential prefixes (>=3 digits), but skip timestamp dirs.
-            if re.match(r"^[0-9]{3,}-", name) and not re.match(
-                r"^[0-9]{8}-[0-9]{6}-", name
-            ):
-                number = int(re.match(r"^[0-9]+", name).group(0))
-                highest = max(highest, number)
-    return highest
-
-
-def _extract_highest_number(names: list[str], scope_prefix: str) -> int:
-    """Extract the highest sequential feature number from a list of ref names."""
-    highest = 0
-    for name in names:
-        if not name:
-            continue
-        if scope_prefix:
-            if not name.startswith(scope_prefix):
-                continue
-            name = name[len(scope_prefix) :]
-        name = name.rsplit("/", 1)[-1]
-        if (
-            re.match(r"^[0-9]{3,}-", name)
-            and not re.match(r"^[0-9]{8}-[0-9]{6}-", name)
-            and not re.match(r"^[0-9]{7}-[0-9]{6}-", name)
-            and not re.fullmatch(r"[0-9]{7,8}-[0-9]{6}", name)
-        ):
-            match = re.match(r"^([0-9]{3,})-", name)
-            number = int(match.group(1)) if match else 0
-            highest = max(highest, number)
-    return highest
-
-
-def _git_lines(repo_root: Path, *args: str, env_extra: dict | None = None) -> list[str]:
-    if shutil.which("git") is None:
-        return []
-    env = {**os.environ, **(env_extra or {})}
-    result = subprocess.run(
-        ["git", *args], cwd=repo_root, capture_output=True, text=True, env=env
-    )
-    if result.returncode != 0:
-        return []
-    return result.stdout.splitlines()
-
-
-def get_highest_from_branches(repo_root: Path, scope_prefix: str) -> int:
-    names = []
-    for line in _git_lines(repo_root, "branch", "-a"):
-        line = re.sub(r"^[+*]\s+", "", line)
-        line = line.lstrip()
-        line = re.sub(r"^remotes/[^/]*/", "", line)
-        names.append(line)
-    return _extract_highest_number(names, scope_prefix)
-
-
-def get_highest_from_remote_refs(repo_root: Path, scope_prefix: str) -> int:
-    """Highest number from remote branches without fetching (side-effect-free)."""
-    highest = 0
-    for remote in _git_lines(repo_root, "remote"):
-        refs = _git_lines(
-            repo_root,
-            "ls-remote",
-            "--heads",
-            remote,
-            env_extra={"GIT_TERMINAL_PROMPT": "0"},
-        )
-        names = [re.sub(r".*refs/heads/", "", ref) for ref in refs]
-        highest = max(highest, _extract_highest_number(names, scope_prefix))
-    return highest
-
-
-def check_existing_branches(
-    repo_root: Path, specs_dir: Path, skip_fetch: bool, scope_prefix: str
-) -> int:
-    """Check existing branches and return the next available number."""
-    if skip_fetch:
-        highest_branch = max(
-            get_highest_from_remote_refs(repo_root, scope_prefix),
-            get_highest_from_branches(repo_root, scope_prefix),
-        )
-    else:
-        subprocess.run(
-            ["git", "fetch", "--all", "--prune"],
-            cwd=repo_root,
-            capture_output=True,
-            text=True,
-        )
-        highest_branch = get_highest_from_branches(repo_root, scope_prefix)
-
-    return max(highest_branch, get_highest_from_specs(specs_dir)) + 1
-
-
-# ── Branch naming ────────────────────────────────────────────────────────────
-
-
-def clean_branch_name(name: str) -> str:
-    name = re.sub(r"[^a-z0-9]", "-", name.lower())
-    name = re.sub(r"-+", "-", name)
-    return name.strip("-")
-
-
-def generate_branch_name(description: str) -> str:
-    """Generate a branch suffix from the description with stop word filtering."""
-    clean_name = re.sub(r"[^a-z0-9]", " ", description.lower())
-
-    meaningful_words = []
-    for word in clean_name.split():
-        if word in STOP_WORDS:
-            continue
-        if len(word) >= 3:
-            meaningful_words.append(word)
-        # Keep short words only when they appear uppercased in the original
-        # description (acronyms like "API" or "DB").
-        elif re.search(rf"\b{re.escape(word.upper())}\b", description):
-            meaningful_words.append(word)
-
-    if meaningful_words:
-        max_words = 4 if len(meaningful_words) == 4 else 3
-        return "-".join(meaningful_words[:max_words])
-
-    cleaned = clean_branch_name(description)
-    return "-".join([part for part in cleaned.split("-") if part][:3])
-
-
-def branch_token(value: str, fallback: str) -> str:
-    cleaned = clean_branch_name(value)
-    return cleaned if cleaned else fallback
-
-
-def get_author_token(repo_root: Path) -> str:
-    author = ""
-    if shutil.which("git") is not None:
-        lines = _git_lines(repo_root, "config", "user.name")
-        author = lines[0] if lines else ""
-        if not author:
-            lines = _git_lines(repo_root, "config", "user.email")
-            email = lines[0] if lines else ""
-            author = email.split("@")[0]
-    if not author:
-        author = os.environ.get("USER") or os.environ.get("USERNAME") or "unknown"
-    return branch_token(author, "unknown")
-
-
-def get_app_token(repo_root: Path) -> str:
-    return branch_token(repo_root.name, "app")
-
-
-def read_git_config_value(config_file: Path, key: str) -> str:
-    if not config_file.is_file():
-        return ""
-    try:
-        lines = config_file.read_text(encoding="utf-8").splitlines()
-    except (OSError, UnicodeDecodeError):
-        return ""
-    for line in lines:
-        if re.match(rf"^\s*{re.escape(key)}:", line):
-            value = re.sub(rf"^\s*{re.escape(key)}:\s*", "", line)
-            value = re.sub(r"\s+#.*$", "", value)
-            value = value.strip()
-            value = re.sub(r'^"|"$', "", value)
-            value = re.sub(r"^'|'$", "", value)
-            return value
-    return ""
-
-
-def resolve_branch_template(config_file: Path) -> str:
-    template = read_git_config_value(config_file, "branch_template")
-    if template:
-        return template
-
-    prefix = read_git_config_value(config_file, "branch_prefix")
-    if not prefix:
-        return ""
-    if prefix.endswith("/"):
-        return f"{prefix}{{number}}-{{slug}}"
-    return f"{prefix}/{{number}}-{{slug}}"
-
-
-def validate_branch_template(template: str) -> None:
-    if not template:
-        return
-    if "{number}" not in template:
-        _err(
-            "Error: branch_template must include the {number} token so generated "
-            "branches remain valid feature branches."
-        )
-        raise SystemExit(1)
-    slug_index = template.find("{slug}")
-    if slug_index != -1 and "{number}" in template[slug_index:]:
-        _err(
-            "Error: branch_template must not place {slug} before {number}; "
-            "use {slug} only in the final feature segment."
-        )
-        raise SystemExit(1)
-    feature_segment = template.rsplit("/", 1)[-1]
-    if not feature_segment.startswith("{number}-"):
-        _err(
-            "Error: branch_template must put {number}- at the start of the final "
-            "path segment so generated branches remain valid feature branches."
-        )
-        raise SystemExit(1)
-
-
-def render_branch_template(
-    template: str, feature_num: str, branch_suffix: str, author_token: str, app_token: str
-) -> str:
-    rendered = template
-    rendered = rendered.replace("{author}", author_token)
-    rendered = rendered.replace("{app}", app_token)
-    rendered = rendered.replace("{number}", feature_num)
-    rendered = rendered.replace("{slug}", branch_suffix)
-    return rendered
-
-
-def extract_feature_num_from_branch(branch_name: str) -> str:
-    feature_segment = branch_name.rsplit("/", 1)[-1]
-    match = re.match(r"^[0-9]{8}-[0-9]{6}-", feature_segment)
-    if match:
-        return match.group(0).rstrip("-")
-    match = re.match(r"^[0-9]+-", feature_segment)
-    if match:
-        return match.group(0).rstrip("-")
-    return branch_name
-
-
-def _byte_length(value: str) -> int:
-    return len(value.encode("utf-8"))
-
-
-# ── Main ─────────────────────────────────────────────────────────────────────
-
-
-def main(argv: list[str]) -> int:
-    args = parse_args(argv)
-
-    feature_description = " ".join(args.description_parts)
-    if not feature_description:
-        _err(USAGE)
-        return 1
-    feature_description = feature_description.strip()
-    if not feature_description:
-        _err("Error: Feature description cannot be empty or contain only whitespace")
-        return 1
-
-    project_root = _find_project_root(SCRIPT_DIR)
-    core = _load_core_common(project_root)
-
-    # SPECIFY_INIT_DIR is resolved (and validated) by the core resolver. If the
-    # core helpers were not found, refuse rather than silently falling back to
-    # the wrong root.
-    if os.environ.get("SPECIFY_INIT_DIR") and (
-        core is None or not hasattr(core, "resolve_specify_init_dir")
-    ):
-        _err(
-            "Error: SPECIFY_INIT_DIR requires updated Spec Kit core scripts "
-            "(common.py with resolve_specify_init_dir), which were not found."
-        )
-        return 1
-
-    if core is not None and hasattr(core, "get_repo_root"):
-        # Pass script path so cwd-outside-repo callers land on the same
-        # fallback the bash twin does. Older cores don't accept the kwarg —
-        # fall back to the no-arg call for compatibility.
-        try:
-            repo_root = core.get_repo_root(script_file=Path(__file__))
-        except TypeError:
-            repo_root = core.get_repo_root()
-    else:
-        toplevel = _git_lines(Path.cwd(), "rev-parse", "--show-toplevel")
-        if toplevel:
-            repo_root = Path(toplevel[0])
-        elif project_root is not None:
-            repo_root = project_root
-        else:
-            _err("Error: Could not determine repository root.")
-            return 1
-    repo_root = Path(repo_root)
-
-    has_git_repo = _local_has_git(repo_root)
-
-    specs_dir = repo_root / "specs"
-    config_file = repo_root / ".specify" / "extensions" / "git" / "git-config.yml"
-
-    author_token = get_author_token(repo_root)
-    app_token = get_app_token(repo_root)
-    branch_template = resolve_branch_template(config_file)
-    validate_branch_template(branch_template)
-
-    def build_branch_name(feature_num: str, branch_suffix: str) -> str:
-        if branch_template:
-            return render_branch_template(
-                branch_template, feature_num, branch_suffix, author_token, app_token
-            )
-        return f"{feature_num}-{branch_suffix}"
-
-    branch_number = args.branch_number
-
-    # Check for GIT_BRANCH_NAME env var override (exact name, no prefix/suffix)
-    env_branch_name = os.environ.get("GIT_BRANCH_NAME", "")
-    if env_branch_name:
-        branch_name = env_branch_name
-        feature_num = extract_feature_num_from_branch(branch_name)
-        branch_suffix = branch_name
-    else:
-        if args.short_name:
-            branch_suffix = clean_branch_name(args.short_name)
-        else:
-            branch_suffix = generate_branch_name(feature_description)
-
-        if args.use_timestamp and branch_number:
-            _err("[specify] Warning: --number is ignored when --timestamp is used")
-            branch_number = ""
-
-        if args.use_timestamp:
-            feature_num = datetime.now().strftime("%Y%m%d-%H%M%S")
-            branch_name = build_branch_name(feature_num, branch_suffix)
-        else:
-            scope_prefix = ""
-            if branch_template:
-                prefix_template = branch_template.split("{number}")[0]
-                scope_prefix = render_branch_template(
-                    prefix_template, "", branch_suffix, author_token, app_token
-                )
-            if not branch_number:
-                if args.dry_run and has_git_repo:
-                    branch_number = check_existing_branches(
-                        repo_root, specs_dir, True, scope_prefix
-                    )
-                elif args.dry_run:
-                    branch_number = get_highest_from_specs(specs_dir) + 1
-                elif has_git_repo:
-                    branch_number = check_existing_branches(
-                        repo_root, specs_dir, False, scope_prefix
-                    )
-                else:
-                    branch_number = get_highest_from_specs(specs_dir) + 1
-
-            feature_num = f"{int(branch_number):03d}"
-            branch_name = build_branch_name(feature_num, branch_suffix)
-
-    branch_byte_len = _byte_length(branch_name)
-    if env_branch_name and branch_byte_len > MAX_BRANCH_LENGTH:
-        _err(
-            "Error: GIT_BRANCH_NAME must be 244 bytes or fewer in UTF-8. "
-            f"Provided value is {branch_byte_len} bytes."
-        )
-        return 1
-    if branch_byte_len > MAX_BRANCH_LENGTH:
-        original_branch_name = branch_name
-        truncated_suffix = branch_suffix
-        while _byte_length(branch_name) > MAX_BRANCH_LENGTH and truncated_suffix:
-            truncated_suffix = truncated_suffix[:-1]
-            truncated_suffix = truncated_suffix.rstrip("-")
-            branch_name = build_branch_name(feature_num, truncated_suffix)
-        if _byte_length(branch_name) > MAX_BRANCH_LENGTH:
-            _err("Error: Branch template prefix exceeds GitHub's 244-byte branch name limit.")
-            return 1
-
-        _err("[specify] Warning: Branch name exceeded GitHub's 244-byte limit")
-        _err(
-            f"[specify] Original: {original_branch_name} "
-            f"({_byte_length(original_branch_name)} bytes)"
-        )
-        _err(f"[specify] Truncated to: {branch_name} ({_byte_length(branch_name)} bytes)")
-
-    if not args.dry_run:
-        if has_git_repo:
-            create = subprocess.run(
-                ["git", "checkout", "-q", "-b", branch_name],
-                cwd=repo_root,
-                capture_output=True,
-                text=True,
-            )
-            if create.returncode != 0:
-                current_branch_lines = _git_lines(
-                    repo_root, "rev-parse", "--abbrev-ref", "HEAD"
-                )
-                current_branch = current_branch_lines[0] if current_branch_lines else ""
-                branch_exists = bool(
-                    _git_lines(repo_root, "branch", "--list", branch_name)
-                )
-                if branch_exists:
-                    if args.allow_existing:
-                        if current_branch != branch_name:
-                            switch = subprocess.run(
-                                ["git", "checkout", "-q", branch_name],
-                                cwd=repo_root,
-                                capture_output=True,
-                                text=True,
-                            )
-                            if switch.returncode != 0:
-                                _err(
-                                    f"Error: Failed to switch to existing branch '{branch_name}'. "
-                                    "Please resolve any local changes or conflicts and try again."
-                                )
-                                if switch.stderr.strip():
-                                    _err(switch.stderr.strip())
-                                return 1
-                    elif args.use_timestamp:
-                        _err(
-                            f"Error: Branch '{branch_name}' already exists. Rerun to get "
-                            "a new timestamp or use a different --short-name."
-                        )
-                        return 1
-                    else:
-                        _err(
-                            f"Error: Branch '{branch_name}' already exists. Please use a "
-                            "different feature name or specify a different number with --number."
-                        )
-                        return 1
-                else:
-                    _err(f"Error: Failed to create git branch '{branch_name}'.")
-                    if create.stderr.strip():
-                        _err(create.stderr.strip())
-                    else:
-                        _err("Please check your git configuration and try again.")
-                    return 1
-        else:
-            _err(
-                "[specify] Warning: Git repository not detected; skipped branch "
-                f"creation for {branch_name}"
-            )
-
-        _err(f"# To persist: {_persist_hint('SPECIFY_FEATURE', branch_name)}")
-
-    if args.json_mode:
-        payload: dict[str, object] = {
-            "BRANCH_NAME": branch_name,
-            "FEATURE_NUM": feature_num,
-        }
-        if args.dry_run:
-            payload["DRY_RUN"] = True
-        print(json.dumps(payload, ensure_ascii=False, separators=(",", ":")))
-    else:
-        print(f"BRANCH_NAME: {branch_name}")
-        print(f"FEATURE_NUM: {feature_num}")
-        if not args.dry_run:
-            print(
-                "# To persist in your shell: "
-                f"{_persist_hint('SPECIFY_FEATURE', branch_name)}"
-            )
-
-    return 0
-
-
-if __name__ == "__main__":
-    raise SystemExit(main(sys.argv[1:]))

extensions/git/scripts/python/git_common.py

@@ -1,81 +0,0 @@
-#!/usr/bin/env python3
-"""Git-specific common helpers for the git extension.
-
-Python port of ``git-common.sh`` / ``git-common.ps1`` — contains only
-git-specific branch validation and detection logic.
-"""
-
-from __future__ import annotations
-
-import re
-import shutil
-import subprocess
-import sys
-from pathlib import Path
-
-
-def has_git(repo_root: Path | None = None) -> bool:
-    """Check if we have git available at the repo root."""
-    root = Path(repo_root) if repo_root is not None else Path.cwd()
-    git_marker = root / ".git"
-    if not (git_marker.is_dir() or git_marker.is_file()):
-        return False
-    if shutil.which("git") is None:
-        return False
-    result = subprocess.run(
-        ["git", "-C", str(root), "rev-parse", "--is-inside-work-tree"],
-        capture_output=True,
-        text=True,
-    )
-    return result.returncode == 0
-
-
-def effective_branch_name(raw: str) -> str:
-    """Strip a single optional path segment (e.g. gitflow "feat/004-name" -> "004-name").
-
-    Only when the full name is exactly two slash-free segments; otherwise
-    returns the raw name.
-    """
-    match = re.fullmatch(r"([^/]+)/([^/]+)", raw)
-    if match:
-        return match.group(2)
-    return raw
-
-
-def check_feature_branch(raw: str, has_git_repo: bool) -> bool:
-    """Validate that a branch name matches the expected feature branch pattern.
-
-    Accepts sequential (###-* with >=3 digits) or timestamp (YYYYMMDD-HHMMSS-*)
-    formats, either at the start of the branch or after path-style namespace
-    prefixes. Logic aligned with the bash/PowerShell twins.
-    """
-    if not has_git_repo:
-        print(
-            "[specify] Warning: Git repository not detected; skipped branch validation",
-            file=sys.stderr,
-        )
-        return True
-
-    branch = effective_branch_name(raw)
-    feature_segment = branch.rsplit("/", 1)[-1]
-
-    # Accept sequential prefix (3+ digits) but exclude malformed timestamps:
-    # 7-or-8 digit date + 6-digit time with no trailing slug.
-    is_sequential = bool(
-        re.match(r"^[0-9]{3,}-", feature_segment)
-        and not re.match(r"^[0-9]{7}-[0-9]{6}-", feature_segment)
-        and not re.fullmatch(r"[0-9]{7,8}-[0-9]{6}", feature_segment)
-    )
-    is_timestamp = bool(re.match(r"^[0-9]{8}-[0-9]{6}-", feature_segment))
-
-    if not is_sequential and not is_timestamp:
-        print(f"ERROR: Not on a feature branch. Current branch: {raw}", file=sys.stderr)
-        print(
-            "Feature branches should be named like: 001-feature-name, "
-            "1234-feature-name, 20260319-143022-feature-name, or "
-            "<prefix>/001-feature-name",
-            file=sys.stderr,
-        )
-        return False
-
-    return True

extensions/git/scripts/python/initialize_repo.py

@@ -1,89 +0,0 @@
-#!/usr/bin/env python3
-"""Git extension: initialize_repo.py
-
-Initialize a Git repository with an initial commit.
-Python port of ``initialize-repo.sh`` / ``initialize-repo.ps1``.
-Customizable — replace this script to add .gitignore templates,
-default branch config, git-flow, LFS, signing, etc.
-"""
-
-from __future__ import annotations
-
-import re
-import shutil
-import subprocess
-import sys
-from pathlib import Path
-
-
-def _find_project_root(start: Path) -> Path | None:
-    current = start
-    while True:
-        if (current / ".specify").is_dir() or (current / ".git").exists():
-            return current
-        if current.parent == current:
-            return None
-        current = current.parent
-
-
-def _read_commit_message(repo_root: Path) -> str:
-    """Read init_commit_message from git-config.yml, mirroring the bash sed pipeline."""
-    default = "[Spec Kit] Initial commit"
-    config_file = repo_root / ".specify" / "extensions" / "git" / "git-config.yml"
-    if not config_file.is_file():
-        return default
-    try:
-        lines = config_file.read_text(encoding="utf-8").splitlines()
-    except (OSError, UnicodeDecodeError):
-        return default
-    for line in lines:
-        if line.startswith("init_commit_message:"):
-            value = re.sub(r"^init_commit_message:\s*", "", line)
-            value = re.sub(r"^[\"']", "", value)
-            value = re.sub(r"[\"']*$", "", value)
-            if value:
-                return value
-    return default
-
-
-def main() -> int:
-    script_dir = Path(__file__).resolve().parent
-    repo_root = _find_project_root(script_dir) or Path.cwd()
-
-    commit_msg = _read_commit_message(repo_root)
-
-    if shutil.which("git") is None:
-        print(
-            "[specify] Warning: Git not found; skipped repository initialization",
-            file=sys.stderr,
-        )
-        return 0
-
-    probe = subprocess.run(
-        ["git", "rev-parse", "--is-inside-work-tree"],
-        cwd=repo_root,
-        capture_output=True,
-        text=True,
-    )
-    if probe.returncode == 0:
-        print("[specify] Git repository already initialized; skipping", file=sys.stderr)
-        return 0
-
-    steps = [
-        (["git", "init", "-q"], "git init"),
-        (["git", "add", "."], "git add"),
-        (["git", "commit", "--allow-empty", "-q", "-m", commit_msg], "git commit"),
-    ]
-    for cmd, label in steps:
-        result = subprocess.run(cmd, cwd=repo_root, capture_output=True, text=True)
-        if result.returncode != 0:
-            output = (result.stdout + result.stderr).strip()
-            print(f"[specify] Error: {label} failed: {output}", file=sys.stderr)
-            return 1
-
-    print("[OK] Git repository initialized", file=sys.stderr)
-    return 0
-
-
-if __name__ == "__main__":
-    raise SystemExit(main())

extensions/selftest/commands/selftest.md

@@ -48,7 +48,7 @@ cat .specify/extensions/.registry/$ARGUMENTS.json
 
 ### Step 4: Verification Report
 
-Analyze the standard output of the three steps.
+Analyze the standard output of the three steps. 
 Generate a terminal-style test output format detailing the results of discovery, installation, and registration. Return this directly to the user.
 
 Example output format:

integrations/catalog.json

@@ -1,6 +1,6 @@
 {
   "schema_version": "1.0",
-  "updated_at": "2026-07-15T00:00:00Z",
+  "updated_at": "2026-06-23T00:00:00Z",
   "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/integrations/catalog.json",
   "integrations": {
     "claude": {
@@ -282,15 +282,6 @@
       "repository": "https://github.com/github/spec-kit",
       "tags": ["cli"]
     },
-    "grok": {
-      "id": "grok",
-      "name": "Grok Build",
-      "version": "1.0.0",
-      "description": "xAI Grok Build CLI skills-based integration",
-      "author": "spec-kit-core",
-      "repository": "https://github.com/github/spec-kit",
-      "tags": ["cli", "skills", "xai"]
-    },
     "hermes": {
       "id": "hermes",
       "name": "Hermes Agent",

newsletters/2026-March.md

@@ -76,3 +76,5 @@ Areas under discussion or in progress for future development:
 - **Continued agent expansion** -- seven new agents were added in March alone. The agent-agnostic design means support for emerging tools can be added by anyone. [\[byteiota.com\]](https://byteiota.com/spec-driven-development-kills-vibe-coding-march-2026/)
 - **Experience simplification** -- the preset system, custom workflows, and growing walkthrough library lower the learning curve, but extension discoverability will need a more robust solution as the catalog grows. [\[github.com\]](https://github.com/github/spec-kit/releases)
 - **Toward a stable release** -- nine releases in one month reflects pre-1.0 momentum. Reaching 1.0 will require stabilizing the extension and preset APIs and ensuring backward compatibility across the agent and extension surface area. [\[github.com\]](https://github.com/github/spec-kit/blob/main/newsletters/2026-February.md)
+
+

presets/ARCHITECTURE.md

@@ -158,7 +158,8 @@ presets/
         ├── plan-template.md
         ├── tasks-template.md
         ├── checklist-template.md
-        └── constitution-template.md
+        ├── constitution-template.md
+        └── agent-file-template.md
 ```
 
 ## Module Structure

presets/catalog.community.json

@@ -1,6 +1,6 @@
 {
   "schema_version": "1.0",
-  "updated_at": "2026-07-14T00:00:00Z",
+  "updated_at": "2026-06-30T00:00:00Z",
   "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/presets/catalog.community.json",
   "presets": {
     "a11y-governance": {
@@ -131,35 +131,6 @@
       "created_at": "2026-04-27T00:00:00Z",
       "updated_at": "2026-06-14T00:00:00Z"
     },
-    "autonomous-run-governance": {
-      "name": "Autonomous Run Governance",
-      "id": "autonomous-run-governance",
-      "version": "0.1.4",
-      "description": "Adds permission-bounded, evidence-first governance for autonomous Spec Kit delivery, convergence, resume, closeout, and retrospective learning.",
-      "author": "Thorsten Hindermann",
-      "repository": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance/archive/refs/tags/v0.1.4.zip",
-      "homepage": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance",
-      "documentation": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance/blob/v0.1.4/README.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.8.3"
-      },
-      "provides": {
-        "templates": 12,
-        "commands": 2,
-        "scripts": 2
-      },
-      "tags": [
-        "autonomous",
-        "governance",
-        "evidence",
-        "permissions",
-        "retrospective"
-      ],
-      "created_at": "2026-07-13T00:00:00Z",
-      "updated_at": "2026-07-14T00:00:00Z"
-    },
     "canon-core": {
       "name": "Canon Core",
       "id": "canon-core",
@@ -647,34 +618,6 @@
       "created_at": "2026-04-30T00:00:00Z",
       "updated_at": "2026-04-30T00:00:00Z"
     },
-    "test-first-governance": {
-      "name": "Test-First Governance",
-      "id": "test-first-governance",
-      "version": "1.3.0",
-      "description": "Governs TDD with coverage-complete BDD/ATDD Gherkin scenarios, explicit suite ownership, professional test reports, traceability, and risk-based quality gates.",
-      "author": "Zoltán Katona, PhD",
-      "repository": "https://github.com/ka-zo/spec-kit-preset-test-first-governance",
-      "download_url": "https://github.com/ka-zo/spec-kit-preset-test-first-governance/archive/refs/tags/1.3.0.zip",
-      "homepage": "https://github.com/ka-zo/spec-kit-preset-test-first-governance",
-      "documentation": "https://github.com/ka-zo/spec-kit-preset-test-first-governance/blob/main/README.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.12.11"
-      },
-      "provides": {
-        "templates": 10,
-        "commands": 8
-      },
-      "tags": [
-        "tdd",
-        "bdd",
-        "atdd",
-        "quality-gates",
-        "traceability"
-      ],
-      "created_at": "2026-07-13T00:00:00Z",
-      "updated_at": "2026-07-13T00:00:00Z"
-    },
     "toc-navigation": {
       "name": "Table of Contents Navigation",
       "id": "toc-navigation",

presets/self-test/preset.yml

@@ -44,6 +44,12 @@ provides:
       description: "Self-test constitution template"
       replaces: "constitution-template"
 
+    - type: "template"
+      name: "agent-file-template"
+      file: "templates/agent-file-template.md"
+      description: "Self-test agent file template"
+      replaces: "agent-file-template"
+
     - type: "command"
       name: "speckit.specify"
       file: "commands/speckit.specify.md"

presets/self-test/templates/agent-file-template.md

@@ -0,0 +1,9 @@
+# Agent File (Self-Test Preset)
+
+<!-- preset:self-test -->
+
+> This template is provided by the self-test preset.
+
+## Agent Instructions
+
+Follow these guidelines when working on this project.

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "specify-cli"
-version = "0.12.18"
+version = "0.12.7"
 description = "Specify CLI, part of GitHub Spec Kit. A tool to bootstrap your projects for Spec-Driven Development (SDD)."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -83,3 +83,4 @@ extend-select = [
     "S604",  # call-with-shell-equals-true
     "S605",  # start-process-with-a-shell
 ]
+

scripts/bash/check-prerequisites.sh

@@ -57,13 +57,13 @@ OPTIONS:
 EXAMPLES:
   # Check task prerequisites (plan.md required)
   ./check-prerequisites.sh --json
-
+  
   # Check implementation prerequisites (plan.md + tasks.md required)
   ./check-prerequisites.sh --json --require-tasks --include-tasks
-
+  
   # Get feature paths only (no validation)
   ./check-prerequisites.sh --paths-only
-
+  
 EOF
             exit 0
             ;;
@@ -182,13 +182,13 @@ else
     # Text output
     echo "FEATURE_DIR:$FEATURE_DIR"
     echo "AVAILABLE_DOCS:"
-
+    
     # Show status of each potential document
     check_file "$RESEARCH" "research.md"
     check_file "$DATA_MODEL" "data-model.md"
     check_dir "$CONTRACTS_DIR" "contracts/"
     check_file "$QUICKSTART" "quickstart.md"
-
+    
     if $INCLUDE_TASKS; then
         check_file "$TASKS" "tasks.md"
     fi

scripts/bash/common.sh

@@ -97,26 +97,17 @@ read_feature_json_feature_directory() {
     local fj="$repo_root/.specify/feature.json"
     [[ -f "$fj" ]] || { printf '%s' ''; return 0; }
 
-    # Try parsers in order (jq -> python3 -> grep/sed), falling through on
-    # failure. Selection is by *parse success*, not mere availability: on
-    # Windows `python3` commonly resolves to the Microsoft Store App Execution
-    # Alias stub, which passes `command -v` but fails at runtime (exit 49), so
-    # an availability-gated `elif` would pick python3, swallow its failure, and
-    # never reach the grep/sed fallback -- leaving feature.json unreadable even
-    # though it is valid (issue #3304).
     local _fd=''
     if command -v jq >/dev/null 2>&1; then
         if ! _fd=$(jq -r '.feature_directory // empty' "$fj" 2>/dev/null); then
             _fd=''
         fi
-    fi
-    if [[ -z "$_fd" ]] && command -v python3 >/dev/null 2>&1; then
+    elif command -v python3 >/dev/null 2>&1; then
         # Use Python so pretty-printed/multi-line JSON still parses correctly.
         if ! _fd=$(python3 -c "import json,sys; d=json.load(open(sys.argv[1])); v=d.get('feature_directory'); print(v if v else '')" "$fj" 2>/dev/null); then
             _fd=''
         fi
-    fi
-    if [[ -z "$_fd" ]]; then
+    else
         # Last-resort single-line grep/sed fallback. The `|| true` guards against
         # grep returning 1 (no match) aborting under `set -e` / `pipefail`.
         _fd=$( { grep -E '"feature_directory"[[:space:]]*:' "$fj" 2>/dev/null || true; } \
@@ -244,29 +235,21 @@ get_invoke_separator() {
 
     local integration_json="$repo_root/.specify/integration.json"
     local separator="."
-    local parsed=0
+    local parsed_with_jq=0
 
     if [[ -f "$integration_json" ]]; then
-        # Try parsers in order (jq -> python3 -> awk), falling through on
-        # failure. Selection is by *parse success*, not mere availability: on
-        # Windows `python3` commonly resolves to the Microsoft Store App
-        # Execution Alias stub, which passes `command -v` but fails at runtime
-        # (exit 49). An availability-gated branch would pick python3, swallow
-        # its failure, and — because this function historically had no text
-        # fallback — silently return "." even for `-`-separator integrations
-        # (e.g. forge, cline), yielding wrong command hints (issue #3304).
         if command -v jq >/dev/null 2>&1; then
             local jq_separator
             if jq_separator=$(jq -r '(.default_integration // .integration // "") as $k | if $k == "" then "." else (.integration_settings[$k].invoke_separator // ".") end' "$integration_json" 2>/dev/null); then
+                parsed_with_jq=1
                 case "$jq_separator" in
-                    "."|"-") separator="$jq_separator"; parsed=1 ;;
+                    "."|"-") separator="$jq_separator" ;;
                 esac
             fi
         fi
 
-        if [[ "$parsed" -eq 0 ]] && command -v python3 >/dev/null 2>&1; then
-            local py_separator
-            if py_separator=$(python3 - "$integration_json" <<'PY' 2>/dev/null
+        if [[ "$parsed_with_jq" -eq 0 ]] && command -v python3 >/dev/null 2>&1; then
+            if separator=$(python3 - "$integration_json" <<'PY' 2>/dev/null
 import json
 import sys
 
@@ -282,64 +265,17 @@ try:
             separator = entry["invoke_separator"]
     print(separator)
 except Exception:
-    sys.exit(1)
+    print(".")
 PY
 ); then
-                case "$py_separator" in
-                    "."|"-") separator="$py_separator"; parsed=1 ;;
+                case "$separator" in
+                    "."|"-") ;;
+                    *) separator="." ;;
                 esac
+            else
+                separator="."
             fi
         fi
-
-        if [[ "$parsed" -eq 0 ]]; then
-            # Last-resort text fallback for environments with neither jq nor a
-            # working python3 (e.g. stock Windows + Git Bash). Reads the active
-            # integration key (default_integration, else integration) and its
-            # invoke_separator from within the integration_settings object.
-            # Handles both pretty-printed (the written form) and compact JSON.
-            # Accumulate all lines into one buffer in END rather than using
-            # gawk-only whole-file slurp (RS="^$"), so this stays portable to
-            # the BSD awk on macOS.
-            local awk_separator
-            awk_separator=$(awk '
-                function keyval(d, name,   v) {
-                    if (match(d, "\"" name "\"[ \t\r\n]*:[ \t\r\n]*\"[^\"]*\"")) {
-                        v=substr(d,RSTART,RLENGTH); sub(/^.*:[ \t\r\n]*"/,"",v); sub(/"$/,"",v); return v
-                    }
-                    return ""
-                }
-                { doc = doc $0 "\n" }
-                END {
-                    key=keyval(doc,"default_integration"); if (key=="") key=keyval(doc,"integration")
-                    sep="."
-                    if (key!="") {
-                        settings=doc
-                        if (match(doc, /"integration_settings"[ \t\r\n]*:[ \t\r\n]*[{]/)) {
-                            settings=substr(doc, RSTART+RLENGTH-1)
-                        }
-                        if (match(settings, "\"" key "\"[ \t\r\n]*:[ \t\r\n]*[{]")) {
-                            start=RSTART+RLENGTH-1
-                            depth=0
-                            obj=""
-                            for (i=start; i<=length(settings); i++) {
-                                c=substr(settings,i,1)
-                                obj=obj c
-                                if (c=="{") depth++
-                                else if (c=="}") { depth--; if (depth==0) break }
-                            }
-                            if (match(obj, /"invoke_separator"[ \t\r\n]*:[ \t\r\n]*"[-.]"/)) {
-                                tok=substr(obj,RSTART,RLENGTH); s=substr(tok,length(tok)-1,1)
-                                if (s=="." || s=="-") sep=s
-                            }
-                        }
-                    }
-                    print sep
-                }
-            ' "$integration_json" 2>/dev/null)
-            case "$awk_separator" in
-                "."|"-") separator="$awk_separator" ;;
-            esac
-        fi
     fi
 
     _SPECIFY_INVOKE_SEPARATOR_CACHE_REPO_ROOT="$repo_root"

scripts/bash/create-new-feature.sh

@@ -94,7 +94,7 @@ fi
 get_highest_from_specs() {
     local specs_dir="$1"
     local highest=0
-
+    
     if [ -d "$specs_dir" ]; then
         for dir in "$specs_dir"/*; do
             [ -d "$dir" ] || continue
@@ -109,7 +109,7 @@ get_highest_from_specs() {
             fi
         done
     fi
-
+    
     echo "$highest"
 }
 
@@ -135,19 +135,19 @@ fi
 # Function to generate branch name with stop word filtering and length filtering
 generate_branch_name() {
     local description="$1"
-
+    
     # Common stop words to filter out
     local stop_words="^(i|a|an|the|to|for|of|in|on|at|by|with|from|is|are|was|were|be|been|being|have|has|had|do|does|did|will|would|should|could|can|may|might|must|shall|this|that|these|those|my|your|our|their|want|need|add|get|set)$"
-
+    
     # Convert to lowercase and split into words
     local clean_name=$(printf '%s' "$description" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/ /g')
-
+    
     # Filter words: remove stop words and words shorter than 3 chars (unless they're uppercase acronyms in original)
     local meaningful_words=()
     for word in $clean_name; do
         # Skip empty words
         [ -z "$word" ] && continue
-
+        
         # Keep words that are NOT stop words AND (length >= 3 OR are potential acronyms)
         if ! echo "$word" | grep -qiE "$stop_words"; then
             if [ ${#word} -ge 3 ]; then
@@ -160,12 +160,12 @@ generate_branch_name() {
             fi
         fi
     done
-
+    
     # If we have meaningful words, use first 3-4 of them
     if [ ${#meaningful_words[@]} -gt 0 ]; then
         local max_words=3
         if [ ${#meaningful_words[@]} -eq 4 ]; then max_words=4; fi
-
+        
         local result=""
         local count=0
         for word in "${meaningful_words[@]}"; do
@@ -221,15 +221,15 @@ if [ ${#BRANCH_NAME} -gt $MAX_BRANCH_LENGTH ]; then
     # Account for prefix length: timestamp (15) + hyphen (1) = 16, or sequential (3) + hyphen (1) = 4
     PREFIX_LENGTH=$(( ${#FEATURE_NUM} + 1 ))
     MAX_SUFFIX_LENGTH=$((MAX_BRANCH_LENGTH - PREFIX_LENGTH))
-
+    
     # Truncate suffix at word boundary if possible
     TRUNCATED_SUFFIX=$(echo "$BRANCH_SUFFIX" | cut -c1-$MAX_SUFFIX_LENGTH)
     # Remove trailing hyphen if truncation created one
     TRUNCATED_SUFFIX=$(echo "$TRUNCATED_SUFFIX" | sed 's/-$//')
-
+    
     ORIGINAL_BRANCH_NAME="$BRANCH_NAME"
     BRANCH_NAME="${FEATURE_NUM}-${TRUNCATED_SUFFIX}"
-
+    
     >&2 echo "[specify] Warning: Branch name exceeded GitHub's 244-byte limit"
     >&2 echo "[specify] Original: $ORIGINAL_BRANCH_NAME (${#ORIGINAL_BRANCH_NAME} bytes)"
     >&2 echo "[specify] Truncated to: $BRANCH_NAME (${#BRANCH_NAME} bytes)"

scripts/bash/setup-plan.sh

@@ -8,17 +8,17 @@ ARGS=()
 
 for arg in "$@"; do
     case "$arg" in
-        --json)
-            JSON_MODE=true
+        --json) 
+            JSON_MODE=true 
             ;;
-        --help|-h)
+        --help|-h) 
             echo "Usage: $0 [--json]"
             echo "  --json    Output results in JSON format"
             echo "  --help    Show this help message"
-            exit 0
+            exit 0 
             ;;
-        *)
-            ARGS+=("$arg")
+        *) 
+            ARGS+=("$arg") 
             ;;
     esac
 done
@@ -77,7 +77,8 @@ if $JSON_MODE; then
     fi
 else
     echo "FEATURE_SPEC: $FEATURE_SPEC"
-    echo "IMPL_PLAN: $IMPL_PLAN"
+    echo "IMPL_PLAN: $IMPL_PLAN" 
     echo "SPECS_DIR: $FEATURE_DIR"
     echo "BRANCH: $CURRENT_BRANCH"
 fi
+

scripts/powershell/check-prerequisites.ps1

@@ -42,10 +42,10 @@ OPTIONS:
 EXAMPLES:
   # Check task prerequisites (plan.md required)
   .\check-prerequisites.ps1 -Json
-
+  
   # Check implementation prerequisites (plan.md + tasks.md required)
   .\check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
-
+  
   # Get feature paths only (no validation)
   .\check-prerequisites.ps1 -PathsOnly
 
@@ -118,35 +118,35 @@ if (Test-Path $paths.RESEARCH) { $docs += 'research.md' }
 if (Test-Path $paths.DATA_MODEL) { $docs += 'data-model.md' }
 
 # Check contracts directory (only if it exists and has files)
-if ((Test-Path $paths.CONTRACTS_DIR) -and (Get-ChildItem -Path $paths.CONTRACTS_DIR -ErrorAction SilentlyContinue | Select-Object -First 1)) {
-    $docs += 'contracts/'
+if ((Test-Path $paths.CONTRACTS_DIR) -and (Get-ChildItem -Path $paths.CONTRACTS_DIR -ErrorAction SilentlyContinue | Select-Object -First 1)) { 
+    $docs += 'contracts/' 
 }
 
 if (Test-Path $paths.QUICKSTART) { $docs += 'quickstart.md' }
 
 # Include tasks.md if requested and it exists
-if ($IncludeTasks -and (Test-Path $paths.TASKS)) {
-    $docs += 'tasks.md'
+if ($IncludeTasks -and (Test-Path $paths.TASKS)) { 
+    $docs += 'tasks.md' 
 }
 
 # Output results
 if ($Json) {
     # JSON output
-    [PSCustomObject]@{
+    [PSCustomObject]@{ 
         FEATURE_DIR = $paths.FEATURE_DIR
-        AVAILABLE_DOCS = $docs
+        AVAILABLE_DOCS = $docs 
     } | ConvertTo-Json -Compress
 } else {
     # Text output
     Write-Output "FEATURE_DIR:$($paths.FEATURE_DIR)"
     Write-Output "AVAILABLE_DOCS:"
-
+    
     # Show status of each potential document
     Test-FileExists -Path $paths.RESEARCH -Description 'research.md' | Out-Null
     Test-FileExists -Path $paths.DATA_MODEL -Description 'data-model.md' | Out-Null
     Test-DirHasFiles -Path $paths.CONTRACTS_DIR -Description 'contracts/' | Out-Null
     Test-FileExists -Path $paths.QUICKSTART -Description 'quickstart.md' | Out-Null
-
+    
     if ($IncludeTasks) {
         Test-FileExists -Path $paths.TASKS -Description 'tasks.md' | Out-Null
     }

scripts/powershell/common.ps1

@@ -191,7 +191,7 @@ function Get-FeaturePathsEnv {
         [Console]::Error.WriteLine("ERROR: Feature directory not found. Set SPECIFY_FEATURE_DIRECTORY or run the specify command to create .specify/feature.json.")
         exit 1
     }
-
+    
     # When no branch context exists (no SPECIFY_FEATURE, feature resolved via
     # SPECIFY_FEATURE_DIRECTORY or feature.json), fall back to the feature
     # directory basename so CURRENT_BRANCH is a usable identifier rather than

scripts/powershell/setup-plan.ps1

@@ -63,7 +63,7 @@ if (Test-Path $paths.IMPL_PLAN -PathType Leaf) {
 
 # Output results
 if ($Json) {
-    $result = [PSCustomObject]@{
+    $result = [PSCustomObject]@{ 
         FEATURE_SPEC = $paths.FEATURE_SPEC
         IMPL_PLAN = $paths.IMPL_PLAN
         SPECS_DIR = $paths.FEATURE_DIR

spec-kit.code-workspace

@@ -5,4 +5,4 @@
 		}
 	],
 	"settings": {}
-}
+}

src/specify_cli/__init__.py

@@ -141,9 +141,8 @@ def _install_shared_infra(
 
     Copies ``.specify/scripts/<variant>/`` and ``.specify/templates/`` from
     the bundled core_pack or source checkout, where ``<variant>`` is
-    ``bash`` when *script_type* is ``"sh"``, ``python`` when it is ``"py"``,
-    and ``powershell`` when it is ``"ps"``.  Tracks all installed files in
-    ``speckit.manifest.json``.
+    ``bash`` when *script_type* is ``"sh"`` and ``powershell`` when it is
+    ``"ps"``.  Tracks all installed files in ``speckit.manifest.json``.
 
     Shared scripts and page templates are processed to resolve
     ``__SPECKIT_COMMAND_<NAME>__`` placeholders using *invoke_separator*

src/specify_cli/_github_http.py

@@ -24,7 +24,6 @@ GITHUB_HOSTS = frozenset({
     "api.github.com",
     "codeload.github.com",
 })
-_MAX_RELEASE_METADATA_BYTES = 5 * 1024 * 1024
 
 
 def build_github_request(url: str) -> urllib.request.Request:
@@ -69,8 +68,6 @@ def resolve_github_release_asset_api_url(
     open_url_fn: Callable,
     timeout: int = 60,
     github_hosts: tuple[str, ...] = (),
-    redirect_validator: Callable[[str, str], None] | None = None,
-    max_metadata_bytes: int = _MAX_RELEASE_METADATA_BYTES,
 ) -> Optional[str]:
     """Resolve a GitHub release browser-download URL to its REST API asset URL.
 
@@ -94,8 +91,6 @@ def resolve_github_release_asset_api_url(
             authenticated release-metadata lookup.
         timeout: Per-request timeout in seconds.
         github_hosts: Host patterns to treat as GitHub Enterprise Server.
-        redirect_validator: Optional policy applied to metadata redirects.
-        max_metadata_bytes: Maximum release-metadata response size.
     """
     import json
     import urllib.error
@@ -132,14 +127,7 @@ def resolve_github_release_asset_api_url(
     if hostname == "github.com":
         api_base = "https://api.github.com"
     elif is_ghes:
-        # ``parsed.port`` raises ValueError on a malformed port (e.g.
-        # ``host:notaport``); the function's contract is to return None for
-        # anything it can't resolve, not to raise.
-        try:
-            port = parsed.port
-        except ValueError:
-            return None
-        authority = hostname if port is None else f"{hostname}:{port}"
+        authority = hostname if parsed.port is None else f"{hostname}:{parsed.port}"
         api_base = f"{parsed.scheme}://{authority}/api/v3"
     else:
         return None
@@ -154,33 +142,13 @@ def resolve_github_release_asset_api_url(
     release_url = f"{api_base}/repos/{owner}/{repo}/releases/tags/{encoded_tag}"
 
     try:
-        open_kwargs = {"timeout": timeout}
-        if redirect_validator is not None:
-            open_kwargs["redirect_validator"] = redirect_validator
-        with open_url_fn(release_url, **open_kwargs) as response:
-            raw_release_data = response.read(max_metadata_bytes + 1)
-            if len(raw_release_data) > max_metadata_bytes:
-                raise ValueError("GitHub release metadata exceeds size limit")
-            release_data = json.loads(raw_release_data)
-    except (
-        urllib.error.URLError,
-        json.JSONDecodeError,
-        TypeError,
-        ValueError,
-    ):
+        with open_url_fn(release_url, timeout=timeout) as response:
+            release_data = json.loads(response.read())
+    except (urllib.error.URLError, json.JSONDecodeError):
         return None
 
-    if not isinstance(release_data, dict):
-        return None
-    assets = release_data.get("assets", [])
-    if not isinstance(assets, list):
-        return None
-    for asset in assets:
-        if (
-            isinstance(asset, dict)
-            and asset.get("name") == asset_name
-            and asset.get("url")
-        ):
+    for asset in release_data.get("assets", []):
+        if asset.get("name") == asset_name and asset.get("url"):
             return str(asset["url"])
 
     return None

src/specify_cli/_init_options.py

@@ -14,7 +14,7 @@ def save_init_options(project_path: Path, options: dict[str, Any]) -> None:
     dest = project_path / INIT_OPTIONS_FILE
     dest.parent.mkdir(parents=True, exist_ok=True)
     dest.write_text(
-        json.dumps(options, indent=2, sort_keys=True, ensure_ascii=False) + "\n",
+        json.dumps(options, indent=2, sort_keys=True, ensure_ascii=False),
         encoding="utf-8",
     )
 

src/specify_cli/_invocation_style.py

@@ -12,7 +12,7 @@ from __future__ import annotations
 DOLLAR_SKILLS_AGENTS: frozenset[str] = frozenset({"codex", "zcode"})
 
 # Agents that always render /speckit-<name>, regardless of ai_skills.
-ALWAYS_SLASH_AGENTS: frozenset[str] = frozenset({"devin", "grok", "trae", "zed"})
+ALWAYS_SLASH_AGENTS: frozenset[str] = frozenset({"devin", "trae", "zed"})
 
 # Agents that render /speckit-<name> only when ai_skills is enabled.
 CONDITIONAL_SLASH_AGENTS: frozenset[str] = frozenset(

src/specify_cli/_toml_string.py

@@ -1,60 +0,0 @@
-"""Shared TOML string-escaping helpers.
-
-Both TOML command renderers — ``TomlIntegration`` (gemini, tabnine) in
-``specify_cli.integrations.base`` and ``CommandRegistrar.render_toml_command``
-(extension/preset commands) in ``specify_cli.agents`` — need the same rules for
-detecting characters TOML forbids literally and for emitting a fully-escaped
-basic string. Keeping one implementation here avoids the two drifting apart if
-the escaping rules change again.
-"""
-from __future__ import annotations
-
-
-def has_illegal_toml_control(value: str) -> bool:
-    """True when *value* contains a character TOML forbids literally.
-
-    TOML basic/literal strings (single- or multi-line) allow tab and, in the
-    multiline forms, newlines — but every other control character
-    (``U+0000``–``U+001F`` and ``U+007F``) must be ``\\u``-escaped, which only a
-    basic string can do. A bare carriage return counts too: a multiline basic
-    string treats ``\\r`` as a newline only when paired into ``\\r\\n``; a lone
-    ``\\r`` is an illegal control character.
-    """
-    length = len(value)
-    for i, ch in enumerate(value):
-        code = ord(ch)
-        if ch == "\r":
-            # Only a CR that is part of a CRLF newline is allowed literally.
-            if i + 1 < length and value[i + 1] == "\n":
-                continue
-            return True
-        if (code < 0x20 and ch not in ("\t", "\n")) or code == 0x7F:
-            return True
-    return False
-
-
-def escape_toml_basic(value: str) -> str:
-    """Render *value* as a single-line basic string, escaping everything.
-
-    Always valid TOML: backslash/quote are escaped, the common control chars
-    use their short escapes, and any remaining control character is emitted as
-    a ``\\uXXXX`` sequence.
-    """
-    out: list[str] = []
-    for ch in value:
-        code = ord(ch)
-        if ch == "\\":
-            out.append("\\\\")
-        elif ch == '"':
-            out.append('\\"')
-        elif ch == "\n":
-            out.append("\\n")
-        elif ch == "\r":
-            out.append("\\r")
-        elif ch == "\t":
-            out.append("\\t")
-        elif code < 0x20 or code == 0x7F:
-            out.append(f"\\u{code:04x}")
-        else:
-            out.append(ch)
-    return '"' + "".join(out) + '"'

src/specify_cli/agents.py

@@ -16,8 +16,6 @@ from typing import Any, Dict, List, Optional
 import yaml
 
 from ._init_options import is_ai_skills_enabled, load_init_options
-from ._toml_string import escape_toml_basic as _escape_toml_basic
-from ._toml_string import has_illegal_toml_control as _has_illegal_toml_control
 from ._utils import relative_extension_path_violation
 
 
@@ -213,52 +211,6 @@ class CommandRegistrar:
             ".specify.specify/", ".specify/"
         )
 
-    @staticmethod
-    def rewrite_extension_paths(
-        text: str, extension_id: str, extension_dir: Path
-    ) -> str:
-        """Rewrite extension-relative paths to their installed locations.
-
-        Extension command bodies reference bundled files relative to the
-        extension root (e.g. ``agents/control/commander.md``). After install
-        those files live under ``.specify/extensions/<id>/``, so bare
-        references would resolve against the workspace root and never be
-        found (#2101).
-
-        Only directories that actually exist inside *extension_dir* are
-        rewritten, keeping the behaviour conservative and avoiding false
-        positives on prose. ``commands`` (slash-command sources), ``specs``
-        (user project artifacts) and dot-directories are never rewritten.
-        """
-        if not isinstance(text, str) or not text:
-            return text
-
-        skip = {"commands", ".git", "specs"}
-        try:
-            subdirs = [
-                entry.name
-                for entry in extension_dir.iterdir()
-                if entry.is_dir()
-                and entry.name not in skip
-                and not entry.name.startswith(".")
-            ]
-        except OSError:
-            return text
-
-        for subdir in subdirs:
-            # Only rewrite relative references (subdir/... or ./subdir/...);
-            # absolute paths like /subdir/... keep their meaning. Use a
-            # callable replacement: subdir/extension_id come from the
-            # filesystem and could contain backslashes or "\1"-like
-            # sequences, which would corrupt a string replacement template.
-            replacement = f".specify/extensions/{extension_id}/{subdir}/"
-            text = re.sub(
-                r'(^|[\s`"\'(])(?:\./)?' + re.escape(subdir) + "/",
-                lambda m: m.group(1) + replacement,
-                text,
-            )
-        return text
-
     def render_markdown_command(
         self, frontmatter: dict, body: str, source_id: str, context_note: str = None
     ) -> str:
@@ -306,12 +258,7 @@ class CommandRegistrar:
         # ``C:\\Users\\...`` whose ``\\U`` reads as an invalid unicode escape) would
         # produce unparseable TOML — route those to the *literal* form ('''...'''),
         # which does not process escapes, or to the escaped basic string.
-        # Control characters (U+0000–U+001F except tab/newline, U+007F) and a bare
-        # CR are illegal in every TOML string form, so a body containing them must
-        # go to the escaped basic string regardless of which delimiters it uses.
-        if self._has_illegal_toml_control(body):
-            toml_lines.append(f"prompt = {self._render_basic_toml_string(body)}")
-        elif '"""' not in body and "\\" not in body:
+        if '"""' not in body and "\\" not in body:
             toml_lines.append('prompt = """')
             toml_lines.append(body)
             toml_lines.append('"""')
@@ -324,11 +271,17 @@ class CommandRegistrar:
 
         return "\n".join(toml_lines)
 
-    # Control-char detection and basic-string escaping are shared with the
-    # gemini/tabnine renderer in ``specify_cli.integrations.base`` via
-    # ``specify_cli._toml_string`` so the two never drift apart.
-    _has_illegal_toml_control = staticmethod(_has_illegal_toml_control)
-    _render_basic_toml_string = staticmethod(_escape_toml_basic)
+    @staticmethod
+    def _render_basic_toml_string(value: str) -> str:
+        """Render *value* as a TOML basic string literal."""
+        escaped = (
+            value.replace("\\", "\\\\")
+            .replace('"', '\\"')
+            .replace("\n", "\\n")
+            .replace("\r", "\\r")
+            .replace("\t", "\\t")
+        )
+        return f'"{escaped}"'
 
     def render_yaml_command(
         self,
@@ -685,9 +638,6 @@ class CommandRegistrar:
                         frontmatter[key] = core_frontmatter[key]
                 frontmatter.pop("strategy", None)
 
-            if extension_id:
-                body = self.rewrite_extension_paths(body, extension_id, source_root)
-
             frontmatter = self._adjust_script_paths(
                 frontmatter, extension_id=extension_id
             )
@@ -750,12 +700,6 @@ class CommandRegistrar:
                 )
                 output = self.render_toml_command(frontmatter, body, source_id)
             elif agent_config["format"] == "yaml":
-                body = self.resolve_skill_placeholders(
-                    agent_name, frontmatter, body, project_root
-                )
-                body = self._convert_argument_placeholder(
-                    body, "$ARGUMENTS", agent_config["args"]
-                )
                 output = self.render_yaml_command(
                     frontmatter, body, source_id, cmd_name
                 )

src/specify_cli/authentication/config.py

@@ -196,15 +196,7 @@ def find_entries_for_url(
     url: str, entries: list[AuthConfigEntry]
 ) -> list[AuthConfigEntry]:
     """Return entries whose ``hosts`` match the hostname of *url*."""
-    # A malformed authority (e.g. an unterminated IPv6 bracket "https://[::1")
-    # makes urlparse/hostname raise ValueError. Treat that the same as a
-    # host-less URL: no entry can match, so return no matches rather than
-    # leaking a raw ValueError out of the shared HTTP client (build_request /
-    # open_url call this before any URL validation).
-    try:
-        hostname = (urlparse(url).hostname or "").lower()
-    except ValueError:
-        return []
+    hostname = (urlparse(url).hostname or "").lower()
     if not hostname:
         return []
     return [

src/specify_cli/authentication/http.py

@@ -73,13 +73,6 @@ class _StripAuthOnRedirect(urllib.request.HTTPRedirectHandler):
         self._redirect_validator = redirect_validator
 
     def redirect_request(self, req, fp, code, msg, headers, newurl):
-        try:
-            new_parsed = urlparse(newurl)
-        except ValueError as exc:
-            # Malformed redirect target (e.g. unterminated IPv6 bracket).
-            # Surface as URLError so callers' download error handling applies.
-            raise urllib.error.URLError(f"malformed redirect URL: {exc}") from exc
-
         if self._redirect_validator is not None:
             self._redirect_validator(req.full_url, newurl)
 
@@ -90,6 +83,7 @@ class _StripAuthOnRedirect(urllib.request.HTTPRedirectHandler):
         new_req = super().redirect_request(req, fp, code, msg, headers, newurl)
         if new_req is not None:
             old_scheme = urlparse(req.full_url).scheme
+            new_parsed = urlparse(newurl)
             hostname = (new_parsed.hostname or "").lower()
             is_https_downgrade = old_scheme == "https" and new_parsed.scheme != "https"
             if _hostname_in_hosts(hostname, self._hosts) and not is_https_downgrade:

src/specify_cli/bundler/lib/yamlio.py

@@ -10,8 +10,6 @@ from __future__ import annotations
 import json
 import os
 import re
-import stat
-import tempfile
 from pathlib import Path, PurePosixPath
 from typing import Any
 
@@ -89,63 +87,17 @@ def loads_json(text: str, *, origin: str = "<string>") -> Any:
 
 
 def dump_json(path: Path, data: Any, *, within: Path | None = None) -> Path:
-    """Atomically write pretty JSON to *path* (optionally confined to *within*)."""
+    """Write *data* as pretty JSON to *path* (optionally confined to *within*)."""
     path = Path(path)
     if within is not None:
         path = ensure_within(within, path)
-    fd = -1
-    temp_path: Path | None = None
     try:
         path.parent.mkdir(parents=True, exist_ok=True)
-        fd, temp_name = tempfile.mkstemp(
-            dir=path.parent,
-            prefix=f".{path.name}.",
-            suffix=".tmp",
-        )
-        temp_path = Path(temp_name)
-        with os.fdopen(os.dup(fd), "w", encoding="utf-8") as handle:
+        with path.open("w", encoding="utf-8") as handle:
             json.dump(data, handle, indent=2, sort_keys=False)
             handle.write("\n")
-
-        try:
-            if path.exists():
-                existing = path.stat(follow_symlinks=False)
-                if stat.S_ISREG(existing.st_mode) and hasattr(os, "fchmod"):
-                    os.fchmod(fd, stat.S_IMODE(existing.st_mode))
-                if stat.S_ISREG(existing.st_mode) and hasattr(os, "fchown"):
-                    try:
-                        os.fchown(fd, existing.st_uid, existing.st_gid)
-                    except PermissionError:
-                        pass
-        except OSError:
-            pass
-
-        staged = os.stat(temp_path, follow_symlinks=False)
-        opened = os.fstat(fd)
-        if (
-            not stat.S_ISREG(staged.st_mode)
-            or staged.st_dev != opened.st_dev
-            or staged.st_ino != opened.st_ino
-        ):
-            raise OSError("staged JSON file changed before commit")
-
-        os.close(fd)
-        fd = -1
-        os.replace(temp_path, path)
-        temp_path = None
     except OSError as exc:
         raise BundlerError(f"Could not write {path}: {exc}") from exc
-    finally:
-        if fd >= 0:
-            try:
-                os.close(fd)
-            except OSError:
-                pass
-        if temp_path is not None:
-            try:
-                temp_path.unlink(missing_ok=True)
-            except OSError:
-                pass
     return path
 
 

src/specify_cli/bundler/services/adapters.py

@@ -68,18 +68,8 @@ def _validate_remote_url(source_id: str, url: str) -> None:
     Mirrors ``specify_cli.catalogs`` URL validation to avoid MITM/downgrade
     issues before any network call.
     """
-    # A malformed authority (e.g. an unclosed IPv6 bracket ``https://[::1``)
-    # makes urlparse / hostname access raise ValueError. This function's
-    # contract is to raise BundlerError for a bad URL, so surface that as a
-    # clean error rather than leaking a raw ValueError to the caller.
-    try:
-        parsed = urlparse(url)
-        hostname = parsed.hostname
-    except ValueError:
-        raise BundlerError(
-            f"Catalog '{source_id}' URL is malformed: {url}"
-        ) from None
-    is_localhost = hostname in ("localhost", "127.0.0.1", "::1")
+    parsed = urlparse(url)
+    is_localhost = parsed.hostname in ("localhost", "127.0.0.1", "::1")
     if parsed.scheme != "https" and not (parsed.scheme == "http" and is_localhost):
         raise BundlerError(
             f"Catalog '{source_id}' URL must use HTTPS (got {parsed.scheme}://). "
@@ -89,7 +79,7 @@ def _validate_remote_url(source_id: str, url: str) -> None:
     # "https://:8080" or "https://user@...", so requiring netloc would let
     # those through even though they carry no host. hostname is None in those
     # cases. Mirrors the fix in ``specify_cli.catalogs`` (#3210).
-    if not hostname:
+    if not parsed.hostname:
         raise BundlerError(
             f"Catalog '{source_id}' URL must be a valid URL with a host: {url}"
         )

src/specify_cli/bundler/services/installer.py

@@ -187,41 +187,19 @@ def remove_bundle(
 
     still_needed = components_still_needed(records, exclude_bundle_id=bundle_id)
     result = InstallResult(bundle_id=bundle_id)
-    remove_attempted = False
 
-    try:
-        for component in target.contributed_components:
-            key = (component.kind, component.id)
-            if key in still_needed:
-                result.skipped.append(component)
-                continue
-            if installer.is_installed(project_root, component):
-                remove_attempted = True
-                installer.remove(project_root, component)
-                result.uninstalled.append(component)
-        save_records(project_root, remove_record(records, bundle_id))
-    except Exception as exc:  # noqa: BLE001
-        if result.uninstalled:
-            detail = (
-                f"{len(result.uninstalled)} component(s) were already removed "
-                "before this failure; the bundle record was left unchanged, "
-                "so the project may be partially uninstalled."
-            )
-        elif remove_attempted:
-            detail = (
-                "No components were removed, but the failing component may "
-                "have made partial changes before raising, so the project "
-                "may be partially uninstalled."
-            )
+    for component in target.contributed_components:
+        key = (component.kind, component.id)
+        if key in still_needed:
+            result.skipped.append(component)
+            continue
+        if installer.is_installed(project_root, component):
+            installer.remove(project_root, component)
+            result.uninstalled.append(component)
         else:
-            detail = (
-                "No components were removed and no removal was attempted; "
-                "the bundle record was left unchanged."
-            )
-        raise BundlerError(
-            f"Failed to remove bundle '{bundle_id}': {exc}. {detail}"
-        ) from exc
+            result.skipped.append(component)
 
+    save_records(project_root, remove_record(records, bundle_id))
     return result
 
 

src/specify_cli/bundler/services/primitives.py

@@ -33,13 +33,12 @@ DEFAULT_PRIORITY = 10
 def _assert_pinned_version(
     kind: str, component_id: str, pinned: str | None, advertised: object
 ) -> None:
-    """Refuse to install when the resolved version differs from the manifest pin.
+    """Refuse to install when the catalog version differs from the manifest pin.
 
     Bundle manifests pin component versions for reproducibility; installing
-    whatever the resolved source (catalog *or* bundled asset) provides would
-    silently violate the pin. When the source advertises no version we cannot
-    enforce the pin, so installation proceeds (the source, not the bundler,
-    owns that gap).
+    whatever the active catalog currently serves would silently violate the
+    pin. When the catalog advertises no version we cannot enforce the pin, so
+    installation proceeds (the catalog, not the bundler, owns that gap).
     """
     if not pinned or advertised is None:
         return
@@ -55,35 +54,11 @@ def _assert_pinned_version(
     if not matches:
         raise BundlerError(
             f"{kind} '{component_id}' is pinned to version {pinned} in the bundle "
-            f"manifest, but the resolved version is {actual}. Update the bundle's "
-            "pinned version or the source before installing."
+            f"manifest, but the active catalog serves {actual}. Update the bundle's "
+            "pinned version or the catalog before installing."
         )
 
 
-def _bundled_manifest_version(manifest_path: Path, root_key: str) -> str | None:
-    """Best-effort read of a bundled asset's declared version from its manifest.
-
-    Returns ``None`` when the manifest is missing/unreadable/invalid, which
-    ``_assert_pinned_version`` treats as "cannot enforce" (proceed) — matching
-    the catalog "advertises no version" escape hatch.
-    """
-    try:
-        import yaml
-
-        data = yaml.safe_load(manifest_path.read_text(encoding="utf-8"))
-        if isinstance(data, dict):
-            section = data.get(root_key)
-            if isinstance(section, dict):
-                version = section.get("version")
-                # Only a non-empty string is a usable version; anything else
-                # (missing / non-string / whitespace) means "cannot enforce".
-                if isinstance(version, str) and version.strip():
-                    return version
-    except Exception:  # noqa: BLE001 - unreadable/invalid manifest: skip pin
-        return None
-    return None
-
-
 class _KindManager(Protocol):
     def is_installed(self, component: ComponentRef) -> bool: ...
 
@@ -159,15 +134,6 @@ class _PresetKindManager:
 
         bundled = _locate_bundled_preset(component.id)
         if bundled is not None:
-            # Enforce the manifest pin against the bundled asset's own version,
-            # mirroring the catalog path below (the bundled path previously
-            # skipped the pin entirely).
-            _assert_pinned_version(
-                "Preset",
-                component.id,
-                component.version,
-                _bundled_manifest_version(bundled / "preset.yml", "preset"),
-            )
             self._manager.install_from_directory(bundled, speckit_version, priority)
             return
 
@@ -232,15 +198,6 @@ class _ExtensionKindManager:
 
         bundled = _locate_bundled_extension(component.id)
         if bundled is not None:
-            # Enforce the manifest pin against the bundled asset's own version,
-            # mirroring the catalog path below (the bundled path previously
-            # skipped the pin entirely).
-            _assert_pinned_version(
-                "Extension",
-                component.id,
-                component.version,
-                _bundled_manifest_version(bundled / "extension.yml", "extension"),
-            )
             self._manager.install_from_directory(
                 bundled, speckit_version, priority=priority
             )

src/specify_cli/catalogs.py

@@ -71,12 +71,8 @@ class CatalogStackBase:
         """Validate that a catalog URL uses HTTPS, except localhost HTTP."""
         from urllib.parse import urlparse
 
-        try:
-            parsed = urlparse(url)
-            hostname = parsed.hostname
-        except ValueError:
-            raise cls._error(f"Catalog URL is malformed: {url}") from None
-        is_localhost = hostname in ("localhost", "127.0.0.1", "::1")
+        parsed = urlparse(url)
+        is_localhost = parsed.hostname in ("localhost", "127.0.0.1", "::1")
         if parsed.scheme != "https" and not (parsed.scheme == "http" and is_localhost):
             raise cls._error(
                 f"Catalog URL must use HTTPS (got {parsed.scheme}://). "
@@ -85,7 +81,7 @@ class CatalogStackBase:
         # Check hostname, not netloc: netloc is truthy for host-less URLs like
         # "https://:8080" or "https://user@", so the host guarantee this error
         # promises would not actually hold. hostname is None in those cases (#3209).
-        if not hostname:
+        if not parsed.hostname:
             raise cls._error("Catalog URL must be a valid URL with a host.")
 
     def _load_catalog_config(self, config_path: Path) -> list[CatalogEntry] | None:

src/specify_cli/commands/bundle/__init__.py

@@ -746,16 +746,11 @@ def _resolve_manifest_path(path: Path | None) -> Path:
 def _download_manifest(resolved, *, offline: bool):
     """Resolve a bundle's manifest from its catalog ``download_url``.
 
-    Catalog ``download_url``s are HTTPS-only (``http`` allowed for localhost),
-    matching the extensions/presets/workflows catalog systems. Remote URLs are
-    fetched with the shared authenticated, redirect-validated HTTP client, and
-    only when not ``--offline``.
-
-    Local and ``file://`` sources are intentionally not resolved here: to
-    install a bundle from disk, pass the path positionally
-    (``specify bundle install ./path/to/bundle.yml`` — a bundle directory or a
-    ``.zip`` artifact also works), which :func:`_local_manifest_source` handles
-    before catalog resolution and which never touches ``download_url``.
+    Local/``file://`` URLs always work offline and may point at a ``.zip``
+    artifact, a bundle directory, or a ``bundle.yml`` (handled by
+    :func:`_local_manifest_source`). Remote ``https://`` URLs are fetched with
+    the shared authenticated, redirect-validated HTTP client, and only when not
+    ``--offline``.
     """
     from urllib.parse import urlparse
 
@@ -768,35 +763,26 @@ def _download_manifest(resolved, *, offline: bool):
     parsed = urlparse(url)
     scheme = parsed.scheme.lower()
 
-    # ``file://`` URLs and bare filesystem paths (including Windows drive paths
-    # like ``C:\bundle.yml``, which urlparse reads as a single-letter scheme)
-    # are not valid catalog download URLs. Catalog URLs are HTTPS-only across
-    # every catalog system; installing from disk is done by passing the path
-    # positionally, which never reaches URL resolution. Give an actionable
-    # error rather than accepting a scheme the rest of the codebase rejects.
+    # On Windows an absolute path like ``C:\bundle.yml`` parses with a
+    # single-letter ``scheme``; treat it as a local file, not a URL scheme.
     if scheme in ("", "file") or re.match(r"^[A-Za-z]:[\\/]", url):
-        raise BundlerError(
-            f"Catalog entry '{resolved.entry.id}' has a non-HTTP(S) download_url "
-            f"({url}); catalog download URLs must be HTTPS (http for localhost) — "
-            "a file:// URL, a local filesystem path, or a scheme-less value "
-            "(e.g. 'example.com/bundle.zip') is not accepted. "
-            "To install a bundle from disk, pass the path directly: "
-            "'specify bundle install <path-to-bundle.yml | bundle-dir | .zip>'."
-        )
+        local = Path(parsed.path if scheme == "file" else url)
+        manifest = _local_manifest_source(str(local))
+        if manifest is None:
+            raise BundlerError(f"Bundle manifest not found: {local}")
+        return manifest
 
-    # Validate the scheme/host *before* the offline gate so an invalid or
-    # non-HTTPS download_url reports the real problem in every mode, rather
-    # than a misleading "Network access disabled" under --offline.
-    # (_download_remote_manifest re-checks this, but only once network access
-    # is permitted.) HTTPS-only, http allowed for localhost.
-    _require_https(f"bundle '{resolved.entry.id}'", url)
+    if scheme in ("http", "https"):
+        if offline:
+            raise BundlerError(
+                f"Network access disabled; cannot download bundle '{resolved.entry.id}' "
+                f"from {url}."
+            )
+        return _download_remote_manifest(resolved.entry.id, url)
 
-    if offline:
-        raise BundlerError(
-            f"Network access disabled; cannot download bundle '{resolved.entry.id}' "
-            f"from {url}."
-        )
-    return _download_remote_manifest(resolved.entry.id, url)
+    raise BundlerError(
+        f"Unsupported download_url scheme for bundle '{resolved.entry.id}': {url}"
+    )
 
 
 def _require_https(label: str, url: str) -> None:

src/specify_cli/commands/init.py

@@ -33,17 +33,11 @@ def _stdin_is_interactive() -> bool:
 def ensure_constitution_from_template(
     project_path: Path, tracker: StepTracker | None = None
 ) -> None:
-    """Materialize the resolved constitution template to memory if missing.
-
-    Resolution walks the full priority stack (project overrides → installed
-    presets → extensions → core) via :class:`PresetResolver`, so a preset that
-    ships a ``constitution-template`` (e.g. ``strategy: replace`` with a ratified
-    constitution) can seed the memory file. When nothing overrides it, the
-    resolver falls through to the core template.
-    """
-    from ..presets import _materialize_constitution_template
-
+    """Copy constitution template to memory if it doesn't exist."""
     memory_constitution = project_path / ".specify" / "memory" / "constitution.md"
+    template_constitution = (
+        project_path / ".specify" / "templates" / "constitution-template.md"
+    )
 
     if memory_constitution.exists():
         if tracker:
@@ -51,21 +45,18 @@ def ensure_constitution_from_template(
             tracker.skip("constitution", "existing file preserved")
         return
 
-    try:
-        materialization = _materialize_constitution_template(
-            project_path, memory_constitution
-        )
-        if materialization is None:
-            if tracker:
-                tracker.add("constitution", "Constitution setup")
-                tracker.error("constitution", "template not found")
-            return
+    if not template_constitution.exists():
         if tracker:
             tracker.add("constitution", "Constitution setup")
-            if materialization == "copied":
-                tracker.complete("constitution", "copied from template")
-            else:
-                tracker.complete("constitution", "composed from template")
+            tracker.error("constitution", "template not found")
+        return
+
+    try:
+        memory_constitution.parent.mkdir(parents=True, exist_ok=True)
+        shutil.copy2(template_constitution, memory_constitution)
+        if tracker:
+            tracker.add("constitution", "Constitution setup")
+            tracker.complete("constitution", "copied from template")
         else:
             console.print("[cyan]Initialized constitution from template[/cyan]")
     except Exception as e:
@@ -229,45 +220,16 @@ def register(app: typer.Typer) -> None:
                 console.print(
                     f"[yellow]Warning:[/yellow] Current directory is not empty ({len(existing_items)} items)"
                 )
+                console.print(
+                    "[yellow]Template files will be merged with existing content and may overwrite existing files[/yellow]"
+                )
                 if force:
-                    # Proceeding: the merge/overwrite warning is accurate here.
-                    console.print(
-                        "[yellow]Template files will be merged with existing content and may overwrite existing files[/yellow]"
-                    )
                     console.print(
                         "[cyan]--force supplied: skipping confirmation and proceeding with merge[/cyan]"
                     )
                 else:
-                    # Fold the merge risk into the confirmation prompt rather than
-                    # printing it unconditionally first: on the EOF/no-input path
-                    # below the command exits without changing anything, so a
-                    # standalone "will be merged" line would mislead. Interactive
-                    # users still see the risk as part of the question.
-                    #
-                    # Call typer.confirm normally so piped y/n is honored — e.g.
-                    # `echo y | specify init --here` keeps reaching the
-                    # non-destructive preserve-merge path.
-                    try:
-                        proceed = typer.confirm(
-                            "Template files will be merged with existing content "
-                            "and may overwrite existing files. Do you want to continue?"
-                        )
-                    except (typer.Abort, EOFError):
-                        # typer.confirm raises Abort for BOTH an interactive Ctrl+C
-                        # and an EOF on closed/empty stdin. Distinguish them: a real
-                        # TTY cancellation is a normal exit (0, "cancelled"), while a
-                        # missing-input EOF (non-interactive) becomes an actionable
-                        # error pointing at --force.
-                        if _stdin_is_interactive():
-                            console.print("[yellow]Operation cancelled[/yellow]")
-                            raise typer.Exit(0) from None
-                        console.print(
-                            "[red]Error:[/red] Current directory is not empty and no "
-                            "confirmation input is available. Re-run with "
-                            "[bold]--force[/bold] to merge into it."
-                        )
-                        raise typer.Exit(1) from None
-                    if not proceed:
+                    response = typer.confirm("Do you want to continue?")
+                    if not response:
                         console.print("[yellow]Operation cancelled[/yellow]")
                         raise typer.Exit(0)
         else:
@@ -485,6 +447,8 @@ def register(app: typer.Typer) -> None:
                     "shared-infra", f"scripts ({selected_script}) + templates"
                 )
 
+                ensure_constitution_from_template(project_path, tracker=tracker)
+
                 try:
                     bundled_wf = _locate_bundled_workflow("speckit")
                     if bundled_wf:
@@ -612,11 +576,6 @@ def register(app: typer.Typer) -> None:
                             continuing="Continuing without the optional preset.",
                         )
 
-                # Seed the constitution AFTER preset installation so that a
-                # preset-provided constitution-template (resolved via the
-                # priority stack) wins over the core template.
-                ensure_constitution_from_template(project_path, tracker=tracker)
-
                 tracker.complete("final", "project ready")
             except (typer.Exit, SystemExit):
                 raise
@@ -701,7 +660,6 @@ def register(app: typer.Typer) -> None:
         copilot_skill_mode = selected_ai == "copilot" and _is_skills_integration
         devin_skill_mode = selected_ai == "devin"
         zed_skill_mode = selected_ai == "zed" and _is_skills_integration
-        grok_skill_mode = selected_ai == "grok" and _is_skills_integration
         cline_skill_mode = selected_ai == "cline"
         native_skill_mode = (
             codex_skill_mode
@@ -714,7 +672,6 @@ def register(app: typer.Typer) -> None:
             or copilot_skill_mode
             or devin_skill_mode
             or zed_skill_mode
-            or grok_skill_mode
         )
 
         if codex_skill_mode:
@@ -747,11 +704,6 @@ def register(app: typer.Typer) -> None:
                 f"{step_num}. Start Zed in this project directory; spec-kit skills were installed to [cyan].agents/skills[/cyan]"
             )
             step_num += 1
-        if grok_skill_mode:
-            steps_lines.append(
-                f"{step_num}. Start Grok Build in this project directory; spec-kit skills were installed to [cyan].grok/skills[/cyan]"
-            )
-            step_num += 1
         usage_label = "skills" if native_skill_mode else "slash commands"
 
         from .._invocation_style import (

src/specify_cli/extensions/__init__.py

@@ -1004,7 +1004,6 @@ class ExtensionManager:
         from .. import load_init_options
         from ..agents import CommandRegistrar
         from ..integrations import get_integration
-        from ..integrations.base import IntegrationBase
 
         written: List[str] = []
         opts = load_init_options(self.project_root)
@@ -1016,30 +1015,6 @@ class ExtensionManager:
         registrar = CommandRegistrar()
         agent_config = registrar.AGENT_CONFIGS.get(selected_ai, {})
         integration = get_integration(selected_ai)
-        ai_skills_enabled = is_ai_skills_enabled(opts)
-
-        def _resolve_command_ref_tokens(body: str) -> str:
-            """Resolve explicit command-ref tokens with the active skill style."""
-
-            def _replacement(match: re.Match[str]) -> str:
-                command_name = "speckit." + match.group(1).lower().replace("_", ".")
-                if is_dollar_skills_agent(selected_ai, ai_skills_enabled):
-                    return "$" + command_name.replace("speckit.", "speckit-").replace(
-                        ".", "-"
-                    )
-                if is_slash_skills_agent(selected_ai, ai_skills_enabled):
-                    return "/" + command_name.replace("speckit.", "speckit-").replace(
-                        ".", "-"
-                    )
-                if integration is not None:
-                    return integration.build_command_invocation(command_name)
-                return IntegrationBase.resolve_command_refs(
-                    match.group(0), agent_config.get("invoke_separator", ".")
-                )
-
-            return re.sub(
-                r"__SPECKIT_COMMAND_([A-Z][A-Z0-9_]*)__", _replacement, body
-            )
 
         for cmd_info in manifest.commands:
             cmd_name = cmd_info["name"]
@@ -1103,15 +1078,9 @@ class ExtensionManager:
             frontmatter = registrar._adjust_script_paths(
                 frontmatter, extension_id=manifest.id
             )
-            # Mirror the register_commands() rewrite (#2101): resolve
-            # extension-relative subdir references (agents/, knowledge-base/,
-            # etc.) to their installed .specify/extensions/<id>/ location
-            # before the generic placeholder/path resolution below.
-            body = registrar.rewrite_extension_paths(body, manifest.id, extension_dir)
             body = registrar.resolve_skill_placeholders(
                 selected_ai, frontmatter, body, self.project_root, extension_id=manifest.id
             )
-            body = _resolve_command_ref_tokens(body)
 
             original_desc = frontmatter.get("description", "")
             description = original_desc or f"Extension command: {cmd_name}"
@@ -2763,36 +2732,6 @@ class ConfigManager:
         config_file = self.extension_dir / "local-config.yml"
         return self._load_yaml_config(config_file)
 
-    def _sibling_extension_ids(self) -> list[str]:
-        """Return IDs of other extensions installed alongside this one.
-
-        Sourced from ``ExtensionRegistry`` (``.specify/extensions/.registry``)
-        rather than a directory scan: ``ExtensionManager.remove(...,
-        keep_config=True)`` deliberately preserves the extension directory
-        while dropping the registry entry, so a directory scan would treat
-        that config-only leftover as an installed sibling and keep silently
-        absorbing its ``SPECKIT_<sibling>_*`` env vars into no one. The
-        registry is the source of truth for "installed".
-
-        Returns an empty list if the registry is missing or corrupted
-        (fresh project, ad-hoc test harness) so ``_get_env_config`` degrades
-        to its pre-fix behaviour rather than crashing. ``UnicodeError`` is
-        caught alongside ``OSError`` because ``ExtensionRegistry._load()``
-        opens the file in text mode and only handles ``JSONDecodeError`` /
-        ``FileNotFoundError``, so a registry file with non-UTF-8 bytes would
-        otherwise surface a ``UnicodeDecodeError`` here and break *every*
-        config read instead of degrading gracefully.
-
-        Used by ``_get_env_config`` to detect env vars whose remainder claims
-        a longer, sibling-owned prefix (e.g. ``SPECKIT_GIT_HOOKS_URL`` is
-        owned by ``git-hooks`` when it is co-installed with ``git``).
-        """
-        extensions_dir = self.project_root / ".specify" / "extensions"
-        try:
-            return list(ExtensionRegistry(extensions_dir).keys())
-        except (OSError, UnicodeError):
-            return []
-
     def _get_env_config(self) -> Dict[str, Any]:
         """Get configuration from environment variables.
 
@@ -2812,70 +2751,22 @@ class ConfigManager:
         ext_id_upper = self.extension_id.replace("-", "_").upper()
         prefix = f"SPECKIT_{ext_id_upper}_"
 
-        # Cross-extension prefix collision: because ``_`` doubles as both the
-        # separator between the extension ID and the config path *and* the
-        # substitute for ``-`` inside an extension ID, an env var like
-        # ``SPECKIT_GIT_HOOKS_URL`` begins with *both* the ``SPECKIT_GIT_``
-        # prefix of the ``git`` extension and the ``SPECKIT_GIT_HOOKS_`` prefix
-        # of a co-installed ``git-hooks`` extension. It logically belongs to
-        # the extension whose normalized ID is the longer, more specific match
-        # — otherwise config intended for one extension silently surfaces
-        # inside another and can drive hooks that only inspect
-        # ``config.<field> is set``. Build the list of sibling-owned
-        # remainder-prefixes here so a later env var can be skipped if it
-        # matches one.
-        sibling_prefixes: list[str] = []
-        for sibling_id in self._sibling_extension_ids():
-            if sibling_id == self.extension_id:
-                continue
-            sib_upper = sibling_id.replace("-", "_").upper()
-            # A sibling collides only when its normalized ID *extends* our own
-            # (i.e. starts with ``<US>_``). ``git`` vs ``not-git`` is not a
-            # collision; ``git`` vs ``git-hooks`` is.
-            if sib_upper.startswith(ext_id_upper + "_"):
-                # The portion of the env-var *remainder* the sibling claims,
-                # including the trailing ``_`` so a shorter ID that shares a
-                # non-boundary prefix cannot false-positive (e.g. sibling
-                # ``hook`` would not eat env vars under key ``hooks``).
-                sibling_prefixes.append(sib_upper[len(ext_id_upper) + 1 :] + "_")
-
         for key, value in os.environ.items():
             if not key.startswith(prefix):
                 continue
 
-            remainder = key[len(prefix) :]
-            # Skip when a longer sibling ID claims this var — see the block
-            # above. Keeps ``SPECKIT_GIT_HOOKS_URL`` out of the ``git``
-            # extension's config when ``git-hooks`` is co-installed.
-            if any(remainder.startswith(sp) for sp in sibling_prefixes):
-                continue
+            # Remove prefix and split into parts
+            config_path = key[len(prefix) :].lower().split("_")
 
-            # Remove prefix and split into parts. Drop empty components from a
-            # malformed name (e.g. ``SPECKIT_<EXT>_`` with no key, or
-            # consecutive underscores ``SPECKIT_X__Y``) so we never create an
-            # entry under an empty key.
-            config_path = [p for p in remainder.lower().split("_") if p]
-            if not config_path:
-                continue
-
-            # Build nested dict. Two env vars can collide on a prefix, e.g.
-            # SPECKIT_X_CONNECTION=a and SPECKIT_X_CONNECTION_URL=b. Guard the
-            # walk so a colliding scalar is replaced by a dict (deeper/more
-            # specific vars win) instead of being indexed into — which raised
-            # TypeError ('str' object does not support item assignment) — and
-            # guard the leaf so a scalar processed after the nested var does
-            # not clobber the nested dict. Order-independent: both insertion
-            # orders yield {'connection': {'url': ...}}. Nested-wins mirrors
-            # _merge_configs' dict-preserving semantics.
+            # Build nested dict
             current = env_config
             for part in config_path[:-1]:
-                if not isinstance(current.get(part), dict):
+                if part not in current:
                     current[part] = {}
                 current = current[part]
 
-            # Set the final value, unless a nested dict already occupies it.
-            if not isinstance(current.get(config_path[-1]), dict):
-                current[config_path[-1]] = value
+            # Set the final value
+            current[config_path[-1]] = value
 
         return env_config
 

src/specify_cli/extensions/_commands.py

@@ -426,11 +426,7 @@ def extension_add(
     if from_url and not dev:
         from urllib.parse import urlparse
 
-        try:
-            parsed = urlparse(from_url)
-        except ValueError:
-            console.print(f"[red]Error:[/red] Invalid URL: {_escape_markup(from_url)}")
-            raise typer.Exit(1)
+        parsed = urlparse(from_url)
         is_localhost = parsed.hostname in ("localhost", "127.0.0.1", "::1")
 
         if parsed.scheme != "https" and not (parsed.scheme == "http" and is_localhost):
@@ -1566,14 +1562,7 @@ def extension_set_priority(
     raw_priority = metadata.get("priority")
     # Only skip if the stored value is already a valid int equal to requested priority
     # This ensures corrupted values (e.g., "high") get repaired even when setting to default (10)
-    # A bool is an int in Python (isinstance(True, int) is True), so exclude it explicitly —
-    # mirroring normalize_priority's bool guard — otherwise a corrupted True/False priority
-    # equals 1/0 here and is never repaired.
-    if (
-        isinstance(raw_priority, int)
-        and not isinstance(raw_priority, bool)
-        and raw_priority == priority
-    ):
+    if isinstance(raw_priority, int) and raw_priority == priority:
         console.print(f"[yellow]Extension '{_escape_markup(str(display_name))}' already has priority {priority}[/yellow]")
         raise typer.Exit(0)
 

src/specify_cli/integrations/__init__.py

@@ -63,7 +63,6 @@ def _register_builtins() -> None:
     from .gemini import GeminiIntegration
     from .generic import GenericIntegration
     from .goose import GooseIntegration
-    from .grok import GrokIntegration
     from .hermes import HermesIntegration
     from .junie import JunieIntegration
     from .kilocode import KilocodeIntegration
@@ -100,7 +99,6 @@ def _register_builtins() -> None:
     _register(GeminiIntegration())
     _register(GenericIntegration())
     _register(GooseIntegration())
-    _register(GrokIntegration())
     _register(HermesIntegration())
     _register(JunieIntegration())
     _register(KilocodeIntegration())

src/specify_cli/integrations/_helpers.py

@@ -190,15 +190,7 @@ def _parse_integration_options(integration: Any, raw_options: str) -> dict[str,
     """
     import shlex
     parsed: dict[str, Any] = {}
-    try:
-        tokens = shlex.split(raw_options)
-    except ValueError as exc:
-        # An unbalanced quote (e.g. --integration-options='--commands-dir "foo')
-        # makes shlex raise "No closing quotation". Translate it into the same
-        # clean exit-1 UX as every other bad-input path below rather than
-        # letting a raw traceback escape.
-        console.print(f"[red]Error:[/red] Could not parse integration options: {exc}.")
-        raise typer.Exit(1)
+    tokens = shlex.split(raw_options)
     declared_options = list(integration.options())
     declared = {opt.name.lstrip("-"): opt for opt in declared_options}
     allowed = ", ".join(sorted(opt.name for opt in declared_options))
@@ -260,7 +252,6 @@ def _update_init_options_for_integration(
     project_root: Path,
     integration: Any,
     script_type: str | None = None,
-    parsed_options: dict[str, Any] | None = None,
 ) -> None:
     """Update init-options.json to reflect *integration* as the active one.
 
@@ -279,17 +270,7 @@ def _update_init_options_for_integration(
     opts["speckit_version"] = _get_speckit_version()
     if script_type:
         opts["script"] = script_type
-    # Skills mode is either intrinsic (SkillsIntegration), set on the instance
-    # during setup() (_skills_mode), or requested via parsed options (e.g.
-    # Copilot's --skills, persisted as parsed_options["skills"]). The latter is
-    # the only signal available on the `use` path, where no setup() runs and a
-    # fresh integration instance has _skills_mode == False (issue #3550).
-    skills_mode = (
-        isinstance(integration, SkillsIntegration)
-        or getattr(integration, "_skills_mode", False)
-        or bool((parsed_options or {}).get("skills"))
-    )
-    if skills_mode:
+    if isinstance(integration, SkillsIntegration) or getattr(integration, "_skills_mode", False):
         opts["ai_skills"] = True
     else:
         opts.pop("ai_skills", None)
@@ -345,9 +326,7 @@ def _set_default_integration(
             ) from exc
 
     _write_integration_json(project_root, key, installed_keys, settings)
-    _update_init_options_for_integration(
-        project_root, integration, script_type=resolved_script, parsed_options=parsed_options
-    )
+    _update_init_options_for_integration(project_root, integration, script_type=resolved_script)
 
 
 def _set_default_integration_or_exit(*args: Any, **kwargs: Any) -> None:

src/specify_cli/integrations/base.py

@@ -17,7 +17,6 @@ import os
 import re
 import shlex
 import shutil
-import subprocess
 import sys
 from abc import ABC
 from dataclasses import dataclass
@@ -26,9 +25,6 @@ from typing import TYPE_CHECKING, Any
 
 import yaml
 
-from .._toml_string import escape_toml_basic as _escape_toml_basic
-from .._toml_string import has_illegal_toml_control as _has_illegal_toml_control
-
 if TYPE_CHECKING:
     from .manifest import IntegrationManifest
 
@@ -55,18 +51,6 @@ _CORE_COMMAND_TEMPLATE_RANK = {
 }
 
 
-def yaml_quote(value: str) -> str:
-    """Emit *value* as a double-quoted YAML scalar on a single line.
-
-    A hand-rolled quote cannot carry raw newlines (YAML folds them to
-    spaces) or control characters (the reader rejects them), so let the
-    YAML emitter produce the escapes.
-    """
-    return yaml.safe_dump(
-        str(value), default_style='"', allow_unicode=True, width=sys.maxsize
-    ).strip()
-
-
 # ---------------------------------------------------------------------------
 # IntegrationOption
 # ---------------------------------------------------------------------------
@@ -605,42 +589,10 @@ class IntegrationBase(ABC):
                 if candidate.exists():
                     return relative
         for name in ("python3", "python"):
-            found = shutil.which(name)
-            if not found:
-                continue
-            # On Windows, python3/python on PATH may be the Microsoft
-            # Store App Execution Alias stub: it exists but only prints
-            # an installer hint and exits non-zero, so existence is not
-            # enough (see #3304 for the same defect in the sh scripts).
-            if sys.platform == "win32" and not IntegrationBase._interpreter_runs(
-                found
-            ):
-                continue
-            return name
+            if shutil.which(name):
+                return name
         return sys.executable or "python3"
 
-    @staticmethod
-    def _interpreter_runs(path: str) -> bool:
-        """Return True when *path* executes as a Python interpreter.
-
-        Runs isolated (``-I``) without ``site`` (``-S``) and discards
-        I/O so the probe is a fast liveness check that cannot trigger
-        ``sitecustomize``/user startup hooks.
-        """
-        try:
-            return (
-                subprocess.run(
-                    [path, "-I", "-S", "-c", ""],
-                    stdin=subprocess.DEVNULL,
-                    stdout=subprocess.DEVNULL,
-                    stderr=subprocess.DEVNULL,
-                    timeout=15,
-                ).returncode
-                == 0
-            )
-        except (OSError, subprocess.SubprocessError):
-            return False
-
     @staticmethod
     def process_template(
         content: str,
@@ -1001,12 +953,6 @@ class TomlIntegration(IntegrationBase):
         body = "".join(lines[frontmatter_end + 1 :])
         return frontmatter, body
 
-    # Control-char detection and basic-string escaping are shared with the
-    # extension/preset renderer in ``specify_cli.agents`` via
-    # ``specify_cli._toml_string`` so the two never drift apart.
-    _has_illegal_toml_control = staticmethod(_has_illegal_toml_control)
-    _escape_toml_basic = staticmethod(_escape_toml_basic)
-
     @staticmethod
     def _render_toml_string(value: str) -> str:
         """Render *value* as a TOML string literal.
@@ -1016,12 +962,6 @@ class TomlIntegration(IntegrationBase):
         literal string or escaped basic string when delimiters appear in
         the content.
         """
-        # Control characters other than tab/newline (and a bare CR) cannot
-        # appear literally in any TOML string; route them to a fully-escaped
-        # basic string so the generated file stays parseable.
-        if TomlIntegration._has_illegal_toml_control(value):
-            return TomlIntegration._escape_toml_basic(value)
-
         if "\n" not in value and "\r" not in value:
             escaped = value.replace("\\", "\\\\").replace('"', '\\"')
             return f'"{escaped}"'
@@ -1034,7 +974,17 @@ class TomlIntegration(IntegrationBase):
         if "'''" not in value and not value.endswith("'"):
             return "'''\n" + value + "'''"
 
-        return TomlIntegration._escape_toml_basic(value)
+        return (
+            '"'
+            + (
+                value.replace("\\", "\\\\")
+                .replace('"', '\\"')
+                .replace("\n", "\\n")
+                .replace("\r", "\\r")
+                .replace("\t", "\\t")
+            )
+            + '"'
+        )
 
     @staticmethod
     def _render_toml(description: str, body: str) -> str:
@@ -1122,16 +1072,6 @@ class TomlIntegration(IntegrationBase):
 # YamlIntegration — YAML-format agents (Goose)
 # ---------------------------------------------------------------------------
 
-# Characters a YAML literal block scalar cannot carry: C0 controls other
-# than tab/LF (a bare CR acts as a line break inside the scalar), DEL, the
-# C1 range, lone UTF-16 surrogates, and the non-characters U+FFFE/U+FFFF.
-# NEL (U+0085) is YAML-printable but, like LS/PS (U+2028/U+2029), YAML 1.1
-# treats it as a line break, which corrupts the block scalar's structure
-# just the same, so all three are included.
-_YAML_BLOCK_SCALAR_UNSAFE = re.compile(
-    r"[\x00-\x08\x0b-\x1f\x7f-\x9f\u2028\u2029\ud800-\udfff\ufffe\uffff]"
-)
-
 
 class YamlIntegration(IntegrationBase):
     """Concrete base for integrations that use YAML recipe format.
@@ -1238,9 +1178,9 @@ class YamlIntegration(IntegrationBase):
     def _render_yaml(cls, title: str, description: str, body: str, source_id: str) -> str:
         """Render a YAML recipe file from title, description, and body.
 
-        Produces a Goose-compatible recipe with a literal block scalar for
-        normal prompt content, or an escaped quoted scalar when control
-        characters require it. Uses ``yaml.safe_dump()`` for the header fields.
+        Produces a Goose-compatible recipe with a literal block scalar
+        for the prompt content.  Uses ``yaml.safe_dump()`` for the
+        header fields to ensure proper escaping.
         """
         header = cls._build_yaml_header(title, description)
 
@@ -1251,23 +1191,6 @@ class YamlIntegration(IntegrationBase):
             default_flow_style=False,
         ).strip()
 
-        # YAML forbids C0 control characters (except tab and newline) and
-        # DEL in every scalar form, and a bare CR acts as a line break
-        # inside a block scalar. A literal block scalar emits such bytes
-        # verbatim, producing a recipe the YAML parser rejects, so fall
-        # back to an escaped double-quoted scalar for those bodies.
-        if _YAML_BLOCK_SCALAR_UNSAFE.search(body):
-            prompt_yaml = yaml.safe_dump(
-                {"prompt": body}, allow_unicode=True, default_style='"', width=sys.maxsize
-            ).strip()
-            lines = [
-                header_yaml,
-                prompt_yaml,
-                "",
-                f"# Source: {source_id}",
-            ]
-            return "\n".join(lines) + "\n"
-
         # Indent the body for YAML block scalar. Use an explicit indentation
         # indicator ("|2") rather than a bare "|": YAML infers a plain block
         # scalar's indentation from its first non-empty line, so a body whose
@@ -1552,17 +1475,21 @@ class SkillsIntegration(IntegrationBase):
             if not description:
                 description = f"Spec Kit: {command_name} workflow"
 
-            # Build SKILL.md with manually formatted frontmatter (stable
-            # double-quoted values). yaml_quote escapes newlines and control
-            # characters that a plain quoted f-string cannot carry.
+            # Build SKILL.md with manually formatted frontmatter to match
+            # the release packaging script output exactly (double-quoted
+            # values, no yaml.safe_dump quoting differences).
+            def _quote(v: str) -> str:
+                escaped = v.replace("\\", "\\\\").replace('"', '\\"')
+                return f'"{escaped}"'
+
             skill_content = (
                 f"---\n"
-                f"name: {yaml_quote(skill_name)}\n"
-                f"description: {yaml_quote(description)}\n"
-                f"compatibility: {yaml_quote('Requires spec-kit project structure with .specify/ directory')}\n"
+                f"name: {_quote(skill_name)}\n"
+                f"description: {_quote(description)}\n"
+                f"compatibility: {_quote('Requires spec-kit project structure with .specify/ directory')}\n"
                 f"metadata:\n"
-                f"  author: {yaml_quote('github-spec-kit')}\n"
-                f"  source: {yaml_quote('templates/commands/' + src_file.name)}\n"
+                f"  author: {_quote('github-spec-kit')}\n"
+                f"  source: {_quote('templates/commands/' + src_file.name)}\n"
                 f"---\n"
                 f"{processed_body}"
             )

src/specify_cli/integrations/devin/__init__.py

@@ -62,4 +62,4 @@ class DevinIntegration(SkillsIntegration):
                 default=True,
                 help="Install as agent skills (default for Devin)",
             ),
-        ]
+        ]

src/specify_cli/integrations/forge/__init__.py

@@ -18,13 +18,13 @@ from ..manifest import IntegrationManifest
 
 def format_forge_command_name(cmd_name: str) -> str:
     """Convert command name to Forge-compatible hyphenated format.
-
+    
     Forge requires command names to use hyphens instead of dots for
     compatibility with ZSH and other shells. This function converts
     dot-notation command names to hyphenated format.
-
+    
     The function is idempotent: already-formatted names are returned unchanged.
-
+    
     Examples:
         >>> format_forge_command_name("plan")
         'speckit-plan'
@@ -38,26 +38,26 @@ def format_forge_command_name(cmd_name: str) -> str:
         'speckit-my-extension-example'
         >>> format_forge_command_name("speckit.jira.sync-status")
         'speckit-jira-sync-status'
-
+    
     Args:
-        cmd_name: Command name in dot notation (speckit.foo.bar),
+        cmd_name: Command name in dot notation (speckit.foo.bar), 
                   hyphenated format (speckit-foo-bar), or plain name (foo)
-
+    
     Returns:
         Hyphenated command name with 'speckit-' prefix
     """
     # Already in hyphenated format - return as-is (idempotent)
     if cmd_name.startswith("speckit-"):
         return cmd_name
-
+    
     # Strip 'speckit.' prefix if present
     short_name = cmd_name
     if short_name.startswith("speckit."):
         short_name = short_name[len("speckit."):]
-
+    
     # Replace all dots with hyphens
     short_name = short_name.replace(".", "-")
-
+    
     # Return with 'speckit-' prefix
     return f"speckit-{short_name}"
 

src/specify_cli/integrations/grok/__init__.py

@@ -1,60 +0,0 @@
-"""Grok Build integration — skills-based agent.
-
-Grok Build discovers project skills from ``.grok/skills/speckit-<name>/SKILL.md``
-(and also scans ``.agents/skills/``). Spec Kit installs into the native
-``.grok/skills`` tree so skills take highest local priority.
-"""
-
-from __future__ import annotations
-
-from ..base import SkillsIntegration
-
-
-class GrokIntegration(SkillsIntegration):
-    """Integration for xAI Grok Build CLI."""
-
-    key = "grok"
-    config = {
-        "name": "Grok Build",
-        "folder": ".grok/",
-        "commands_subdir": "skills",
-        "install_url": "https://docs.x.ai/build/overview",
-        "requires_cli": True,
-    }
-    registrar_config = {
-        "dir": ".grok/skills",
-        "format": "markdown",
-        "args": "$ARGUMENTS",
-        "extension": "/SKILL.md",
-    }
-    multi_install_safe = True
-
-    def build_exec_args(
-        self,
-        prompt: str,
-        *,
-        model: str | None = None,
-        output_json: bool = True,
-    ) -> list[str] | None:
-        """Build CLI arguments for non-interactive ``grok`` execution.
-
-        Mandatory headless flag:
-
-        * ``--always-approve`` — auto-approve tool executions so workflow
-          dispatch and ``dispatch_command()`` are not blocked at permission
-          gates (same role as Cursor's ``--force`` / Copilot's ``--yolo``).
-        """
-        if not self.config or not self.config.get("requires_cli"):
-            return None
-        args = [
-            self._resolve_executable(),
-            "-p",
-            prompt,
-            "--always-approve",
-        ]
-        self._apply_extra_args_env_var(args)
-        if model:
-            args.extend(["--model", model])
-        if output_json:
-            args.extend(["--output-format", "json"])
-        return args

src/specify_cli/integrations/hermes/__init__.py

@@ -18,7 +18,7 @@ from typing import Any
 
 import yaml
 
-from ..base import IntegrationOption, SkillsIntegration, yaml_quote
+from ..base import IntegrationOption, SkillsIntegration
 from ..manifest import IntegrationManifest
 
 
@@ -153,18 +153,20 @@ class HermesIntegration(SkillsIntegration):
             if not description:
                 description = f"Spec Kit: {command_name} workflow"
 
-            # Build SKILL.md with manually formatted frontmatter. yaml_quote
-            # escapes newlines and control characters that a plain quoted
-            # f-string cannot carry.
+            # Build SKILL.md with manually formatted frontmatter
+            def _quote(v: str) -> str:
+                escaped = v.replace("\\", "\\\\").replace('"', '\\"')
+                return f'"{escaped}"'
+
             skill_content = (
                 f"---\n"
-                f"name: {yaml_quote(skill_name)}\n"
-                f"description: {yaml_quote(description)}\n"
+                f"name: {_quote(skill_name)}\n"
+                f"description: {_quote(description)}\n"
                 f"compatibility: "
-                f"{yaml_quote('Requires spec-kit project structure with .specify/ directory')}\n"
+                f"{_quote('Requires spec-kit project structure with .specify/ directory')}\n"
                 f"metadata:\n"
-                f"  author: {yaml_quote('github-spec-kit')}\n"
-                f"  source: {yaml_quote('templates/commands/' + src_file.name)}\n"
+                f"  author: {_quote('github-spec-kit')}\n"
+                f"  source: {_quote('templates/commands/' + src_file.name)}\n"
                 f"---\n"
                 f"{processed_body}"
             )

src/specify_cli/integrations/kiro_cli/__init__.py

@@ -13,7 +13,6 @@ _KIRO_ARG_FALLBACK = "(the user will provide the argument in this conversation)"
 
 class KiroCliIntegration(MarkdownIntegration):
     key = "kiro-cli"
-    multi_install_safe = True
     config = {
         "name": "Kiro CLI",
         "folder": ".kiro/",
@@ -27,10 +26,3 @@ class KiroCliIntegration(MarkdownIntegration):
         "args": _KIRO_ARG_FALLBACK,
         "extension": ".md",
     }
-
-    # Kiro CLI keeps everything under a static, isolated agent root
-    # (``.kiro/`` with commands in ``.kiro/prompts``) that no other
-    # integration writes to, so it is safe to install alongside others
-    # (issue #3471). The registry's multi-install-safe contract tests
-    # enforce that isolation for every integration setting this flag.
-    multi_install_safe = True

src/specify_cli/integrations/manifest.py

@@ -309,14 +309,7 @@ class IntegrationManifest:
             if abs_path.is_symlink() or not abs_path.is_file():
                 modified.append(rel)
                 continue
-            try:
-                changed = _sha256(abs_path) != expected_hash
-            except OSError:
-                # Unreadable regular file (e.g. permission denied): treat as
-                # modified, consistent with the symlink / non-regular-file
-                # handling above, rather than letting the OSError escape.
-                changed = True
-            if changed:
+            if _sha256(abs_path) != expected_hash:
                 modified.append(rel)
         return modified
 
@@ -365,17 +358,9 @@ class IntegrationManifest:
                     skipped.append(path)
                     continue
             else:
-                if not force:
-                    try:
-                        matches = _sha256(path) == expected_hash
-                    except OSError:
-                        # Unreadable: can't verify it's ours, so preserve it
-                        # (mirrors the path.unlink() OSError guard below).
-                        skipped.append(path)
-                        continue
-                    if not matches:
-                        skipped.append(path)
-                        continue
+                if not force and _sha256(path) != expected_hash:
+                    skipped.append(path)
+                    continue
             try:
                 path.unlink()
             except OSError:

src/specify_cli/presets/__init__.py

@@ -31,117 +31,7 @@ from ..extensions import REINSTALL_COMMAND, ExtensionRegistry, normalize_priorit
 from .._init_options import is_ai_skills_enabled
 from ..integrations.base import IntegrationBase
 from .._utils import dump_frontmatter, version_satisfies
-from ..shared_infra import (
-    _ensure_safe_shared_destination,
-    _ensure_safe_shared_directory,
-    _write_shared_bytes,
-    _write_shared_text,
-    verify_archive_sha256,
-)
-
-
-_CONSTITUTION_PROVENANCE_FILE = ".constitution-template.json"
-
-
-def _content_sha256(content: bytes) -> str:
-    return hashlib.sha256(content).hexdigest()
-
-
-def _constitution_is_generated(
-    project_root: Path,
-    memory_constitution: Path,
-    resolver: "PresetResolver",
-) -> bool:
-    """Return whether the live constitution is an unchanged generated file."""
-    _ensure_safe_shared_destination(project_root, memory_constitution)
-    content = memory_constitution.read_bytes()
-    provenance = memory_constitution.parent / _CONSTITUTION_PROVENANCE_FILE
-    _ensure_safe_shared_destination(project_root, provenance)
-
-    if provenance.exists():
-        try:
-            metadata = json.loads(provenance.read_text(encoding="utf-8"))
-        except (json.JSONDecodeError, UnicodeDecodeError):
-            return False
-        return (
-            isinstance(metadata, dict)
-            and metadata.get("sha256") == _content_sha256(content)
-        )
-
-    # Older projects have no provenance sidecar. Only the immutable bundled or
-    # source-checkout core template is safe to treat as generated.
-    core = resolver._find_bundled_core(
-        "constitution-template", "template", ".md"
-    )
-    return core is not None and core.read_bytes() == content
-
-
-def _constitution_provenance_matches_preset(
-    project_root: Path,
-    memory_constitution: Path,
-    pack_id: str,
-    pack_version: str,
-) -> bool:
-    """Return whether provenance identifies a preset as the materialized source."""
-    provenance = memory_constitution.parent / _CONSTITUTION_PROVENANCE_FILE
-    if not provenance.parent.exists():
-        return False
-    _ensure_safe_shared_destination(project_root, provenance)
-    if not provenance.exists():
-        return False
-    try:
-        metadata = json.loads(provenance.read_text(encoding="utf-8"))
-    except (json.JSONDecodeError, UnicodeDecodeError):
-        return False
-    return (
-        isinstance(metadata, dict)
-        and metadata.get("source") == f"{pack_id} v{pack_version}"
-    )
-
-
-def _materialize_constitution_template(
-    project_root: Path,
-    memory_constitution: Path,
-) -> str | None:
-    """Materialize constitution-template content into memory/constitution.md.
-
-    Returns:
-        "copied" when the winning layer is ``replace`` and the source file is
-        copied verbatim; "composed" when a composing strategy is materialized
-        via ``resolve_content``; ``None`` when no constitution template resolves.
-    """
-    resolver = PresetResolver(project_root)
-    layers = resolver.collect_all_layers("constitution-template", "template")
-    if not layers:
-        return None
-
-    top_layer = layers[0]
-    if top_layer["strategy"] == "replace":
-        content = top_layer["path"].read_bytes()
-        result = "copied"
-    else:
-        composed_content = resolver.resolve_content("constitution-template", "template")
-        if composed_content is None:
-            return None
-        content = composed_content.encode("utf-8")
-        result = "composed"
-
-    _ensure_safe_shared_directory(project_root, memory_constitution.parent)
-    _write_shared_bytes(project_root, memory_constitution, content)
-    provenance = memory_constitution.parent / _CONSTITUTION_PROVENANCE_FILE
-    _write_shared_text(
-        project_root,
-        provenance,
-        json.dumps(
-            {
-                "sha256": _content_sha256(content),
-                "source": top_layer["source"],
-            },
-            indent=2,
-        )
-        + "\n",
-    )
-    return result
+from ..shared_infra import verify_archive_sha256
 
 
 def _substitute_core_template(
@@ -888,7 +778,6 @@ class PresetManager:
                                         matching_cmds, ext_id, ext_dir,
                                         self.project_root,
                                         context_note=f"\n<!-- Extension: {ext_id} -->\n<!-- Config: .specify/extensions/{ext_id}/ -->\n",
-                                        extension_id=ext_id,
                                     )
                                     registered = True
                             except Exception:
@@ -1310,8 +1199,6 @@ class PresetManager:
                     "command_name": cmd_name,
                     "source_file": source_file,
                     "source": f"extension:{manifest.id}",
-                    "extension_id": manifest.id,
-                    "extension_dir": ext_root,
                 }
                 modern_skill_name, legacy_skill_name = self._skill_names_for_command(cmd_name)
                 restore_index.setdefault(modern_skill_name, restore_info)
@@ -1576,17 +1463,6 @@ class PresetManager:
             if extension_restore:
                 content = extension_restore["source_file"].read_text(encoding="utf-8")
                 frontmatter, body = registrar.parse_frontmatter(content)
-                # Mirror the register-time rewrite (#2101): resolve
-                # extension-relative subdir references (agents/,
-                # knowledge-base/, etc.) to their installed location before
-                # the generic placeholder resolution below, otherwise
-                # restoring after a preset override removal would leave
-                # bare, unresolvable paths in the skill body.
-                body = registrar.rewrite_extension_paths(
-                    body,
-                    extension_restore["extension_id"],
-                    extension_restore["extension_dir"],
-                )
                 if isinstance(selected_ai, str):
                     body = registrar.resolve_skill_placeholders(
                         selected_ai, frontmatter, body, self.project_root
@@ -1739,73 +1615,8 @@ class PresetManager:
                     stacklevel=2,
                 )
 
-        # Seed/re-seed memory/constitution.md from a preset-provided
-        # constitution-template. The constitution is the only template that is
-        # materialized to a live file rather than resolved on demand, so a
-        # preset that ships one (e.g. strategy: replace with a ratified
-        # constitution) must be propagated here. Guard against clobbering an
-        # already-authored constitution by only replacing a file whose recorded
-        # hash (or exact legacy core-template content) proves it was generated.
-        self._seed_constitution_from_preset(manifest, dest_dir)
-
         return manifest
 
-    def _seed_constitution_from_preset(
-        self, manifest: PresetManifest, preset_dir: Path
-    ) -> None:
-        """Seed memory/constitution.md from a preset constitution-template.
-
-        Only runs when the preset declares a ``type: template`` entry named
-        ``constitution-template`` or provides one at a convention path, and the
-        live memory file is either missing or is an unchanged generated file.
-        Authored constitutions are never overwritten.
-        """
-        provides_constitution = any(
-            t.get("type") == "template" and t.get("name") == "constitution-template"
-            for t in manifest.templates
-        ) or any(
-            (preset_dir / relative_path).is_file()
-            for relative_path in (
-                "templates/constitution-template.md",
-                "constitution-template.md",
-            )
-        )
-        if not provides_constitution:
-            return
-
-        self.reconcile_constitution(
-            f"Failed to seed constitution from preset {manifest.id}",
-            create_if_missing=True,
-        )
-
-    def reconcile_constitution(
-        self, failure_context: str, *, create_if_missing: bool = False
-    ) -> None:
-        """Reconcile generated constitution content without failing a persisted change."""
-        try:
-            self._reconcile_constitution(create_if_missing=create_if_missing)
-        except (OSError, UnicodeDecodeError, PresetValidationError, ValueError) as exc:
-            import warnings
-
-            warnings.warn(
-                f"{failure_context}: {exc}.",
-                stacklevel=2,
-            )
-
-    def _reconcile_constitution(self, *, create_if_missing: bool = False) -> None:
-        """Materialize the winning constitution layer when the live file is generated."""
-        memory_constitution = (
-            self.project_root / ".specify" / "memory" / "constitution.md"
-        )
-        if not memory_constitution.exists() and not create_if_missing:
-            return
-        resolver = PresetResolver(self.project_root)
-        if memory_constitution.exists() and not _constitution_is_generated(
-            self.project_root, memory_constitution, resolver
-        ):
-            return
-        _materialize_constitution_template(self.project_root, memory_constitution)
-
     def install_from_zip(
         self,
         zip_path: Path,
@@ -1885,25 +1696,6 @@ class PresetManager:
         # Also include aliases from the manifest as a safety net for registries
         # populated by older versions that may not track aliases.
         removed_cmd_names = set()
-        removed_constitution = any(
-            path.exists()
-            for path in (
-                pack_dir / "templates" / "constitution-template.md",
-                pack_dir / "constitution-template.md",
-            )
-        )
-        if metadata and isinstance(metadata.get("version"), str):
-            memory_constitution = (
-                self.project_root / ".specify" / "memory" / "constitution.md"
-            )
-            removed_constitution = removed_constitution or (
-                _constitution_provenance_matches_preset(
-                    self.project_root,
-                    memory_constitution,
-                    pack_id,
-                    metadata["version"],
-                )
-            )
         for cmd_names in registered_commands.values():
             removed_cmd_names.update(cmd_names)
         manifest_path = pack_dir / "preset.yml"
@@ -1911,11 +1703,6 @@ class PresetManager:
             try:
                 manifest = PresetManifest(manifest_path)
                 for tmpl in manifest.templates:
-                    if (
-                        tmpl.get("type") == "template"
-                        and tmpl.get("name") == "constitution-template"
-                    ):
-                        removed_constitution = True
                     if tmpl.get("type") == "command":
                         for alias in tmpl.get("aliases", []):
                             if isinstance(alias, str):
@@ -1962,18 +1749,6 @@ class PresetManager:
                     stacklevel=2,
                 )
 
-        if removed_constitution:
-            try:
-                self._reconcile_constitution()
-            except (OSError, UnicodeDecodeError, PresetValidationError, ValueError) as exc:
-                import warnings
-
-                warnings.warn(
-                    f"Post-removal constitution reconciliation failed for {pack_id}: "
-                    f"{exc}. The live constitution may be stale.",
-                    stacklevel=2,
-                )
-
         return True
 
     def list_installed(self) -> List[Dict[str, Any]]:
@@ -2799,39 +2574,6 @@ class PresetResolver:
                 self._manifest_cache[key] = None
         return self._manifest_cache[key]
 
-    def _manifest_declared_template(
-        self, pack_dir: Path, template_name: str, template_type: str
-    ) -> tuple[dict | None, Path | None]:
-        """Resolve a preset's manifest-declared template entry and usable file.
-
-        Returns ``(entry, candidate)``:
-        - ``entry`` is the matching ``provides.templates`` mapping, or ``None`` if
-          the manifest is absent or does not list this ``(name, type)``.
-        - ``candidate`` is the declared ``file:`` resolved under ``pack_dir`` IFF
-          it is a regular file (``is_file()``); ``None`` otherwise — a missing,
-          empty, or non-file (e.g. directory) declaration yields ``(entry, None)``.
-
-        The manifest is authoritative: when it declares a template (``entry`` is
-        not ``None``) but the file is unusable (``candidate`` is ``None``),
-        callers must NOT fall back to the convention lookup — that would mask a
-        typo or pick up an undeclared file. Shared by ``resolve()`` and
-        ``collect_all_layers()`` so their manifest-first resolution cannot
-        silently diverge again (the divergence this fix addressed).
-        """
-        manifest = self._get_manifest(pack_dir)
-        if not manifest:
-            return None, None
-        for tmpl in manifest.templates:
-            if tmpl.get("name") == template_name and tmpl.get("type") == template_type:
-                file_path = tmpl.get("file")
-                if file_path:
-                    manifest_candidate = pack_dir / file_path
-                    return tmpl, (
-                        manifest_candidate if manifest_candidate.is_file() else None
-                    )
-                return tmpl, None
-        return None, None
-
     def _get_all_extensions_by_priority(self) -> list[tuple[int, str, dict | None]]:
         """Build unified list of registered and unregistered extensions sorted by priority.
 
@@ -2934,27 +2676,6 @@ class PresetResolver:
             registry = PresetRegistry(self.presets_dir)
             for pack_id, _metadata in registry.list_by_priority():
                 pack_dir = self.presets_dir / pack_id
-                # The preset manifest is authoritative: if it declares this
-                # template with an explicit ``file:``, resolve to that path —
-                # and do NOT fall back to convention when it's missing, to
-                # avoid masking typos or picking up an undeclared file. Only
-                # when the manifest is absent or doesn't list this template do
-                # we use the convention-based subdir lookup. Mirrors
-                # collect_all_layers()/resolve_content() so resolve() and
-                # resolve_with_source() agree with them instead of returning
-                # the core template (or a stray convention file).
-                entry, manifest_candidate = self._manifest_declared_template(
-                    pack_dir, template_name, template_type
-                )
-                if manifest_candidate is not None:
-                    return manifest_candidate
-                if entry is not None:
-                    # Manifest declares this template but the file is missing,
-                    # non-file (e.g. a directory), or an empty/falsey ``file``
-                    # value. The manifest is authoritative, so skip this pack's
-                    # convention fallback rather than mask a typo — mirrors
-                    # collect_all_layers().
-                    continue
                 for subdir in subdirs:
                     if subdir:
                         candidate = pack_dir / subdir / f"{template_name}{ext}"
@@ -3222,22 +2943,31 @@ class PresetResolver:
                 pack_dir = self.presets_dir / pack_id
                 # Read strategy and manifest file path from preset manifest
                 strategy = "replace"
+                manifest_file_path = None
                 manifest_has_strategy = False
-                entry, manifest_candidate = self._manifest_declared_template(
-                    pack_dir, template_name, template_type
-                )
-                if entry is not None:
-                    strategy = entry.get("strategy", "replace")
-                    manifest_has_strategy = "strategy" in entry
-                # Use the manifest's declared file when it's a usable regular file;
-                # only fall back to convention-based lookup when the manifest
-                # doesn't list this template at all, so preset.yml stays
-                # authoritative (a declared-but-unusable file skips convention —
-                # parity with resolve()).
+                manifest_found_entry = False
+                manifest = self._get_manifest(pack_dir)
+                if manifest:
+                    for tmpl in manifest.templates:
+                        if (tmpl.get("name") == template_name
+                                and tmpl.get("type") == template_type):
+                            strategy = tmpl.get("strategy", "replace")
+                            manifest_has_strategy = "strategy" in tmpl
+                            manifest_file_path = tmpl.get("file")
+                            manifest_found_entry = True
+                            break
+                # Use manifest file path if specified, otherwise convention-based
+                # lookup — but only when the manifest doesn't exist or doesn't
+                # list this template, so preset.yml stays authoritative.
                 candidate = None
-                if manifest_candidate is not None:
-                    candidate = manifest_candidate
-                elif entry is None:
+                if manifest_file_path:
+                    manifest_candidate = pack_dir / manifest_file_path
+                    if manifest_candidate.exists():
+                        candidate = manifest_candidate
+                    # Explicit file path that doesn't exist: skip convention
+                    # fallback to avoid masking typos or picking up unintended files.
+                elif not manifest_found_entry:
+                    # Manifest doesn't list this template — check convention paths
                     candidate = _find_in_subdirs(pack_dir)
                 if candidate:
                     # Legacy fallback: if manifest doesn't explicitly declare a
@@ -3308,8 +3038,6 @@ class PresetResolver:
                     "path": candidate,
                     "source": source,
                     "strategy": "replace",
-                    "extension_id": ext_id,
-                    "extension_dir": ext_dir,
                 })
 
         # Priority 4: Core templates (always "replace")
@@ -3429,32 +3157,10 @@ class PresetResolver:
         if not layers:
             return None
 
-        def _read_layer_content(layer: Dict[str, Any]) -> str:
-            """Read a layer's raw text, rewriting extension-relative subdir
-            references (agents/, knowledge-base/, etc.) to their installed
-            location when the layer is extension-provided (#2101).
-
-            Extension layers are always inserted with strategy "replace"
-            (see collect_all_layers), so a layer only ever needs this
-            rewrite when it wins outright above or serves as the
-            composition base below — never as a mid-stack composing
-            (append/prepend/wrap) layer.
-            """
-            text = layer["path"].read_text(encoding="utf-8")
-            extension_id = layer.get("extension_id")
-            extension_dir = layer.get("extension_dir")
-            if extension_id and extension_dir:
-                from ..agents import CommandRegistrar
-
-                text = CommandRegistrar.rewrite_extension_paths(
-                    text, extension_id, extension_dir
-                )
-            return text
-
         # If the top (highest-priority) layer is replace, it wins entirely —
         # lower layers are irrelevant regardless of their strategies.
         if layers[0]["strategy"] == "replace":
-            return _read_layer_content(layers[0])
+            return layers[0]["path"].read_text(encoding="utf-8")
 
         # Composition: build content bottom-up from the effective base.
         # The base is the nearest replace layer scanning from highest priority
@@ -3477,7 +3183,7 @@ class PresetResolver:
 
         # Convert to reversed_layers index
         base_reversed_idx = len(layers) - 1 - base_layer_idx
-        content = _read_layer_content(layers[base_layer_idx])
+        content = layers[base_layer_idx]["path"].read_text(encoding="utf-8")
         # Compose only the layers above the base (higher priority = lower index in layers,
         # higher index in reversed_layers). Process bottom-up from base+1.
         start_idx = base_reversed_idx + 1

src/specify_cli/presets/_commands.py

@@ -104,13 +104,7 @@ def preset_add(
             from ipaddress import ip_address
             from urllib.parse import urlparse as _urlparse
 
-            try:
-                _parsed = _urlparse(from_url)
-            except ValueError:
-                from rich.markup import escape as _escape_markup
-
-                console.print(f"[red]Error:[/red] Invalid URL: {_escape_markup(from_url)}")
-                raise typer.Exit(1)
+            _parsed = _urlparse(from_url)
 
             def _is_allowed_download_url(parsed_url):
                 host = parsed_url.hostname
@@ -141,9 +135,7 @@ def preset_add(
                 )
                 raise typer.Exit(1)
 
-            from rich.markup import escape as _esc
-
-            console.print(f"Installing preset from [cyan]{_esc(from_url)}[/cyan]...")
+            console.print(f"Installing preset from [cyan]{from_url}[/cyan]...")
             import urllib.error
             import tempfile
             import shutil
@@ -469,14 +461,7 @@ def preset_set_priority(
     raw_priority = metadata.get("priority")
     # Only skip if the stored value is already a valid int equal to requested priority
     # This ensures corrupted values (e.g., "high") get repaired even when setting to default (10)
-    # A bool is an int in Python (isinstance(True, int) is True), so exclude it explicitly —
-    # mirroring normalize_priority's bool guard — otherwise a corrupted True/False priority
-    # equals 1/0 here and is never repaired.
-    if (
-        isinstance(raw_priority, int)
-        and not isinstance(raw_priority, bool)
-        and raw_priority == priority
-    ):
+    if isinstance(raw_priority, int) and raw_priority == priority:
         console.print(f"[yellow]Preset '{preset_id}' already has priority {priority}[/yellow]")
         raise typer.Exit(0)
 
@@ -484,9 +469,6 @@ def preset_set_priority(
 
     # Update priority
     manager.registry.update(preset_id, {"priority": priority})
-    manager.reconcile_constitution(
-        f"Failed to reconcile constitution after changing priority for preset {preset_id}"
-    )
 
     console.print(f"[green]✓[/green] Preset '{preset_id}' priority changed: {old_priority} → {priority}")
     console.print("\n[dim]Lower priority = higher precedence in template resolution[/dim]")
@@ -520,9 +502,6 @@ def preset_enable(
 
     # Enable the preset
     manager.registry.update(preset_id, {"enabled": True})
-    manager.reconcile_constitution(
-        f"Failed to reconcile constitution after enabling preset {preset_id}"
-    )
 
     console.print(f"[green]✓[/green] Preset '{preset_id}' enabled")
     console.print("\nTemplates from this preset will now be included in resolution.")
@@ -557,9 +536,6 @@ def preset_disable(
 
     # Disable the preset
     manager.registry.update(preset_id, {"enabled": False})
-    manager.reconcile_constitution(
-        f"Failed to reconcile constitution after disabling preset {preset_id}"
-    )
 
     console.print(f"[green]✓[/green] Preset '{preset_id}' disabled")
     console.print("\nTemplates from this preset will be skipped during resolution.")

src/specify_cli/shared_infra.py

@@ -328,10 +328,7 @@ def refresh_shared_templates(
         _ensure_safe_shared_destination(project_path, dst)
         rel = dst.relative_to(project_path).as_posix()
         if dst.exists() and not force:
-            if rel not in tracked_files or rel in modified or manifest.is_recovered(rel):
-                # Never overwrite a recovered (pre-existing user) file without
-                # --force, matching install_shared_infra's is_recovered gate
-                # (#2918). Without this, refresh clobbers user content.
+            if rel not in tracked_files or rel in modified:
                 skipped_files.append(rel)
                 continue
 
@@ -347,7 +344,7 @@ def refresh_shared_templates(
 
     if skipped_files:
         console.print(
-            f"[yellow]⚠[/yellow]  {len(skipped_files)} modified, untracked, or preserved (recovered) shared template file(s) were not updated:"
+            f"[yellow]⚠[/yellow]  {len(skipped_files)} modified or untracked shared template file(s) were not updated:"
         )
         for rel in skipped_files:
             console.print(f"    {rel}")
@@ -403,7 +400,7 @@ def install_shared_infra(
     # manifest entries the core no longer ships (stale-script cleanup, #3076).
     seen_rels: set[str] = set()
     scripts_scanned = False
-    variant_dir = {"sh": "bash", "py": "python"}.get(script_type, "powershell")
+    variant_dir = "bash" if script_type == "sh" else "powershell"
 
     def _decide_overwrite(rel: str, dst: Path) -> tuple[bool, str | None]:
         """Return (write, bucket) where bucket is 'skip', 'preserved', or None."""
@@ -465,10 +462,6 @@ def install_shared_infra(
                     for src_path in variant_src.rglob("*"):
                         if not src_path.is_file():
                             continue
-                        # Python bytecode caches are local artifacts, not
-                        # workflow scripts — never install them.
-                        if "__pycache__" in src_path.parts:
-                            continue
                         # Mark scanned only once a real source file is seen. An
                         # empty (or symlink-skipped) variant keeps this False, so
                         # stale-cleanup is skipped — otherwise it would treat every