chore: bump version to 0.8.7

2026-07-04 04:45:43 +08:00 · 2026-05-07 15:41:10 +00:00
132 changed files with 3163 additions and 16315 deletions
--- a/.gitattributes
+++ b/.gitattributes
@@ -1,3 +1 @@
 * text=auto eol=lf
-
-.github/workflows/*.lock.yml linguist-generated=true merge=ours -whitespace
--- a/.github/aw/actions-lock.json
+++ b/.github/aw/actions-lock.json
@@ -1,14 +0,0 @@
-{
-  "entries": {
-    "actions/github-script@v9.0.0": {
-      "repo": "actions/github-script",
-      "version": "v9.0.0",
-      "sha": "3a2844b7e9c422d3c10d287c895573f7108da1b3"
-    },
-    "github/gh-aw-actions/setup@v0.74.8": {
-      "repo": "github/gh-aw-actions/setup",
-      "version": "v0.74.8",
-      "sha": "efa55847f72aadb03490d955263ff911bf758700"
-    }
-  }
-}
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -1,12 +1,11 @@
-updates:
- directory: /
-  package-ecosystem: pip
-  schedule:
-    interval: weekly
- directory: /
-  ignore:
-  - dependency-name: "github/gh-aw-actions/**" # Managed by gh aw compile. Version-locked to the gh-aw compiler; do not bump.
-  package-ecosystem: github-actions
-  schedule:
-    interval: weekly
 version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
--- a/.github/skills/add-community-extension/SKILL.md
+++ b/.github/skills/add-community-extension/SKILL.md
@@ -1,169 +0,0 @@
---
-name: add-community-extension
-description: 'Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension work.'
-argument-hint: 'GitHub issue URL or number for the extension submission'
---
-
-# Add Community Extension
-
-Process an extension submission issue and add or update it in the community catalog.
-
-## When to Use
-
- A new `[Extension]` submission issue is filed
- An existing extension submits an update issue (new version, changed metadata)
- You need to add or update a community extension in `extensions/catalog.community.json` and `docs/community/extensions.md`
-
-## Procedure
-
-### 1. Fetch the submission issue
-
-Read the GitHub issue to extract all metadata:
- Extension ID, name, version, description, author
- Repository URL, download URL, homepage, documentation, changelog
- License, required spec-kit version, optional tool dependencies
- Number of commands and hooks
- Tags
-
-### 2. Validate against publishing rules
-
-Check **all** of the following (per `extensions/EXTENSION-PUBLISHING-GUIDE.md`):
-
-| Check | How |
-|-------|-----|
-| Repository exists and is public | Fetch the repository URL |
-| `extension.yml` manifest present | Confirm in repo file listing |
-| README.md present | Confirm in repo file listing |
-| LICENSE file present | Confirm in repo file listing |
-| GitHub release exists matching version | Check releases on the repo page |
-| Download URL is accessible | Verify it follows `archive/refs/tags/vX.Y.Z.zip` pattern and release exists |
-| Extension ID is lowercase-with-hyphens only | Regex: `^[a-z][a-z0-9-]*$` |
-| Version follows semver | Format: `X.Y.Z` |
-| Submission checklists are all checked | Confirm in issue body |
-
-### 3. Determine if this is an add or update
-
-Search `extensions/catalog.community.json` for the extension ID.
-
- **Not found** → this is a **new addition**. Proceed to step 4.
- **Found** → this is an **update**. Proceed to step 4 but replace the existing entry in-place instead of inserting.
-
-### 4. Add or update `extensions/catalog.community.json`
-
-**New extension:** Insert the entry in **alphabetical order** by extension ID.
-
-**Update:** Replace the existing entry in-place. Update only the fields that changed (typically `version`, `download_url`, `description`, `provides`, `requires`, `tags`, `updated_at`). Preserve `created_at` and `downloads`/`stars` from the existing entry.
-
-Use the existing entries as the format template. Required fields:
-
-```json
-{
-  "<id>": {
-    "name": "<name>",
-    "id": "<id>",
-    "description": "<description>",
-    "author": "<author>",
-    "version": "<version>",
-    "download_url": "<download_url>",
-    "repository": "<repository>",
-    "homepage": "<homepage>",
-    "documentation": "<documentation>",
-    "changelog": "<changelog>",
-    "license": "<license>",
-    "requires": {
-      "speckit_version": "<speckit_version>"
-    },
-    "provides": {
-      "commands": <N>,
-      "hooks": <N>
-    },
-    "tags": ["<tag1>", "<tag2>"],
-    "verified": false,
-    "downloads": 0,
-    "stars": 0,
-    "created_at": "<today>T00:00:00Z",
-    "updated_at": "<today>T00:00:00Z"
-  }
-}
-```
-
-If the extension has optional tool dependencies, add a `"tools"` array inside `"requires"`:
-
-```json
-"tools": [{ "name": "<tool>", "required": false }]
-```
-
-Also update the top-level `"updated_at"` timestamp in the catalog.
-
-After editing, **validate the JSON** by running:
-
-```bash
-python3 -c "import json; json.load(open('extensions/catalog.community.json')); print('Valid JSON')"
-```
-
-### 5. Add or update `docs/community/extensions.md` community extensions table
-
-**New extension:** Insert a new row into the `# Community Extensions` table in **alphabetical order** by extension name.
-
-**Update:** Find the existing row and update the description or other changed fields in-place.
-
-Determine the category and effect from the extension's behavior:
-
-```
-| <Name> | <Description> | `<category>` | <Effect> | [<repo-name>](<repository-url>) |
-```
-
-**Category** — one of: `docs`, `code`, `process`, `integration`, `visibility`
-**Effect** — `Read-only` (produces reports only) or `Read+Write` (modifies project files)
-
-### 6. Commit, push, and open PR
-
-Use `add-` for new extensions, `update-` for updates:
-
-```bash
-# New extension
-git checkout -b add-<extension-id>-extension
-
-# Update
-git checkout -b update-<extension-id>-extension
-```
-
-```bash
-git add extensions/catalog.community.json docs/community/extensions.md
-
-# New extension
-git commit -m "Add <Name> extension to community catalog
-
-Add <id> extension submitted by @<issue-author> to:
- extensions/catalog.community.json (alphabetical order)
- docs/community/extensions.md community extensions table
-
-Closes #<issue-number>"
-
-# Update
-git commit -m "Update <Name> extension to v<version>
-
-Update <id> extension submitted by @<issue-author>:
- extensions/catalog.community.json (version, download_url, etc.)
- docs/community/extensions.md community extensions table
-
-Closes #<issue-number>"
-
-git push origin <branch-name>
-```
-
-Then create a PR to `upstream` (`github/spec-kit`) with:
- **Title:** `Add <Name> extension to community catalog` (or `Update <Name> extension to v<version>`)
- **Body:** Include validation summary, `Closes #<issue-number>`, and `cc @<issue-author>`
- **Head:** `<fork-owner>:<branch-name>`
- **Base:** `main`
-
-## Common Pitfalls
-
- **Alphabetical order matters** — entries must be sorted by ID in the JSON and by name in the docs table.
- **Don't forget the catalog `updated_at`** — the top-level timestamp in `catalog.community.json` must be refreshed.
- **Validate JSON after editing** — a trailing comma or missing brace will break the catalog.
- **Use `Closes` not `Fixes`** — `Closes #N` is the correct keyword for submission issues.
- **Match the proposed entry but verify** — the issue may include a proposed JSON block, but always validate field values against the actual repository state.
- **Preserve `created_at` on updates** — keep the original `created_at` value; only change `updated_at`.
- **Preserve `downloads` and `stars` on updates** — these reflect usage metrics and must not be reset.
--- a/.github/workflows/add-community-extension.lock.yml
+++ b/.github/workflows/add-community-extension.lock.yml
--- a/.github/workflows/add-community-extension.md
+++ b/.github/workflows/add-community-extension.md
@@ -1,288 +0,0 @@
---
-description: "Process community extension submission issues — validate, add to catalog, and open a PR for maintainer review"
-emoji: "🧩"
-
-on:
-  issues:
-    types: [opened, edited, labeled]
-  skip-bots: [github-actions, copilot, dependabot]
-
-tools:
-  edit:
-  bash: ["echo", "cat", "head", "tail", "grep", "wc", "sort", "python3", "jq", "date"]
-  github:
-    toolsets: [issues, repos]
-  web-fetch:
-
-permissions:
-  contents: read
-  issues: read
-
-checkout:
-  fetch-depth: 0
-
-safe-outputs:
-  create-pull-request:
-    title-prefix: "[extension] "
-    labels: [extension-submission, automated]
-    draft: true
-    max: 1
-    protected-files:
-      policy: blocked
-      exclude:
-        - README.md
-        - CHANGELOG.md
-  add-comment:
-    max: 2
-  add-labels:
-    allowed: [extension-submission, validation-passed, validation-failed, needs-info]
-    max: 3
---
-
-# Add Community Extension from Issue Submission
-
-You are a catalog maintenance agent for the Spec Kit project. Your job is to
-process community extension submission issues and create pull requests that add
-or update entries in the community extension catalog.
-
-## Triggering Conditions
-
-This workflow triggers on issue events. **Only process the issue if ALL of these
-conditions are met:**
-
-1. The issue has the `extension-submission` label
-2. The issue title starts with `[Extension]:`
-
-If the issue does not meet these conditions, add a brief comment explaining that
-this workflow only processes extension submission issues, then stop.
-
-## Step 1 — Read and Parse the Issue
-
-Read issue #${{ github.event.issue.number }}.
-
-Extract the following fields from the structured issue body (GitHub issue form
-fields):
-
-| Field | Issue Form ID | Required |
-|-------|--------------|----------|
-| Extension ID | `extension-id` | Yes |
-| Extension Name | `extension-name` | Yes |
-| Version | `version` | Yes |
-| Description | `description` | Yes |
-| Author | `author` | Yes |
-| Repository URL | `repository` | Yes |
-| Download URL | `download-url` | Yes |
-| License | `license` | Yes |
-| Homepage | `homepage` | No |
-| Documentation URL | `documentation` | No |
-| Changelog URL | `changelog` | No |
-| Required Spec Kit Version | `speckit-version` | Yes |
-| Required Tools | `required-tools` | No |
-| Number of Commands | `commands-count` | Yes |
-| Number of Hooks | `hooks-count` | No (default 0) |
-| Tags | `tags` | Yes |
-| Proposed Catalog Entry | `catalog-entry` | Yes |
-
-The issue body uses GitHub's issue form format. Each field appears under a
-heading matching the field label (e.g., `### Extension ID` followed by the
-value). Parse accordingly.
-
-## Step 2 — Validate the Submission
-
-Run **all** of the following validation checks. Collect all results before
-deciding pass/fail:
-
-### 2a. Extension ID format
- Must match regex: `^[a-z][a-z0-9-]*$`
- Must be lowercase with hyphens only
-
-### 2b. Version format
- Must follow semver: `X.Y.Z` (digits only, no `v` prefix)
-
-### 2c. Repository validation
- Fetch the repository URL — confirm it exists and is publicly accessible
- Confirm the repository contains an `extension.yml` file
- Confirm the repository contains a `README.md` file
- Confirm the repository contains a `LICENSE` file
-
-### 2d. Release and download URL validation
- The download URL should follow the pattern
-  `https://github.com/<owner>/<repo>/archive/refs/tags/v<version>.zip`
-  or
-  `https://github.com/<owner>/<repo>/releases/download/<tag>/<asset>.zip`
- Verify a GitHub release exists matching the submitted version
-
-### 2e. Submission checklists
- Confirm that all required checkboxes in the Testing Checklist and Submission
-  Requirements sections are checked (`[x]`)
-
-### Validation outcome
-
-If **any** validation fails:
-1. Add a comment on the issue listing each failed check with a clear explanation
-   of what's wrong and how to fix it
-2. Add the `validation-failed` label
-3. **Stop — do not proceed further**
-
-If all validations pass:
-1. Add the `validation-passed` label
-2. Continue to Step 3
-
-## Step 3 — Determine Add vs Update
-
-Search `extensions/catalog.community.json` for the extension ID.
-
- **Not found** → this is a **new addition**
- **Found** → this is an **update** — replace the existing entry in-place;
-  preserve `created_at`, `downloads`, and `stars` from the existing entry
-
-## Step 4 — Update `extensions/catalog.community.json`
-
-Edit `extensions/catalog.community.json` to add or update the extension entry.
-
-### For a new extension
-
-Insert the entry in **alphabetical order by extension ID** within the
-`"extensions"` object. Use this structure:
-
-```json
-{
-  "<id>": {
-    "name": "<name>",
-    "id": "<id>",
-    "description": "<description>",
-    "author": "<author>",
-    "version": "<version>",
-    "download_url": "<download_url>",
-    "repository": "<repository>",
-    "homepage": "<homepage or repository>",
-    "documentation": "<documentation or repository README>",
-    "changelog": "<changelog or empty string>",
-    "license": "<license>",
-    "requires": {
-      "speckit_version": "<speckit_version>"
-    },
-    "provides": {
-      "commands": <N>,
-      "hooks": <N>
-    },
-    "tags": ["<tag1>", "<tag2>"],
-    "verified": false,
-    "downloads": 0,
-    "stars": 0,
-    "created_at": "<today>T00:00:00Z",
-    "updated_at": "<today>T00:00:00Z"
-  }
-}
-```
-
-If the extension has optional tool dependencies, add a `"tools"` array inside
-`"requires"`:
-
-```json
-"tools": [{ "name": "<tool>", "required": false }]
-```
-
-### For an update
-
-Replace only the changed fields (typically `version`, `download_url`,
-`description`, `provides`, `requires`, `tags`, `updated_at`). **Preserve**
-`created_at`, `downloads`, and `stars` from the existing entry.
-
-### After editing
-
-Update the **top-level `"updated_at"` timestamp** in the catalog to today's date
-in ISO 8601 format.
-
-Validate the JSON by running:
-
-```bash
-python3 -c "import json; json.load(open('extensions/catalog.community.json')); print('Valid JSON')"
-```
-
-If validation fails, fix the JSON and re-validate before continuing.
-
-## Step 5 — Update `docs/community/extensions.md`
-
-Edit `docs/community/extensions.md` to add or update a row in the Community
-Extensions table.
-
-### For a new extension
-
-Insert a new row in **alphabetical order by extension name**:
-
-```
-| <Name> | <Description> | `<category>` | <Effect> | [<repo-name>](<repository-url>) |
-```
-
-Determine the category from the extension's behavior:
- `docs` — reads, validates, or generates spec artifacts
- `code` — reviews, validates, or modifies source code
- `process` — orchestrates workflow across phases
- `integration` — syncs with external platforms
- `visibility` — reports on project health or progress
-
-Determine the effect:
- `Read-only` — produces reports only
- `Read+Write` — modifies project files
-
-### For an update
-
-Find the existing row and update any changed fields in-place.
-
-## Step 6 — Create Pull Request
-
-Create a pull request with the changes. Use this branch naming convention:
-
- **New extension:** `add-<extension-id>-extension`
- **Update:** `update-<extension-id>-extension`
-
-### Commit message
-
-For a new extension:
-```
-Add <Name> extension to community catalog
-
-Add <id> extension submitted by @<issue-author> to:
- extensions/catalog.community.json (alphabetical order)
- docs/community/extensions.md community extensions table
-
-Closes #<issue-number>
-```
-
-For an update:
-```
-Update <Name> extension to v<version>
-
-Update <id> extension submitted by @<issue-author>:
- extensions/catalog.community.json (version, download_url, etc.)
- docs/community/extensions.md community extensions table
-
-Closes #<issue-number>
-```
-
-### PR description
-
-Include:
- A summary of what changed
- Validation results (all checks passed)
- `Closes #${{ github.event.issue.number }}`
- `cc @<issue-author>` — mention the submitter
-
-## Important Rules
-
- **Alphabetical order matters** — entries must be sorted by ID in the JSON and
-  by name in the docs table
- **Always validate JSON** after editing — a trailing comma or missing brace
-  will break the catalog
- **Use `Closes` not `Fixes`** — `Closes #N` is the correct keyword for
-  submission issues
- **Match the proposed entry but verify** — the issue may include a proposed
-  JSON block, but always validate field values against the actual repository
-  state rather than blindly trusting the submitter's JSON
- **Preserve `created_at` on updates** — keep the original value; only update
-  `updated_at`
- **Preserve `downloads` and `stars` on updates** — these reflect usage metrics
-  and must not be reset
- **Do not modify any other files** — only `extensions/catalog.community.json`
-  and `docs/community/extensions.md`
--- a/.github/workflows/add-community-preset.lock.yml
+++ b/.github/workflows/add-community-preset.lock.yml
--- a/.github/workflows/add-community-preset.md
+++ b/.github/workflows/add-community-preset.md
@@ -1,282 +0,0 @@
---
-description: "Process community preset submission issues — validate, add to catalog, and open a PR for maintainer review"
-emoji: "🎨"
-
-on:
-  issues:
-    types: [opened, edited, labeled]
-  skip-bots: [github-actions, copilot, dependabot]
-
-tools:
-  edit:
-  bash: ["echo", "cat", "head", "tail", "grep", "wc", "sort", "python3", "jq", "date"]
-  github:
-    toolsets: [issues, repos]
-  web-fetch:
-
-permissions:
-  contents: read
-  issues: read
-
-checkout:
-  fetch-depth: 0
-
-safe-outputs:
-  create-pull-request:
-    title-prefix: "[preset] "
-    labels: [preset-submission, automated]
-    draft: true
-    max: 1
-    protected-files:
-      policy: blocked
-      exclude:
-        - README.md
-        - CHANGELOG.md
-  add-comment:
-    max: 2
-  add-labels:
-    allowed: [preset-submission, validation-passed, validation-failed, needs-info]
-    max: 3
---
-
-# Add Community Preset from Issue Submission
-
-You are a catalog maintenance agent for the Spec Kit project. Your job is to
-process community preset submission issues and create pull requests that add
-or update entries in the community preset catalog.
-
-## Triggering Conditions
-
-This workflow triggers on issue events. **Only process the issue if ALL of these
-conditions are met:**
-
-1. The issue has the `preset-submission` label
-2. The issue title starts with `[Preset]:`
-
-If the issue does not meet these conditions, add a brief comment explaining that
-this workflow only processes preset submission issues, then stop.
-
-## Step 1 — Read and Parse the Issue
-
-Read issue #${{ github.event.issue.number }}.
-
-Extract the following fields from the structured issue body (GitHub issue form
-fields):
-
-| Field | Issue Form ID | Required |
-|-------|--------------|----------|
-| Preset ID | `preset-id` | Yes |
-| Preset Name | `preset-name` | Yes |
-| Version | `version` | Yes |
-| Description | `description` | Yes |
-| Author | `author` | Yes |
-| Repository URL | `repository` | Yes |
-| Download URL | `download-url` | Yes |
-| License | `license` | Yes |
-| Required Spec Kit Version | `speckit-version` | Yes |
-| Required Extensions | `required-extensions` | No |
-| Templates Provided | `templates-provided` | Yes |
-| Commands Provided | `commands-provided` | Yes |
-| Number of Scripts | `scripts-count` | No (default 0) |
-| Tags | `tags` | Yes |
-
-The issue body uses GitHub's issue form format. Each field appears under a
-heading matching the field label (e.g., `### Preset ID` followed by the
-value). Parse accordingly.
-
-## Step 2 — Validate the Submission
-
-Run **all** of the following validation checks. Collect all results before
-deciding pass/fail:
-
-### 2a. Preset ID format
- Must match regex: `^[a-z][a-z0-9-]*$`
- Must be lowercase with hyphens only
-
-### 2b. Version format
- Must follow semver: `X.Y.Z` (digits only, no `v` prefix)
-
-### 2c. Repository validation
- Fetch the repository URL — confirm it exists and is publicly accessible
- Confirm the repository contains a `preset.yml` file
- Confirm the repository contains a `README.md` file
- Confirm the repository contains a `LICENSE` file
-
-### 2d. Release and download URL validation
- The download URL should follow the pattern
-  `https://github.com/<owner>/<repo>/archive/refs/tags/v<version>.zip`
-  or
-  `https://github.com/<owner>/<repo>/releases/download/<tag>/<asset>.zip`
- Verify a GitHub release exists matching the submitted version
-
-### 2e. Submission checklists
- Confirm that all required checkboxes in the Testing Checklist and Submission
-  Requirements sections are checked (`[x]`)
-
-### Validation outcome
-
-If **any** validation fails:
-1. Add a comment on the issue listing each failed check with a clear explanation
-   of what's wrong and how to fix it
-2. Add the `validation-failed` label
-3. **Stop — do not proceed further**
-
-If all validations pass:
-1. Add the `validation-passed` label
-2. Continue to Step 3
-
-## Step 3 — Determine Add vs Update
-
-Search `presets/catalog.community.json` for the preset ID.
-
- **Not found** → this is a **new addition**
- **Found** → this is an **update** — replace the existing entry in-place;
-  preserve `created_at` from the existing entry
-
-## Step 4 — Update `presets/catalog.community.json`
-
-Edit `presets/catalog.community.json` to add or update the preset entry.
-
-### For a new preset
-
-Insert the entry in **alphabetical order by preset ID** within the
-`"presets"` object. Use this structure:
-
-```json
-{
-  "<id>": {
-    "name": "<name>",
-    "id": "<id>",
-    "version": "<version>",
-    "description": "<description>",
-    "author": "<author>",
-    "repository": "<repository>",
-    "download_url": "<download_url>",
-    "homepage": "<homepage or repository>",
-    "documentation": "<documentation or repository README>",
-    "license": "<license>",
-    "requires": {
-      "speckit_version": "<speckit_version>"
-    },
-    "provides": {
-      "templates": <N>,
-      "commands": <N>
-    },
-    "tags": ["<tag1>", "<tag2>"],
-    "created_at": "<today>T00:00:00Z",
-    "updated_at": "<today>T00:00:00Z"
-  }
-}
-```
-
-If the preset has required extensions, add an `"extensions"` array inside
-`"requires"`:
-
-```json
-"requires": {
-  "speckit_version": "<speckit_version>",
-  "extensions": ["<extension-id>"]
-}
-```
-
-If the preset provides scripts, add `"scripts": <N>` inside `"provides"`.
-
-### For an update
-
-Replace only the changed fields (typically `version`, `download_url`,
-`description`, `provides`, `requires`, `tags`, `updated_at`). **Preserve**
-`created_at` from the existing entry.
-
-### Counting templates and commands
-
-Parse the "Templates Provided" and "Commands Provided" issue fields:
- Count the number of list items (lines starting with `-`)
- If the field says "None", the count is 0
-
-### After editing
-
-Update the **top-level `"updated_at"` timestamp** in the catalog to today's date
-in ISO 8601 format.
-
-Validate the JSON by running:
-
-```bash
-python3 -c "import json; json.load(open('presets/catalog.community.json')); print('Valid JSON')"
-```
-
-If validation fails, fix the JSON and re-validate before continuing.
-
-## Step 5 — Update `docs/community/presets.md`
-
-Edit `docs/community/presets.md` to add or update a row in the Community
-Presets table.
-
-### For a new preset
-
-Insert a new row in **alphabetical order by preset name**:
-
-```
-| <Name> | <Description> | <N> templates, <N> commands | <Requires> | [<repo-name>](<repository-url>) |
-```
-
-For the Requires column:
- Use `—` if no extensions are required
- List required extension names if any (e.g., `AIDE extension`)
-
-If the preset provides scripts, include them: `<N> templates, <N> commands, <N> scripts`
-
-### For an update
-
-Find the existing row and update any changed fields in-place.
-
-## Step 6 — Create Pull Request
-
-Create a pull request with the changes. Use this branch naming convention:
-
- **New preset:** `add-<preset-id>-preset`
- **Update:** `update-<preset-id>-preset`
-
-### Commit message
-
-For a new preset:
-```
-Add <Name> preset to community catalog
-
-Add <id> preset submitted by @<issue-author> to:
- presets/catalog.community.json (alphabetical order)
- docs/community/presets.md community presets table
-
-Closes #<issue-number>
-```
-
-For an update:
-```
-Update <Name> preset to v<version>
-
-Update <id> preset submitted by @<issue-author>:
- presets/catalog.community.json (version, download_url, etc.)
- docs/community/presets.md community presets table
-
-Closes #<issue-number>
-```
-
-### PR description
-
-Include:
- A summary of what changed
- Validation results (all checks passed)
- `Closes #${{ github.event.issue.number }}`
- `cc @<issue-author>` — mention the submitter
-
-## Important Rules
-
- **Alphabetical order matters** — entries must be sorted by ID in the JSON and
-  by name in the docs table
- **Always validate JSON** after editing — a trailing comma or missing brace
-  will break the catalog
- **Use `Closes` not `Fixes`** — `Closes #N` is the correct keyword for
-  submission issues
- **Preserve `created_at` on updates** — keep the original value; only update
-  `updated_at`
- **Do not modify any other files** — only `presets/catalog.community.json`
-  and `docs/community/presets.md`
--- a/.github/workflows/catalog-assign.yml
+++ b/.github/workflows/catalog-assign.yml
@@ -19,7 +19,7 @@ jobs:
    permissions:
      issues: write
    steps:
-      - uses: actions/github-script@v9
+      - uses: actions/github-script@v7
        with:
          script: |
            const issue = context.payload.issue;
--- a/.github/workflows/codeql.yml
+++ b/.github/workflows/codeql.yml
@@ -19,14 +19,14 @@ jobs:
        language: [ 'actions', 'python' ]
    steps:
      - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4

      - name: Initialize CodeQL
-        uses: github/codeql-action/init@9e0d7b8d25671d64c341c19c0152d693099fb5ba # v4
+        uses: github/codeql-action/init@e46ed2cbd01164d986452f91f178727624ae40d7 # v4
        with:
          languages: ${{ matrix.language }}

      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@9e0d7b8d25671d64c341c19c0152d693099fb5ba # v4
+        uses: github/codeql-action/analyze@e46ed2cbd01164d986452f91f178727624ae40d7 # v4
        with:
          category: "/language:${{ matrix.language }}"
--- a/.github/workflows/docs.yml
+++ b/.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@c2fa09f4bde5ebb9d1777cf28262a3eb3db3ced7 # v5.2.0
+        uses: actions/setup-dotnet@67a3573c9a986a3f9c594539f4ab511d57bb3ce9 # v4
        with:
          dotnet-version: '8.x'

--- a/.github/workflows/lint.yml
+++ b/.github/workflows/lint.yml
@@ -13,31 +13,9 @@ jobs:
    steps:
      - name: Checkout
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
-        with:
-          fetch-depth: 1
-
-      - name: Run git diff --check
-        shell: bash
-        env:
-          EVENT_NAME: ${{ github.event_name }}
-          PR_BASE_SHA: ${{ github.event.pull_request.base.sha }}
-          PUSH_BEFORE_SHA: ${{ github.event.before }}
-          GITHUB_SHA: ${{ github.sha }}
-        run: |
-          set -euo pipefail
-
-          if [ "$EVENT_NAME" = "pull_request" ]; then
-            git fetch --no-tags --depth=1 origin "+${PR_BASE_SHA}:refs/checks/pr-base"
-            git diff --check refs/checks/pr-base HEAD
-          elif [ "$PUSH_BEFORE_SHA" = "0000000000000000000000000000000000000000" ]; then
-            git diff-tree --check --no-commit-id --root -r "$GITHUB_SHA"
-          else
-            git fetch --no-tags --depth=1 origin "+${PUSH_BEFORE_SHA}:refs/checks/push-before"
-            git diff --check refs/checks/push-before HEAD
-          fi

      - name: Run markdownlint-cli2
-        uses: DavidAnson/markdownlint-cli2-action@ded1f9488f68a970bc66ea5619e13e9b52e601cd # v23
+        uses: DavidAnson/markdownlint-cli2-action@6b51ade7a9e4a75a7ad929842dd298a3804ebe8b # v23
        with:
          globs: |
            '**/*.md'
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -14,7 +14,7 @@ jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
-      - uses: actions/stale@eb5cf3af3ac0a1aa4c9c45633dd1ae542a27a899 # v10
+      - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # v10
        with:
          # Days of inactivity before an issue or PR becomes stale
          days-before-stale: 150
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -13,7 +13,7 @@ jobs:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4

      - name: Install uv
        uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
@@ -34,7 +34,7 @@ jobs:
        python-version: ["3.11", "3.12", "3.13"]
    steps:
      - name: Checkout
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4

      - name: Install uv
        uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -379,33 +379,6 @@ Implementation: Extends `YamlIntegration` (parallel to `TomlIntegration`):
 4. Uses `yaml.safe_dump()` for header fields to ensure proper escaping
 5. Sets `context_file = "AGENTS.md"` so the base setup manages the Spec Kit context section there

-## Branch Naming Convention
-
-Branches follow one of two patterns depending on whether an issue exists:
-
-```
-<type>/<number>-<short-slug>   # when an issue is created first
-<type>/<short-slug>            # when no issue exists (PR-only changes)
-```
-
-When an issue exists, include its number immediately after the prefix — this is what makes branches traceable. For small or self-contained changes that go straight to a PR without a tracking issue, omit the number.
-
-| Prefix | When to use | Example |
-|---|---|---|
-| `feat/` | New features | `feat/2342-workflow-cli-alignment` |
-| `fix/` | Bug fixes | `fix/2653-paths-only-validation` |
-| `docs/` | Documentation changes | `docs/2677-branch-naming-convention`, `docs/update-landing-stats` |
-| `community/` | Community catalog additions | `community/2492-add-mde-extension` |
-| `chore/` | Maintenance, tooling, CI | `chore/2366-editorconfig` |
-
-**Rules:**
-
-1. Include the issue number when one exists — this is what makes branches traceable
-2. Use kebab-case for the slug
-3. Keep the slug short — enough to identify the work without looking up the issue
-
---
-
 ## Common Pitfalls

 1. **Using shorthand keys for CLI-based integrations**: For CLI-based integrations (`requires_cli: True`), the `key` must match the executable name (e.g., `"cursor-agent"` not `"cursor"`). `shutil.which(key)` is used for CLI tool checks — mismatches require special-case mappings. IDE-based integrations (`requires_cli: False`) are not subject to this constraint.
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,157 +2,6 @@

 <!-- insert new changelog below this comment -->

-## [0.8.17] - 2026-05-28
-
-### Changed
-
- docs: consolidate Community sections in README (#2736)
- Fix shared script command hints for integration separators (#2627)
- docs: update security-governance preset to v0.4.0 (#2703)
- feat(agy): enhance Google Antigravity CLI integration (#2689)
- Fix --dev extension agent symlinks (#2554)
- Share skills hook note post-processing (#2679)
- feat: add Hermes Agent integration (with review fixes) (#2651)
- Update Superpowers Implementation Bridge to v0.7.0 (#2732)
- chore: release 0.8.16, begin 0.8.17.dev0 development (#2729)
-
-## [0.8.16] - 2026-05-27
-
-### Changed
-
- docs: update landing page stats and branch naming convention (#2727)
- feat(workflows): expose {{ context.run_id }} template variable (#2664)
- fix: resolve __SPECKIT_COMMAND_*__ refs in preset skill rendering (#2717) (#2718)
- Add Workflow Preset to community catalog (#2725)
- fix: paths-only skips branch validation, setup-plan preserves existing plan (#2672)
- docs: fix broken pipx homepage URLs to point to pipx.pypa.io (#2670)
- Update Architecture Guard extension to v1.8.9 (#2723)
- Re-validate spec quality checklist after clarify updates spec (#2715)
- chore: release 0.8.15, begin 0.8.16.dev0 development (#2722)
-
-## [0.8.15] - 2026-05-27
-
-### Changed
-
- Update Fiction Book Writing preset to v1.8.1 (#2714)
- chore: update memorylint and superb to 1.4.0 (#2690)
- fix: promote post-execution hook dispatch to H2 with directive language (#2713)
- Add Token Budget extension to community catalog (#2712)
- fix: create skills directory on demand during extension/preset install (#2711)
- fix: PS 5.1 compat — replace non-ASCII chars in shipped PowerShell scripts (#2709)
- docs: update security-governance preset to v0.3.0 (#2676)
- Update README.md (#2675)
- chore: release 0.8.14, begin 0.8.15.dev0 development (#2706)
-
-## [0.8.14] - 2026-05-26
-
-### Changed
-
- Add util for windows sub-process (#2598)
- refactor: create commands/ package and move init handler (PR-4/8) (#2615)
- Add Product Spec Extension to community catalog (#2705)
- fix init-options speckit version refresh (#2647)
- chore(deps): bump github/gh-aw-actions from 0.74.8 to 0.74.9 (#2658)
- docs: add branch naming convention to AGENTS.md and CONTRIBUTING.md (#2678)
- chore(deps): bump actions/stale from 10.2.0 to 10.3.0 (#2657)
- chore(deps): bump github/codeql-action from 4.35.4 to 4.35.5 (#2656)
- chore: release 0.8.13, begin 0.8.14.dev0 development (#2669)
-
-## [0.8.13] - 2026-05-21
-
-### Changed
-
- fix: while/do-while loop condition reads stale iteration-0 step output (#2662)
- docs: fix directory hierarchy in README examples (#2639)
- fix(catalogs): reject boolean priority in extension and preset catalog readers (#2589)
- Update Agent Governance extension to v1.2.0 (#2659)
- Add agentic workflows for community catalog submissions (#2655)
- feat: add self-check tip to check output (#2574)
- fix(cli): clarify exception diagnostics (#2602)
- ci: add diff whitespace check (#2572)
- chore: release 0.8.12, begin 0.8.13.dev0 development (#2648)
-
-## [0.8.12] - 2026-05-20
-
-### Changed
-
- fix(codex): inject dot-to-hyphen hook command note in Codex skills (#2503)
- Update Squad Bridge extension to v1.3.0 (#2645)
- Update Superpowers Implementation Bridge extension to v0.5.0 (#2644)
- Add Team Assign extension to community catalog (#2642)
- refactor: migrate extension catalog stack parsing to shared base (#2576)
- Update Architecture Workflow extension to v1.1.0 (#2588)
-  fix(workflow): support integration: auto to follow project's initialized AI (#2421)
- Add Superpowers Implementation Bridge extension to community catalog (#2586)
- Add Interactive HTML Preview extension to community catalog (#2585)
- chore: release 0.8.11, begin 0.8.12.dev0 development (#2584)
- Update Agent Governance extension to v1.1.0 (#2583)
-
-## [0.8.11] - 2026-05-15
-
-### Changed
-
- refactor: extract _version.py from __init__.py (PR-3/8) (#2550)
- Add Time Machine extension to community catalog (#2580)
- fix(powershell): ensure UTF-8 templates are written without BOM (#2280)
- docs: document high-assurance spec workflow (#2518)
- docs: fix script name in directory tree examples (#2555)
- Fix preset skill description precedence (#2538)
- fix(integration): clarify multi-install guidance (#2549)
- feat: add version feature reporting (#2548)
- Add Architecture Workflow extension to community catalog (#2565)
- chore: release 0.8.10, begin 0.8.11.dev0 development (#2562)
-
-## [0.8.10] - 2026-05-14
-
-### Changed
-
- docs: streamline install section and add community overview (#2561)
- Move community extensions table from README to docs site (#2560)
- Add Agent Governance extension to community catalog (#2559)
- Add Reqnroll BDD extension to community catalog (#2545)
- fix(cli): harden extension registration and discovery workflows (#2499)
- refactor: extract _assets.py and _utils.py from __init__.py (PR-2/8) (#2543)
- fix(opencode): use commands/ directory (plural) to match OpenCode docs (#2453)
- refactor: extract _console.py from __init__.py (PR-1/8) (#2474)
- Fix constitution reference in README (#2491)
- chore: release 0.8.9, begin 0.8.10.dev0 development (#2532)
-
-## [0.8.9] - 2026-05-12
-
-### Changed
-
- docs: revamp landing page with four-pillar card layout (#2531)
- feat(extensions): update governance ecosystem extensions to latest versions (#2514)
- Add changelog extension (#2177)
- Add install directory to docfx.json file references (#2522)
- feat(catalog): add BrownKit (brownkit) community extension (#2510) (#2520)
- fix(kiro-cli): replace literal $ARGUMENTS with prose fallback (#2482)
- Preset: Add game-narrative-writing  preset to community catalog (#2454)
- docs: clarify CLI upgrade discovery (#2519)
- fix: make template metadata line breaks markdownlint-safe (#2505)
- refactor(catalogs): extract integration catalog config loading (#2497)
- test(presets): silence expected UserWarnings in self-test composition… (#2373)
- chore: release 0.8.8, begin 0.8.9.dev0 development (#2516)
-
-## [0.8.8] - 2026-05-11
-
-### Changed
-
- chore(deps): bump actions/checkout from 4.3.1 to 6.0.2 (#2486)
- feat(catalog): add Spec Kit Schedule (schedule) community extension (#2473)
- fix(integration): refresh shared infra on `integration switch` (#2375)
- Add MDE preset to community catalog (#2513)
- Add MDE extension to community catalog (#2512)
- chore: update community catalog with latest extension versions (#2490)
- chore(deps): bump actions/setup-dotnet from 4.3.1 to 5.2.0 (#2489)
- chore(deps): bump actions/github-script from 7 to 9 (#2488)
- chore(deps): bump DavidAnson/markdownlint-cli2-action (#2487)
- chore(deps): bump github/codeql-action from 4.35.3 to 4.35.4 (#2485)
- feat(catalog): add API Evolve (api-evolve) community extension (#2479)
- feat: Config-driven opt-in authentication registry with multi-platform support (#2393)
- chore: release 0.8.7, begin 0.8.8.dev0 development (#2480)
-
 ## [0.8.7] - 2026-05-07

 ### Changed
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -38,7 +38,7 @@ On [GitHub Codespaces](https://github.com/features/codespaces) it's even simpler
 1. Fork and clone the repository
 1. Configure and install the dependencies: `uv sync --extra test`
 1. Make sure the CLI works on your machine: `uv run specify --help`
-1. Create a new branch: `git checkout -b <type>/<number>-<short-slug>` (see [Branch naming](#branch-naming) below)
+1. Create a new branch: `git checkout -b my-branch-name`
 1. Make your change, add tests, and make sure everything still works
 1. Test the CLI functionality with a sample project if relevant
 1. Push to your fork and submit a pull request
@@ -55,20 +55,6 @@ Here are a few things you can do that will increase the likelihood of your pull
 - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 - Test your changes with the Spec-Driven Development workflow to ensure compatibility.

-### Branch naming
-
-We recommend naming branches as `<type>/<number>-<short-slug>`, where `<number>` is the issue or PR number (whichever comes first) and `<type>` is one of:
-
-| Prefix | When to use | Example |
-|---|---|---|
-| `feat/` | New features | `feat/2342-workflow-cli-alignment` |
-| `fix/` | Bug fixes | `fix/2653-paths-only-validation` |
-| `docs/` | Documentation changes | `docs/2677-branch-naming-convention` |
-| `community/` | Community catalog additions | `community/2492-add-mde-extension` |
-| `chore/` | Maintenance, tooling, CI | `chore/2366-editorconfig` |
-
-Including the issue or PR number makes branches traceable — especially useful since the project uses squash merges and `git branch --merged` won't detect merged branches. If you start with a PR (no issue), use the PR number once it's assigned.
-
 ## Development workflow

 When working on spec-kit:
--- a/0
+++ b/0
--- a/README.md
+++ b/README.md
@@ -22,7 +22,10 @@
 - [🤔 What is Spec-Driven Development?](#-what-is-spec-driven-development)
 - [⚡ Get Started](#-get-started)
 - [📽️ Video Overview](#️-video-overview)
- [🌍 Community](#-community)
+- [🧩 Community Extensions](#-community-extensions)
+- [🎨 Community Presets](#-community-presets)
+- [🚶 Community Walkthroughs](#-community-walkthroughs)
+- [🛠️ Community Friends](#️-community-friends)
 - [🤖 Supported AI Coding Agent Integrations](#-supported-ai-coding-agent-integrations)
 - [🔧 Specify CLI Reference](#-specify-cli-reference)
 - [🧩 Making Spec Kit Your Own: Extensions & Presets](#-making-spec-kit-your-own-extensions--presets)
@@ -32,6 +35,7 @@
 - [🔧 Prerequisites](#-prerequisites)
 - [📖 Learn More](#-learn-more)
 - [📋 Detailed Process](#-detailed-process)
+- [🔍 Troubleshooting](#-troubleshooting)
 - [💬 Support](#-support)
 - [🙏 Acknowledgements](#-acknowledgements)
 - [📄 License](#-license)
@@ -44,22 +48,83 @@ 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 tag from [Releases](https://github.com/github/spec-kit/releases):
+Choose your preferred installation method:
+
+> **Important:** The only official, maintained packages for Spec Kit are published from this GitHub repository. Any packages with the same name on PyPI are **not** affiliated with this project and are not maintained by the Spec Kit maintainers. Always install directly from GitHub as shown below.
+
+#### Option 1: Persistent Installation (Recommended)
+
+Install once and use everywhere. Pin a specific release tag for stability (check [Releases](https://github.com/github/spec-kit/releases) for the latest):
+
+> [!NOTE]
+> The `uv tool install` commands below require **[uv](https://docs.astral.sh/uv/)** — a fast Python package manager. If you see `command not found: uv`, [install uv first](./docs/install/uv.md). The `pipx` alternative does not require uv.

 ```bash
+# Install a specific stable release (recommended — replace vX.Y.Z with the latest tag)
 uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@vX.Y.Z
+
+# Or install latest from main (may include unreleased changes)
+uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
+
+# Alternative: using pipx (also works)
+pipx install git+https://github.com/github/spec-kit.git@vX.Y.Z
+pipx install git+https://github.com/github/spec-kit.git
 ```

-See the [Installation Guide](./docs/installation.md) for alternative methods, verification, upgrade, and troubleshooting.
-
-### 2. Initialize a project
+Then verify the correct version is installed:

 ```bash
-specify init my-project --integration copilot
-cd my-project
+specify version
 ```

-### 3. Establish project principles
+And use the tool directly:
+
+```bash
+# Create new project
+specify init <PROJECT_NAME>
+
+# Or initialize in existing project
+specify init . --integration copilot
+# or
+specify init --here --integration copilot
+
+# Check installed tools
+specify check
+```
+
+To upgrade Specify, see the [Upgrade Guide](./docs/upgrade.md) for detailed instructions. Quick upgrade:
+
+```bash
+uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git@vX.Y.Z
+# pipx users: pipx install --force git+https://github.com/github/spec-kit.git@vX.Y.Z
+```
+
+#### Option 2: One-time Usage
+
+Run directly without installing:
+
+```bash
+# Create new project (pinned to a stable release — replace vX.Y.Z with the latest tag)
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <PROJECT_NAME>
+
+# Or initialize in existing project
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init . --integration copilot
+# or
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init --here --integration copilot
+```
+
+**Benefits of persistent installation:**
+
+- Tool stays installed and available in PATH
+- No need to create shell aliases
+- Better tool management with `uv tool list`, `uv tool upgrade`, `uv tool uninstall`
+- Cleaner shell configuration
+
+#### Option 3: Enterprise / Air-Gapped Installation
+
+If your environment blocks access to PyPI or GitHub, see the [Enterprise / Air-Gapped Installation](./docs/installation.md#enterprise--air-gapped-installation) guide for step-by-step instructions on using `pip download` to create portable, OS-specific wheel bundles on a connected machine.
+
+### 2. Establish project principles

 Launch your coding agent in the project directory. Most agents expose spec-kit as `/speckit.*` slash commands; Codex CLI in skills mode uses `$speckit-*` instead.

@@ -69,7 +134,7 @@ Use the **`/speckit.constitution`** command to create your project's governing p
 /speckit.constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements
 ```

-### 4. Create the spec
+### 3. Create the spec

 Use the **`/speckit.specify`** command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.

@@ -77,7 +142,7 @@ Use the **`/speckit.specify`** command to describe what you want to build. Focus
 /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.
 ```

-### 5. Create a technical implementation plan
+### 4. Create a technical implementation plan

 Use the **`/speckit.plan`** command to provide your tech stack and architecture choices.

@@ -85,7 +150,7 @@ Use the **`/speckit.plan`** command to provide your tech stack and architecture
 /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.
 ```

-### 6. Break down into tasks
+### 5. Break down into tasks

 Use **`/speckit.tasks`** to create an actionable task list from your implementation plan.

@@ -93,7 +158,7 @@ Use **`/speckit.tasks`** to create an actionable task list from your implementat
 /speckit.tasks
 ```

-### 7. Execute implementation
+### 6. Execute implementation

 Use **`/speckit.implement`** to execute all tasks and build your feature according to the plan.

@@ -109,19 +174,140 @@ Want to see Spec Kit in action? Watch our [video overview](https://www.youtube.c

 [![Spec Kit video header](/media/spec-kit-video-header.jpg)](https://www.youtube.com/watch?v=a9eR1xsfvHg&pp=0gcJCckJAYcqIYzv)

-## 🌍 Community
-
-Explore community-contributed resources on the [Spec Kit docs site](https://github.github.io/spec-kit/):
-
- [Extensions](https://github.github.io/spec-kit/community/extensions.html) — commands, hooks, and capabilities
- [Presets](https://github.github.io/spec-kit/community/presets.html) — template and terminology overrides
- [Walkthroughs](https://github.github.io/spec-kit/community/walkthroughs.html) — end-to-end SDD scenarios
- [Friends](https://github.github.io/spec-kit/community/friends.html) — projects that extend or build on Spec Kit
+## 🧩 Community Extensions

 > [!NOTE]
-> Community contributions are independently created and maintained by their respective authors. Review source code before installation and use at your own discretion.
+> Community extensions are independently created and maintained by their respective authors. Maintainers only verify that catalog entries are complete and correctly formatted — they do **not review, audit, endorse, or support the extension code itself**. The Community Extensions website is also a third-party resource. Review extension source code before installation and use at your own discretion.

-Want to contribute? See the [Extension Publishing Guide](extensions/EXTENSION-PUBLISHING-GUIDE.md) or the [Presets Publishing Guide](presets/PUBLISHING.md).
+🔍 **Browse and search community extensions on the [Community Extensions website](https://speckit-community.github.io/extensions/).**
+
+The following community-contributed extensions are available in [`catalog.community.json`](extensions/catalog.community.json):
+
+**Categories:**
+
+- `docs` — reads, validates, or generates spec artifacts
+- `code` — reviews, validates, or modifies source code
+- `process` — orchestrates workflow across phases
+- `integration` — syncs with external platforms
+- `visibility` — reports on project health or progress
+
+**Effect:**
+
+- `Read-only` — produces reports without modifying files
+- `Read+Write` — modifies files, creates artifacts, or updates specs
+
+| Extension | Purpose | Category | Effect | URL |
+|-----------|---------|----------|--------|-----|
+| Agent Assign | Assign specialized Claude Code agents to spec-kit tasks for targeted execution | `process` | Read+Write | [spec-kit-agent-assign](https://github.com/xymelon/spec-kit-agent-assign) |
+| AI-Driven Engineering (AIDE) | A structured 7-step workflow for building new projects from scratch with AI assistants — from vision through implementation | `process` | Read+Write | [aide](https://github.com/mnriem/spec-kit-extensions/tree/main/aide) |
+| Architect Impact Previewer | Predicts architectural impact, complexity, and risks of proposed changes before implementation. | `visibility` | Read-only | [spec-kit-architect-preview](https://github.com/UmmeHabiba1312/spec-kit-architect-preview) |
+| Architecture Guard | Continuous architecture governance for AI-assisted development. Reviews specs, plans, and code for architecture drift, producing structured refactor tasks and evolution proposals. | `process` | Read+Write | [spec-kit-architecture-guard](https://github.com/DyanGalih/spec-kit-architecture-guard) |
+| Archive Extension | Archive merged features into main project memory. | `docs` | Read+Write | [spec-kit-archive](https://github.com/stn1slv/spec-kit-archive) |
+| Azure DevOps Integration | Sync user stories and tasks to Azure DevOps work items using OAuth authentication | `integration` | Read+Write | [spec-kit-azure-devops](https://github.com/pragya247/spec-kit-azure-devops) |
+| Blueprint | Stay code-literate in AI-driven development: review a complete code blueprint for every task from spec artifacts before /speckit.implement runs | `docs` | Read+Write | [spec-kit-blueprint](https://github.com/chordpli/spec-kit-blueprint) |
+| Branch Convention | Configurable branch and folder naming conventions for /specify with presets and custom patterns | `process` | Read+Write | [spec-kit-branch-convention](https://github.com/Quratulain-bilal/spec-kit-branch-convention) |
+| Brownfield Bootstrap | Bootstrap spec-kit for existing codebases — auto-discover architecture and adopt SDD incrementally | `process` | Read+Write | [spec-kit-brownfield](https://github.com/Quratulain-bilal/spec-kit-brownfield) |
+| Bugfix Workflow | Structured bugfix workflow — capture bugs, trace to spec artifacts, and patch specs surgically | `process` | Read+Write | [spec-kit-bugfix](https://github.com/Quratulain-bilal/spec-kit-bugfix) |
+| Canon | Adds canon-driven (baseline-driven) workflows: spec-first, code-first, spec-drift. Requires Canon Core preset installation. | `process` | Read+Write | [spec-kit-canon](https://github.com/maximiliamus/spec-kit-canon/tree/master/extension) |
+| Catalog CI | Automated validation for spec-kit community catalog entries — structure, URLs, diffs, and linting | `process` | Read-only | [spec-kit-catalog-ci](https://github.com/Quratulain-bilal/spec-kit-catalog-ci) |
+| CI Guard | Spec compliance gates for CI/CD — verify specs exist, check drift, and block merges on gaps | `process` | Read-only | [spec-kit-ci-guard](https://github.com/Quratulain-bilal/spec-kit-ci-guard) |
+| Checkpoint Extension | Commit the changes made during the middle of the implementation, so you don't end up with just one very large commit at the end | `code` | Read+Write | [spec-kit-checkpoint](https://github.com/aaronrsun/spec-kit-checkpoint) |
+| Cleanup Extension | Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues | `code` | Read+Write | [spec-kit-cleanup](https://github.com/dsrednicki/spec-kit-cleanup) |
+| Conduct Extension | Orchestrates spec-kit phases via sub-agent delegation to reduce context pollution. | `process` | Read+Write | [spec-kit-conduct-ext](https://github.com/twbrandon7/spec-kit-conduct-ext) |
+| 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) |
+| DocGuard — CDD Enforcement | Canonical-Driven Development enforcement. Validates, scores, and traces project documentation with automated checks, AI-driven workflows, and spec-kit hooks. Zero NPM runtime dependencies. | `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) |
+| 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) |
+| 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) |
+| Iterate | Iterate on spec documents with a two-phase define-and-apply workflow — refine specs mid-implementation and go straight back to building | `docs` | Read+Write | [spec-kit-iterate](https://github.com/imviancagrace/spec-kit-iterate) |
+| Jira Integration | Create Jira Epics, Stories, and Issues from spec-kit specifications and task breakdowns with configurable hierarchy and custom field support | `integration` | Read+Write | [spec-kit-jira](https://github.com/mbachorik/spec-kit-jira) |
+| 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) |
+| 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) |
+| MAQA CI/CD Gate | Auto-detects GitHub Actions, CircleCI, GitLab CI, and Bitbucket Pipelines. Blocks QA handoff until pipeline is green. | `process` | Read+Write | [spec-kit-maqa-ci](https://github.com/GenieRobot/spec-kit-maqa-ci) |
+| MAQA GitHub Projects Integration | GitHub Projects v2 integration for MAQA — syncs draft issues and Status columns as features progress | `integration` | Read+Write | [spec-kit-maqa-github-projects](https://github.com/GenieRobot/spec-kit-maqa-github-projects) |
+| MAQA Jira Integration | Jira integration for MAQA — syncs Stories and Subtasks as features progress through the board | `integration` | Read+Write | [spec-kit-maqa-jira](https://github.com/GenieRobot/spec-kit-maqa-jira) |
+| MAQA Linear Integration | Linear integration for MAQA — syncs issues and sub-issues across workflow states as features progress | `integration` | Read+Write | [spec-kit-maqa-linear](https://github.com/GenieRobot/spec-kit-maqa-linear) |
+| MAQA Trello Integration | Trello board integration for MAQA — populates board from specs, moves cards, real-time checklist ticking | `integration` | Read+Write | [spec-kit-maqa-trello](https://github.com/GenieRobot/spec-kit-maqa-trello) |
+| MarkItDown Document Converter | Convert documents (PDF, Word, PowerPoint, Excel, and more) to Markdown for use as spec reference material | `docs` | Read+Write | [spec-kit-markitdown](https://github.com/BenBtg/spec-kit-markitdown) |
+| Memory Loader | Loads .specify/memory/ files before lifecycle commands so LLM agents have project governance context | `docs` | Read-only | [spec-kit-memory-loader](https://github.com/KevinBrown5280/spec-kit-memory-loader) |
+| Memory MD | Spec Kit extension for repository-native Markdown memory that captures durable decisions, bugs, and project context | `docs` | Read+Write | [spec-kit-memory-hub](https://github.com/DyanGalih/spec-kit-memory-hub) |
+| MemoryLint | Agent memory governance tool: Automatically audits and fixes boundary conflicts between AGENTS.md and the constitution. | `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) |
+| .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) |
+| 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) |
+| 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) |
+| Product Forge | Full product lifecycle from research to release — portfolio, lite mode, monorepo, optional V-Model | `process` | Read+Write | [speckit-product-forge](https://github.com/VaiYav/speckit-product-forge) |
+| 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) |
+| 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) |
+| Red Team | Adversarial review of specs before /speckit.plan — parallel lens agents surface risks that clarify/analyze structurally can't (prompt injection, integrity gaps, cross-spec drift, silent failures). Produces a structured findings report; no auto-edits to specs. | `docs` | Read+Write | [spec-kit-red-team](https://github.com/ashbrener/spec-kit-red-team) |
+| Repository Index | Generate index for existing repo for overview, architecture and module level. | `docs` | Read-only | [spec-kit-repoindex](https://github.com/liuyiyu/spec-kit-repoindex) |
+| Retro Extension | Sprint retrospective analysis with metrics, spec accuracy assessment, and improvement suggestions | `process` | Read+Write | [spec-kit-retro](https://github.com/arunt14/spec-kit-retro) |
+| Retrospective Extension | Post-implementation retrospective with spec adherence scoring, drift analysis, and human-gated spec updates | `docs` | Read+Write | [spec-kit-retrospective](https://github.com/emi-dm/spec-kit-retrospective) |
+| Review Extension | Post-implementation comprehensive code review with specialized agents for code quality, comments, tests, error handling, type design, and simplification | `code` | Read-only | [spec-kit-review](https://github.com/ismaelJimenez/spec-kit-review) |
+| Ripple | Detect side effects that tests can't catch after implementation — delta-anchored analysis across 9 domain-agnostic categories | `code` | Read+Write | [spec-kit-ripple](https://github.com/chordpli/spec-kit-ripple) |
+| SDD Utilities | Resume interrupted workflows, validate project health, and verify spec-to-task traceability | `process` | Read+Write | [speckit-utils](https://github.com/mvanhorn/speckit-utils) |
+| Security Review | Full-project secure-by-design security audits plus staged, branch/PR, plan, task, follow-up, and apply reviews | `code` | Read+Write | [spec-kit-security-review](https://github.com/DyanGalih/spec-kit-security-review) |
+| SFSpeckit | Enterprise Salesforce SDLC with 18 commands for the full SDD lifecycle. | `process` | Read+Write | [spec-kit-sf](https://github.com/ysumanth06/spec-kit-sf) |
+| Ship Release Extension | Automates release pipeline: pre-flight checks, branch sync, changelog generation, CI verification, and PR creation | `process` | Read+Write | [spec-kit-ship](https://github.com/arunt14/spec-kit-ship) |
+| Spec Reference Loader | Reads the ## References section from the feature spec and loads only the listed docs into context | `docs` | Read-only | [spec-kit-spec-reference-loader](https://github.com/KevinBrown5280/spec-kit-spec-reference-loader) |
+| 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 Orchestrator | Cross-feature orchestration — track state, select tasks, and detect conflicts across parallel specs | `process` | Read-only | [spec-kit-orchestrator](https://github.com/Quratulain-bilal/spec-kit-orchestrator) |
+| Spec Refine | Update specs in-place, propagate changes to plan and tasks, and diff impact across artifacts | `process` | Read+Write | [spec-kit-refine](https://github.com/Quratulain-bilal/spec-kit-refine) |
+| Spec Scope | Effort estimation and scope tracking — estimate work, detect creep, and budget time per phase | `process` | Read-only | [spec-kit-scope-](https://github.com/Quratulain-bilal/spec-kit-scope-) |
+| 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 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) |
+| Spec2Cloud | Spec-driven workflow tuned for shipping to Azure | `process` | Read+Write | [spec2cloud](https://github.com/Azure-Samples/Spec2Cloud) |
+| 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) |
+| Squad Bridge | Bootstrap and synchronize a Squad agent team from your Speckit spec and tasks | `process` | Read+Write | [spec-kit-squad](https://github.com/jwill824/spec-kit-squad) |
+| Staff Review Extension | Staff-engineer-level code review that validates implementation against spec, checks security, performance, and test coverage | `code` | Read-only | [spec-kit-staff-review](https://github.com/arunt14/spec-kit-staff-review) |
+| Status Report | Project status, feature progress, and next-action recommendations for spec-driven workflows | `visibility` | Read-only | [Open-Agent-Tools/spec-kit-status](https://github.com/Open-Agent-Tools/spec-kit-status) |
+| Superpowers Bridge | Orchestrates obra/superpowers skills within the spec-kit SDD workflow across the full lifecycle (clarification, TDD, review, verification, critique, debugging, branch completion) | `process` | Read+Write | [superpowers-bridge](https://github.com/RbBtSn0w/spec-kit-extensions/tree/main/superpowers-bridge) |
+| Superpowers Bridge (WangX0111) | Bridges spec-kit with obra/superpowers (brainstorming, TDD, subagent, code-review) into a unified, resumable workflow with graceful degradation and session progress tracking | `process` | Read+Write | [superspec](https://github.com/WangX0111/superspec) |
+| TinySpec | Lightweight single-file workflow for small tasks — skip the heavy multi-step SDD process | `process` | Read+Write | [spec-kit-tinyspec](https://github.com/Quratulain-bilal/spec-kit-tinyspec) |
+| Token Consumption Analyzer | Captures, analyzes, and compares token consumption across SDD workflows | `visibility` | Read-only | [spec-kit-token-analyzer](https://github.com/coderandhiker/spec-kit-token-analyzer) |
+| 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 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) |
+| Wireframe Visual Feedback Loop | SVG wireframe generation, review, and sign-off for spec-driven development. Approved wireframes become spec constraints honored by /speckit.plan, /speckit.tasks, and /speckit.implement | `visibility` | Read+Write | [spec-kit-extension-wireframe](https://github.com/TortoiseWolfe/spec-kit-extension-wireframe) |
+| Work IQ | Integrate Microsoft 365 organizational knowledge into spec-driven development workflows | `integration` | Read-only | [spec-kit-workiq](https://github.com/sakitA/spec-kit-workiq) |
+| Worktree Isolation | Spawn isolated git worktrees for parallel feature development without checkout switching | `process` | Read+Write | [spec-kit-worktree](https://github.com/Quratulain-bilal/spec-kit-worktree) |
+| Worktrees | Default-on worktree isolation for parallel agents — sibling or nested layout | `process` | Read+Write | [spec-kit-worktree-parallel](https://github.com/dango85/spec-kit-worktree-parallel) |
+
+To submit your own extension, see the [Extension Publishing Guide](extensions/EXTENSION-PUBLISHING-GUIDE.md).
+
+## 🎨 Community Presets
+
+Community-contributed presets customize how Spec Kit behaves — overriding templates, commands, and terminology without changing any tooling. See the full list on the [Community Presets](https://github.github.io/spec-kit/community/presets.html) page.
+
+> [!NOTE]
+> Community presets are third-party contributions and are not maintained by the Spec Kit team. Review them carefully before use, and see the docs page above for the full disclaimer.
+
+To submit your own preset, see the [Presets Publishing Guide](presets/PUBLISHING.md).
+
+## 🚶 Community Walkthroughs
+
+See Spec-Driven Development in action across different scenarios with community-contributed walkthroughs; find the full list on the [Community Walkthroughs](https://github.github.io/spec-kit/community/walkthroughs.html) page.
+
+## 🛠️ Community Friends
+
+Community projects that extend, visualize, or build on Spec Kit. See the full list on the [Community Friends](https://github.github.io/spec-kit/community/friends.html) page.

 ## 🤖 Supported AI Coding Agent Integrations

@@ -191,7 +377,7 @@ specify extension add <extension-name>

 For example, extensions could add Jira integration, post-implementation code review, V-Model test traceability, or project health diagnostics.

-See the [Extensions reference](https://github.github.io/spec-kit/reference/extensions.html) for the full command guide. Browse the [community extensions](https://github.github.io/spec-kit/community/extensions.html) for what's available.
+See the [Extensions reference](https://github.github.io/spec-kit/reference/extensions.html) for the full command guide. Browse the [community extensions](#-community-extensions) above for what's available.

 ### Presets — Customize Existing Workflows

@@ -266,7 +452,7 @@ Our research and experimentation focus on:

 - **Linux/macOS/Windows**
 - [Supported](#-supported-ai-coding-agent-integrations) AI coding agent.
- [uv](https://docs.astral.sh/uv/) for package management (recommended) or [pipx](https://pipx.pypa.io/) for persistent installation
+- [uv](https://docs.astral.sh/uv/) for package management (recommended) or [pipx](https://pypa.github.io/pipx/) for persistent installation
 - [Python 3.11+](https://www.python.org/downloads/)
 - [Git](https://git-scm.com/downloads)

@@ -385,24 +571,22 @@ The produced specification should contain a set of user stories and functional r
 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
+└── .specify
+    ├── memory
+    │  └── constitution.md
+    ├── scripts
+    │  ├── check-prerequisites.sh
+    │  ├── common.sh
+    │  ├── create-new-feature.sh
+    │  ├── setup-plan.sh
+    │  └── update-claude-md.sh
+    ├── specs
+    │  └── 001-create-taskify
+    │      └── spec.md
+    └── templates
+        ├── plan-template.md
+        ├── spec-template.md
+        └── tasks-template.md
 ```

 ### **STEP 3:** Functional specification clarification (required before planning)
@@ -449,31 +633,29 @@ The output of this step will include a number of implementation detail documents
 ```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
+├── memory
+│  └── constitution.md
+├── scripts
+│  ├── check-prerequisites.sh
+│  ├── common.sh
+│  ├── create-new-feature.sh
+│  ├── setup-plan.sh
+│  └── update-claude-md.sh
+├── specs
+│  └── 001-create-taskify
+│      ├── contracts
+│      │  ├── api-spec.json
+│      │  └── signalr-spec.md
+│      ├── data-model.md
+│      ├── plan.md
+│      ├── quickstart.md
+│      ├── research.md
+│      └── spec.md
+└── templates
+    ├── CLAUDE-template.md
+    ├── plan-template.md
+    ├── spec-template.md
+    └── tasks-template.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).
@@ -520,7 +702,7 @@ This helps refine the implementation plan and helps you avoid potential blind sp
 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.
+> 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](base/memory/constitution.md) as the foundational piece that it must adhere to when establishing the plan.

 ### **STEP 6:** Generate task breakdown with /speckit.tasks

@@ -566,6 +748,25 @@ Once the implementation is complete, test the application and resolve any runtim

 ---

+## 🔍 Troubleshooting
+
+### Git Credential Manager on Linux
+
+If you're having issues with Git authentication on Linux, you can install Git Credential Manager:
+
+```bash
+#!/usr/bin/env bash
+set -e
+echo "Downloading Git Credential Manager v2.6.1..."
+wget https://github.com/git-ecosystem/git-credential-manager/releases/download/v2.6.1/gcm-linux_amd64.2.6.1.deb
+echo "Installing Git Credential Manager..."
+sudo dpkg -i gcm-linux_amd64.2.6.1.deb
+echo "Configuring Git to use GCM..."
+git config --global credential.helper manager
+echo "Cleaning up..."
+rm gcm-linux_amd64.2.6.1.deb
+```
+
 ## 💬 Support

 For support, please open a [GitHub issue](https://github.com/github/spec-kit/issues/new). We welcome bug reports, feature requests, and questions about using Spec-Driven Development.
--- a/docs/community/extensions.md
+++ b/docs/community/extensions.md
@@ -1,131 +0,0 @@
-# Community Extensions
-
-> [!NOTE]
-> Community extensions are independently created and maintained by their respective authors. Maintainers only verify that catalog entries are complete and correctly formatted — they do **not review, audit, endorse, or support the extension code itself**. The Community Extensions website is also a third-party resource. Review extension source code before installation and use at your own discretion.
-
-🔍 **Browse and search community extensions on the [Community Extensions website](https://speckit-community.github.io/extensions/).**
-
-The following community-contributed extensions are available in [`catalog.community.json`](https://github.com/github/spec-kit/blob/main/extensions/catalog.community.json):
-
-**Categories:**
-
- `docs` — reads, validates, or generates spec artifacts
- `code` — reviews, validates, or modifies source code
- `process` — orchestrates workflow across phases
- `integration` — syncs with external platforms
- `visibility` — reports on project health or progress
-
-**Effect:**
-
- `Read-only` — produces reports without modifying files
- `Read+Write` — modifies files, creates artifacts, or updates specs
-
-| Extension | Purpose | Category | Effect | URL |
-|-----------|---------|----------|--------|-----|
-| Agent Assign | Assign specialized Claude Code agents to spec-kit tasks for targeted execution | `process` | Read+Write | [spec-kit-agent-assign](https://github.com/xymelon/spec-kit-agent-assign) |
-| Agent Governance | Generate agent-platform repository governance files from Spec Kit metadata | `process` | Read+Write | [spec-kit-agent-governance](https://github.com/bigsmartben/spec-kit-agent-governance) |
-| AI-Driven Engineering (AIDE) | A structured 7-step workflow for building new projects from scratch with AI assistants — from vision through implementation | `process` | Read+Write | [aide](https://github.com/mnriem/spec-kit-extensions/tree/main/aide) |
-| API Evolve | Managed API contract evolution — breaking-change detection, semver enforcement, deprecation orchestration, and lifecycle gates across REST, GraphQL, and gRPC | `process` | Read+Write | [spec-kit-api-evolve](https://github.com/Quratulain-bilal/spec-kit-api-evolve) |
-| Architect Impact Previewer | Predicts architectural impact, complexity, and risks of proposed changes before implementation. | `visibility` | Read-only | [spec-kit-architect-preview](https://github.com/UmmeHabiba1312/spec-kit-architect-preview) |
-| Architecture Guard | Framework-agnostic architecture review extension for validating implementation against governance and architecture constitutions, detecting architectural drift, and generating non-blocking refactor tasks | `process` | Read+Write | [spec-kit-architecture-guard](https://github.com/DyanGalih/spec-kit-architecture-guard) |
-| Architecture Workflow | Generate or reverse project-level 4+1 architecture view artifacts and synthesis | `docs` | Read+Write | [spec-kit-arch](https://github.com/bigsmartben/spec-kit-arch) |
-| Archive Extension | Archive merged features into main project memory. | `docs` | Read+Write | [spec-kit-archive](https://github.com/stn1slv/spec-kit-archive) |
-| Azure DevOps Integration | Sync user stories and tasks to Azure DevOps work items using OAuth authentication | `integration` | Read+Write | [spec-kit-azure-devops](https://github.com/pragya247/spec-kit-azure-devops) |
-| Blueprint | Stay code-literate in AI-driven development: review a complete code blueprint for every task from spec artifacts before /speckit.implement runs | `docs` | Read+Write | [spec-kit-blueprint](https://github.com/chordpli/spec-kit-blueprint) |
-| Branch Convention | Configurable branch and folder naming conventions for /specify with presets and custom patterns | `process` | Read+Write | [spec-kit-branch-convention](https://github.com/Quratulain-bilal/spec-kit-branch-convention) |
-| Brownfield Bootstrap | Bootstrap spec-kit for existing codebases — auto-discover architecture and adopt SDD incrementally | `process` | Read+Write | [spec-kit-brownfield](https://github.com/Quratulain-bilal/spec-kit-brownfield) |
-| BrownKit | Evidence-driven capability discovery, security and QA risk assessment for existing codebases | `process` | Read+Write | [BrownKit](https://github.com/MaksimShevtsov/BrownKit) |
-| Bugfix Workflow | Structured bugfix workflow — capture bugs, trace to spec artifacts, and patch specs surgically | `process` | Read+Write | [spec-kit-bugfix](https://github.com/Quratulain-bilal/spec-kit-bugfix) |
-| Canon | Adds canon-driven (baseline-driven) workflows: spec-first, code-first, spec-drift. Requires Canon Core preset installation. | `process` | Read+Write | [spec-kit-canon](https://github.com/maximiliamus/spec-kit-canon/tree/master/extension) |
-| Catalog CI | Automated validation for spec-kit community catalog entries — structure, URLs, diffs, and linting | `process` | Read-only | [spec-kit-catalog-ci](https://github.com/Quratulain-bilal/spec-kit-catalog-ci) |
-| CI Guard | Spec compliance gates for CI/CD — verify specs exist, check drift, and block merges on gaps | `process` | Read-only | [spec-kit-ci-guard](https://github.com/Quratulain-bilal/spec-kit-ci-guard) |
-| Checkpoint Extension | Commit the changes made during the middle of the implementation, so you don't end up with just one very large commit at the end | `code` | Read+Write | [spec-kit-checkpoint](https://github.com/aaronrsun/spec-kit-checkpoint) |
-| Cleanup Extension | Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues | `code` | Read+Write | [spec-kit-cleanup](https://github.com/dsrednicki/spec-kit-cleanup) |
-| Conduct Extension | Orchestrates spec-kit phases via sub-agent delegation to reduce context pollution. | `process` | Read+Write | [spec-kit-conduct-ext](https://github.com/twbrandon7/spec-kit-conduct-ext) |
-| 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) |
-| DocGuard — CDD Enforcement | Canonical-Driven Development enforcement. Validates, scores, and traces project documentation with automated checks, AI-driven workflows, and spec-kit hooks. Zero NPM runtime dependencies. | `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) |
-| 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) |
-| Interactive HTML Preview | Generate self-contained interactive HTML prototypes from Spec Kit artifacts | `docs` | Read+Write | [spec-kit-preview](https://github.com/bigsmartben/spec-kit-preview) |
-| 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) |
-| Iterate | Iterate on spec documents with a two-phase define-and-apply workflow — refine specs mid-implementation and go straight back to building | `docs` | Read+Write | [spec-kit-iterate](https://github.com/imviancagrace/spec-kit-iterate) |
-| Jira Integration | Create Jira Epics, Stories, and Issues from spec-kit specifications and task breakdowns with configurable hierarchy and custom field support | `integration` | Read+Write | [spec-kit-jira](https://github.com/mbachorik/spec-kit-jira) |
-| 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) |
-| 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) |
-| MAQA CI/CD Gate | Auto-detects GitHub Actions, CircleCI, GitLab CI, and Bitbucket Pipelines. Blocks QA handoff until pipeline is green. | `process` | Read+Write | [spec-kit-maqa-ci](https://github.com/GenieRobot/spec-kit-maqa-ci) |
-| MAQA GitHub Projects Integration | GitHub Projects v2 integration for MAQA — syncs draft issues and Status columns as features progress | `integration` | Read+Write | [spec-kit-maqa-github-projects](https://github.com/GenieRobot/spec-kit-maqa-github-projects) |
-| MAQA Jira Integration | Jira integration for MAQA — syncs Stories and Subtasks as features progress through the board | `integration` | Read+Write | [spec-kit-maqa-jira](https://github.com/GenieRobot/spec-kit-maqa-jira) |
-| MAQA Linear Integration | Linear integration for MAQA — syncs issues and sub-issues across workflow states as features progress | `integration` | Read+Write | [spec-kit-maqa-linear](https://github.com/GenieRobot/spec-kit-maqa-linear) |
-| MAQA Trello Integration | Trello board integration for MAQA — populates board from specs, moves cards, real-time checklist ticking | `integration` | Read+Write | [spec-kit-maqa-trello](https://github.com/GenieRobot/spec-kit-maqa-trello) |
-| MarkItDown Document Converter | Convert documents (PDF, Word, PowerPoint, Excel, and more) to Markdown for use as spec reference material | `docs` | Read+Write | [spec-kit-markitdown](https://github.com/BenBtg/spec-kit-markitdown) |
-| MDE | Minimal model-driven engineering workflow with setup, next, and status commands | `process` | Read+Write | [spec-kit-mde](https://github.com/AI-MDE/spec-kit-mde) |
-| Memory Loader | Loads .specify/memory/ files before lifecycle commands so LLM agents have project governance context | `docs` | Read-only | [spec-kit-memory-loader](https://github.com/KevinBrown5280/spec-kit-memory-loader) |
-| Memory MD | Spec Kit extension for repository-native Markdown memory that captures durable decisions, bugs, and project context | `docs` | Read+Write | [spec-kit-memory-hub](https://github.com/DyanGalih/spec-kit-memory-hub) |
-| MemoryLint | Agent memory governance tool: Automatically audits and fixes boundary conflicts between AGENTS.md and the constitution. | `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) |
-| .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) |
-| 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) |
-| 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) |
-| Product Forge | Full product lifecycle from research to release — portfolio, lite mode, monorepo, optional V-Model | `process` | Read+Write | [speckit-product-forge](https://github.com/VaiYav/speckit-product-forge) |
-| Product Spec Extension | Generates PRFAQ, Lean PRD, stakeholder summaries, and technical designs from engineering specs | `docs` | Read+Write | [spec-kit-product](https://github.com/d0whc3r/spec-kit-product) |
-| 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) |
-| 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) |
-| Red Team | Adversarial review of specs before /speckit.plan — parallel lens agents surface risks that clarify/analyze structurally can't (prompt injection, integrity gaps, cross-spec drift, silent failures). Produces a structured findings report; no auto-edits to specs. | `docs` | Read+Write | [spec-kit-red-team](https://github.com/ashbrener/spec-kit-red-team) |
-| Repository Index | Generate index for existing repo for overview, architecture and module level. | `docs` | Read-only | [spec-kit-repoindex](https://github.com/liuyiyu/spec-kit-repoindex) |
-| Reqnroll BDD | Adds Reqnroll BDD planning, Gherkin generation, traceability, safe task injection, handoff, and verification to Spec Kit | `process` | Read+Write | [spec-kit-reqnroll-bdd](https://github.com/LoogacyStudio/spec-kit-reqnroll-bdd) |
-| Retro Extension | Sprint retrospective analysis with metrics, spec accuracy assessment, and improvement suggestions | `process` | Read+Write | [spec-kit-retro](https://github.com/arunt14/spec-kit-retro) |
-| Retrospective Extension | Post-implementation retrospective with spec adherence scoring, drift analysis, and human-gated spec updates | `docs` | Read+Write | [spec-kit-retrospective](https://github.com/emi-dm/spec-kit-retrospective) |
-| Review Extension | Post-implementation comprehensive code review with specialized agents for code quality, comments, tests, error handling, type design, and simplification | `code` | Read-only | [spec-kit-review](https://github.com/ismaelJimenez/spec-kit-review) |
-| Ripple | Detect side effects that tests can't catch after implementation — delta-anchored analysis across 9 domain-agnostic categories | `code` | Read+Write | [spec-kit-ripple](https://github.com/chordpli/spec-kit-ripple) |
-| SDD Utilities | Resume interrupted workflows, validate project health, and verify spec-to-task traceability | `process` | Read+Write | [speckit-utils](https://github.com/mvanhorn/speckit-utils) |
-| Security Review | Full-project secure-by-design security audits plus staged, branch/PR, plan, task, follow-up, and apply reviews | `code` | Read+Write | [spec-kit-security-review](https://github.com/DyanGalih/spec-kit-security-review) |
-| SFSpeckit | Enterprise Salesforce SDLC with 18 commands for the full SDD lifecycle. | `process` | Read+Write | [spec-kit-sf](https://github.com/ysumanth06/spec-kit-sf) |
-| Ship Release Extension | Automates release pipeline: pre-flight checks, branch sync, changelog generation, CI verification, and PR creation | `process` | Read+Write | [spec-kit-ship](https://github.com/arunt14/spec-kit-ship) |
-| Spec Changelog | Auto-generate changelogs and release notes from spec git history and requirement diffs | `docs` | Read-only | [spec-kit-changelog](https://github.com/Quratulain-bilal/spec-kit-changelog) |
-| 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 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 Orchestrator | Cross-feature orchestration — track state, select tasks, and detect conflicts across parallel specs | `process` | Read-only | [spec-kit-orchestrator](https://github.com/Quratulain-bilal/spec-kit-orchestrator) |
-| Spec Reference Loader | Reads the ## References section from the feature spec and loads only the listed docs into context | `docs` | Read-only | [spec-kit-spec-reference-loader](https://github.com/KevinBrown5280/spec-kit-spec-reference-loader) |
-| Spec Refine | Update specs in-place, propagate changes to plan and tasks, and diff impact across artifacts | `process` | Read+Write | [spec-kit-refine](https://github.com/Quratulain-bilal/spec-kit-refine) |
-| Spec Scope | Effort estimation and scope tracking — estimate work, detect creep, and budget time per phase | `process` | Read-only | [spec-kit-scope-](https://github.com/Quratulain-bilal/spec-kit-scope-) |
-| 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 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) |
-| Spec2Cloud | Spec-driven workflow tuned for shipping to Azure | `process` | Read+Write | [spec2cloud](https://github.com/Azure-Samples/Spec2Cloud) |
-| 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) |
-| Squad Bridge | Bootstrap and synchronize a Squad agent team from your Speckit spec and tasks. | `process` | Read+Write | [spec-kit-squad](https://github.com/jwill824/spec-kit-squad) |
-| Staff Review Extension | Staff-engineer-level code review that validates implementation against spec, checks security, performance, and test coverage | `code` | Read-only | [spec-kit-staff-review](https://github.com/arunt14/spec-kit-staff-review) |
-| Status Report | Project status, feature progress, and next-action recommendations for spec-driven workflows | `visibility` | Read-only | [Open-Agent-Tools/spec-kit-status](https://github.com/Open-Agent-Tools/spec-kit-status) |
-| Superpowers Bridge | Orchestrates obra/superpowers skills within the spec-kit SDD workflow across the full lifecycle (clarification, TDD, review, verification, critique, debugging, branch completion) | `process` | Read+Write | [superpowers-bridge](https://github.com/RbBtSn0w/spec-kit-extensions/tree/main/superpowers-bridge) |
-| Superpowers Bridge (WangX0111) | Bridges spec-kit with obra/superpowers (brainstorming, TDD, subagent, code-review) into a unified, resumable workflow with graceful degradation and session progress tracking | `process` | Read+Write | [superspec](https://github.com/WangX0111/superspec) |
-| Superpowers Implementation Bridge | Thin orchestrator between Spec Kit (design) and Superpowers (implementation). Cross-agent. | `process` | Read+Write | [speckit-superpowers-bridge](https://github.com/lihan3238/speckit-superpowers-bridge) |
-| Team Assign | Assign tasks.md items to human engineers, split into subtasks, and generate a per-engineer workboard | `process` | Read+Write | [spec-kit-team-assign](https://github.com/tarunkumarbhati/spec-kit-team-assign) |
-| Time Machine | Retroactively apply the full SDD workflow to existing codebases — analyse, spec, and ship feature-by-feature | `process` | Read+Write | [spec-kit-time-machine](https://github.com/teeyo/spec-kit-time-machine) |
-| TinySpec | Lightweight single-file workflow for small tasks — skip the heavy multi-step SDD process | `process` | Read+Write | [spec-kit-tinyspec](https://github.com/Quratulain-bilal/spec-kit-tinyspec) |
-| Token Budget | Reduces LLM token consumption in Spec Kit workflows: compact artifacts in-place, scope per-phase reading, suppress prose padding, and report token usage | `process` | Read+Write | [spec-kit-token-budget](https://github.com/tinesoft/spec-kit-token-budget) |
-| Token Consumption Analyzer | Captures, analyzes, and compares token consumption across SDD workflows | `visibility` | Read-only | [spec-kit-token-analyzer](https://github.com/coderandhiker/spec-kit-token-analyzer) |
-| 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 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) |
-| Wireframe Visual Feedback Loop | SVG wireframe generation, review, and sign-off for spec-driven development. Approved wireframes become spec constraints honored by /speckit.plan, /speckit.tasks, and /speckit.implement | `visibility` | Read+Write | [spec-kit-extension-wireframe](https://github.com/TortoiseWolfe/spec-kit-extension-wireframe) |
-| Work IQ | Integrate Microsoft 365 organizational knowledge into spec-driven development workflows | `integration` | Read-only | [spec-kit-workiq](https://github.com/sakitA/spec-kit-workiq) |
-| Worktree Isolation | Spawn isolated git worktrees for parallel feature development without checkout switching | `process` | Read+Write | [spec-kit-worktree](https://github.com/Quratulain-bilal/spec-kit-worktree) |
-| Worktrees | Default-on worktree isolation for parallel agents — sibling or nested layout | `process` | Read+Write | [spec-kit-worktree-parallel](https://github.com/dango85/spec-kit-worktree-parallel) |
-
-To submit your own extension, see the [Extension Publishing Guide](https://github.com/github/spec-kit/blob/main/extensions/EXTENSION-PUBLISHING-GUIDE.md).
--- a/docs/community/overview.md
+++ b/docs/community/overview.md
@@ -1,27 +0,0 @@
-# Community
-
-The Spec Kit community builds extensions, presets, walkthroughs, and companion projects that expand what you can do with Spec-Driven Development. All community contributions are independently created and maintained by their respective authors.
-
-## Extensions
-
-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)
-
-## Presets
-
-Presets customize how Spec Kit behaves — overriding templates, commands, and terminology without changing any tooling. Community presets range from language localizations to entirely different development methodologies.
-
-[Browse community presets →](presets.md)
-
-## Walkthroughs
-
-Step-by-step guides that show Spec-Driven Development in action across different scenarios, languages, and frameworks.
-
-[Browse community walkthroughs →](walkthroughs.md)
-
-## Friends
-
-Community projects that extend, visualize, or build on Spec Kit — including VS Code extensions, Claude Code plugins, and more.
-
-[Browse friend projects →](friends.md)
--- a/docs/community/presets.md
+++ b/docs/community/presets.md
@@ -15,18 +15,15 @@ The following community-contributed presets customize how Spec Kit behaves — o
 | 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) |
 | Cross-Platform Governance | Adds Bash/PowerShell parity, dry-run/WhatIf parity, Unix man-page expectations, PowerShell comment-based help, and Verb-Noun Cmdlet discipline | 8 templates, 3 commands | — | [spec-kit-preset-cross-platform-governance](https://github.com/hindermath/spec-kit-preset-cross-platform-governance) |
 | Explicit Task Dependencies | Adds explicit `(depends on T###)` dependency declarations and an Execution Wave DAG to tasks.md for parallel scheduling | 1 template, 1 command | — | [spec-kit-preset-explicit-task-dependencies](https://github.com/Quratulain-bilal/spec-kit-preset-explicit-task-dependencies) |
-| Fiction Book Writing | It adapts the Spec-Driven Development workflow for storytelling to create books or audiobooks (with annotations) in 12 languages: features become story elements, specs become story briefs, plans become story structures, and tasks become scene-by-scene writing tasks. Supports single and multi-POV, all major plot structure frameworks, and two style modes: an author voice sample or humanized AI prose principles. Supports interactive elements like brainstorming, interview, roleplay and extras like statistics, cover builder and bio command. Export with templates for KDP, D2D etc. | 25 templates, 33 commands, 2 scripts | — | [speckit-preset-fiction-book-writing](https://github.com/adaumann/speckit-preset-fiction-book-writing) |
-| Game Narrative Writing | Spec-Driven Development for interactive game narrative pre-production for video games. Authors write in a portable generic format, Twine/Sugarcube (.twee) or Ink (.ink). Covers choice-IF, visual novels, and branching dialogue. Supports Tier 1 mechanic hooks (flag, counter, inventory, timer, trust, currency, npc_state, ending_condition), multi-ending design, series carry-over variable registry, and NPC-focused character architecture. | 22 templates, 36 commands, 2 scripts | — | [speckit-preset-game-narrative-writing](https://github.com/adaumann/speckit-preset-game-narrative-writing) |
+| Fiction Book Writing | It adapts the Spec-Driven Development workflow for storytelling to create books or audiobooks (with annotations) in 12 languages: features become story elements, specs become story briefs, plans become story structures, and tasks become scene-by-scene writing tasks. Supports single and multi-POV, all major plot structure frameworks, and two style modes: an author voice sample or humanized AI prose. Supports interactive elements like brainstorming, interview, roleplay and extras like statistics, cover builder and bio command. Export with templates for KDP, D2D etc. | 22 templates, 27 commands, 2 scripts | — | [speckit-preset-fiction-book-writing](https://github.com/adaumann/speckit-preset-fiction-book-writing) |
 | iSAQB Architecture Governance | Adds general iSAQB/CPSA-F and arc42 architecture governance: goals, context, building blocks, runtime and deployment views, quality scenarios, ADRs, risks, and technical debt | 13 templates, 3 commands | — | [spec-kit-preset-isaqb-architecture-governance](https://github.com/hindermath/spec-kit-preset-isaqb-architecture-governance) |
 | Jira Issue Tracking | Overrides `speckit.taskstoissues` to create Jira epics, stories, and tasks instead of GitHub Issues via Atlassian MCP tools | 1 command | — | [spec-kit-preset-jira](https://github.com/luno/spec-kit-preset-jira) |
-| Model Driven Engineering | Focuses on streamlined commands, app repository support, cross-spec support, and capability-aware project memory for model-driven engineering workflows | 6 templates, 11 commands | MDE extension | [spec-kit-preset-mde](https://github.com/AI-MDE/spec-kit-preset-mde) |
 | Multi-Repo Branching | Coordinates feature branch creation across multiple git repositories (independent repos and submodules) during plan and tasks phases | 2 commands | — | [spec-kit-preset-multi-repo-branching](https://github.com/sakitA/spec-kit-preset-multi-repo-branching) |
 | Pirate Speak (Full) | Transforms all Spec Kit output into pirate speak — specs become "Voyage Manifests", plans become "Battle Plans", tasks become "Crew Assignments" | 6 templates, 9 commands | — | [spec-kit-presets](https://github.com/mnriem/spec-kit-presets) |
 | Screenwriting | Spec-Driven Development for screenwriting/scriptwriting/tutorials: feature films, television (pilot, episode, limited series), and stage plays. Adapts the Spec Kit workflow to screenplay craft — slug lines, action lines, act breaks, beat sheets, and industry-standard pitch documents. Supports three-act, Save the Cat, TV pilot, network episode, cable/streaming episode, and stage-play structural frameworks. Export to Fountain, FTX, PDF | 26 templates, 32 commands, 1 script | — | [speckit-preset-screenwriting](https://github.com/adaumann/speckit-preset-screenwriting) |
-| Security Governance | Adds secure development governance: memory-safe-language preference, language-specific secure-coding profiles, NIST SSDF, CWE Top 25, OWASP ASVS, SBOM/AI-SBOM, VEX/SLSA, OpenSSF Scorecard, G7/BSI AI-SBOM target evidence, and EU CRA applicability | 12 templates, 3 commands | — | [spec-kit-preset-security-governance](https://github.com/hindermath/spec-kit-preset-security-governance) |
+| Security Governance | Adds secure development governance: memory-safe-language preference, secure code generation, NIST SSDF, CWE Top 25, OWASP ASVS, SBOM/VEX/SLSA, OpenSSF Scorecard, and EU CRA applicability | 12 templates, 3 commands | — | [spec-kit-preset-security-governance](https://github.com/hindermath/spec-kit-preset-security-governance) |
 | 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) |
 | 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 | 23 templates, 7 commands | — | [spec-kit-workflow-preset](https://github.com/bigsmartben/spec-kit-workflow-preset) |

 To build and publish your own preset, see the [Presets Publishing Guide](https://github.com/github/spec-kit/blob/main/presets/PUBLISHING.md).
--- a/docs/concepts/sdd.md
+++ b/docs/concepts/sdd.md
@@ -1,46 +0,0 @@
-# What is Spec-Driven Development?
-
-Spec-Driven Development **flips the script** on traditional software development. For decades, code has been king — specifications were just scaffolding we built and discarded once the "real work" of coding began. Spec-Driven Development changes this: **specifications become executable**, directly generating working implementations rather than just guiding them.
-
-## Core Philosophy
-
-Spec-Driven Development is a structured process that emphasizes:
-
- **Intent-driven development** where specifications define the "*what*" before the "*how*"
- **Rich specification creation** using guardrails and organizational principles
- **Multi-step refinement** rather than one-shot code generation from prompts
- **Heavy reliance** on advanced AI model capabilities for specification interpretation
-
-## Development Phases
-
-| Phase | Focus | Key Activities |
-|-------|-------|----------------|
-| **0-to-1 Development** ("Greenfield") | Generate from scratch | <ul><li>Start with high-level requirements</li><li>Generate specifications</li><li>Plan implementation steps</li><li>Build production-ready applications</li></ul> |
-| **Creative Exploration** | Parallel implementations | <ul><li>Explore diverse solutions</li><li>Support multiple technology stacks & architectures</li><li>Experiment with UX patterns</li></ul> |
-| **Iterative Enhancement** ("Brownfield") | Brownfield modernization | <ul><li>Add features iteratively</li><li>Modernize legacy systems</li><li>Adapt processes</li></ul> |
-
-## Experimental Goals
-
-Our research and experimentation focus on:
-
-### Technology Independence
-
- Create applications using diverse technology stacks
- Validate the hypothesis that Spec-Driven Development is a process not tied to specific technologies, programming languages, or frameworks
-
-### Enterprise Constraints
-
- Demonstrate mission-critical application development
- Incorporate organizational constraints (cloud providers, tech stacks, engineering practices)
- Support enterprise design systems and compliance requirements
-
-### User-Centric Development
-
- Build applications for different user cohorts and preferences
- Support various development approaches (from vibe-coding to AI-native development)
-
-### Creative & Iterative Processes
-
- Validate the concept of parallel implementation exploration
- Provide robust iterative feature development workflows
- Extend processes to handle upgrades and modernization tasks
--- a/docs/docfx.json
+++ b/docs/docfx.json
@@ -6,9 +6,7 @@
          "*.md",
          "toc.yml",
          "community/*.md",
-          "concepts/*.md",
-          "reference/*.md",
-          "install/*.md"
+          "reference/*.md"
        ]
      },
      {
@@ -51,8 +49,7 @@
    "fileMetadataFiles": [],
    "template": [
      "default",
-      "modern",
-      "template"
+      "modern"
    ],
    "postProcessors": [],
    "markdownEngineName": "markdig",
@@ -70,11 +67,6 @@
        "repo": "https://github.com/github/spec-kit",
        "branch": "main"
      }
-    },
-    "fileMetadata": {
-      "_layout": {
-        "index.md": "landing"
-      }
    }
  }
 }
--- a/docs/index.md
+++ b/docs/index.md
@@ -1,154 +1,67 @@
-<div class="landing-hero">
+# Spec Kit

-# GitHub Spec Kit
+*Build high-quality software faster.*

-**Define what to build before building it — with any AI coding agent.**
+**An effort to allow organizations to focus on product scenarios rather than writing undifferentiated code with the help of Spec-Driven Development.**

-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.
+## What is Spec-Driven Development?

-<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>
+Spec-Driven Development **flips the script** on traditional software development. For decades, code has been king — specifications were just scaffolding we built and discarded once the "real work" of coding began. Spec-Driven Development changes this: **specifications become executable**, directly generating working implementations rather than just guiding them.

-</div>
+## Getting Started

---
+- [Installation Guide](installation.md)
+- [Quick Start Guide](quickstart.md)
+- [Upgrade Guide](upgrade.md)
+- [Local Development](local-development.md)

-<div class="pillar-grid">
+## Core Philosophy

-<div class="pillar-card">
+Spec-Driven Development is a structured process that emphasizes:

-### Spec-driven by default
+- **Intent-driven development** where specifications define the "*what*" before the "*how*"
+- **Rich specification creation** using guardrails and organizational principles
+- **Multi-step refinement** rather than one-shot code generation from prompts
+- **Heavy reliance** on advanced AI model capabilities for specification interpretation

-The core SDD process ships ready to use: **Spec → Plan → Tasks → Implement**.
+## Development Phases

-Define what to build before building it. Rich templates, quality checklists, and cross-artifact analysis come out of the box. Each phase produces a Markdown artifact that feeds the next — giving your AI coding agent structured context instead of ad-hoc prompts.
+| Phase | Focus | Key Activities |
+|-------|-------|----------------|
+| **0-to-1 Development** ("Greenfield") | Generate from scratch | <ul><li>Start with high-level requirements</li><li>Generate specifications</li><li>Plan implementation steps</li><li>Build production-ready applications</li></ul> |
+| **Creative Exploration** | Parallel implementations | <ul><li>Explore diverse solutions</li><li>Support multiple technology stacks & architectures</li><li>Experiment with UX patterns</li></ul> |
+| **Iterative Enhancement** ("Brownfield") | Brownfield modernization | <ul><li>Add features iteratively</li><li>Modernize legacy systems</li><li>Adapt processes</li></ul> |

-<a href="quickstart.md" class="pillar-link">Walk through the workflow →</a>
+## Experimental Goals

-</div>
+Our research and experimentation focus on:

-<div class="pillar-card">
+### Technology Independence

-### Use any coding agent
+- Create applications using diverse technology stacks
+- Validate the hypothesis that Spec-Driven Development is a process not tied to specific technologies, programming languages, or frameworks

-<span class="pillar-stat">30 integrations</span> — Copilot, Gemini, Codex, Windsurf, Claude, Forge, Kiro, and more. Switch freely between agents with a single command. No lock-in.
+### Enterprise Constraints

-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.
+- Demonstrate mission-critical application development
+- Incorporate organizational constraints (cloud providers, tech stacks, engineering practices)
+- Support enterprise design systems and compliance requirements

-<a href="reference/integrations.md" class="pillar-link">See all integrations →</a>
+### User-Centric Development

-</div>
+- Build applications for different user cohorts and preferences
+- Support various development approaches (from vibe-coding to AI-native development)

-<div class="pillar-card">
+### Creative & Iterative Processes

-### Make it your own
+- Validate the concept of parallel implementation exploration
+- Provide robust iterative feature development workflows
+- Extend processes to handle upgrades and modernization tasks

-<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.
+## Contributing

-Including entirely different SDD processes:
+Please see our [Contributing Guide](https://github.com/github/spec-kit/blob/main/CONTRIBUTING.md) for information on how to contribute to this project.

- **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
+## Support

-<a href="community/presets.md" class="pillar-link">Browse community presets →</a>
-
-</div>
-
-<div class="pillar-card">
-
-### Integrate into your organization
-
-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="installation.md" class="pillar-link">Installation guide →</a>&nbsp;&nbsp;
-<a href="reference/extensions.md" class="pillar-link">Extensions reference →</a>
-
-</div>
-
-</div>
-
---
-
-<div class="community-section">
-
-## Built by the community
-
-**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">106K+</span>
-    <span class="stat-label">GitHub stars</span>
-  </div>
-  <div class="stat-item">
-    <span class="stat-number">200+</span>
-    <span class="stat-label">Contributors</span>
-  </div>
-  <div class="stat-item">
-    <span class="stat-number">30</span>
-    <span class="stat-label">Integrations</span>
-  </div>
-  <div class="stat-item">
-    <span class="stat-number">105</span>
-    <span class="stat-label">Extensions</span>
-  </div>
-  <div class="stat-item">
-    <span class="stat-number">22</span>
-    <span class="stat-label">Presets</span>
-  </div>
-  <div class="stat-item">
-    <span class="stat-number">4</span>
-    <span class="stat-label">Friends projects</span>
-  </div>
-</div>
-
-<a href="community/presets.md">Presets</a> · <a href="community/walkthroughs.md">Walkthroughs</a> · <a href="community/friends.md">Friends</a>
-
-</div>
-
---
-
-## Explore the docs
-
-<div class="nav-cards">
-  <a href="quickstart.md" class="nav-card">
-    <strong>Getting Started</strong>
-    <span>Install, configure, and run your first SDD workflow</span>
-  </a>
-  <a href="reference/overview.md" class="nav-card">
-    <strong>Reference</strong>
-    <span>Core commands, integrations, extensions, presets, and workflows</span>
-  </a>
-  <a href="community/overview.md" class="nav-card">
-    <strong>Community</strong>
-    <span>Extensions, presets, walkthroughs, and friend projects</span>
-  </a>
-  <a href="local-development.md" class="nav-card">
-    <strong>Development</strong>
-    <span>Contribute to Spec Kit</span>
-  </a>
-  <a href="concepts/sdd.md" class="nav-card">
-    <strong>What is SDD?</strong>
-    <span>The philosophy behind Spec-Driven Development</span>
-  </a>
-</div>
-
---
-
-<div class="footer-cta">
-
-```bash
-uvx --from git+https://github.com/github/spec-kit.git
-specify init my-project --integration copilot
-```
-
-Ready to start? Follow the [Quick Start Guide](quickstart.md).
-
-</div>
-
-<p class="text-end small text-body-secondary">Last updated: May 27, 2026</p>
+For support, please check our [Support Guide](https://github.com/github/spec-kit/blob/main/SUPPORT.md) or open an issue on GitHub.
--- a/docs/install/air-gapped.md
+++ b/docs/install/air-gapped.md
@@ -1,59 +0,0 @@
-# Enterprise / Air-Gapped Installation
-
-If your environment blocks access to PyPI or GitHub, you can create a portable wheel bundle on a connected machine and transfer it to the air-gapped target.
-
-## Step 1: Build the wheel on a connected machine
-
-> **Important:** `pip download` resolves platform-specific wheels (e.g., PyYAML includes native extensions). You must run this step on a machine with the **same OS and Python version** as the air-gapped target. If you need to support multiple platforms, repeat this step on each target OS (Linux, macOS, Windows) and Python version.
-
-```bash
-# Clone the repository
-git clone https://github.com/github/spec-kit.git
-cd spec-kit
-
-# Build the wheel
-pip install build
-python -m build --wheel --outdir dist/
-
-# Download the wheel and all its runtime dependencies
-pip download -d dist/ dist/specify_cli-*.whl
-```
-
-## Step 2: Transfer the `dist/` directory
-
-Copy the entire `dist/` directory (which contains the `specify-cli` wheel and all dependency wheels) to the target machine via USB, network share, or other approved transfer method.
-
-## Step 3: Install on the air-gapped machine
-
-```bash
-pip install --no-index --find-links=./dist specify-cli
-```
-
-## Step 4: Initialize a project
-
-No network access is required — bundled assets are used by default:
-
-```bash
-specify init my-project --integration copilot
-```
-
-> **Note:** Python 3.11+ is required.
-
-> **Windows note:** Offline scaffolding requires PowerShell 7+ (`pwsh`), not Windows PowerShell 5.x (`powershell.exe`). Install from https://aka.ms/powershell.
-
-## Git Credential Manager on Linux
-
-If you're having issues with Git authentication on Linux, you can install Git Credential Manager:
-
-```bash
-#!/usr/bin/env bash
-set -e
-echo "Downloading Git Credential Manager v2.6.1..."
-wget https://github.com/git-ecosystem/git-credential-manager/releases/download/v2.6.1/gcm-linux_amd64.2.6.1.deb
-echo "Installing Git Credential Manager..."
-sudo dpkg -i gcm-linux_amd64.2.6.1.deb
-echo "Configuring Git to use GCM..."
-git config --global credential.helper manager
-echo "Cleaning up..."
-rm gcm-linux_amd64.2.6.1.deb
-```
--- a/docs/install/one-time.md
+++ b/docs/install/one-time.md
@@ -1,32 +0,0 @@
-# One-time Usage (uvx)
-
-If you want to try Spec Kit without installing it permanently, use `uvx` to run it directly. This downloads the tool into a temporary environment that is discarded after the command finishes.
-
-> [!NOTE]
-> The commands below require **[uv](https://docs.astral.sh/uv/)**. If you see `command not found: uvx`, [install uv first](uv.md).
-
-## Run Specify CLI
-
-```bash
-# 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)
-uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <PROJECT_NAME>
-
-# Initialize in the current directory
-uvx --from git+https://github.com/github/spec-kit.git specify init . --integration copilot
-
-# Or use the --here flag
-uvx --from git+https://github.com/github/spec-kit.git specify init --here --integration copilot
-```
-
-## When to use persistent installation instead
-
-If you plan to use Spec Kit regularly, a persistent installation is recommended:
-
- Tool stays installed and available in PATH
- No re-download on every invocation
- Better tool management with `uv tool list`, `uv tool upgrade`, `uv tool uninstall`
-
-See the main [Installation Guide](../installation.md) for persistent installation instructions.
--- a/docs/install/pipx.md
+++ b/docs/install/pipx.md
@@ -1,37 +0,0 @@
-# Installing with pipx
-
-[pipx](https://pipx.pypa.io/) is a tool for installing Python CLI applications in isolated environments. It does not require [uv](https://docs.astral.sh/uv/).
-
-## Install Specify CLI
-
-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)
-pipx install git+https://github.com/github/spec-kit.git@vX.Y.Z
-
-# Or install latest from main (may include unreleased changes)
-pipx install git+https://github.com/github/spec-kit.git
-```
-
-## Verify
-
-```bash
-specify version
-```
-
-## Upgrade
-
-```bash
-pipx install --force git+https://github.com/github/spec-kit.git@vX.Y.Z
-```
-
-## Uninstall
-
-```bash
-pipx uninstall specify-cli
-```
-
-## Next steps
-
-Head to the [Quick Start](../quickstart.md) to initialize your first project.
--- a/docs/installation.md
+++ b/docs/installation.md
@@ -4,41 +4,44 @@

 - **Linux/macOS** (or Windows; PowerShell scripts now supported without WSL)
 - AI coding agent: [Claude Code](https://www.anthropic.com/claude-code), [GitHub Copilot](https://code.visualstudio.com/), [Codebuddy CLI](https://www.codebuddy.ai/cli), [Gemini CLI](https://github.com/google-gemini/gemini-cli), or [Pi Coding Agent](https://pi.dev)
- [uv](https://docs.astral.sh/uv/) for package management (recommended) or [pipx](https://pipx.pypa.io/) for persistent installation
+- [uv](https://docs.astral.sh/uv/) for package management (recommended) or [pipx](https://pypa.github.io/pipx/) for persistent installation
 - [Python 3.11+](https://www.python.org/downloads/)
 - [Git](https://git-scm.com/downloads)

 ## Installation

-> [!IMPORTANT]
-> 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.
+> **Important:** 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.

-### Persistent Installation (Recommended)
+### Initialize a New Project

-Install once and use everywhere. Replace `vX.Y.Z` with a tag from [Releases](https://github.com/github/spec-kit/releases):
+The easiest way to get started is to initialize a new project. Pin a specific release tag for stability (check [Releases](https://github.com/github/spec-kit/releases) for the latest):

 > [!NOTE]
-> The command below requires **[uv](https://docs.astral.sh/uv/)**. If you see `command not found: uv`, [install uv first](./install/uv.md).
+> The `uvx` commands below require **[uv](https://docs.astral.sh/uv/)**. If you see `command not found: uvx`, [install uv first](./install/uv.md). The `pipx` alternative does not require uv.

 ```bash
-uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@vX.Y.Z
+# Install from a specific stable release (recommended — replace vX.Y.Z with the latest tag)
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <PROJECT_NAME>
+
+# Or install latest from main (may include unreleased changes)
+uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME>
 ```

-Then initialize a project:
+> [!NOTE]
+> For a persistent installation, `pipx` works equally well:
+> ```bash
+> pipx install git+https://github.com/github/spec-kit.git@vX.Y.Z
+> ```
+> The project uses a standard `hatchling` build backend and has no uv-specific dependencies.
+
+Or initialize in the current directory:

 ```bash
-specify init <PROJECT_NAME> --integration copilot
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init .
+# or use the --here flag
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init --here
 ```

-### One-time Usage
-
-Run directly without installing — see the [One-time usage (uvx)](install/one-time.md) guide.
-
-### Alternative Package Managers
-
- **pipx** — see the [pipx installation guide](install/pipx.md)
- **Enterprise / Air-Gapped** — see the [air-gapped installation guide](install/air-gapped.md)
-
 ### Specify Integration

 Interactive terminals prompt you to choose a coding agent integration during initialization. Non-interactive sessions, such as CI or piped runs, default to GitHub Copilot unless you pass `--integration`.
@@ -46,11 +49,11 @@ Interactive terminals prompt you to choose a coding agent integration during ini
 You can proactively specify your coding agent integration during initialization:

 ```bash
-specify init <project_name> --integration claude
-specify init <project_name> --integration gemini
-specify init <project_name> --integration copilot
-specify init <project_name> --integration codebuddy
-specify init <project_name> --integration pi
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <project_name> --integration claude
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <project_name> --integration gemini
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <project_name> --integration copilot
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <project_name> --integration codebuddy
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <project_name> --integration pi
 ```

 ### Specify Script Type (Shell vs PowerShell)
@@ -66,8 +69,8 @@ Auto behavior:
 Force a specific script type:

 ```bash
-specify init <project_name> --script sh
-specify init <project_name> --script ps
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <project_name> --script sh
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <project_name> --script ps
 ```

 ### Ignore Agent Tools Check
@@ -75,7 +78,7 @@ specify init <project_name> --script ps
 If you prefer to get the templates without checking for the right tools:

 ```bash
-specify init <project_name> --integration claude --ignore-agent-tools
+uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init <project_name> --integration claude --ignore-agent-tools
 ```

 ## Verification
@@ -94,17 +97,67 @@ After initialization, you should see the following commands available in your co
 - `/speckit.plan` - Generate implementation plans  
 - `/speckit.tasks` - Break down into actionable tasks

-Scripts are installed into a variant subdirectory matching the chosen script type:
-
- `.specify/scripts/bash/` — contains `.sh` scripts (default on Linux/macOS)
- `.specify/scripts/powershell/` — contains `.ps1` scripts (default on Windows)
+The `.specify/scripts` directory will contain both `.sh` and `.ps1` scripts.

 ## Troubleshooting

 ### Enterprise / Air-Gapped Installation

-If your environment blocks access to PyPI or GitHub, see the [Enterprise / Air-Gapped Installation](install/air-gapped.md) guide for step-by-step instructions on creating portable wheel bundles.
+If your environment blocks access to PyPI (you see 403 errors when running `uv tool install` or `pip install`), you can create a portable wheel bundle on a connected machine and transfer it to the air-gapped target.
+
+**Step 1: Build the wheel on a connected machine (same OS and Python version as the target)**
+
+```bash
+# Clone the repository
+git clone https://github.com/github/spec-kit.git
+cd spec-kit
+
+# Build the wheel
+pip install build
+python -m build --wheel --outdir dist/
+
+# Download the wheel and all its runtime dependencies
+pip download -d dist/ dist/specify_cli-*.whl
+```
+
+> **Important:** `pip download` resolves platform-specific wheels (e.g., PyYAML includes native extensions). You must run this step on a machine with the **same OS and Python version** as the air-gapped target. If you need to support multiple platforms, repeat this step on each target OS (Linux, macOS, Windows) and Python version.
+
+**Step 2: Transfer the `dist/` directory to the air-gapped machine**
+
+Copy the entire `dist/` directory (which contains the `specify-cli` wheel and all dependency wheels) to the target machine via USB, network share, or other approved transfer method.
+
+**Step 3: Install on the air-gapped machine**
+
+```bash
+pip install --no-index --find-links=./dist specify-cli
+```
+
+**Step 4: Initialize a project (no network required)**
+
+```bash
+# Initialize a project — no GitHub access needed
+specify init my-project --integration claude
+```
+
+Bundled assets are used by default — no network access is required.
+
+> **Note:** Python 3.11+ is required.
+
+> **Windows note:** Offline scaffolding requires PowerShell 7+ (`pwsh`), not Windows PowerShell 5.x (`powershell.exe`). Install from https://aka.ms/powershell.

 ### Git Credential Manager on Linux

-If you're having issues with Git authentication on Linux, see the [Air-Gapped Installation guide](install/air-gapped.md#git-credential-manager-on-linux) for Git Credential Manager setup instructions.
+If you're having issues with Git authentication on Linux, you can install Git Credential Manager:
+
+```bash
+#!/usr/bin/env bash
+set -e
+echo "Downloading Git Credential Manager v2.6.1..."
+wget https://github.com/git-ecosystem/git-credential-manager/releases/download/v2.6.1/gcm-linux_amd64.2.6.1.deb
+echo "Installing Git Credential Manager..."
+sudo dpkg -i gcm-linux_amd64.2.6.1.deb
+echo "Configuring Git to use GCM..."
+git config --global credential.helper manager
+echo "Cleaning up..."
+rm gcm-linux_amd64.2.6.1.deb
+```
--- a/docs/quickstart.md
+++ b/docs/quickstart.md
@@ -5,19 +5,11 @@ This guide will help you get started with Spec-Driven Development using Spec Kit
 > [!NOTE]
 > 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`.

-## Recommended Workflow
+## The 6-Step Process

 > [!TIP]
 > **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 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:
-
-```text
-/speckit.constitution -> /speckit.specify -> /speckit.clarify -> /speckit.checklist -> /speckit.plan -> /speckit.tasks -> /speckit.analyze -> /speckit.implement
-```
-
-Use `/speckit.clarify` to reduce requirement ambiguity before planning, `/speckit.checklist` to validate requirements quality before planning, 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.
-
 ### Step 1: Install Specify

 **In your terminal**, run the `specify` CLI command to initialize your project:
@@ -32,13 +24,10 @@ uvx --from git+https://github.com/github/spec-kit.git specify init .

 > [!NOTE]
 > 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 .
@@ -67,7 +56,7 @@ uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME
 /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: Refine and Validate the Spec
+### Step 4: Refine the Spec

 **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.

@@ -75,12 +64,6 @@ uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME
 /speckit.clarify Focus on security and performance requirements.
 ```

-Then validate the requirements with `/speckit.checklist` before creating the technical plan:
-
-```bash
-/speckit.checklist
-```
-
 ### Step 5: Create a Technical Implementation Plan

 **In the chat**, use the `/speckit.plan` slash command to provide your tech stack and architecture choices.
@@ -89,7 +72,7 @@ Then validate the requirements with `/speckit.checklist` before creating the tec
 /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.
 ```

-### Step 6: Break Down, Analyze, and Implement
+### Step 6: Break Down and Implement

 **In the chat**, use the `/speckit.tasks` slash command to create an actionable task list.

@@ -97,13 +80,13 @@ Then validate the requirements with `/speckit.checklist` before creating the tec
 /speckit.tasks
 ```

-Validate cross-artifact consistency with `/speckit.analyze` before implementation:
+Optionally, validate the plan with `/speckit.analyze`:

 ```markdown
 /speckit.analyze
 ```

-Use the `/speckit.implement` slash command to execute the plan.
+Then, use the `/speckit.implement` slash command to execute the plan.

 ```markdown
 /speckit.implement
@@ -176,7 +159,7 @@ Generate an actionable task list using the `/speckit.tasks` command:

 ### Step 7: Validate and Implement

-Have your coding agent audit the spec, plan, and tasks with `/speckit.analyze` before implementation:
+Have your coding agent audit the implementation plan using `/speckit.analyze`:

 ```bash
 /speckit.analyze
@@ -196,7 +179,7 @@ Finally, implement the solution:
 - **Be explicit** about what you're building and why
 - **Don't focus on tech stack** during specification phase
 - **Iterate and refine** your specifications before implementation
- **Validate** requirements and plans before coding begins
+- **Validate** the plan before coding begins
 - **Let the coding agent handle** the implementation details

 ## Next Steps
--- a/docs/reference/authentication.md
+++ b/docs/reference/authentication.md
@@ -1,181 +0,0 @@
-# Authentication
-
-Specify CLI uses **opt-in authentication** for HTTP requests to catalog
-sources, extension downloads, and release checks.  No credentials are
-sent unless you explicitly configure them.
-
-## Configuration
-
-Create `~/.specify/auth.json` to enable authentication:
-
-```json
-{
-  "providers": [
-    {
-      "hosts": ["github.com", "api.github.com", "raw.githubusercontent.com", "codeload.github.com"],
-      "provider": "github",
-      "auth": "bearer",
-      "token_env": "GH_TOKEN"
-    }
-  ]
-}
-```
-
-> **Security:** Restrict the file to owner-only access:
-> ```bash
-> chmod 600 ~/.specify/auth.json
-> ```
-
-Without this file, all HTTP requests are unauthenticated.
-
-## Fields
-
-Each entry in the `providers` array has the following fields:
-
-| Field | Required | Description |
-|---|---|---|
-| `hosts` | Yes | Array of hostnames this entry applies to. Supports exact hostnames, or a leading `*.` wildcard for subdomains only (for example, `*.visualstudio.com`). `*.visualstudio.com` matches `foo.visualstudio.com`, but not `visualstudio.com`. Other glob patterns such as `*github.com` or `gith?b.com` are not supported. |
-| `provider` | Yes | Built-in provider key: `github` or `azure-devops`. |
-| `auth` | Yes | Auth scheme (see below). |
-| `token` | No | Token value (inline). Use `token_env` instead when possible. |
-| `token_env` | No | Environment variable name to read the token from. |
-
-For `azure-ad` auth, additional fields are required:
-
-| Field | Required | Description |
-|---|---|---|
-| `tenant_id` | Yes | Azure AD tenant ID. |
-| `client_id` | Yes | Service principal client ID. |
-| `client_secret_env` | Yes | Environment variable containing the client secret. |
-
-Either `token` or `token_env` must be set for `bearer` and `basic-pat` schemes.
-
-## Providers and auth schemes
-
-### GitHub (`github`)
-
-| Scheme | Header | Use for |
-|---|---|---|
-| `bearer` | `Authorization: Bearer <token>` | PATs, fine-grained PATs, OAuth tokens, GitHub App tokens |
-
-**Example — PAT via environment variable:**
-
-```json
-{
-  "hosts": ["github.com", "api.github.com", "raw.githubusercontent.com", "codeload.github.com"],
-  "provider": "github",
-  "auth": "bearer",
-  "token_env": "GH_TOKEN"
-}
-```
-
-### Azure DevOps (`azure-devops`)
-
-| Scheme | Header | Use for |
-|---|---|---|
-| `basic-pat` | `Authorization: Basic base64(:<PAT>)` | Personal Access Tokens |
-| `bearer` | `Authorization: Bearer <token>` | Pre-acquired OAuth / Azure AD tokens |
-| `azure-cli` | `Authorization: Bearer <token>` | Token acquired via `az account get-access-token` |
-| `azure-ad` | `Authorization: Bearer <token>` | Token acquired via OAuth2 client credentials flow |
-
-**Example — PAT via environment variable:**
-
-```json
-{
-  "hosts": ["dev.azure.com"],
-  "provider": "azure-devops",
-  "auth": "basic-pat",
-  "token_env": "AZURE_DEVOPS_PAT"
-}
-```
-
-**Example — Azure CLI (interactive login):**
-
-```json
-{
-  "hosts": ["dev.azure.com"],
-  "provider": "azure-devops",
-  "auth": "azure-cli"
-}
-```
-
-Requires `az login` to have been run beforehand.
-
-**Example — Azure AD service principal (CI/automation):**
-
-```json
-{
-  "hosts": ["dev.azure.com"],
-  "provider": "azure-devops",
-  "auth": "azure-ad",
-  "tenant_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
-  "client_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
-  "client_secret_env": "AZURE_CLIENT_SECRET"
-}
-```
-
-## Multiple entries
-
-You can configure multiple entries for different hosts or organizations:
-
-```json
-{
-  "providers": [
-    {
-      "hosts": ["github.com", "api.github.com", "raw.githubusercontent.com", "codeload.github.com"],
-      "provider": "github",
-      "auth": "bearer",
-      "token_env": "GH_TOKEN"
-    },
-    {
-      "hosts": ["dev.azure.com"],
-      "provider": "azure-devops",
-      "auth": "basic-pat",
-      "token_env": "AZURE_DEVOPS_PAT"
-    }
-  ]
-}
-```
-
-## How it works
-
-1. For each outbound HTTP request, the URL hostname is matched against
-   the `hosts` patterns in `auth.json`.
-2. If a match is found, the corresponding provider resolves the token
-   and attaches the appropriate `Authorization` header.
-3. If the request receives a 401 or 403, the next matching entry is tried.
-4. After all matching entries are exhausted, an unauthenticated request
-   is attempted as a final fallback.
-5. On redirects, the `Authorization` header is stripped if the redirect
-   target leaves the entry's declared hosts — preventing credential
-   leakage to CDNs or third-party services.
-
-## Template
-
-A reference `auth.json` with GitHub pre-configured:
-
-```json
-{
-  "providers": [
-    {
-      "hosts": [
-        "github.com",
-        "api.github.com",
-        "raw.githubusercontent.com",
-        "codeload.github.com"
-      ],
-      "provider": "github",
-      "auth": "bearer",
-      "token_env": "GH_TOKEN"
-    }
-  ]
-}
-```
-
-To use it:
-
-```bash
-mkdir -p ~/.specify
-# Copy the JSON above into ~/.specify/auth.json
-chmod 600 ~/.specify/auth.json
-```
--- a/docs/reference/core.md
+++ b/docs/reference/core.md
@@ -69,8 +69,6 @@ specify check

 Checks that required tools are available on your system: `git` and any CLI-based AI coding agents. IDE-based agents are skipped since they don't require a CLI tool.

-This command stays offline. If a command behaves like an older Spec Kit version or an expected CLI feature is missing, run `specify self check` to check whether your local CLI is behind the latest release.
-
 ## Version Information

 ```bash
@@ -79,16 +77,6 @@ specify version

 Displays the Spec Kit CLI version, Python version, platform, and architecture.

-To inspect local CLI capabilities without checking the network:
-
-```bash
-specify version --features
-specify version --features --json
-```
-
-The JSON form is intended for scripts and coding agents that need to choose a
-workflow based on the installed CLI's supported features.
-
 A quick version check is also available via:

 ```bash
--- a/docs/reference/integrations.md
+++ b/docs/reference/integrations.md
@@ -23,7 +23,7 @@ The Specify CLI supports a wide range of AI coding agents. When you run `specify
 | [Junie](https://junie.jetbrains.com/)                                                | `junie`          |                                                                                                                                           |
 | [Kilo Code](https://github.com/Kilo-Org/kilocode)                                    | `kilocode`       |                                                                                                                                           |
 | [Kimi Code](https://code.kimi.com/)                                                  | `kimi`           | Skills-based integration; supports `--migrate-legacy` for dotted→hyphenated directory migration                                            |
-| [Kiro CLI](https://kiro.dev/docs/cli/)                                               | `kiro-cli`       | Kiro CLI does not substitute `$ARGUMENTS` in file-based prompts, so Spec Kit ships a prose fallback at render time (see [Manage prompts](https://kiro.dev/docs/cli/chat/manage-prompts/) and issue [#1926](https://github.com/github/spec-kit/issues/1926)). Alias: `--integration kiro` |
+| [Kiro CLI](https://kiro.dev/docs/cli/)                                               | `kiro-cli`       | Alias: `--integration kiro`                                                                                                               |
 | [Lingma](https://lingma.aliyun.com/)                                                 | `lingma`         | Skills-based integration; skills are installed automatically                                                                               |
 | [Mistral Vibe](https://github.com/mistralai/mistral-vibe)                            | `vibe`           |                                                                                                                                           |
 | [opencode](https://opencode.ai/)                                                     | `opencode`       |                                                                                                                                           |
@@ -65,8 +65,6 @@ Installing an additional integration does not change the default integration. Us

 > **Note:** All integration management commands require a project already initialized with `specify init`. To start a new project with a specific agent, use `specify init <project> --integration <key>` instead.

-**Version note:** Controlled multi-install support was introduced in Spec Kit 0.8.5. If `specify integration install <key>` says another integration is already installed and only suggests `switch` or `uninstall`, check your local CLI with `specify version` and upgrade it. Running a one-shot command such as `uvx --from git+https://github.com/github/spec-kit.git specify ...` uses a temporary copy for that command only; it does not update the persistent `specify` executable on your `PATH`.
-
 ## Uninstall an Integration

 ```bash
--- a/docs/template/public/main.css
+++ b/docs/template/public/main.css
@@ -1,264 +0,0 @@
-/* Spec Kit landing page — GitHub Primer colors */
-
-:root {
-  /* GitHub Primer palette */
-  --gh-blue: #0969da;
-  --gh-green: #1a7f37;
-  --gh-purple: #8250df;
-  --gh-coral: #cf222e;
-  --gh-orange: #bf8700;
-  --gh-blue-subtle: #ddf4ff;
-  --gh-green-subtle: #dafbe1;
-  --gh-purple-subtle: #fbefff;
-  --gh-coral-subtle: #ffebe9;
-}
-
-[data-bs-theme="dark"] {
-  --gh-blue: #58a6ff;
-  --gh-green: #3fb950;
-  --gh-purple: #bc8cff;
-  --gh-coral: #f85149;
-  --gh-orange: #d29922;
-  --gh-blue-subtle: #0d1d30;
-  --gh-green-subtle: #0d1d14;
-  --gh-purple-subtle: #1c0d2e;
-  --gh-coral-subtle: #2d0f0d;
-}
-
-/* Override Bootstrap primary with GitHub blue */
-body[data-layout="landing"] {
-  --bs-primary: var(--gh-blue);
-  --bs-primary-rgb: 9, 105, 218;
-  --bs-link-color: var(--gh-blue);
-  --bs-link-hover-color: var(--gh-blue);
-}
-
-[data-bs-theme="dark"] body[data-layout="landing"],
-body[data-layout="landing"][data-bs-theme="dark"] {
-  --bs-primary-rgb: 88, 166, 255;
-}
-
-/* Hero section */
-.landing-hero {
-  text-align: center;
-  padding: 3rem 0 1.5rem;
-}
-
-.landing-hero h1 {
-  font-size: 2.6rem;
-  font-weight: 800;
-  margin-bottom: 0.5rem;
-  background: linear-gradient(135deg, var(--gh-blue), var(--gh-purple));
-  -webkit-background-clip: text;
-  -webkit-text-fill-color: transparent;
-  background-clip: text;
-}
-
-.landing-hero p {
-  font-size: 1.15rem;
-  max-width: 640px;
-  margin: 0 auto 1.5rem;
-  opacity: 0.85;
-}
-
-.landing-hero .btn-primary {
-  background-color: var(--gh-blue);
-  border-color: var(--gh-blue);
-  color: #fff;
-}
-
-.landing-hero .btn-primary:hover {
-  background-color: #0860ca;
-  border-color: #0860ca;
-}
-
-.landing-hero .btn-outline-primary {
-  color: var(--gh-blue);
-  border-color: var(--gh-blue);
-}
-
-.landing-hero .btn-outline-primary:hover {
-  background-color: var(--gh-blue);
-  border-color: var(--gh-blue);
-  color: #fff;
-}
-
-/* Pillar cards grid */
-.pillar-grid {
-  display: grid;
-  grid-template-columns: 1fr 1fr;
-  gap: 1.5rem;
-  margin: 2rem 0;
-}
-
-@media (max-width: 768px) {
-  .pillar-grid {
-    grid-template-columns: 1fr;
-  }
-}
-
-.pillar-card {
-  border: 1px solid var(--bs-border-color);
-  border-radius: 0.5rem;
-  padding: 1.5rem;
-  background: var(--bs-body-bg);
-  transition: box-shadow 0.2s ease-in-out, border-color 0.2s ease-in-out;
-  border-top: 3px solid transparent;
-}
-
-/* Each pillar gets a distinct GitHub color accent */
-.pillar-card:nth-child(1) { border-top-color: var(--gh-green); }
-.pillar-card:nth-child(2) { border-top-color: var(--gh-blue); }
-.pillar-card:nth-child(3) { border-top-color: var(--gh-purple); }
-.pillar-card:nth-child(4) { border-top-color: var(--gh-coral); }
-
-.pillar-card:nth-child(1):hover { box-shadow: 0 4px 16px rgba(26, 127, 55, 0.12); }
-.pillar-card:nth-child(2):hover { box-shadow: 0 4px 16px rgba(9, 105, 218, 0.12); }
-.pillar-card:nth-child(3):hover { box-shadow: 0 4px 16px rgba(130, 80, 223, 0.12); }
-.pillar-card:nth-child(4):hover { box-shadow: 0 4px 16px rgba(207, 34, 46, 0.12); }
-
-[data-bs-theme="dark"] .pillar-card:nth-child(1):hover { box-shadow: 0 4px 16px rgba(63, 185, 80, 0.15); }
-[data-bs-theme="dark"] .pillar-card:nth-child(2):hover { box-shadow: 0 4px 16px rgba(88, 166, 255, 0.15); }
-[data-bs-theme="dark"] .pillar-card:nth-child(3):hover { box-shadow: 0 4px 16px rgba(188, 140, 255, 0.15); }
-[data-bs-theme="dark"] .pillar-card:nth-child(4):hover { box-shadow: 0 4px 16px rgba(248, 81, 73, 0.15); }
-
-.pillar-card h3 {
-  font-size: 1.2rem;
-  font-weight: 600;
-  margin-bottom: 0.75rem;
-}
-
-/* Pillar headings pick up their card's accent color */
-.pillar-card:nth-child(1) h3 { color: var(--gh-green); }
-.pillar-card:nth-child(2) h3 { color: var(--gh-blue); }
-.pillar-card:nth-child(3) h3 { color: var(--gh-purple); }
-.pillar-card:nth-child(4) h3 { color: var(--gh-coral); }
-
-.pillar-card .pillar-stat {
-  font-weight: 600;
-  color: var(--gh-blue);
-}
-
-.pillar-card:nth-child(3) .pillar-stat {
-  color: var(--gh-purple);
-}
-
-.pillar-card p:last-child {
-  margin-bottom: 0;
-}
-
-.pillar-card ul {
-  padding-left: 1.2rem;
-  margin-bottom: 0.5rem;
-}
-
-.pillar-card .pillar-link {
-  display: inline-block;
-  margin-top: 0.5rem;
-  font-size: 0.9rem;
-  font-weight: 500;
-}
-
-.pillar-card:nth-child(1) .pillar-link { color: var(--gh-blue); }
-.pillar-card:nth-child(2) .pillar-link { color: var(--gh-green); }
-.pillar-card:nth-child(3) .pillar-link { color: var(--gh-purple); }
-.pillar-card:nth-child(4) .pillar-link { color: var(--gh-coral); }
-
-/* Community stats section */
-.community-section {
-  text-align: center;
-  padding: 2rem 0;
-}
-
-.stats-grid {
-  display: grid;
-  grid-template-columns: repeat(3, 1fr);
-  gap: 1rem;
-  margin: 1.5rem auto;
-  max-width: 700px;
-}
-
-@media (max-width: 576px) {
-  .stats-grid {
-    grid-template-columns: repeat(2, 1fr);
-  }
-}
-
-.stat-item {
-  padding: 1rem;
-}
-
-.stat-item .stat-number {
-  display: block;
-  font-size: 1.8rem;
-  font-weight: 700;
-  color: var(--gh-blue);
-  line-height: 1.2;
-}
-
-.stat-item .stat-label {
-  display: block;
-  font-size: 0.85rem;
-  opacity: 0.75;
-  margin-top: 0.25rem;
-}
-
-/* Nav cards */
-.nav-cards {
-  display: grid;
-  grid-template-columns: 1fr 1fr;
-  gap: 1rem;
-  margin: 1.5rem 0;
-}
-
-@media (max-width: 576px) {
-  .nav-cards {
-    grid-template-columns: 1fr;
-  }
-}
-
-.nav-card {
-  border: 1px solid var(--bs-border-color);
-  border-radius: 0.5rem;
-  padding: 1rem 1.25rem;
-  text-decoration: none;
-  color: inherit;
-  transition: box-shadow 0.2s ease-in-out, border-color 0.2s ease-in-out;
-  display: block;
-  border-left: 3px solid var(--gh-blue);
-}
-
-.nav-card:hover {
-  border-color: var(--gh-blue);
-  border-left-color: var(--gh-blue);
-  box-shadow: 0 2px 8px rgba(9, 105, 218, 0.1);
-  text-decoration: none;
-  color: inherit;
-}
-
-[data-bs-theme="dark"] .nav-card:hover {
-  box-shadow: 0 2px 8px rgba(88, 166, 255, 0.12);
-}
-
-.nav-card strong {
-  display: block;
-  margin-bottom: 0.25rem;
-  color: var(--gh-blue);
-}
-
-.nav-card span {
-  font-size: 0.9rem;
-  opacity: 0.75;
-}
-
-/* Footer CTA */
-.footer-cta {
-  text-align: center;
-  padding: 2rem 0 1rem;
-}
-
-.footer-cta code {
-  font-size: 1.05rem;
-  padding: 0.5rem 1rem;
-  border-radius: 0.375rem;
-}
--- a/docs/toc.yml
+++ b/docs/toc.yml
@@ -13,12 +13,6 @@
      href: upgrade.md
    - name: Install uv
      href: install/uv.md
-    - name: Install with pipx
-      href: install/pipx.md
-    - name: One-time Usage (uvx)
-      href: install/one-time.md
-    - name: Enterprise / Air-Gapped
-      href: install/air-gapped.md

 # Reference
 - name: Reference
@@ -36,12 +30,6 @@
    - name: Workflows
      href: reference/workflows.md

-# Concepts
- name: Concepts
-  items:
-    - name: What is SDD?
-      href: concepts/sdd.md
-
 # Development workflows
 - name: Development
  items:
@@ -50,12 +38,7 @@

 # Community
 - name: Community
-  href: community/overview.md
  items:
-    - name: Overview
-      href: community/overview.md
-    - name: Extensions
-      href: community/extensions.md
    - name: Presets
      href: community/presets.md
    - name: Walkthroughs
--- a/docs/upgrade.md
+++ b/docs/upgrade.md
@@ -19,12 +19,6 @@

 The CLI tool (`specify`) is separate from your project files. Upgrade it to get the latest features and bug fixes.

-Before upgrading, you can check whether a newer released version is available:
-
-```bash
-specify self check
-```
-
 ### If you installed with `uv tool install`

 Upgrade to a specific release (check [Releases](https://github.com/github/spec-kit/releases) for the latest tag):
@@ -41,8 +35,6 @@ Specify the desired release tag:
 uvx --from git+https://github.com/github/spec-kit.git@vX.Y.Z specify init --here --integration copilot
 ```

-`uvx` runs a temporary copy of Spec Kit for that single command. It does not update a persistent `specify` installed with `uv tool install`, `pipx`, or another tool manager. If a newer feature works through `uvx` but your local `specify` still reports an older version, upgrade the persistent CLI with the command that matches your install method.
-
 ### If you installed with `pipx`

 Upgrade to a specific release:
@@ -57,7 +49,7 @@ pipx install --force git+https://github.com/github/spec-kit.git@vX.Y.Z
 specify check
 ```

-This shows installed tools and confirms the CLI is working. Use `specify version` to confirm which persistent CLI version is currently on your `PATH`.
+This shows installed tools and confirms the CLI is working.

 ---

@@ -388,14 +380,6 @@ Only Spec Kit infrastructure files:

 ### "CLI upgrade doesn't seem to work"

-If a command behaves like an older Spec Kit version, first check for local CLI drift:
-
-```bash
-specify self check
-```
-
-`specify check` is an offline environment scan; `specify self check` is the CLI version lookup.
-
 Verify the installation:

 ```bash
--- a/extensions/README.md
+++ b/extensions/README.md
@@ -76,7 +76,7 @@ specify extension add <extension-name> --from https://github.com/org/spec-kit-ex

 🔍 **Browse and search community extensions on the [Community Extensions website](https://speckit-community.github.io/extensions/).**

-See the [Community Extensions](https://github.github.io/spec-kit/community/extensions.html) page for the full list of available community-contributed extensions.
+See the [Community Extensions](../README.md#-community-extensions) section in the main README for the full list of available community-contributed extensions.

 For the raw catalog data, see [`catalog.community.json`](catalog.community.json).

--- a/extensions/catalog.community.json
+++ b/extensions/catalog.community.json
@@ -1,6 +1,6 @@
 {
  "schema_version": "1.0",
-  "updated_at": "2026-05-28T00:00:00Z",
+  "updated_at": "2026-05-07T05:51:00Z",
  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.community.json",
  "extensions": {
    "aide": {
@@ -68,43 +68,6 @@
      "created_at": "2026-03-31T00:00:00Z",
      "updated_at": "2026-03-31T00:00:00Z"
    },
-    "agent-governance": {
-      "name": "Agent Governance",
-      "id": "agent-governance",
-      "description": "Generate agent-platform repository governance files from Spec Kit metadata.",
-      "author": "bigben",
-      "version": "1.2.0",
-      "download_url": "https://github.com/bigsmartben/spec-kit-agent-governance/archive/refs/tags/v1.2.0.zip",
-      "repository": "https://github.com/bigsmartben/spec-kit-agent-governance",
-      "homepage": "https://github.com/bigsmartben/spec-kit-agent-governance",
-      "documentation": "https://github.com/bigsmartben/spec-kit-agent-governance/blob/main/README.md",
-      "changelog": "https://github.com/bigsmartben/spec-kit-agent-governance/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.8.0",
-        "tools": [
-          {
-            "name": "uv",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 1,
-        "hooks": 3
-      },
-      "tags": [
-        "governance",
-        "agents",
-        "memory",
-        "context"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-14T00:00:00Z",
-      "updated_at": "2026-05-21T00:00:00Z"
-    },
    "agent-orchestrator": {
      "name": "Intelligent Agent Orchestrator",
      "id": "agent-orchestrator",
@@ -137,74 +100,6 @@
      "created_at": "2026-05-04T00:00:00Z",
      "updated_at": "2026-05-04T00:00:00Z"
    },
-    "api-evolve": {
-      "name": "API Evolve",
-      "id": "api-evolve",
-      "description": "Managed API contract evolution — breaking-change detection, semver enforcement, deprecation orchestration, and lifecycle gates across REST, GraphQL, and gRPC.",
-      "author": "Quratulain-bilal",
-      "version": "1.0.0",
-      "download_url": "https://github.com/Quratulain-bilal/spec-kit-api-evolve/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/Quratulain-bilal/spec-kit-api-evolve",
-      "homepage": "https://github.com/Quratulain-bilal/spec-kit-api-evolve",
-      "documentation": "https://github.com/Quratulain-bilal/spec-kit-api-evolve/blob/main/README.md",
-      "changelog": "https://github.com/Quratulain-bilal/spec-kit-api-evolve/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.4.0"
-      },
-      "provides": {
-        "commands": 12,
-        "hooks": 5
-      },
-      "tags": [
-        "api",
-        "contracts",
-        "versioning",
-        "openapi",
-        "graphql",
-        "grpc",
-        "deprecation",
-        "breaking-changes",
-        "semver",
-        "governance"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-07T00:00:00Z",
-      "updated_at": "2026-05-07T00:00:00Z"
-    },
-    "arch": {
-      "name": "Architecture Workflow",
-      "id": "arch",
-      "description": "Generate or reverse project-level 4+1 architecture view artifacts and synthesis",
-      "author": "bigsmartben",
-      "version": "1.1.0",
-      "download_url": "https://github.com/bigsmartben/spec-kit-arch/archive/refs/tags/v1.1.0.zip",
-      "repository": "https://github.com/bigsmartben/spec-kit-arch",
-      "homepage": "https://github.com/bigsmartben/spec-kit-arch",
-      "documentation": "https://github.com/bigsmartben/spec-kit-arch/blob/main/README.md",
-      "changelog": "https://github.com/bigsmartben/spec-kit-arch/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.8.10.dev0"
-      },
-      "provides": {
-        "commands": 2,
-        "hooks": 0
-      },
-      "tags": [
-        "architecture",
-        "4plus1",
-        "workflow",
-        "design"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-14T00:00:00Z",
-      "updated_at": "2026-05-15T00:00:00Z"
-    },
    "architect-preview": {
      "name": "Architect Impact Previewer",
      "id": "architect-preview",
@@ -240,10 +135,10 @@
    "architecture-guard": {
      "name": "Architecture Guard",
      "id": "architecture-guard",
-      "description": "Framework-agnostic architecture review extension for validating implementation against governance and architecture constitutions, detecting architectural drift, and generating non-blocking refactor tasks.",
+      "description": "Continuous architecture governance for AI-assisted development. Reviews specs, plans, and code for architecture drift, producing structured refactor tasks and evolution proposals.",
      "author": "DyanGalih",
-      "version": "1.8.9",
-      "download_url": "https://github.com/DyanGalih/spec-kit-architecture-guard/archive/refs/tags/v1.8.9.zip",
+      "version": "1.6.7",
+      "download_url": "https://github.com/DyanGalih/spec-kit-architecture-guard/archive/refs/tags/v1.6.7.zip",
      "repository": "https://github.com/DyanGalih/spec-kit-architecture-guard",
      "homepage": "https://github.com/DyanGalih/spec-kit-architecture-guard",
      "documentation": "https://github.com/DyanGalih/spec-kit-architecture-guard/blob/main/README.md",
@@ -253,23 +148,22 @@
        "speckit_version": ">=0.1.0"
      },
      "provides": {
-        "commands": 10,
-        "hooks": 3
+        "commands": 6,
+        "hooks": 0
      },
      "tags": [
        "architecture",
-        "spec-kit",
-        "review",
-        "refactor",
-        "workflow",
        "governance",
-        "guardrails"
+        "drift-detection",
+        "refactor",
+        "monolithic",
+        "microservices"
      ],
      "verified": false,
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-05-05T07:26:00Z",
-      "updated_at": "2026-05-27T00:00:00Z"
+      "updated_at": "2026-05-06T22:28:55Z"
    },
    "archive": {
      "name": "Archive Extension",
@@ -437,38 +331,6 @@
      "created_at": "2026-04-10T00:00:00Z",
      "updated_at": "2026-04-10T00:00:00Z"
    },
-    "brownkit": {
-      "name": "BrownKit \u2014 Brownfield Discovery for Spec-Kit",
-      "id": "brownkit",
-      "description": "Evidence-driven capability discovery, security and QA risk assessment for existing codebases.",
-      "author": "Maksim Shautsou",
-      "version": "1.0.1",
-      "download_url": "https://github.com/MaksimShevtsov/BrownKit/archive/refs/tags/v1.0.1.zip",
-      "repository": "https://github.com/MaksimShevtsov/BrownKit",
-      "homepage": "https://github.com/MaksimShevtsov/BrownKit",
-      "documentation": "https://github.com/MaksimShevtsov/BrownKit/blob/main/README.md",
-      "changelog": "https://github.com/MaksimShevtsov/BrownKit/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 10,
-        "hooks": 5
-      },
-      "tags": [
-        "brownfield",
-        "discovery",
-        "security",
-        "qa",
-        "capabilities"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-10T00:00:00Z",
-      "updated_at": "2026-05-10T00:00:00Z"
-    },
    "bugfix": {
      "name": "Bugfix Workflow",
      "id": "bugfix",
@@ -568,38 +430,6 @@
      "created_at": "2026-04-16T00:00:00Z",
      "updated_at": "2026-04-16T00:00:00Z"
    },
-    "changelog": {
-      "name": "Spec Changelog",
-      "id": "changelog",
-      "description": "Auto-generate changelogs and release notes from spec git history and requirement diffs.",
-      "author": "Quratulain-bilal",
-      "version": "1.0.0",
-      "download_url": "https://github.com/Quratulain-bilal/spec-kit-changelog/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/Quratulain-bilal/spec-kit-changelog",
-      "homepage": "https://github.com/Quratulain-bilal/spec-kit-changelog",
-      "documentation": "https://github.com/Quratulain-bilal/spec-kit-changelog/blob/main/README.md",
-      "changelog": "https://github.com/Quratulain-bilal/spec-kit-changelog/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.4.0"
-      },
-      "provides": {
-        "commands": 4,
-        "hooks": 1
-      },
-      "tags": [
-        "changelog",
-        "release-notes",
-        "documentation",
-        "git-history",
-        "notifications"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-04-11T18:00:00Z",
-      "updated_at": "2026-04-11T18:00:00Z"
-    },
    "ci-guard": {
      "name": "CI Guard",
      "id": "ci-guard",
@@ -1549,35 +1379,6 @@
      "created_at": "2026-04-28T00:00:00Z",
      "updated_at": "2026-04-28T00:00:00Z"
    },
-    "mde": {
-      "name": "MDE",
-      "id": "mde",
-      "description": "A Spec Kit extension that exposes a minimal model-driven engineering workflow with setup, next, and status commands.",
-      "author": "AI-MDE",
-      "version": "0.5.1",
-      "download_url": "https://github.com/AI-MDE/spec-kit-mde/archive/refs/tags/v0.5.1.zip",
-      "repository": "https://github.com/AI-MDE/spec-kit-mde",
-      "homepage": "https://github.com/AI-MDE/spec-kit-mde",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 4,
-        "hooks": 1
-      },
-      "tags": [
-        "mde",
-        "model-driven-engineering",
-        "workflow",
-        "process"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-08T00:00:00Z",
-      "updated_at": "2026-05-08T00:00:00Z"
-    },
    "memory-loader": {
      "name": "Memory Loader",
      "id": "memory-loader",
@@ -1614,8 +1415,8 @@
      "id": "memory-md",
      "description": "Spec Kit extension for repository-native Markdown memory that captures durable decisions, bugs, and project context",
      "author": "DyanGalih",
-      "version": "0.8.5",
-      "download_url": "https://github.com/DyanGalih/spec-kit-memory-hub/archive/refs/tags/v0.8.5.zip",
+      "version": "0.7.9",
+      "download_url": "https://github.com/DyanGalih/spec-kit-memory-hub/archive/refs/tags/v0.7.9.zip",
      "repository": "https://github.com/DyanGalih/spec-kit-memory-hub",
      "homepage": "https://github.com/DyanGalih/spec-kit-memory-hub",
      "documentation": "https://github.com/DyanGalih/spec-kit-memory-hub/blob/main/README.md",
@@ -1625,8 +1426,8 @@
        "speckit_version": ">=0.2.0"
      },
      "provides": {
-        "commands": 7,
-        "hooks": 2
+        "commands": 6,
+        "hooks": 0
      },
      "tags": [
        "memory",
@@ -1640,15 +1441,15 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-04-23T00:00:00Z",
-      "updated_at": "2026-05-11T14:58:00Z"
+      "updated_at": "2026-05-06T22:28:55Z"
    },
    "memorylint": {
      "name": "MemoryLint",
      "id": "memorylint",
      "description": "Agent memory governance tool: Automatically audits and fixes boundary conflicts between AGENTS.md and the constitution.",
      "author": "RbBtSn0w",
-      "version": "1.4.0",
-      "download_url": "https://github.com/RbBtSn0w/spec-kit-extensions/releases/download/memorylint-v1.4.0/memorylint.zip",
+      "version": "1.3.0",
+      "download_url": "https://github.com/RbBtSn0w/spec-kit-extensions/releases/download/memorylint-v1.3.0/memorylint.zip",
      "repository": "https://github.com/RbBtSn0w/spec-kit-extensions",
      "homepage": "https://github.com/RbBtSn0w/spec-kit-extensions/tree/main/memorylint",
      "documentation": "https://github.com/RbBtSn0w/spec-kit-extensions/blob/main/memorylint/README.md",
@@ -1658,8 +1459,8 @@
        "speckit_version": ">=0.5.1"
      },
      "provides": {
-        "commands": 2,
-        "hooks": 3
+        "commands": 1,
+        "hooks": 1
      },
      "tags": [
        "memory",
@@ -1672,7 +1473,7 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-04-09T00:00:00Z",
-      "updated_at": "2026-05-24T01:06:49Z"
+      "updated_at": "2026-04-16T13:10:26Z"
    },
    "multi-model-review": {
      "name": "Multi-Model Review",
@@ -1915,69 +1716,6 @@
      "created_at": "2026-03-18T00:00:00Z",
      "updated_at": "2026-03-18T00:00:00Z"
    },
-    "preview": {
-      "name": "Interactive HTML Preview",
-      "id": "preview",
-      "description": "Generate self-contained interactive HTML prototypes from Spec Kit artifacts",
-      "author": "bigsmartben",
-      "version": "1.0.0",
-      "download_url": "https://github.com/bigsmartben/spec-kit-preview/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/bigsmartben/spec-kit-preview",
-      "homepage": "https://github.com/bigsmartben/spec-kit-preview",
-      "documentation": "https://github.com/bigsmartben/spec-kit-preview/blob/main/README.md",
-      "changelog": "https://github.com/bigsmartben/spec-kit-preview/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.8.10.dev0"
-      },
-      "provides": {
-        "commands": 1,
-        "hooks": 0
-      },
-      "tags": [
-        "preview",
-        "prototype",
-        "html",
-        "ux"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-15T00:00:00Z",
-      "updated_at": "2026-05-15T00:00:00Z"
-    },
-    "product": {
-      "name": "Product Spec Extension",
-      "id": "product",
-      "description": "Generates PRFAQ, Lean PRD, stakeholder summaries, and technical designs from engineering specs.",
-      "author": "spec-kit-product contributors",
-      "version": "0.1.3",
-      "download_url": "https://github.com/d0whc3r/spec-kit-product/releases/download/v0.1.3/product-0.1.3.zip",
-      "repository": "https://github.com/d0whc3r/spec-kit-product",
-      "homepage": "https://github.com/d0whc3r/spec-kit-product",
-      "documentation": "https://github.com/d0whc3r/spec-kit-product/blob/main/README.md",
-      "changelog": "https://github.com/d0whc3r/spec-kit-product/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.2.0"
-      },
-      "provides": {
-        "commands": 4,
-        "hooks": 6
-      },
-      "tags": [
-        "product",
-        "spec",
-        "prd",
-        "design",
-        "documentation"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-26T00:00:00Z",
-      "updated_at": "2026-05-26T00:00:00Z"
-    },
    "product-forge": {
      "name": "Product Forge",
      "id": "product-forge",
@@ -2213,44 +1951,6 @@
      "created_at": "2026-03-23T13:30:00Z",
      "updated_at": "2026-03-23T13:30:00Z"
    },
-    "reqnroll-bdd": {
-      "name": "Reqnroll BDD",
-      "id": "reqnroll-bdd",
-      "description": "Adds Reqnroll BDD planning, Gherkin generation, traceability, safe task injection, handoff, and verification to Spec Kit.",
-      "author": "LoogaCY Studio",
-      "version": "1.0.0",
-      "download_url": "https://github.com/LoogacyStudio/spec-kit-reqnroll-bdd/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/LoogacyStudio/spec-kit-reqnroll-bdd",
-      "homepage": "https://github.com/LoogacyStudio/spec-kit-reqnroll-bdd",
-      "documentation": "https://github.com/LoogacyStudio/spec-kit-reqnroll-bdd#readme",
-      "changelog": "https://github.com/LoogacyStudio/spec-kit-reqnroll-bdd/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.8.0",
-        "tools": [
-          {
-            "name": "dotnet",
-            "required": false
-          }
-        ]
-      },
-      "provides": {
-        "commands": 4,
-        "hooks": 1
-      },
-      "tags": [
-        "bdd",
-        "reqnroll",
-        "dotnet",
-        "gherkin",
-        "acceptance-testing"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-13T00:00:00Z",
-      "updated_at": "2026-05-13T00:00:00Z"
-    },
    "retro": {
      "name": "Retro Extension",
      "id": "retro",
@@ -2379,38 +2079,6 @@
      "created_at": "2026-04-20T00:00:00Z",
      "updated_at": "2026-04-20T00:00:00Z"
    },
-    "schedule": {
-      "name": "Spec Kit Schedule — CP-SAT Agent Orchestrator",
-      "id": "schedule",
-      "description": "Optimal multi-agent task scheduling via CP-SAT solver with DAG precedence, hallucination-aware caps, file-conflict avoidance, stochastic durations, replanning, and interactive HTML output",
-      "author": "Julio César Franco Ardila",
-      "version": "0.6.2",
-      "download_url": "https://github.com/jfranc38/spec-kit-schedule/archive/refs/tags/v0.6.2.zip",
-      "repository": "https://github.com/jfranc38/spec-kit-schedule",
-      "homepage": "https://github.com/jfranc38/spec-kit-schedule",
-      "documentation": "https://github.com/jfranc38/spec-kit-schedule/blob/main/README.md",
-      "changelog": "https://github.com/jfranc38/spec-kit-schedule/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.4.0"
-      },
-      "provides": {
-        "commands": 5,
-        "hooks": 1
-      },
-      "tags": [
-        "scheduling",
-        "optimization",
-        "multi-agent",
-        "cp-sat",
-        "operations-research"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-06T22:35:00Z",
-      "updated_at": "2026-05-07T17:25:00Z"
-    },
    "scope": {
      "name": "Spec Scope",
      "id": "scope",
@@ -2449,8 +2117,8 @@
      "id": "security-review",
      "description": "Full-project secure-by-design security audits plus staged, branch/PR, plan, task, follow-up, and apply reviews",
      "author": "DyanGalih",
-      "version": "1.5.0",
-      "download_url": "https://github.com/DyanGalih/spec-kit-security-review/archive/refs/tags/v1.5.0.zip",
+      "version": "1.4.5",
+      "download_url": "https://github.com/DyanGalih/spec-kit-security-review/archive/refs/tags/v1.4.5.zip",
      "repository": "https://github.com/DyanGalih/spec-kit-security-review",
      "homepage": "https://github.com/DyanGalih/spec-kit-security-review",
      "documentation": "https://github.com/DyanGalih/spec-kit-security-review/blob/main/README.md",
@@ -2460,8 +2128,8 @@
        "speckit_version": ">=0.1.0"
      },
      "provides": {
-        "commands": 9,
-        "hooks": 3
+        "commands": 7,
+        "hooks": 0
      },
      "tags": [
        "security",
@@ -2474,7 +2142,7 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-04-03T03:24:03Z",
-      "updated_at": "2026-05-11T14:58:00Z"
+      "updated_at": "2026-05-06T22:28:55Z"
    },
    "sf": {
      "name": "SFSpeckit — Salesforce Spec-Driven Development",
@@ -2645,55 +2313,6 @@
      "created_at": "2026-04-30T00:00:00Z",
      "updated_at": "2026-04-30T00:00:00Z"
    },
-    "speckit-superpowers-bridge": {
-      "name": "Superpowers Implementation Bridge",
-      "id": "speckit-superpowers-bridge",
-      "description": "Thin orchestrator between Spec Kit (design) and Superpowers (implementation). Cross-agent.",
-      "author": "lihan3238",
-      "version": "0.7.0",
-      "download_url": "https://github.com/lihan3238/speckit-superpowers-bridge/releases/download/v0.7.0/speckit-superpowers-bridge-v0.7.0.zip",
-      "repository": "https://github.com/lihan3238/speckit-superpowers-bridge",
-      "homepage": "https://github.com/lihan3238/speckit-superpowers-bridge",
-      "documentation": "https://github.com/lihan3238/speckit-superpowers-bridge#readme",
-      "changelog": "https://github.com/lihan3238/speckit-superpowers-bridge/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.8.10",
-        "tools": [
-          {
-            "name": "powershell",
-            "version": ">=5.1",
-            "required": false
-          },
-          {
-            "name": "bash",
-            "version": ">=4.0",
-            "required": false
-          },
-          {
-            "name": "jq",
-            "version": ">=1.6",
-            "required": false
-          }
-        ]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 5
-      },
-      "tags": [
-        "bridge",
-        "superpowers",
-        "cross-agent",
-        "tdd",
-        "workflow"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-15T00:00:00Z",
-      "updated_at": "2026-05-28T00:00:00Z"
-    },
    "speckit-utils": {
      "name": "SDD Utilities",
      "id": "speckit-utils",
@@ -2762,21 +2381,21 @@
    "squad": {
      "name": "Squad Bridge",
      "id": "squad",
-      "description": "Bootstrap and synchronize a Squad agent team from your Speckit spec and tasks.",
+      "description": "Bootstrap and synchronize a Squad agent team from your Spec Kit spec and tasks.",
      "author": "jwill824",
-      "version": "1.3.0",
-      "download_url": "https://github.com/jwill824/spec-kit-squad/archive/refs/tags/v1.3.0.zip",
+      "version": "1.1.0",
+      "download_url": "https://github.com/jwill824/spec-kit-squad/archive/refs/tags/v1.1.0.zip",
      "repository": "https://github.com/jwill824/spec-kit-squad",
      "homepage": "https://github.com/jwill824/spec-kit-squad",
      "documentation": "https://github.com/jwill824/spec-kit-squad/blob/main/README.md",
      "changelog": "https://github.com/jwill824/spec-kit-squad/blob/main/docs/CHANGELOG.md",
      "license": "MIT",
      "requires": {
-        "speckit_version": ">=0.8.11",
+        "speckit_version": ">=0.1.0",
        "tools": [
          {
            "name": "@bradygaster/squad-cli",
-            "version": ">=0.9.4",
+            "version": ">=0.1.0",
            "required": true
          }
        ]
@@ -2796,7 +2415,7 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-04-29T00:00:00Z",
-      "updated_at": "2026-05-20T00:00:00Z"
+      "updated_at": "2026-04-29T00:00:00Z"
    },
    "staff-review": {
      "name": "Staff Review Extension",
@@ -2895,8 +2514,8 @@
      "id": "superb",
      "description": "Orchestrates obra/superpowers skills within the spec-kit SDD workflow. Thin bridge commands delegate to superpowers' authoritative SKILL.md files at runtime (with graceful fallback), while bridge-original commands provide spec-kit-native value. Eight commands cover the full lifecycle: intent clarification, TDD enforcement, task review, verification, critique, systematic debugging, branch completion, and review response. Hook-bound commands fire automatically; standalone commands are invoked when needed.",
      "author": "rbbtsn0w",
-      "version": "1.4.0",
-      "download_url": "https://github.com/RbBtSn0w/spec-kit-extensions/releases/download/superpowers-bridge-v1.4.0/superpowers-bridge.zip",
+      "version": "1.3.0",
+      "download_url": "https://github.com/RbBtSn0w/spec-kit-extensions/releases/download/superpowers-bridge-v1.3.0/superpowers-bridge.zip",
      "repository": "https://github.com/RbBtSn0w/spec-kit-extensions",
      "homepage": "https://github.com/RbBtSn0w/spec-kit-extensions",
      "documentation": "https://github.com/RbBtSn0w/spec-kit-extensions/blob/main/superpowers-bridge/README.md",
@@ -2914,7 +2533,7 @@
      },
      "provides": {
        "commands": 8,
-        "hooks": 3
+        "hooks": 4
      },
      "tags": [
        "methodology",
@@ -2931,7 +2550,7 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-03-30T00:00:00Z",
-      "updated_at": "2026-05-24T01:07:34Z"
+      "updated_at": "2026-04-16T14:08:23Z"
    },
    "superpowers-bridge": {
      "name": "Superpowers Bridge",
@@ -2998,74 +2617,6 @@
      "created_at": "2026-03-02T00:00:00Z",
      "updated_at": "2026-03-02T00:00:00Z"
    },
-    "team-assign": {
-      "name": "Team Assign",
-      "id": "team-assign",
-      "description": "Assign tasks.md items to human engineers, split into subtasks, and generate a per-engineer workboard",
-      "author": "tarunkumarbhati",
-      "version": "1.0.0",
-      "download_url": "https://github.com/tarunkumarbhati/spec-kit-team-assign/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/tarunkumarbhati/spec-kit-team-assign",
-      "homepage": "https://github.com/tarunkumarbhati/spec-kit-team-assign",
-      "documentation": "https://github.com/tarunkumarbhati/spec-kit-team-assign/blob/main/README.md",
-      "changelog": "https://github.com/tarunkumarbhati/spec-kit-team-assign/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 3
-      },
-      "tags": [
-        "team",
-        "assignment",
-        "process",
-        "planning",
-        "subtasks"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-20T00:00:00Z",
-      "updated_at": "2026-05-20T00:00:00Z"
-    },
-    "time-machine": {
-      "name": "Time Machine",
-      "id": "time-machine",
-      "description": "Retroactively apply the full SDD workflow to existing codebases — analyse, spec, and ship feature-by-feature",
-      "author": "te3yo",
-      "version": "1.1.0",
-      "download_url": "https://github.com/teeyo/spec-kit-time-machine/archive/refs/tags/v1.1.0.zip",
-      "repository": "https://github.com/teeyo/spec-kit-time-machine",
-      "homepage": "https://github.com/teeyo/spec-kit-time-machine",
-      "documentation": "https://github.com/teeyo/spec-kit-time-machine",
-      "changelog": "https://github.com/teeyo/spec-kit-time-machine/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          {
-            "name": "git",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 1
-      },
-      "tags": [
-        "brownfield",
-        "automation",
-        "workflow",
-        "process"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-15T00:00:00Z",
-      "updated_at": "2026-05-15T00:00:00Z"
-    },
    "tinyspec": {
      "name": "TinySpec",
      "id": "tinyspec",
@@ -3161,48 +2712,6 @@
      "created_at": "2026-05-01T00:00:00Z",
      "updated_at": "2026-05-01T00:00:00Z"
    },
-    "token-budget": {
-      "name": "Token Budget",
-      "id": "token-budget",
-      "description": "Reduces LLM token consumption in Spec Kit workflows: compact artifacts in-place, scope per-phase reading, suppress prose padding, and report token usage.",
-      "author": "Tine Kondo",
-      "version": "1.0.1",
-      "download_url": "https://github.com/tinesoft/spec-kit-token-budget/archive/refs/tags/v1.0.1.zip",
-      "repository": "https://github.com/tinesoft/spec-kit-token-budget",
-      "homepage": "https://github.com/tinesoft/spec-kit-token-budget",
-      "documentation": "https://github.com/tinesoft/spec-kit-token-budget/blob/main/README.md",
-      "changelog": "https://github.com/tinesoft/spec-kit-token-budget/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          {
-            "name": "python3",
-            "required": false
-          },
-          {
-            "name": "rtk",
-            "required": false
-          }
-        ]
-      },
-      "provides": {
-        "commands": 4,
-        "hooks": 6
-      },
-      "tags": [
-        "tokens",
-        "budget",
-        "context",
-        "efficiency",
-        "cost-optimization"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-05-26T00:00:00Z",
-      "updated_at": "2026-05-26T00:00:00Z"
-    },
    "v-model": {
      "name": "V-Model Extension Pack",
      "id": "v-model",
--- a/extensions/git/commands/speckit.git.initialize.md
+++ b/extensions/git/commands/speckit.git.initialize.md
@@ -35,7 +35,7 @@ Replace the script to add project-specific Git initialization steps:
 ## Output

 On success:
- `[OK] Git repository initialized`
+- `✓ Git repository initialized`

 ## Graceful Degradation

--- a/extensions/git/scripts/powershell/auto-commit.ps1
+++ b/extensions/git/scripts/powershell/auto-commit.ps1
@@ -115,7 +115,7 @@ if (Test-Path $configFile) {
        }
    }
 } else {
-    # No config file -- auto-commit disabled by default
+    # No config file — auto-commit disabled by default
    exit 0
 }

--- a/extensions/git/scripts/powershell/git-common.ps1
+++ b/extensions/git/scripts/powershell/git-common.ps1
@@ -1,6 +1,6 @@
 #!/usr/bin/env pwsh
 # Git-specific common functions for the git extension.
-# Extracted from scripts/powershell/common.ps1 -- contains only git-specific
+# Extracted from scripts/powershell/common.ps1 — contains only git-specific
 # branch validation and detection logic.

 function Test-HasGit {
--- a/extensions/git/scripts/powershell/initialize-repo.ps1
+++ b/extensions/git/scripts/powershell/initialize-repo.ps1
@@ -1,7 +1,7 @@
 #!/usr/bin/env pwsh
 # Git extension: initialize-repo.ps1
 # Initialize a Git repository with an initial commit.
-# Customizable -- replace this script to add .gitignore templates,
+# Customizable — replace this script to add .gitignore templates,
 # default branch config, git-flow, LFS, signing, etc.
 $ErrorActionPreference = 'Stop'

@@ -66,4 +66,4 @@ try {
    exit 1
 }

-Write-Host "[OK] Git repository initialized"
+Write-Host "✓ Git repository initialized"
--- a/integrations/catalog.json
+++ b/integrations/catalog.json
@@ -272,15 +272,6 @@
      "author": "spec-kit-core",
      "repository": "https://github.com/github/spec-kit",
      "tags": ["cli"]
-    },
-    "hermes": {
-      "id": "hermes",
-      "name": "Hermes Agent",
-      "version": "1.0.0",
-      "description": "Hermes Agent skills-based integration by Nous Research",
-      "author": "spec-kit-core",
-      "repository": "https://github.com/github/spec-kit",
-      "tags": ["cli", "skills"]
    }
  }
 }
--- a/presets/catalog.community.json
+++ b/presets/catalog.community.json
@@ -1,6 +1,6 @@
 {
  "schema_version": "1.0",
-  "updated_at": "2026-05-27T00:00:00Z",
+  "updated_at": "2026-05-05T10:00:00Z",
  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/presets/catalog.community.json",
  "presets": {
    "a11y-governance": {
@@ -222,11 +222,11 @@
    "fiction-book-writing": {
      "name": "Fiction Book Writing",
      "id": "fiction-book-writing",
-      "version": "1.8.1",
-      "description": "Spec-Driven Development for novel and long-form fiction. 33 AI commands from idea to submission: story bible governance, 9 POV modes, all major plot structure frameworks, scene-by-scene drafting with quality gates, audiobook pipeline (SSML/ElevenLabs), cover design, sensitivity review, pacing and prose statistics, and pandoc-based export to DOCX/EPUB/LaTeX. Two style modes: author voice sample extraction or humanized-AI prose with 5 craft profiles. 12 languages supported. Support for offline semantic search.",
+      "version": "1.7.0",
+      "description": "Spec-Driven Development for novel and long-form fiction. 27 AI commands from idea to submission: story bible governance, 9 POV modes, all major plot structure frameworks, scene-by-scene drafting with quality gates, audiobook pipeline (SSML/ElevenLabs), cover design, sensitivity review, pacing and prose statistics, and pandoc-based export to DOCX/EPUB/LaTeX. Two style modes: author voice sample extraction or humanized-AI prose with 5 craft profiles. 12 languages supported. Support for offline semantic search.",
      "author": "Andreas Daumann",
      "repository": "https://github.com/adaumann/speckit-preset-fiction-book-writing",
-      "download_url": "https://github.com/adaumann/speckit-preset-fiction-book-writing/archive/refs/tags/v1.8.1.zip",
+      "download_url": "https://github.com/adaumann/speckit-preset-fiction-book-writing/archive/refs/tags/v1.7.0.zip",
      "homepage": "https://github.com/adaumann/speckit-preset-fiction-book-writing",
      "documentation": "https://github.com/adaumann/speckit-preset-fiction-book-writing/blob/main/fiction-book-writing/README.md",
      "license": "MIT",
@@ -234,8 +234,8 @@
        "speckit_version": ">=0.5.0"
      },
      "provides": {
-        "templates": 25,
-        "commands": 33,
+        "templates": 22,
+        "commands": 27,
        "scripts": 2
      },
      "tags": [
@@ -254,44 +254,7 @@
        "language-support"
      ],
      "created_at": "2026-04-09T08:00:00Z",
-      "updated_at": "2026-05-24T08:00:00Z"
-    },
-    "game-narrative-writing": {
-      "name": "Game Narrative Writing",
-      "id": "game-narrative-writing",
-      "version": "1.0.0",
-      "description": "Spec-Driven Development for interactive game-narrative pre-production in video games. Authors write in a portable generic format, Twine/Sugarcube (.twee) or Ink (.ink). Covers choice-IF, visual novels, and branching dialogue. Supports Tier 1 mechanic hooks (flag, counter, inventory, timer, trust, currency, npc_state, ending_condition), multi-ending design, series carry-over variable registry, and NPC-focused character architecture.",
-      "author": "Andreas Daumann",
-      "repository": "https://github.com/adaumann/speckit-preset-game-narrative-writing",
-      "download_url": "https://github.com/adaumann/speckit-preset-game-narrative-writing/archive/refs/tags/v1.0.0.zip",
-      "homepage": "https://github.com/adaumann/speckit-preset-game-narrative-writing",
-      "documentation": "https://github.com/adaumann/speckit-preset-game-narrative-writing/blob/main/game-narrative-writing/README.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.5.0"
-      },
-      "provides": {
-        "templates": 22,
-        "commands": 36,
-        "scripts": 2
-      },
-      "tags": [
-        "game-writing",
-        "interactive-fiction",
-        "twine",
-        "ink",
-        "renpy",
-        "point-and-click",
-        "branching-narrative",
-        "choice-if",
-        "visual-novel",
-        "mechanic-hooks",
-        "game-narrative",
-        "export",
-        "series"
-      ],
-      "created_at": "2026-05-05T08:00:00Z",
-      "updated_at": "2026-05-05T08:00:00Z"
+      "updated_at": "2026-04-27T08:00:00Z"
    },
    "isaqb-architecture-governance": {
      "name": "iSAQB Architecture Governance",
@@ -348,37 +311,6 @@
      "created_at": "2026-04-15T00:00:00Z",
      "updated_at": "2026-04-15T00:00:00Z"
    },
-    "mde": {
-      "name": "Model Driven Engineering",
-      "id": "mde",
-      "version": "0.5.1",
-      "description": "Focuses on streamlined commands, app repository support, cross-spec support, and capability-aware project memory for model-driven engineering workflows.",
-      "author": "Ralph Hanna",
-      "repository": "https://github.com/AI-MDE/spec-kit-preset-mde",
-      "download_url": "https://github.com/AI-MDE/spec-kit-preset-mde/archive/refs/tags/v0.5.1.zip",
-      "homepage": "https://github.com/AI-MDE/spec-kit-preset-mde",
-      "documentation": "https://github.com/AI-MDE/spec-kit-preset-mde/blob/main/README.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "extensions": [
-          "mde"
-        ]
-      },
-      "provides": {
-        "templates": 6,
-        "commands": 11
-      },
-      "tags": [
-        "model-driven-engineering",
-        "software-lifecycle",
-        "business-analysis",
-        "business-application",
-        "multi-layered-architecture"
-      ],
-      "created_at": "2026-05-08T00:00:00Z",
-      "updated_at": "2026-05-08T00:00:00Z"
-    },
    "multi-repo-branching": {
      "name": "Multi-Repo Branching",
      "id": "multi-repo-branching",
@@ -472,11 +404,11 @@
    "security-governance": {
      "name": "Security Governance",
      "id": "security-governance",
-      "version": "0.4.0",
-      "description": "Adds memory-safe-language preference, language-specific secure coding profiles, ASVS verification, SBOM/AI-SBOM supply-chain transparency, and EU Cyber Resilience Act awareness.",
+      "version": "0.2.0",
+      "description": "Adds secure development governance, MSL preference, ASVS verification, supply-chain transparency, and EU CRA awareness.",
      "author": "Thorsten Hindermann",
      "repository": "https://github.com/hindermath/spec-kit-preset-security-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-security-governance/archive/refs/tags/v0.4.0.zip",
+      "download_url": "https://github.com/hindermath/spec-kit-preset-security-governance/archive/refs/tags/v0.2.0.zip",
      "homepage": "https://github.com/hindermath/spec-kit-preset-security-governance",
      "documentation": "https://github.com/hindermath/spec-kit-preset-security-governance/blob/main/README.md",
      "license": "MIT",
@@ -491,28 +423,11 @@
        "security",
        "governance",
        "msl",
-        "ssdf",
        "asvs",
-        "supply-chain",
-        "sbom",
-        "ai-sbom",
-        "vex",
-        "slsa",
-        "cwe-top-25",
-        "secure-coding",
-        "rust",
-        "go",
-        "swift",
-        "java",
-        "kotlin",
-        "python",
-        "typescript",
-        "g7",
-        "bsi",
-        "cra"
+        "supply-chain"
      ],
      "created_at": "2026-04-27T00:00:00Z",
-      "updated_at": "2026-05-26T00:00:00Z"
+      "updated_at": "2026-04-27T00:00:00Z"
    },
    "spec2cloud": {
      "name": "Spec2Cloud",
@@ -589,34 +504,6 @@
        "clarify",
        "interactive"
      ]
-    },
-    "workflow-preset": {
-      "name": "Workflow Preset",
-      "id": "workflow-preset",
-      "version": "1.2.0",
-      "description": "Behavior-first specification, design artifacts, and agent-native handoff orchestration.",
-      "author": "bigsmartben",
-      "repository": "https://github.com/bigsmartben/spec-kit-workflow-preset",
-      "download_url": "https://github.com/bigsmartben/spec-kit-workflow-preset/archive/refs/tags/v1.2.0.zip",
-      "homepage": "https://github.com/bigsmartben/spec-kit-workflow-preset",
-      "documentation": "https://github.com/bigsmartben/spec-kit-workflow-preset/blob/main/README.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.8.10.dev0"
-      },
-      "provides": {
-        "templates": 23,
-        "commands": 7
-      },
-      "tags": [
-        "behavior",
-        "bdd",
-        "planning",
-        "implementation",
-        "handoff"
-      ],
-      "created_at": "2026-05-27T00:00:00Z",
-      "updated_at": "2026-05-27T00:00:00Z"
    }
  }
 }
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,6 +1,6 @@
 [project]
 name = "specify-cli"
-version = "0.8.17"
+version = "0.8.7"
 description = "Specify CLI, part of GitHub Spec Kit. A tool to bootstrap your projects for Spec-Driven Development (SDD)."
 requires-python = ">=3.11"
 dependencies = [
--- a/scripts/bash/check-prerequisites.sh
+++ b/scripts/bash/check-prerequisites.sh
@@ -78,12 +78,13 @@ done
 SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 source "$SCRIPT_DIR/common.sh"

-# Get feature paths
+# Get feature paths and validate branch
 _paths_output=$(get_feature_paths) || { echo "ERROR: Failed to resolve feature paths" >&2; exit 1; }
 eval "$_paths_output"
 unset _paths_output
+check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1

-# If paths-only mode, output paths and exit (no validation)
+# If paths-only mode, output paths and exit (support JSON + paths-only combined)
 if $PATHS_ONLY; then
    if $JSON_MODE; then
        # Minimal JSON paths payload (no validation performed)
@@ -111,26 +112,23 @@ if $PATHS_ONLY; then
    exit 0
 fi

-# Validate branch name
-check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
-
 # Validate required directories and files
 if [[ ! -d "$FEATURE_DIR" ]]; then
    echo "ERROR: Feature directory not found: $FEATURE_DIR" >&2
-    echo "Run __SPECKIT_COMMAND_SPECIFY__ first to create the feature structure." >&2
+    echo "Run /speckit.specify first to create the feature structure." >&2
    exit 1
 fi

 if [[ ! -f "$IMPL_PLAN" ]]; then
    echo "ERROR: plan.md not found in $FEATURE_DIR" >&2
-    echo "Run __SPECKIT_COMMAND_PLAN__ first to create the implementation plan." >&2
+    echo "Run /speckit.plan first to create the implementation plan." >&2
    exit 1
 fi

 # Check for tasks.md if required
 if $REQUIRE_TASKS && [[ ! -f "$TASKS" ]]; then
    echo "ERROR: tasks.md not found in $FEATURE_DIR" >&2
-    echo "Run __SPECKIT_COMMAND_TASKS__ first to create the task list." >&2
+    echo "Run /speckit.tasks first to create the task list." >&2
    exit 1
 fi

--- a/scripts/bash/common.sh
+++ b/scripts/bash/common.sh
@@ -186,7 +186,7 @@ read_feature_json_feature_directory() {
 }

 # Returns 0 when .specify/feature.json lists feature_directory that exists as a directory
-# and matches the resolved active FEATURE_DIR (so __SPECKIT_COMMAND_PLAN__ can skip git branch pattern checks).
+# and matches the resolved active FEATURE_DIR (so /speckit.plan can skip git branch pattern checks).
 # Delegates parsing to read_feature_json_feature_directory, which is safe under `set -e`.
 feature_json_matches_feature_dir() {
    local repo_root="$1"
@@ -262,7 +262,7 @@ get_feature_paths() {

    # Resolve feature directory.  Priority:
    #   1. SPECIFY_FEATURE_DIRECTORY env var (explicit override)
-    #   2. .specify/feature.json "feature_directory" key (persisted by __SPECKIT_COMMAND_SPECIFY__)
+    #   2. .specify/feature.json "feature_directory" key (persisted by /speckit.specify)
    #   3. Branch-name-based prefix lookup (legacy fallback)
    local feature_dir
    if [[ -n "${SPECIFY_FEATURE_DIRECTORY:-}" ]]; then
@@ -642,3 +642,4 @@ except Exception:
    printf '%s' "$content"
    return 0
 }
+
--- a/scripts/bash/setup-plan.sh
+++ b/scripts/bash/setup-plan.sh
@@ -40,31 +40,15 @@ fi
 # Ensure the feature directory exists
 mkdir -p "$FEATURE_DIR"

-# Copy plan template if plan doesn't already exist
-if [[ -f "$IMPL_PLAN" ]]; then
-    if $JSON_MODE; then
-        echo "Plan already exists at $IMPL_PLAN, skipping template copy" >&2
-    else
-        echo "Plan already exists at $IMPL_PLAN, skipping template copy"
-    fi
+# Copy plan template if it exists
+TEMPLATE=$(resolve_template "plan-template" "$REPO_ROOT") || true
+if [[ -n "$TEMPLATE" ]] && [[ -f "$TEMPLATE" ]]; then
+    cp "$TEMPLATE" "$IMPL_PLAN"
+    echo "Copied plan template to $IMPL_PLAN"
 else
-    TEMPLATE=$(resolve_template "plan-template" "$REPO_ROOT") || true
-    if [[ -n "$TEMPLATE" ]] && [[ -f "$TEMPLATE" ]]; then
-        cp "$TEMPLATE" "$IMPL_PLAN"
-        if $JSON_MODE; then
-            echo "Copied plan template to $IMPL_PLAN" >&2
-        else
-            echo "Copied plan template to $IMPL_PLAN"
-        fi
-    else
-        if $JSON_MODE; then
-            echo "Warning: Plan template not found" >&2
-        else
-            echo "Warning: Plan template not found"
-        fi
-        # Create a basic plan file if template doesn't exist
-        touch "$IMPL_PLAN"
-    fi
+    echo "Warning: Plan template not found"
+    # Create a basic plan file if template doesn't exist
+    touch "$IMPL_PLAN"
 fi

 # Output results
--- a/scripts/bash/setup-tasks.sh
+++ b/scripts/bash/setup-tasks.sh
@@ -35,13 +35,13 @@ fi

 if [[ ! -f "$IMPL_PLAN" ]]; then
    echo "ERROR: plan.md not found in $FEATURE_DIR" >&2
-    echo "Run __SPECKIT_COMMAND_PLAN__ first to create the implementation plan." >&2
+    echo "Run /speckit.plan first to create the implementation plan." >&2
    exit 1
 fi

 if [[ ! -f "$FEATURE_SPEC" ]]; then
    echo "ERROR: spec.md not found in $FEATURE_DIR" >&2
-    echo "Run __SPECKIT_COMMAND_SPECIFY__ first to create the feature structure." >&2
+    echo "Run /speckit.specify first to create the feature structure." >&2
    exit 1
 fi

--- a/scripts/powershell/check-prerequisites.ps1
+++ b/scripts/powershell/check-prerequisites.ps1
@@ -56,10 +56,14 @@ EXAMPLES:
 # Source common functions
 . "$PSScriptRoot/common.ps1"

-# Get feature paths
+# Get feature paths and validate branch
 $paths = Get-FeaturePathsEnv

-# If paths-only mode, output paths and exit (no validation)
+if (-not (Test-FeatureBranch -Branch $paths.CURRENT_BRANCH -HasGit:$paths.HAS_GIT)) { 
+    exit 1 
+}
+
+# If paths-only mode, output paths and exit (support combined -Json -PathsOnly)
 if ($PathsOnly) {
    if ($Json) {
        [PSCustomObject]@{
@@ -81,28 +85,23 @@ if ($PathsOnly) {
    exit 0
 }

-# Validate branch name
-if (-not (Test-FeatureBranch -Branch $paths.CURRENT_BRANCH -HasGit:$paths.HAS_GIT)) {
-    exit 1
-}
-
 # Validate required directories and files
 if (-not (Test-Path $paths.FEATURE_DIR -PathType Container)) {
    Write-Output "ERROR: Feature directory not found: $($paths.FEATURE_DIR)"
-    Write-Output "Run __SPECKIT_COMMAND_SPECIFY__ first to create the feature structure."
+    Write-Output "Run /speckit.specify first to create the feature structure."
    exit 1
 }

 if (-not (Test-Path $paths.IMPL_PLAN -PathType Leaf)) {
    Write-Output "ERROR: plan.md not found in $($paths.FEATURE_DIR)"
-    Write-Output "Run __SPECKIT_COMMAND_PLAN__ first to create the implementation plan."
+    Write-Output "Run /speckit.plan first to create the implementation plan."
    exit 1
 }

 # Check for tasks.md if required
 if ($RequireTasks -and -not (Test-Path $paths.TASKS -PathType Leaf)) {
    Write-Output "ERROR: tasks.md not found in $($paths.FEATURE_DIR)"
-    Write-Output "Run __SPECKIT_COMMAND_TASKS__ first to create the task list."
+    Write-Output "Run /speckit.tasks first to create the task list."
    exit 1
 }

--- a/scripts/powershell/common.ps1
+++ b/scripts/powershell/common.ps1
@@ -165,7 +165,7 @@ function Test-FeatureBranch {
 }

 # True when .specify/feature.json pins an existing feature directory that matches the
-# active FEATURE_DIR from Get-FeaturePathsEnv (so __SPECKIT_COMMAND_PLAN__ can skip git branch pattern checks).
+# active FEATURE_DIR from Get-FeaturePathsEnv (so /speckit.plan can skip git branch pattern checks).
 function Test-FeatureJsonMatchesFeatureDir {
    param(
        [Parameter(Mandatory = $true)][string]$RepoRoot,
@@ -288,7 +288,7 @@ function Get-FeaturePathsEnv {

    # Resolve feature directory.  Priority:
    #   1. SPECIFY_FEATURE_DIRECTORY env var (explicit override)
-    #   2. .specify/feature.json "feature_directory" key (persisted by __SPECKIT_COMMAND_SPECIFY__)
+    #   2. .specify/feature.json "feature_directory" key (persisted by /speckit.specify)
    #   3. Branch-name-based prefix lookup (same as scripts/bash/common.sh)
    $featureJson = Join-Path $repoRoot '.specify/feature.json'
    if ($env:SPECIFY_FEATURE_DIRECTORY) {
@@ -336,10 +336,10 @@ function Get-FeaturePathsEnv {
 function Test-FileExists {
    param([string]$Path, [string]$Description)
    if (Test-Path -Path $Path -PathType Leaf) {
-        Write-Output "  [OK] $Description"
+        Write-Output "  ✓ $Description"
        return $true
    } else {
-        Write-Output "  [FAIL] $Description"
+        Write-Output "  ✗ $Description"
        return $false
    }
 }
@@ -347,10 +347,10 @@ function Test-FileExists {
 function Test-DirHasFiles {
    param([string]$Path, [string]$Description)
    if ((Test-Path -Path $Path -PathType Container) -and (Get-ChildItem -Path $Path -ErrorAction SilentlyContinue | Where-Object { -not $_.PSIsContainer } | Select-Object -First 1)) {
-        Write-Output "  [OK] $Description"
+        Write-Output "  ✓ $Description"
        return $true
    } else {
-        Write-Output "  [FAIL] $Description"
+        Write-Output "  ✗ $Description"
        return $false
    }
 }
@@ -591,7 +591,7 @@ except Exception:

    if ($layerPaths.Count -eq 0) { return $null }

-    # If the top (highest-priority) layer is replace, it wins entirely --
+    # If the top (highest-priority) layer is replace, it wins entirely —
    # lower layers are irrelevant regardless of their strategies.
    if ($layerStrategies[0] -eq 'replace') {
        return (Get-Content $layerPaths[0] -Raw)
@@ -640,4 +640,4 @@ except Exception:
    }

    return $content
-}
+}
--- a/scripts/powershell/create-new-feature.ps1
+++ b/scripts/powershell/create-new-feature.ps1
@@ -312,7 +312,7 @@ if (-not $DryRun) {
                if ($AllowExistingBranch) {
                    # If we're already on the branch, continue without another checkout.
                    if ($currentBranch -eq $branchName) {
-                        # Already on the target branch -- nothing to do
+                        # Already on the target branch — nothing to do
                    } else {
                        # Otherwise switch to the existing branch instead of failing.
                        $switchBranchError = git checkout -q $branchName 2>&1 | Out-String
@@ -350,10 +350,7 @@ if (-not $DryRun) {
    if (-not (Test-Path -PathType Leaf $specFile)) {
        $template = Resolve-Template -TemplateName 'spec-template' -RepoRoot $repoRoot
        if ($template -and (Test-Path $template)) {
-            # Read the template content and write it to the spec file with UTF-8 encoding without BOM
-            $content = [System.IO.File]::ReadAllText($template)
-            $utf8NoBom = New-Object System.Text.UTF8Encoding($false)
-            [System.IO.File]::WriteAllText($specFile, $content, $utf8NoBom)
+            Copy-Item $template $specFile -Force
        } else {
            New-Item -ItemType File -Path $specFile -Force | Out-Null
        }
--- a/scripts/powershell/setup-plan.ps1
+++ b/scripts/powershell/setup-plan.ps1
@@ -33,25 +33,15 @@ if (-not (Test-FeatureJsonMatchesFeatureDir -RepoRoot $paths.REPO_ROOT -ActiveFe
 # Ensure the feature directory exists
 New-Item -ItemType Directory -Path $paths.FEATURE_DIR -Force | Out-Null

-# Copy plan template if plan doesn't already exist
-if (Test-Path $paths.IMPL_PLAN -PathType Leaf) {
-    if ($Json) {
-        [Console]::Error.WriteLine("Plan already exists at $($paths.IMPL_PLAN), skipping template copy")
-    } else {
-        Write-Output "Plan already exists at $($paths.IMPL_PLAN), skipping template copy"
-    }
+# Copy plan template if it exists, otherwise note it or create empty file
+$template = Resolve-Template -TemplateName 'plan-template' -RepoRoot $paths.REPO_ROOT
+if ($template -and (Test-Path $template)) { 
+    Copy-Item $template $paths.IMPL_PLAN -Force
+    Write-Output "Copied plan template to $($paths.IMPL_PLAN)"
 } else {
-    $template = Resolve-Template -TemplateName 'plan-template' -RepoRoot $paths.REPO_ROOT
-    if ($template -and (Test-Path $template)) {
-        # Read the template content and write it to the implementation plan file with UTF-8 encoding without BOM
-        $content = [System.IO.File]::ReadAllText($template)
-        $utf8NoBom = New-Object System.Text.UTF8Encoding($false)
-        [System.IO.File]::WriteAllText($paths.IMPL_PLAN, $content, $utf8NoBom)
-    } else {
-        Write-Warning "Plan template not found"
-        # Create a basic plan file if template doesn't exist
-        New-Item -ItemType File -Path $paths.IMPL_PLAN -Force | Out-Null
-    }
+    Write-Warning "Plan template not found"
+    # Create a basic plan file if template doesn't exist
+    New-Item -ItemType File -Path $paths.IMPL_PLAN -Force | Out-Null
 }

 # Output results
--- a/scripts/powershell/setup-tasks.ps1
+++ b/scripts/powershell/setup-tasks.ps1
@@ -28,13 +28,13 @@ if (-not (Test-FeatureJsonMatchesFeatureDir -RepoRoot $paths.REPO_ROOT -ActiveFe

 if (-not (Test-Path $paths.IMPL_PLAN -PathType Leaf)) {
    [Console]::Error.WriteLine("ERROR: plan.md not found in $($paths.FEATURE_DIR)")
-    [Console]::Error.WriteLine("Run __SPECKIT_COMMAND_PLAN__ first to create the implementation plan.")
+    [Console]::Error.WriteLine("Run /speckit.plan first to create the implementation plan.")
    exit 1
 }

 if (-not (Test-Path $paths.FEATURE_SPEC -PathType Leaf)) {
    [Console]::Error.WriteLine("ERROR: spec.md not found in $($paths.FEATURE_DIR)")
-    [Console]::Error.WriteLine("Run __SPECKIT_COMMAND_SPECIFY__ first to create the feature structure.")
+    [Console]::Error.WriteLine("Run /speckit.specify first to create the feature structure.")
    exit 1
 }

--- a/src/specify_cli/init.py
+++ b/src/specify_cli/init.py
--- a/src/specify_cli/_agent_config.py
+++ b/src/specify_cli/_agent_config.py
@@ -1,45 +0,0 @@
-"""Agent configuration constants derived from the integration registry."""
-from __future__ import annotations
-
-from typing import Any
-
-
-def _build_agent_config() -> dict[str, dict[str, Any]]:
-    from .integrations import INTEGRATION_REGISTRY
-    config: dict[str, dict[str, Any]] = {}
-    for key, integration in INTEGRATION_REGISTRY.items():
-        if integration.config:
-            config[key] = dict(integration.config)
-    return config
-
-
-AGENT_CONFIG: dict[str, dict[str, Any]] = _build_agent_config()
-
-DEFAULT_INIT_INTEGRATION = "copilot"
-
-AI_ASSISTANT_ALIASES: dict[str, str] = {
-    "kiro": "kiro-cli",
-}
-
-
-def _build_ai_assistant_help() -> str:
-    non_generic_agents = sorted(agent for agent in AGENT_CONFIG if agent != "generic")
-    base_help = (
-        f"AI assistant to use: {', '.join(non_generic_agents)}, "
-        "or generic (requires --ai-commands-dir)."
-    )
-    if not AI_ASSISTANT_ALIASES:
-        return base_help
-    alias_phrases = []
-    for alias, target in sorted(AI_ASSISTANT_ALIASES.items()):
-        alias_phrases.append(f"'{alias}' as an alias for '{target}'")
-    if len(alias_phrases) == 1:
-        aliases_text = alias_phrases[0]
-    else:
-        aliases_text = ", ".join(alias_phrases[:-1]) + " and " + alias_phrases[-1]
-    return base_help + " Use " + aliases_text + "."
-
-
-AI_ASSISTANT_HELP: str = _build_ai_assistant_help()
-
-SCRIPT_TYPE_CHOICES: dict[str, str] = {"sh": "POSIX Shell (bash/zsh)", "ps": "PowerShell"}
--- a/src/specify_cli/_assets.py
+++ b/src/specify_cli/_assets.py
@@ -1,121 +0,0 @@
-"""Bundle path resolution and version lookup for specify_cli.
-
-Stdlib-only; zero internal imports so it sits at the base of the dependency
-graph without risk of circular imports.
-"""
-from __future__ import annotations
-
-import importlib.metadata
-import re
-from pathlib import Path
-
-
-def _locate_core_pack() -> Path | None:
-    """Return the filesystem path to the bundled core_pack directory, or None.
-
-    Only present in wheel installs: hatchling's force-include copies
-    templates/, scripts/ etc. into specify_cli/core_pack/ at build time.
-
-    Source-checkout and editable installs do NOT have this directory.
-    Callers that need to work in both environments must check the repo-root
-    trees (templates/, scripts/) as a fallback when this returns None.
-    """
-    # Wheel install: core_pack is a sibling directory of this file
-    candidate = Path(__file__).parent / "core_pack"
-    if candidate.is_dir():
-        return candidate
-    return None
-
-
-def _repo_root() -> Path:
-    """Return the source checkout root used for editable installs."""
-    return Path(__file__).parent.parent.parent
-
-
-def _locate_bundled_extension(extension_id: str) -> Path | None:
-    """Return the path to a bundled extension, or None.
-
-    Checks the wheel's core_pack first, then falls back to the
-    source-checkout ``extensions/<id>/`` directory.
-    """
-    if not re.match(r'^[a-z0-9-]+$', extension_id):
-        return None
-
-    core = _locate_core_pack()
-    if core is not None:
-        candidate = core / "extensions" / extension_id
-        if (candidate / "extension.yml").is_file():
-            return candidate
-
-    # Source-checkout / editable install: look relative to repo root
-    candidate = _repo_root() / "extensions" / extension_id
-    if (candidate / "extension.yml").is_file():
-        return candidate
-
-    return None
-
-
-def _locate_bundled_workflow(workflow_id: str) -> Path | None:
-    """Return the path to a bundled workflow directory, or None.
-
-    Checks the wheel's core_pack first, then falls back to the
-    source-checkout ``workflows/<id>/`` directory.
-    """
-    if not re.match(r'^[a-z0-9](?:[a-z0-9-]*[a-z0-9])?$', workflow_id):
-        return None
-
-    core = _locate_core_pack()
-    if core is not None:
-        candidate = core / "workflows" / workflow_id
-        if (candidate / "workflow.yml").is_file():
-            return candidate
-
-    # Source-checkout / editable install: look relative to repo root
-    candidate = _repo_root() / "workflows" / workflow_id
-    if (candidate / "workflow.yml").is_file():
-        return candidate
-
-    return None
-
-
-def _locate_bundled_preset(preset_id: str) -> Path | None:
-    """Return the path to a bundled preset, or None.
-
-    Checks the wheel's core_pack first, then falls back to the
-    source-checkout ``presets/<id>/`` directory.
-    """
-    if not re.match(r'^[a-z0-9-]+$', preset_id):
-        return None
-
-    core = _locate_core_pack()
-    if core is not None:
-        candidate = core / "presets" / preset_id
-        if (candidate / "preset.yml").is_file():
-            return candidate
-
-    # Source-checkout / editable install: look relative to repo root
-    candidate = _repo_root() / "presets" / preset_id
-    if (candidate / "preset.yml").is_file():
-        return candidate
-
-    return None
-
-
-def get_speckit_version() -> str:
-    """Get current spec-kit version."""
-    try:
-        return importlib.metadata.version("specify-cli")
-    except Exception:
-        # Fallback: try reading from pyproject.toml
-        try:
-            import tomllib
-            pyproject_path = _repo_root() / "pyproject.toml"
-            if pyproject_path.exists():
-                with open(pyproject_path, "rb") as f:
-                    data = tomllib.load(f)
-                    return data.get("project", {}).get("version", "unknown")
-        except Exception:
-            # Intentionally ignore any errors while reading/parsing pyproject.toml.
-            # If this lookup fails for any reason, we fall back to returning "unknown" below.
-            pass
-    return "unknown"
--- a/src/specify_cli/_console.py
+++ b/src/specify_cli/_console.py
@@ -1,245 +0,0 @@
-"""Base Rich/Typer console layer for the specify CLI.
-
-This module is the single source of Rich ``Console`` instances and Typer UI
-helpers used throughout ``specify_cli``.  Nothing in this file should import
-from other ``specify_cli`` sub-modules; all dependencies must flow *into* this
-layer, not out of it, to avoid circular imports.
-"""
-from __future__ import annotations
-
-from collections.abc import Callable
-
-import readchar
-import typer
-from rich.align import Align
-from rich.console import Console
-from rich.live import Live
-from rich.panel import Panel
-from rich.table import Table
-from rich.text import Text
-from rich.tree import Tree
-from typer.core import TyperGroup
-
-BANNER = """
-███████╗██████╗ ███████╗ ██████╗██╗███████╗██╗   ██╗
-██╔════╝██╔══██╗██╔════╝██╔════╝██║██╔════╝╚██╗ ██╔╝
-███████╗██████╔╝█████╗  ██║     ██║█████╗   ╚████╔╝
-╚════██║██╔═══╝ ██╔══╝  ██║     ██║██╔══╝    ╚██╔╝
-███████║██║     ███████╗╚██████╗██║██║        ██║
-╚══════╝╚═╝     ╚══════╝ ╚═════╝╚═╝╚═╝        ╚═╝
-"""
-
-TAGLINE = "GitHub Spec Kit - Spec-Driven Development Toolkit"
-
-console = Console(highlight=False)
-
-class StepTracker:
-    """Track and render hierarchical steps without emojis, similar to Claude Code tree output.
-    Supports live auto-refresh via an attached refresh callback.
-    """
-    def __init__(self, title: str):
-        self.title = title
-        self.steps = []  # list of dicts: {key, label, status, detail}
-        self.status_order = {"pending": 0, "running": 1, "done": 2, "error": 3, "skipped": 4}
-        self._refresh_cb: Callable[[], None] | None = None
-
-    def attach_refresh(self, cb: Callable[[], None]) -> None:
-        self._refresh_cb = cb
-
-    def add(self, key: str, label: str):
-        if key not in [s["key"] for s in self.steps]:
-            self.steps.append({"key": key, "label": label, "status": "pending", "detail": ""})
-            self._maybe_refresh()
-
-    def start(self, key: str, detail: str = ""):
-        self._update(key, status="running", detail=detail)
-
-    def complete(self, key: str, detail: str = ""):
-        self._update(key, status="done", detail=detail)
-
-    def error(self, key: str, detail: str = ""):
-        self._update(key, status="error", detail=detail)
-
-    def skip(self, key: str, detail: str = ""):
-        self._update(key, status="skipped", detail=detail)
-
-    def _update(self, key: str, status: str, detail: str):
-        for s in self.steps:
-            if s["key"] == key:
-                s["status"] = status
-                if detail:
-                    s["detail"] = detail
-                self._maybe_refresh()
-                return
-
-        self.steps.append({"key": key, "label": key, "status": status, "detail": detail})
-        self._maybe_refresh()
-
-    def _maybe_refresh(self):
-        if self._refresh_cb:
-            try:
-                self._refresh_cb()
-            except Exception:
-                pass
-
-    def render(self):
-        tree = Tree(f"[cyan]{self.title}[/cyan]", guide_style="grey50")
-        for step in self.steps:
-            label = step["label"]
-            detail_text = step["detail"].strip() if step["detail"] else ""
-
-            status = step["status"]
-            if status == "done":
-                symbol = "[green]●[/green]"
-            elif status == "pending":
-                symbol = "[green dim]○[/green dim]"
-            elif status == "running":
-                symbol = "[cyan]○[/cyan]"
-            elif status == "error":
-                symbol = "[red]●[/red]"
-            elif status == "skipped":
-                symbol = "[yellow]○[/yellow]"
-            else:
-                symbol = " "
-
-            if status == "pending":
-                # Entire line light gray (pending)
-                if detail_text:
-                    line = f"{symbol} [bright_black]{label} ({detail_text})[/bright_black]"
-                else:
-                    line = f"{symbol} [bright_black]{label}[/bright_black]"
-            else:
-                # Label white, detail (if any) light gray in parentheses
-                if detail_text:
-                    line = f"{symbol} [white]{label}[/white] [bright_black]({detail_text})[/bright_black]"
-                else:
-                    line = f"{symbol} [white]{label}[/white]"
-
-            tree.add(line)
-        return tree
-
-
-def get_key():
-    """Get a single keypress in a cross-platform way using readchar."""
-    key = readchar.readkey()
-
-    if key == readchar.key.UP or key == readchar.key.CTRL_P:
-        return 'up'
-    if key == readchar.key.DOWN or key == readchar.key.CTRL_N:
-        return 'down'
-
-    if key == readchar.key.ENTER:
-        return 'enter'
-
-    if key == readchar.key.ESC:
-        return 'escape'
-
-    if key == readchar.key.CTRL_C:
-        raise KeyboardInterrupt
-
-    return key
-
-def select_with_arrows(
-    options: dict[str, str],
-    prompt_text: str = "Select an option",
-    default_key: str | None = None,
-) -> str:
-    """
-    Interactive selection using arrow keys with Rich Live display.
-
-    Args:
-        options: Dict with keys as option keys and values as descriptions
-        prompt_text: Text to show above the options
-        default_key: Default option key to start with
-
-    Returns:
-        Selected option key
-    """
-    if not options:
-        raise ValueError("select_with_arrows() requires at least one option.")
-
-    option_keys = list(options.keys())
-    if default_key and default_key in option_keys:
-        selected_index = option_keys.index(default_key)
-    else:
-        selected_index = 0
-
-    selected_key = None
-
-    def create_selection_panel():
-        """Create the selection panel with current selection highlighted."""
-        table = Table.grid(padding=(0, 2))
-        table.add_column(style="cyan", justify="left", width=3)
-        table.add_column(style="white", justify="left")
-
-        for i, key in enumerate(option_keys):
-            if i == selected_index:
-                table.add_row("▶", f"[cyan]{key}[/cyan] [dim]({options[key]})[/dim]")
-            else:
-                table.add_row(" ", f"[cyan]{key}[/cyan] [dim]({options[key]})[/dim]")
-
-        table.add_row("", "")
-        table.add_row("", "[dim]Use ↑/↓ to navigate, Enter to select, Esc to cancel[/dim]")
-
-        return Panel(
-            table,
-            title=f"[bold]{prompt_text}[/bold]",
-            border_style="cyan",
-            padding=(1, 2)
-        )
-
-    console.print()
-
-    def run_selection_loop():
-        nonlocal selected_key, selected_index
-        with Live(create_selection_panel(), console=console, transient=True, auto_refresh=False) as live:
-            while True:
-                try:
-                    key = get_key()
-                    if key == 'up':
-                        selected_index = (selected_index - 1) % len(option_keys)
-                    elif key == 'down':
-                        selected_index = (selected_index + 1) % len(option_keys)
-                    elif key == 'enter':
-                        selected_key = option_keys[selected_index]
-                        break
-                    elif key == 'escape':
-                        console.print("\n[yellow]Selection cancelled[/yellow]")
-                        raise typer.Exit(code=1)
-
-                    live.update(create_selection_panel(), refresh=True)
-
-                except KeyboardInterrupt:
-                    console.print("\n[yellow]Selection cancelled[/yellow]")
-                    raise typer.Exit(code=1)
-
-    run_selection_loop()
-
-    if selected_key is None:
-        console.print("\n[red]Selection failed.[/red]")
-        raise typer.Exit(code=1)
-
-    return selected_key
-
-class BannerGroup(TyperGroup):
-    """Custom group that shows banner before help."""
-
-    def format_help(self, ctx, formatter):
-        # Show banner before help
-        show_banner()
-        super().format_help(ctx, formatter)
-
-
-def show_banner():
-    """Display the ASCII art banner."""
-    banner_lines = BANNER.strip().split('\n')
-    colors = ["bright_blue", "blue", "cyan", "bright_cyan", "white", "bright_white"]
-
-    styled_banner = Text()
-    for i, line in enumerate(banner_lines):
-        color = colors[i % len(colors)]
-        styled_banner.append(line + "\n", style=color)
-
-    console.print(Align.center(styled_banner))
-    console.print(Align.center(Text(TAGLINE, style="italic bright_yellow")))
-    console.print()
--- a/src/specify_cli/_utils.py
+++ b/src/specify_cli/_utils.py
@@ -1,282 +0,0 @@
-"""System utilities: subprocess, tool detection, file operations."""
-from __future__ import annotations
-
-import json
-import json5
-import os
-import shutil
-import stat
-import subprocess
-import tempfile
-from pathlib import Path
-from typing import Any
-from ._console import console
-
-CLAUDE_LOCAL_PATH = Path.home() / ".claude" / "local" / "claude"
-CLAUDE_NPM_LOCAL_PATH = Path.home() / ".claude" / "local" / "node_modules" / ".bin" / "claude"
-
-
-def run_command(cmd: list[str], check_return: bool = True, capture: bool = False, shell: bool = False) -> str | None:
-    """Run a shell command and optionally capture output."""
-    try:
-        if capture:
-            result = subprocess.run(cmd, check=check_return, capture_output=True, text=True, shell=shell)
-            return result.stdout.strip()
-        else:
-            subprocess.run(cmd, check=check_return, shell=shell)
-            return None
-    except subprocess.CalledProcessError as e:
-        if check_return:
-            console.print(f"[red]Error running command:[/red] {' '.join(cmd)}")
-            console.print(f"[red]Exit code:[/red] {e.returncode}")
-            if hasattr(e, 'stderr') and e.stderr:
-                console.print(f"[red]Error output:[/red] {e.stderr}")
-            raise
-        return None
-
-
-def check_tool(tool: str, tracker=None) -> bool:
-    """Check if a tool is installed. Optionally update tracker.
-
-    Args:
-        tool: Name of the tool to check
-        tracker: StepTracker | None to update with results
-
-    Returns:
-        True if tool is found, False otherwise
-    """
-    # Special handling for Claude CLI local installs
-    # See: https://github.com/github/spec-kit/issues/123
-    # See: https://github.com/github/spec-kit/issues/550
-    # Claude Code can be installed in two local paths:
-    #   1. ~/.claude/local/claude          (after `claude migrate-installer`)
-    #   2. ~/.claude/local/node_modules/.bin/claude  (npm-local install, e.g. via nvm)
-    # Neither path may be on the system PATH, so we check them explicitly.
-    if tool == "claude":
-        if CLAUDE_LOCAL_PATH.is_file() or CLAUDE_NPM_LOCAL_PATH.is_file():
-            if tracker:
-                tracker.complete(tool, "available")
-            return True
-
-    if tool == "kiro-cli":
-        # Kiro currently supports both executable names. Prefer kiro-cli and
-        # accept kiro as a compatibility fallback.
-        found = shutil.which("kiro-cli") is not None or shutil.which("kiro") is not None
-    else:
-        found = shutil.which(tool) is not None
-
-    if tracker:
-        if found:
-            tracker.complete(tool, "available")
-        else:
-            tracker.error(tool, "not found")
-
-    return found
-
-
-def is_git_repo(path: Path | None = None) -> bool:
-    """Check if the specified path is inside a git repository."""
-    if path is None:
-        path = Path.cwd()
-
-    if not path.is_dir():
-        return False
-
-    try:
-        subprocess.run(
-            ["git", "rev-parse", "--is-inside-work-tree"],
-            check=True,
-            capture_output=True,
-            cwd=path,
-        )
-        return True
-    except (subprocess.CalledProcessError, FileNotFoundError):
-        return False
-
-
-def init_git_repo(project_path: Path, quiet: bool = False) -> tuple[bool, str | None]:
-    """Initialize a git repository in the specified path."""
-    try:
-        original_cwd = Path.cwd()
-        os.chdir(project_path)
-        if not quiet:
-            console.print("[cyan]Initializing git repository...[/cyan]")
-        subprocess.run(["git", "init"], check=True, capture_output=True, text=True)
-        subprocess.run(["git", "add", "."], check=True, capture_output=True, text=True)
-        subprocess.run(["git", "commit", "-m", "Initial commit from Specify template"], check=True, capture_output=True, text=True)
-        if not quiet:
-            console.print("[green]✓[/green] Git repository initialized")
-        return True, None
-    except subprocess.CalledProcessError as e:
-        error_msg = f"Command: {' '.join(e.cmd)}\nExit code: {e.returncode}"
-        if e.stderr:
-            error_msg += f"\nError: {e.stderr.strip()}"
-        elif e.stdout:
-            error_msg += f"\nOutput: {e.stdout.strip()}"
-        if not quiet:
-            console.print(f"[red]Error initializing git repository:[/red] {e}")
-        return False, error_msg
-    finally:
-        os.chdir(original_cwd)
-
-
-def handle_vscode_settings(sub_item, dest_file, rel_path, verbose=False, tracker=None) -> None:
-    """Handle merging or copying of .vscode/settings.json files.
-
-    Note: when merge produces changes, rewritten output is normalized JSON and
-    existing JSONC comments/trailing commas are not preserved.
-    """
-    def log(message, color="green"):
-        if verbose and not tracker:
-            console.print(f"[{color}]{message}[/] {rel_path}")
-
-    def atomic_write_json(target_file: Path, payload: dict[str, Any]) -> None:
-        """Atomically write JSON while preserving existing mode bits when possible."""
-        temp_path: Path | None = None
-        try:
-            with tempfile.NamedTemporaryFile(
-                mode='w',
-                encoding='utf-8',
-                dir=target_file.parent,
-                prefix=f"{target_file.name}.",
-                suffix=".tmp",
-                delete=False,
-            ) as f:
-                temp_path = Path(f.name)
-                json.dump(payload, f, indent=4)
-                f.write('\n')
-
-            if target_file.exists():
-                try:
-                    existing_stat = target_file.stat()
-                    os.chmod(temp_path, stat.S_IMODE(existing_stat.st_mode))
-                    if hasattr(os, "chown"):
-                        try:
-                            os.chown(temp_path, existing_stat.st_uid, existing_stat.st_gid)
-                        except PermissionError:
-                            # Best-effort owner/group preservation without requiring elevated privileges.
-                            pass
-                except OSError:
-                    # Best-effort metadata preservation; data safety is prioritized.
-                    pass
-
-            os.replace(temp_path, target_file)
-        except Exception:
-            if temp_path and temp_path.exists():
-                temp_path.unlink()
-            raise
-
-    try:
-        with open(sub_item, 'r', encoding='utf-8') as f:
-            # json5 natively supports comments and trailing commas (JSONC)
-            new_settings = json5.load(f)
-
-        if dest_file.exists():
-            merged = merge_json_files(dest_file, new_settings, verbose=verbose and not tracker)
-            if merged is not None:
-                atomic_write_json(dest_file, merged)
-                log("Merged:", "green")
-                log("Note: comments/trailing commas are normalized when rewritten", "yellow")
-            else:
-                log("Skipped merge (preserved existing settings)", "yellow")
-        else:
-            shutil.copy2(sub_item, dest_file)
-            log("Copied (no existing settings.json):", "blue")
-
-    except Exception as e:
-        log(f"Warning: Could not merge settings: {e}", "yellow")
-        if not dest_file.exists():
-            shutil.copy2(sub_item, dest_file)
-
-
-def merge_json_files(existing_path: Path, new_content: Any, verbose: bool = False) -> dict[str, Any] | None:
-    """Merge new JSON content into existing JSON file.
-
-    Performs a polite deep merge where:
-    - New keys are added
-    - Existing keys are preserved (not overwritten) unless both values are dictionaries
-    - Nested dictionaries are merged recursively only when both sides are dictionaries
-    - Lists and other values are preserved from base if they exist
-
-    Args:
-        existing_path: Path to existing JSON file
-        new_content: New JSON content to merge in
-        verbose: Whether to print merge details
-
-    Returns:
-        Merged JSON content as dict, or None if the existing file should be left untouched.
-    """
-    # Load existing content first to have a safe fallback
-    existing_content = None
-    exists = existing_path.exists()
-
-    if exists:
-        try:
-            with open(existing_path, 'r', encoding='utf-8') as f:
-                # Handle comments (JSONC) natively with json5
-                # Note: json5 handles BOM automatically
-                existing_content = json5.load(f)
-        except FileNotFoundError:
-            # Handle race condition where file is deleted after exists() check
-            exists = False
-        except Exception as e:
-            if verbose:
-                console.print(f"[yellow]Warning: Could not read or parse existing JSON in {existing_path.name} ({e}).[/yellow]")
-            # Skip merge to preserve existing file if unparseable or inaccessible (e.g. PermissionError)
-            return None
-
-    # Validate template content
-    if not isinstance(new_content, dict):
-        if verbose:
-            console.print(f"[yellow]Warning: Template content for {existing_path.name} is not a dictionary. Preserving existing settings.[/yellow]")
-        return None
-
-    if not exists:
-        return new_content
-
-    # If existing content parsed but is not a dict, skip merge to avoid data loss
-    if not isinstance(existing_content, dict):
-        if verbose:
-            console.print(f"[yellow]Warning: Existing JSON in {existing_path.name} is not an object. Skipping merge to avoid data loss.[/yellow]")
-        return None
-
-    def deep_merge_polite(base: dict[str, Any], update: dict[str, Any]) -> dict[str, Any]:
-        """Recursively merge update dict into base dict, preserving base values."""
-        result = base.copy()
-        for key, value in update.items():
-            if key not in result:
-                # Add new key
-                result[key] = value
-            elif isinstance(result[key], dict) and isinstance(value, dict):
-                # Recursively merge nested dictionaries
-                result[key] = deep_merge_polite(result[key], value)
-            else:
-                # Key already exists and values are not both dicts; preserve existing value.
-                # This ensures user settings aren't overwritten by template defaults.
-                pass
-        return result
-
-    merged = deep_merge_polite(existing_content, new_content)
-
-    # Detect if anything actually changed. If not, return None so the caller
-    # can skip rewriting the file (preserving user's comments/formatting).
-    if merged == existing_content:
-        return None
-
-    if verbose:
-        console.print(f"[cyan]Merged JSON file:[/cyan] {existing_path.name}")
-
-    return merged
-
-
-def _display_project_path(project_root: Path, path: str | Path) -> str:
-    """Return a stable POSIX-style display path for paths under a project."""
-    path_obj = Path(path)
-    try:
-        rel_path = path_obj.relative_to(project_root) if path_obj.is_absolute() else path_obj
-    except ValueError:
-        try:
-            rel_path = path_obj.resolve().relative_to(project_root.resolve())
-        except (OSError, ValueError):
-            return path_obj.as_posix()
-    return rel_path.as_posix()
--- a/src/specify_cli/_version.py
+++ b/src/specify_cli/_version.py
@@ -1,173 +0,0 @@
-"""Version checking and self-update commands for specify_cli.
-
-Pure helpers for comparing PEP 440 versions and fetching the latest GitHub
-release tag.  The ``self_app`` Typer sub-command group is co-located here so
-all version-related logic lives in one place.
-
-Dependencies: stdlib + packaging + ._console only (no other internal imports
-at module level, keeping this layer thin and circular-import-safe).
-"""
-from __future__ import annotations
-
-import json
-import urllib.error
-
-import typer
-from packaging.version import InvalidVersion, Version
-
-from ._console import console
-
-GITHUB_API_LATEST = "https://api.github.com/repos/github/spec-kit/releases/latest"
-
-
-def _get_installed_version() -> str:
-    """Return the installed specify-cli distribution version or 'unknown'.
-
-    Uses importlib.metadata so the value reflects what was actually installed
-    by pip/uv/pipx — not a value read from pyproject.toml. This is
-    intentional for `specify self check`, which should reason about the
-    installed distribution rather than a source-tree fallback. Callers must
-    treat the sentinel string 'unknown' as an indeterminate value (see FR-020).
-    """
-    import importlib.metadata
-
-    metadata_errors = [importlib.metadata.PackageNotFoundError]
-    invalid_metadata_error = getattr(importlib.metadata, "InvalidMetadataError", None)
-    if invalid_metadata_error is not None:
-        metadata_errors.append(invalid_metadata_error)
-
-    try:
-        return importlib.metadata.version("specify-cli")
-    except tuple(metadata_errors):
-        return "unknown"
-
-
-def _normalize_tag(tag: str) -> str:
-    """Strip exactly one leading 'v' from a release tag.
-
-    Returns the rest of the string unchanged. This handles the common
-    'vX.Y.Z' tag convention in this repo; it MUST NOT strip more
-    aggressively (e.g., two leading 'v's keeps one).
-    """
-    return tag[1:] if tag.startswith("v") else tag
-
-
-def _is_newer(latest: str, current: str) -> bool:
-    """Return True iff `latest` is strictly greater than `current` under PEP 440.
-
-    Returns False whenever either side is 'unknown' or fails to parse; this
-    keeps the comparison indeterminate (rather than crashing or falsely
-    recommending a downgrade) on edge inputs.
-    """
-    if latest == "unknown" or current == "unknown":
-        return False
-    try:
-        return Version(latest) > Version(current)
-    except InvalidVersion:
-        return False
-
-
-def _fetch_latest_release_tag() -> tuple[str | None, str | None]:
-    """Return (tag, failure_category). Exactly one outbound call, 5 s timeout.
-
-    On success: (tag_name, None).
-    On a documented network/HTTP failure (added in T029/T030): (None, category).
-    On anything else — including a malformed response body — the exception
-    propagates; there is no catch-all (research D-006).
-    """
-    from .authentication.http import open_url
-
-    try:
-        with open_url(
-            GITHUB_API_LATEST,
-            timeout=5,
-            extra_headers={"Accept": "application/vnd.github+json"},
-        ) as resp:
-            payload = json.loads(resp.read().decode("utf-8"))
-            tag = payload.get("tag_name")
-            if not isinstance(tag, str) or not tag:
-                raise ValueError("GitHub API response missing valid tag_name")
-            return tag, None
-    except urllib.error.HTTPError as e:
-        # Order matters: HTTPError is a subclass of URLError.
-        if e.code == 403:
-            return None, (
-                "rate limited (configure ~/.specify/auth.json with a GitHub token)"
-            )
-        return None, f"HTTP {e.code}"
-    except (urllib.error.URLError, OSError):
-        return None, "offline or timeout"
-
-
-# ===== Self Commands =====
-
-self_app = typer.Typer(
-    name="self",
-    help="Manage the specify CLI itself (read-only check and reserved upgrade command).",
-    add_completion=False,
-)
-
-
-@self_app.command("check")
-def self_check() -> None:
-    """Check whether a newer specify-cli release is available. Read-only.
-
-    This command only checks for updates; it does not modify your installation.
-    The reserved (and currently non-destructive) `specify self upgrade` command
-    is the name that a future release will use for actual self-upgrade — its
-    behavior is not implemented in this release and is intentionally out of
-    scope here. See `specify self upgrade --help` for its current status.
-    """
-    installed = _get_installed_version()
-    tag, failure_reason = _fetch_latest_release_tag()
-
-    if tag is None:
-        # Graceful-failure path (FR-008). `failure_reason` is one of the
-        # enumerated strings produced by _fetch_latest_release_tag() — it
-        # never contains a URL, headers, response body, or traceback.
-        assert failure_reason is not None
-        console.print(f"Installed: {installed}")
-        console.print(f"[yellow]Could not check latest release:[/yellow] {failure_reason}")
-        return
-
-    latest_normalized = _normalize_tag(tag)
-
-    if installed == "unknown":
-        # FR-020: surface the latest release and the recovery action even
-        # when the local distribution metadata is unavailable.
-        console.print("Current version could not be determined.")
-        console.print(f"Latest release: {latest_normalized}")
-        console.print("\nTo reinstall:")
-        console.print("  uv tool install specify-cli --force \\")
-        console.print(f"    --from git+https://github.com/github/spec-kit.git@{tag}")
-        return
-
-    if _is_newer(latest_normalized, installed):
-        console.print(f"[green]Update available:[/green] {installed} → {latest_normalized}")
-        console.print("\nTo upgrade:")
-        console.print("  uv tool install specify-cli --force \\")
-        console.print(f"    --from git+https://github.com/github/spec-kit.git@{tag}")
-        return
-
-    # Installed is parseable AND is >= latest → "up to date" (FR-006).
-    # Also reached when the tag is unparseable (InvalidVersion) → _is_newer
-    # returns False, and the up-to-date branch is the safer default per
-    # FR-004 / test T016.
-    console.print(f"[green]Up to date:[/green] {installed}")
-
-
-@self_app.command("upgrade")
-def self_upgrade() -> None:
-    """Reserved command surface for self-upgrade; not implemented in this release.
-
-    This command is a documented non-destructive stub in this release: it
-    performs no outbound network request, no install-method detection, and
-    invokes no installer. It prints a three-line guidance message and exits 0.
-    Actual self-upgrade is planned as follow-up work.
-
-    Use `specify self check` today to see whether a newer release is available
-    and to get a copy-pasteable reinstall command.
-    """
-    console.print("specify self upgrade is not implemented yet.")
-    console.print("Run 'specify self check' to see whether a newer release is available.")
-    console.print("Actual self-upgrade is planned as follow-up work.")
--- a/src/specify_cli/agents.py
+++ b/src/specify_cli/agents.py
@@ -438,8 +438,6 @@ class CommandRegistrar:
        source_dir: Path,
        project_root: Path,
        context_note: str = None,
-        _resolved_dir: Path = None,
-        link_outputs: bool = False,
    ) -> List[str]:
        """Register commands for a specific agent.

@@ -450,13 +448,6 @@ class CommandRegistrar:
            source_dir: Directory containing command source files
            project_root: Path to project root
            context_note: Custom context comment for markdown output
-            _resolved_dir: Pre-resolved command directory (internal use
-                only — avoids a second ``_resolve_agent_dir`` call and
-                duplicate deprecation warnings when invoked from
-                ``register_commands_for_all_agents``).
-            link_outputs: If True, write rendered output to a source-local
-                dev cache and symlink the agent command file to it. Falls back
-                to a normal file write when symlinks are unavailable.

        Returns:
            List of registered command names
@@ -469,9 +460,7 @@ class CommandRegistrar:
            raise ValueError(f"Unsupported agent: {agent_name}")

        agent_config = self.AGENT_CONFIGS[agent_name]
-        commands_dir = _resolved_dir or self._resolve_agent_dir(
-            agent_name, agent_config, project_root,
-        )
+        commands_dir = project_root / agent_config["dir"]
        commands_dir.mkdir(parents=True, exist_ok=True)

        registered = []
@@ -563,15 +552,7 @@ class CommandRegistrar:
            dest_file = commands_dir / f"{output_name}{agent_config['extension']}"
            self._ensure_inside(dest_file, commands_dir)
            dest_file.parent.mkdir(parents=True, exist_ok=True)
-            self._write_registered_output(
-                dest_file,
-                output,
-                source_dir,
-                agent_name,
-                output_name,
-                agent_config["extension"],
-                link_outputs,
-            )
+            dest_file.write_text(output, encoding="utf-8")

            if agent_name == "copilot":
                self.write_copilot_prompt(project_root, cmd_name)
@@ -637,56 +618,13 @@ class CommandRegistrar:
                )
                self._ensure_inside(alias_file, commands_dir)
                alias_file.parent.mkdir(parents=True, exist_ok=True)
-                self._write_registered_output(
-                    alias_file,
-                    alias_output,
-                    source_dir,
-                    agent_name,
-                    alias_output_name,
-                    agent_config["extension"],
-                    link_outputs,
-                )
+                alias_file.write_text(alias_output, encoding="utf-8")
                if agent_name == "copilot":
                    self.write_copilot_prompt(project_root, alias)
                registered.append(alias)

        return registered

-    @staticmethod
-    def _write_registered_output(
-        dest_file: Path,
-        content: str,
-        source_dir: Path,
-        agent_name: str,
-        output_name: str,
-        extension: str,
-        link_outputs: bool,
-    ) -> None:
-        """Write a rendered agent artifact, optionally as a dev-mode symlink."""
-        if not link_outputs:
-            dest_file.write_text(content, encoding="utf-8")
-            return
-
-        rel_output = Path(f"{output_name}{extension}")
-        cache_root = source_dir / ".specify-dev" / "agent-commands" / agent_name
-        cache_file = cache_root / rel_output
-        CommandRegistrar._ensure_inside(cache_file, cache_root)
-
-        try:
-            cache_file.parent.mkdir(parents=True, exist_ok=True)
-            cache_file.write_text(content, encoding="utf-8")
-            if dest_file.exists() or dest_file.is_symlink():
-                dest_file.unlink()
-            target = os.path.relpath(cache_file, dest_file.parent)
-            os.symlink(target, dest_file)
-        except (OSError, ValueError):
-            # Windows often requires Developer Mode or admin privileges for
-            # symlinks, and relpath can fail across drives. Keep dev installs
-            # functional by falling back to a copy.
-            if dest_file.is_symlink():
-                dest_file.unlink()
-            dest_file.write_text(content, encoding="utf-8")
-
    @staticmethod
    def write_copilot_prompt(project_root: Path, cmd_name: str) -> None:
        """Generate a companion .prompt.md file for a Copilot agent command.
@@ -701,53 +639,6 @@ class CommandRegistrar:
        CommandRegistrar._ensure_inside(prompt_file, prompts_dir)
        prompt_file.write_text(f"---\nagent: {cmd_name}\n---\n", encoding="utf-8")

-    @staticmethod
-    def _resolve_agent_dir(
-        agent_name: str,
-        agent_config: dict[str, Any],
-        project_root: Path,
-    ) -> Path:
-        """Return the agent command directory, falling back to legacy_dir.
-
-        Supports project-relative paths (e.g. ``.claude/skills/``),
-        home-relative paths (e.g. ``~/.hermes/skills``), and absolute
-        paths — the ``agent_config["dir"]`` value is resolved verbatim
-        when absolute or starting with ``~/``, or joined with
-        ``project_root`` when relative.
-
-        When the canonical directory does not exist but a ``legacy_dir``
-        is configured and present on disk, returns the legacy path and
-        emits a deprecation warning advising the user to upgrade.
-
-        Integrations that do not declare ``legacy_dir`` get the canonical
-        path unconditionally — no fallback, no warning.
-        """
-        dir_str = agent_config["dir"]
-        if dir_str.startswith("~"):
-            # Use Path.home() + remainder instead of expanduser() so tests
-            # that monkeypatch Path.home() can properly isolate the home dir.
-            # expanduser() uses OS env/user lookup and ignores monkeypatches.
-            agent_dir = Path.home() / dir_str[1:].lstrip("/")
-        else:
-            p = Path(dir_str)
-            agent_dir = p if p.is_absolute() else project_root / p
-        if not agent_dir.exists():
-            legacy = agent_config.get("legacy_dir")
-            if legacy:
-                legacy_dir = project_root / legacy
-                if legacy_dir.exists():
-                    import warnings
-
-                    warnings.warn(
-                        f"Found legacy '{legacy}' directory for "
-                        f"{agent_name}. Run 'specify integration "
-                        f"upgrade {agent_name}' to migrate to "
-                        f"'{agent_config['dir']}'.",
-                        stacklevel=3,
-                    )
-                    return legacy_dir
-        return agent_dir
-
    def register_commands_for_all_agents(
        self,
        commands: List[Dict[str, Any]],
@@ -755,7 +646,6 @@ class CommandRegistrar:
        source_dir: Path,
        project_root: Path,
        context_note: str = None,
-        link_outputs: bool = False,
    ) -> Dict[str, List[str]]:
        """Register commands for all detected agents in the project.

@@ -765,8 +655,6 @@ class CommandRegistrar:
            source_dir: Directory containing command source files
            project_root: Path to project root
            context_note: Custom context comment for markdown output
-            link_outputs: If True, create dev-mode symlinks for rendered
-                command files when supported by the OS.

        Returns:
            Dictionary mapping agent names to list of registered commands
@@ -775,18 +663,7 @@ class CommandRegistrar:

        self._ensure_configs()
        for agent_name, agent_config in self.AGENT_CONFIGS.items():
-            # Check detect_dir first (project-local marker) if configured,
-            # falling back to the resolved dir for output.  This prevents
-            # global dirs (e.g. ~/.hermes/skills) from causing false
-            # detection in every project.
-            detect_dir_str = agent_config.get("detect_dir")
-            if detect_dir_str:
-                detect_path = project_root / detect_dir_str
-                if not detect_path.exists():
-                    continue
-            agent_dir = self._resolve_agent_dir(
-                agent_name, agent_config, project_root,
-            )
+            agent_dir = project_root / agent_config["dir"]

            if agent_dir.exists():
                try:
@@ -797,8 +674,6 @@ class CommandRegistrar:
                        source_dir,
                        project_root,
                        context_note=context_note,
-                        _resolved_dir=agent_dir,
-                        link_outputs=link_outputs,
                    )
                    if registered:
                        results[agent_name] = registered
@@ -814,7 +689,6 @@ class CommandRegistrar:
        source_dir: Path,
        project_root: Path,
        context_note: Optional[str] = None,
-        link_outputs: bool = False,
    ) -> Dict[str, List[str]]:
        """Register commands for all non-skill agents in the project.

@@ -828,8 +702,6 @@ class CommandRegistrar:
            source_dir: Directory containing command source files
            project_root: Path to project root
            context_note: Custom context comment for markdown output
-            link_outputs: If True, create dev-mode symlinks for rendered
-                command files when supported by the OS.

        Returns:
            Dictionary mapping agent names to list of registered commands
@@ -839,14 +711,7 @@ class CommandRegistrar:
        for agent_name, agent_config in self.AGENT_CONFIGS.items():
            if agent_config.get("extension") == "/SKILL.md":
                continue
-            detect_dir_str = agent_config.get("detect_dir")
-            if detect_dir_str:
-                detect_path = project_root / detect_dir_str
-                if not detect_path.exists():
-                    continue
-            agent_dir = self._resolve_agent_dir(
-                agent_name, agent_config, project_root,
-            )
+            agent_dir = project_root / agent_config["dir"]
            if agent_dir.exists():
                try:
                    registered = self.register_commands(
@@ -856,8 +721,6 @@ class CommandRegistrar:
                        source_dir,
                        project_root,
                        context_note=context_note,
-                        _resolved_dir=agent_dir,
-                        link_outputs=link_outputs,
                    )
                    if registered:
                        results[agent_name] = registered
@@ -870,11 +733,6 @@ class CommandRegistrar:
    ) -> None:
        """Remove previously registered command files from agent directories.

-        When a ``legacy_dir`` is configured, files are removed from
-        *both* the canonical and the legacy directory so that orphaned
-        commands left behind after an ``integration upgrade`` are
-        cleaned up as well.
-
        Args:
            registered_commands: Dict mapping agent names to command name lists
            project_root: Path to project root
@@ -885,39 +743,24 @@ class CommandRegistrar:
                continue

            agent_config = self.AGENT_CONFIGS[agent_name]
-            commands_dir = self._resolve_agent_dir(
-                agent_name, agent_config, project_root,
-            )
-
-            # Collect all directories to clean: canonical (or resolved
-            # legacy) plus the legacy dir if it exists separately.
-            dirs_to_clean = [commands_dir]
-            legacy = agent_config.get("legacy_dir")
-            if legacy:
-                legacy_dir = project_root / legacy
-                if legacy_dir.exists() and legacy_dir != commands_dir:
-                    dirs_to_clean.append(legacy_dir)
+            commands_dir = project_root / agent_config["dir"]

            for cmd_name in cmd_names:
                output_name = self._compute_output_name(
                    agent_name, cmd_name, agent_config
                )
-                for target_dir in dirs_to_clean:
-                    cmd_file = (
-                        target_dir / f"{output_name}{agent_config['extension']}"
-                    )
-                    if cmd_file.exists() or cmd_file.is_symlink():
-                        cmd_file.unlink()
-                        # For SKILL.md agents each command lives in its own
-                        # subdirectory (e.g. .agents/skills/speckit-ext-cmd/
-                        # SKILL.md).  Remove the parent dir when it becomes
-                        # empty to avoid orphaned directories.
-                        parent = cmd_file.parent
-                        if parent != target_dir and parent.exists():
-                            try:
-                                parent.rmdir()
-                            except OSError:
-                                pass
+                cmd_file = commands_dir / f"{output_name}{agent_config['extension']}"
+                if cmd_file.exists():
+                    cmd_file.unlink()
+                    # For SKILL.md agents each command lives in its own subdirectory
+                    # (e.g. .agents/skills/speckit-ext-cmd/SKILL.md). Remove the
+                    # parent dir when it becomes empty to avoid orphaned directories.
+                    parent = cmd_file.parent
+                    if parent != commands_dir and parent.exists():
+                        try:
+                            parent.rmdir()  # no-op if dir still has other files
+                        except OSError:
+                            pass

                if agent_name == "copilot":
                    prompt_file = (
--- a/src/specify_cli/authentication/init.py
+++ b/src/specify_cli/authentication/init.py
@@ -1,50 +0,0 @@
-"""Authentication provider registry for multi-platform support.
-
-Credentials are **opt-in only**.  No authentication headers are sent unless
-the user creates ``~/.specify/auth.json`` mapping hosts to providers.
-Provider classes define *how* to authenticate (Bearer, Basic-PAT, etc.)
-while the config file defines *where* and *with what credentials*.
-"""
-
-from __future__ import annotations
-
-from typing import TYPE_CHECKING
-
-if TYPE_CHECKING:
-    from .base import AuthProvider
-
-# Maps provider key → AuthProvider class instance.
-AUTH_REGISTRY: dict[str, AuthProvider] = {}
-
-
-def _register(provider: AuthProvider) -> None:
-    """Register a provider instance in the global registry.
-
-    Raises ``ValueError`` for falsy keys and ``KeyError`` for duplicates.
-    """
-    key = provider.key
-    if not key:
-        raise ValueError("Cannot register provider with an empty key.")
-    if key in AUTH_REGISTRY:
-        raise KeyError(f"Provider with key {key!r} is already registered.")
-    AUTH_REGISTRY[key] = provider
-
-
-def get_provider(key: str) -> AuthProvider | None:
-    """Return the provider for *key*, or ``None`` if not registered."""
-    return AUTH_REGISTRY.get(key)
-
-
-# -- Register built-in providers -----------------------------------------
-
-
-def _register_builtins() -> None:
-    """Register all built-in authentication providers (alphabetical)."""
-    from .azure_devops import AzureDevOpsAuth
-    from .github import GitHubAuth
-
-    _register(AzureDevOpsAuth())
-    _register(GitHubAuth())
-
-
-_register_builtins()
--- a/src/specify_cli/authentication/azure_devops.py
+++ b/src/specify_cli/authentication/azure_devops.py
@@ -1,117 +0,0 @@
-"""Azure DevOps authentication provider."""
-
-from __future__ import annotations
-
-import base64
-import json as _json
-import os
-import subprocess
-from typing import TYPE_CHECKING
-
-from .base import AuthProvider
-
-if TYPE_CHECKING:
-    from .config import AuthConfigEntry
-
-# Azure DevOps resource ID for OAuth / Azure AD token acquisition.
-_ADO_RESOURCE_ID = "499b84ac-1321-427f-aa17-267ca6975798"
-
-
-class AzureDevOpsAuth(AuthProvider):
-    """Azure DevOps authentication provider.
-
-    Supports four auth schemes:
-
-    * ``basic-pat`` — PAT with empty username, Base64-encoded as ``:<PAT>``
-    * ``bearer`` — pre-acquired OAuth / Azure AD token
-    * ``azure-cli`` — acquires a token via ``az account get-access-token``
-    * ``azure-ad`` — acquires a token via OAuth2 client credentials flow
-    """
-
-    key = "azure-devops"
-    supported_auth_schemes = ("basic-pat", "bearer", "azure-cli", "azure-ad")
-
-    def auth_headers(self, token: str, auth_scheme: str) -> dict[str, str]:
-        """Build the ``Authorization`` header for the given scheme."""
-        if auth_scheme == "basic-pat":
-            encoded = base64.b64encode(f":{token}".encode("ascii")).decode("ascii")
-            return {"Authorization": f"Basic {encoded}"}
-        if auth_scheme in ("bearer", "azure-cli", "azure-ad"):
-            return {"Authorization": f"Bearer {token}"}
-        raise ValueError(
-            f"AzureDevOpsAuth does not support auth scheme {auth_scheme!r}"
-        )
-
-    def resolve_token(self, entry: AuthConfigEntry) -> str | None:
-        """Resolve token, with special handling for azure-cli and azure-ad."""
-        if entry.auth == "azure-cli":
-            return self._acquire_via_az_cli()
-        if entry.auth == "azure-ad":
-            return self._acquire_via_client_credentials(entry)
-        return super().resolve_token(entry)
-
-    # -- Token acquisition ------------------------------------------------
-
-    @staticmethod
-    def _acquire_via_az_cli() -> str | None:
-        """Run ``az account get-access-token`` and return the access token."""
-        try:
-            result = subprocess.run(  # noqa: S603, S607
-                [
-                    "az",
-                    "account",
-                    "get-access-token",
-                    "--resource",
-                    _ADO_RESOURCE_ID,
-                    "--output",
-                    "json",
-                ],
-                capture_output=True,
-                text=True,
-                timeout=30,
-                check=False,
-            )
-            if result.returncode != 0:
-                return None
-            payload = _json.loads(result.stdout)
-            token = payload.get("accessToken", "").strip()
-            return token or None
-        except (OSError, subprocess.TimeoutExpired, _json.JSONDecodeError, KeyError):
-            return None
-
-    @staticmethod
-    def _acquire_via_client_credentials(entry: AuthConfigEntry) -> str | None:
-        """Acquire a token via OAuth2 client credentials flow."""
-        import urllib.error
-        import urllib.request
-
-        if not entry.tenant_id or not entry.client_id or not entry.client_secret_env:
-            return None
-        client_secret = os.environ.get(entry.client_secret_env, "").strip()
-        if not client_secret:
-            return None
-
-        url = (
-            f"https://login.microsoftonline.com/{entry.tenant_id}"
-            "/oauth2/v2.0/token"
-        )
-        from urllib.parse import urlencode
-        body = urlencode({
-            "grant_type": "client_credentials",
-            "client_id": entry.client_id,
-            "client_secret": client_secret,
-            "scope": f"{_ADO_RESOURCE_ID}/.default",
-        }).encode("utf-8")
-
-        req = urllib.request.Request(
-            url,
-            data=body,
-            headers={"Content-Type": "application/x-www-form-urlencoded"},
-        )
-        try:
-            with urllib.request.urlopen(req, timeout=30) as resp:  # noqa: S310
-                payload = _json.loads(resp.read().decode("utf-8"))
-                token = payload.get("access_token", "").strip()
-                return token or None
-        except (urllib.error.URLError, OSError, _json.JSONDecodeError, KeyError):
-            return None
--- a/src/specify_cli/authentication/base.py
+++ b/src/specify_cli/authentication/base.py
@@ -1,57 +0,0 @@
-"""Abstract base class for authentication providers."""
-
-from __future__ import annotations
-
-from abc import ABC, abstractmethod
-from typing import TYPE_CHECKING
-
-if TYPE_CHECKING:
-    from .config import AuthConfigEntry
-
-
-class AuthProvider(ABC):
-    """Abstract base class every authentication provider must implement.
-
-    Subclasses must set:
-
-    * ``key`` — unique provider identifier (e.g. ``"github"``, ``"azure-devops"``)
-    * ``supported_auth_schemes`` — tuple of auth scheme strings this provider handles
-
-    And implement:
-
-    * ``auth_headers(token, auth_scheme)`` — build headers from a resolved token
-    * ``resolve_token(entry)`` — obtain the token for a config entry
-    """
-
-    key: str = ""
-    """Unique provider identifier."""
-
-    supported_auth_schemes: tuple[str, ...] = ()
-    """Auth schemes this provider supports (e.g. ``("bearer",)``)."""
-
-    @abstractmethod
-    def auth_headers(self, token: str, auth_scheme: str) -> dict[str, str]:
-        """Build authentication headers for *token* using *auth_scheme*.
-
-        Must return a dict with at least an ``Authorization`` key.
-        """
-
-    def resolve_token(self, entry: AuthConfigEntry) -> str | None:
-        """Resolve the token for *entry*.
-
-        Default implementation reads from ``entry.token`` directly
-        or from the environment variable named by ``entry.token_env``.
-        Override for schemes that acquire tokens dynamically
-        (e.g. ``azure-cli``, ``azure-ad``).
-        """
-        import os
-
-        if entry.token:
-            return entry.token.strip() or None
-        if entry.token_env:
-            val = os.environ.get(entry.token_env)
-            if val is not None:
-                val = val.strip()
-                if val:
-                    return val
-        return None
--- a/src/specify_cli/authentication/config.py
+++ b/src/specify_cli/authentication/config.py
@@ -1,209 +0,0 @@
-"""Authentication configuration loader.
-
-Reads ``~/.specify/auth.json`` to determine which hosts receive credentials
-and which provider/auth-scheme to use.  No credentials are sent without
-an explicit opt-in via this file.
-"""
-
-from __future__ import annotations
-
-import json
-import os
-import stat
-from dataclasses import dataclass
-from fnmatch import fnmatch
-from pathlib import Path
-from urllib.parse import urlparse
-
-
-@dataclass(frozen=True)
-class AuthConfigEntry:
-    """A single provider entry from ``auth.json``."""
-
-    hosts: tuple[str, ...]
-    provider: str
-    auth: str
-    token: str | None = None
-    token_env: str | None = None
-    # Azure AD service-principal fields
-    tenant_id: str | None = None
-    client_id: str | None = None
-    client_secret_env: str | None = None
-
-
-def _default_config_path() -> Path:
-    """Return ``~/.specify/auth.json``."""
-    return Path.home() / ".specify" / "auth.json"
-
-
-def _is_valid_host_pattern(pattern: str) -> bool:
-    """Return True for safe host patterns: exact hostnames or ``*.suffix`` only.
-
-    Rejects patterns like ``*github.com`` (which would match
-    ``github.com.evil.com``) or multi-wildcard forms.  Only these two
-    forms are accepted:
-
-    * ``example.com``           — exact hostname
-    * ``*.example.com``         — leading ``*.`` wildcard; matches subdomains
-      such as ``myorg.example.com`` but not ``example.com`` itself
-    """
-    if "*" not in pattern:
-        return True  # exact hostname — already validated as non-empty
-    # Only *.suffix is allowed; no other wildcard positions
-    return pattern.startswith("*.") and "*" not in pattern[2:]
-
-
-def load_auth_config(
-    path: Path | None = None,
-) -> list[AuthConfigEntry]:
-    """Load and validate ``auth.json``, returning configured entries.
-
-    Returns an empty list when the file does not exist — this means
-    all HTTP requests will be unauthenticated (opt-in model).
-
-    Raises ``ValueError`` on schema violations.  Callers that want
-    misconfigurations to fail fast can allow this exception to
-    propagate; higher-level HTTP helpers may instead catch it,
-    warn, and continue with unauthenticated requests.
-    """
-    config_path = path or _default_config_path()
-
-    if not config_path.is_file():
-        return []
-
-    # Warn (but don't fail) if the file is world-readable (POSIX only).
-    if os.name != "nt":
-        try:
-            mode = config_path.stat().st_mode
-            if mode & (stat.S_IRGRP | stat.S_IROTH):
-                import warnings
-
-                warnings.warn(
-                    f"{config_path} is readable by group/others. "
-                    "Consider restricting with: chmod 600 "
-                    f"{config_path}",
-                    UserWarning,
-                    stacklevel=2,
-                )
-        except OSError:
-            pass  # stat failed — skip permission check
-
-    raw = json.loads(config_path.read_text(encoding="utf-8"))
-
-    if not isinstance(raw, dict):
-        raise ValueError(f"auth.json must be a JSON object, got {type(raw).__name__}")
-
-    providers_raw = raw.get("providers")
-    if not isinstance(providers_raw, list):
-        raise ValueError("auth.json must contain a 'providers' array")
-
-    entries: list[AuthConfigEntry] = []
-    for i, entry_raw in enumerate(providers_raw):
-        if not isinstance(entry_raw, dict):
-            raise ValueError(f"providers[{i}]: must be a JSON object")
-
-        hosts = entry_raw.get("hosts")
-        if not isinstance(hosts, list) or not hosts:
-            raise ValueError(f"providers[{i}]: 'hosts' must be a non-empty array")
-        if not all(isinstance(h, str) and h.strip() for h in hosts):
-            raise ValueError(f"providers[{i}]: each host must be a non-empty string")
-        # Normalize hosts: strip whitespace and lowercase
-        hosts = [h.strip().lower() for h in hosts]
-        # Reject dangerous wildcard forms (e.g. *github.com matches github.com.evil.com)
-        for h in hosts:
-            if not _is_valid_host_pattern(h):
-                raise ValueError(
-                    f"providers[{i}]: invalid host pattern {h!r}. "
-                    "Only exact hostnames or '*.suffix' forms are allowed "
-                    "(e.g. 'github.com' or '*.visualstudio.com')."
-                )
-
-        provider = entry_raw.get("provider", "")
-        if not isinstance(provider, str) or not provider:
-            raise ValueError(f"providers[{i}]: 'provider' must be a non-empty string")
-
-        auth = entry_raw.get("auth", "")
-        if not isinstance(auth, str) or not auth:
-            raise ValueError(f"providers[{i}]: 'auth' must be a non-empty string")
-
-        token = entry_raw.get("token")
-        token_env = entry_raw.get("token_env")
-
-        # Validate token/token_env types
-        if token is not None and (not isinstance(token, str) or not token.strip()):
-            raise ValueError(f"providers[{i}]: 'token' must be a non-empty string")
-        if token_env is not None and (not isinstance(token_env, str) or not token_env.strip()):
-            raise ValueError(f"providers[{i}]: 'token_env' must be a non-empty string")
-
-        # Validate provider+scheme compatibility
-        from . import get_provider as _get_provider
-        _prov = _get_provider(provider)
-        if _prov is None:
-            from . import AUTH_REGISTRY
-            raise ValueError(
-                f"providers[{i}]: unknown provider {provider!r}; "
-                f"registered: {sorted(AUTH_REGISTRY.keys())}"
-            )
-        if auth not in _prov.supported_auth_schemes:
-            raise ValueError(
-                f"providers[{i}]: provider {provider!r} does not support "
-                f"auth scheme {auth!r}; supported: {list(_prov.supported_auth_schemes)}"
-            )
-
-        # Validate token source based on auth scheme
-        if auth in ("bearer", "basic-pat"):
-            if not token and not token_env:
-                raise ValueError(
-                    f"providers[{i}]: auth={auth!r} requires 'token' or 'token_env'"
-                )
-        elif auth == "azure-ad":
-            tenant_id = entry_raw.get("tenant_id")
-            client_id = entry_raw.get("client_id")
-            client_secret_env = entry_raw.get("client_secret_env")
-            if not all([tenant_id, client_id, client_secret_env]):
-                raise ValueError(
-                    f"providers[{i}]: auth='azure-ad' requires "
-                    "'tenant_id', 'client_id', and 'client_secret_env'"
-                )
-            for field_name, field_val in [
-                ("tenant_id", tenant_id),
-                ("client_id", client_id),
-                ("client_secret_env", client_secret_env),
-            ]:
-                if not isinstance(field_val, str) or not field_val.strip():
-                    raise ValueError(
-                        f"providers[{i}]: '{field_name}' must be a non-empty string"
-                    )
-        # azure-cli needs no extra fields
-
-        entries.append(
-            AuthConfigEntry(
-                hosts=tuple(hosts),
-                provider=provider,
-                auth=auth,
-                token=token,
-                token_env=token_env,
-                tenant_id=entry_raw.get("tenant_id"),
-                client_id=entry_raw.get("client_id"),
-                client_secret_env=entry_raw.get("client_secret_env"),
-            )
-        )
-
-    return entries
-
-
-def find_entries_for_url(
-    url: str, entries: list[AuthConfigEntry]
-) -> list[AuthConfigEntry]:
-    """Return entries whose ``hosts`` match the hostname of *url*."""
-    hostname = (urlparse(url).hostname or "").lower()
-    if not hostname:
-        return []
-    return [
-        e
-        for e in entries
-        if any(
-            pattern == hostname or fnmatch(hostname, pattern)
-            for pattern in e.hosts
-        )
-    ]
--- a/src/specify_cli/authentication/github.py
+++ b/src/specify_cli/authentication/github.py
@@ -1,24 +0,0 @@
-"""GitHub authentication provider."""
-
-from __future__ import annotations
-
-from .base import AuthProvider
-
-
-class GitHubAuth(AuthProvider):
-    """GitHub authentication provider.
-
-    Supports the ``bearer`` auth scheme, used for PATs, fine-grained PATs,
-    OAuth tokens, and GitHub App installation tokens.
-    """
-
-    key = "github"
-    supported_auth_schemes = ("bearer",)
-
-    def auth_headers(self, token: str, auth_scheme: str) -> dict[str, str]:
-        """Return ``Authorization: Bearer <token>``."""
-        if auth_scheme != "bearer":
-            raise ValueError(
-                f"GitHubAuth does not support auth scheme {auth_scheme!r}"
-            )
-        return {"Authorization": f"Bearer {token}"}
--- a/src/specify_cli/authentication/http.py
+++ b/src/specify_cli/authentication/http.py
@@ -1,149 +0,0 @@
-"""Authenticated HTTP helpers driven by ``~/.specify/auth.json``.
-
-No credentials are sent unless the user has created ``auth.json``.
-For each outbound URL the helper matches the hostname against
-configured entries, resolves the token via the appropriate provider
-class, and attaches auth headers.  Redirect safety is enforced:
-the ``Authorization`` header is stripped when a redirect leaves the
-entry's declared hosts.  On 401/403 the next matching entry is tried,
-then unauthenticated.
-"""
-
-from __future__ import annotations
-
-import urllib.error
-import urllib.request
-from fnmatch import fnmatch
-from urllib.parse import urlparse
-
-from . import get_provider
-from .config import AuthConfigEntry, _default_config_path, find_entries_for_url, load_auth_config
-
-
-_config_override: list[AuthConfigEntry] | None = None
-_config_cache: list[AuthConfigEntry] | None = None  # None = not yet loaded
-
-
-def _load_config() -> list[AuthConfigEntry]:
-    """Load auth config, using override if set (for testing).
-
-    The result is cached per-process so ``auth.json`` is read at most once,
-    and any warning about a malformed file fires only once.
-    """
-    global _config_cache
-    if _config_override is not None:
-        return _config_override
-    if _config_cache is not None:
-        return _config_cache
-    try:
-        _config_cache = load_auth_config()
-    except (ValueError, OSError) as exc:
-        import warnings
-        config_path = _default_config_path()
-        warnings.warn(
-            f"Failed to load {config_path}: {exc}. "
-            "All requests will be unauthenticated.",
-            UserWarning,
-            stacklevel=2,
-        )
-        _config_cache = []
-    return _config_cache
-
-
-def _hostname_in_hosts(hostname: str, hosts: tuple[str, ...]) -> bool:
-    """Return True if *hostname* matches any pattern in *hosts*."""
-    hostname = hostname.lower()
-    return any(p == hostname or fnmatch(hostname, p) for p in hosts)
-
-
-class _StripAuthOnRedirect(urllib.request.HTTPRedirectHandler):
-    """Drop ``Authorization`` when a redirect leaves the entry's declared hosts."""
-
-    def __init__(self, hosts: tuple[str, ...]) -> None:
-        super().__init__()
-        self._hosts = hosts
-
-    def redirect_request(self, req, fp, code, msg, headers, newurl):
-        original_auth = (
-            req.get_header("Authorization")
-            or req.unredirected_hdrs.get("Authorization")
-        )
-        new_req = super().redirect_request(req, fp, code, msg, headers, newurl)
-        if new_req is not None:
-            hostname = (urlparse(newurl).hostname or "").lower()
-            if _hostname_in_hosts(hostname, self._hosts):
-                if original_auth:
-                    new_req.add_unredirected_header("Authorization", original_auth)
-            else:
-                new_req.headers.pop("Authorization", None)
-                new_req.unredirected_hdrs.pop("Authorization", None)
-        return new_req
-
-
-def build_request(url: str, extra_headers: dict[str, str] | None = None) -> urllib.request.Request:
-    """Build a :class:`~urllib.request.Request`, attaching auth when config matches.
-
-    Uses the first matching entry from ``auth.json`` whose token resolves.
-    Returns a plain request when no entry matches or the file doesn't exist.
-    """
-    headers: dict[str, str] = {}
-    if extra_headers:
-        # Strip Authorization from extra_headers to prevent bypass
-        headers.update({k: v for k, v in extra_headers.items() if k.lower() != "authorization"})
-    # Auth headers applied last — cannot be overridden by extra_headers
-    entries = find_entries_for_url(url, _load_config())
-    for entry in entries:
-        provider = get_provider(entry.provider)
-        if provider is None:
-            continue
-        token = provider.resolve_token(entry)
-        if token:
-            headers.update(provider.auth_headers(token, entry.auth))
-            break
-    return urllib.request.Request(url, headers=headers)
-
-
-def open_url(url: str, timeout: int = 10, extra_headers: dict[str, str] | None = None):
-    """Open *url* with config-driven auth, redirect stripping, and fallthrough.
-
-    1. Find ``auth.json`` entries whose hosts match the URL.
-    2. For each entry, resolve the token and try the request.
-    3. On 401/403 move to the next matching entry.
-    4. After all entries exhausted (or none matched), try unauthenticated.
-    5. Non-auth errors (404, 500, network) raise immediately.
-
-    *extra_headers* (e.g. ``Accept``) are merged into every attempt.
-    """
-    entries = find_entries_for_url(url, _load_config())
-
-    def _make_req(auth_headers: dict[str, str]) -> urllib.request.Request:
-        merged = {}
-        if extra_headers:
-            # Strip Authorization from extra_headers to prevent bypass
-            merged.update({k: v for k, v in extra_headers.items() if k.lower() != "authorization"})
-        # Auth headers applied last — cannot be overridden by extra_headers
-        merged.update(auth_headers)
-        return urllib.request.Request(url, headers=merged)
-
-    # Try each matching entry
-    for entry in entries:
-        provider = get_provider(entry.provider)
-        if provider is None:
-            continue
-        token = provider.resolve_token(entry)
-        if not token:
-            continue
-
-        req = _make_req(provider.auth_headers(token, entry.auth))
-        opener = urllib.request.build_opener(_StripAuthOnRedirect(entry.hosts))
-        try:
-            return opener.open(req, timeout=timeout)
-        except urllib.error.HTTPError as exc:
-            if exc.code in (401, 403):
-                exc.close()
-                continue  # try next entry
-            raise
-
-    # No entry worked (or none matched) — unauthenticated fallback
-    req = _make_req({})
-    return urllib.request.urlopen(req, timeout=timeout)  # noqa: S310
--- a/src/specify_cli/catalogs.py
+++ b/src/specify_cli/catalogs.py
@@ -1,180 +0,0 @@
-"""Shared catalog stack config primitives.
-
-Catalog-backed features use the same local config shape and URL validation
-rules. This module keeps those narrow primitives in one place while individual
-catalog types keep their active source resolution, fetch, cache, and
-domain-specific validation behavior.
-"""
-
-from __future__ import annotations
-
-from dataclasses import dataclass
-from pathlib import Path
-from typing import ClassVar
-
-import yaml
-
-
-@dataclass
-class CatalogEntry:
-    """Represents a single catalog source in a catalog stack."""
-
-    url: str
-    name: str
-    priority: int
-    install_allowed: bool
-    description: str = ""
-
-
-class CatalogStackBase:
-    """Base class for ordered catalog-source resolution.
-
-    Subclasses provide catalog-specific metadata and exception classes. Fetching
-    and schema validation stay in each concrete catalog because those formats
-    differ across integrations, extensions, presets, and workflows.
-    """
-
-    ENTRY_CLASS: ClassVar[type[CatalogEntry]] = CatalogEntry
-    ERROR_TYPE: ClassVar[type[Exception]] = ValueError
-    VALIDATION_ERROR_TYPE: ClassVar[type[Exception]] = ValueError
-
-    CONFIG_FILENAME: ClassVar[str]
-
-    @classmethod
-    def _error(cls, message: str) -> Exception:
-        return cls.ERROR_TYPE(message)
-
-    @classmethod
-    def _validation_error(cls, message: str) -> Exception:
-        return cls.VALIDATION_ERROR_TYPE(message)
-
-    @classmethod
-    def _entry(
-        cls,
-        *,
-        url: str,
-        name: str,
-        priority: int,
-        install_allowed: bool,
-        description: str = "",
-    ) -> CatalogEntry:
-        return cls.ENTRY_CLASS(
-            url=url,
-            name=name,
-            priority=priority,
-            install_allowed=install_allowed,
-            description=description,
-        )
-
-    @classmethod
-    def _validate_catalog_url(cls, url: str) -> None:
-        """Validate that a catalog URL uses HTTPS, except localhost HTTP."""
-        from urllib.parse import urlparse
-
-        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}://). "
-                "HTTP is only allowed for localhost."
-            )
-        if not parsed.netloc:
-            raise cls._error("Catalog URL must be a valid URL with a host.")
-
-    def _load_catalog_config(self, config_path: Path) -> list[CatalogEntry] | None:
-        """Load catalog stack configuration from a YAML file.
-
-        Returns ``None`` when the file does not exist. Existing files fail
-        closed when they are malformed, empty, or contain no usable URLs.
-        """
-        if not config_path.exists():
-            return None
-        try:
-            data = yaml.safe_load(config_path.read_text(encoding="utf-8"))
-        except (yaml.YAMLError, OSError, UnicodeError) as exc:
-            raise self._validation_error(
-                f"Failed to read catalog config {config_path}: {exc}"
-            ) from exc
-        if data is None:
-            data = {}
-        if not isinstance(data, dict):
-            raise self._validation_error(
-                f"Invalid catalog config {config_path}: expected a YAML mapping at the root"
-            )
-
-        catalogs_data = data.get("catalogs", [])
-        if not isinstance(catalogs_data, list):
-            raise self._validation_error(
-                f"Invalid catalog config {config_path}: 'catalogs' must be a list, "
-                f"got {type(catalogs_data).__name__}"
-            )
-        if not catalogs_data:
-            raise self._validation_error(
-                f"Catalog config {config_path} exists but contains no 'catalogs' entries. "
-                f"Remove the file to use built-in defaults, or add valid catalog entries."
-            )
-
-        entries: list[CatalogEntry] = []
-        skipped: list[int] = []
-        for idx, item in enumerate(catalogs_data):
-            if not isinstance(item, dict):
-                raise self._validation_error(
-                    f"Invalid catalog config {config_path}: catalog entry at index {idx}: "
-                    f"expected a mapping, got {type(item).__name__}"
-                )
-            url = str(item.get("url", "")).strip()
-            if not url:
-                skipped.append(idx)
-                continue
-            try:
-                self._validate_catalog_url(url)
-            except self.ERROR_TYPE as exc:
-                raise self._validation_error(
-                    f"Invalid catalog URL in {config_path} at index {idx}: {exc}"
-                ) from exc
-
-            raw_priority = item.get("priority", idx + 1)
-            if isinstance(raw_priority, bool):
-                raise self._validation_error(
-                    f"Invalid catalog config {config_path}: "
-                    f"Invalid priority for catalog '{item.get('name', idx + 1)}': "
-                    f"expected integer, got {raw_priority!r}"
-                )
-            try:
-                priority = int(raw_priority)
-            except (TypeError, ValueError):
-                raise self._validation_error(
-                    f"Invalid catalog config {config_path}: "
-                    f"Invalid priority for catalog '{item.get('name', idx + 1)}': "
-                    f"expected integer, got {raw_priority!r}"
-                )
-
-            raw_install = item.get("install_allowed", False)
-            if isinstance(raw_install, str):
-                install_allowed = raw_install.strip().lower() in ("true", "yes", "1")
-            else:
-                install_allowed = bool(raw_install)
-
-            raw_name = item.get("name")
-            name = str(raw_name).strip() if raw_name is not None else ""
-            if not name:
-                name = f"catalog-{len(entries) + 1}"
-
-            entries.append(
-                self._entry(
-                    url=url,
-                    name=name,
-                    priority=priority,
-                    install_allowed=install_allowed,
-                    description=str(item.get("description", "")),
-                )
-            )
-
-        entries.sort(key=lambda e: e.priority)
-        if not entries:
-            raise self._validation_error(
-                f"Catalog config {config_path} contains {len(catalogs_data)} "
-                f"entries but none have valid URLs (entries at indices {skipped} "
-                f"were skipped). Each catalog entry must have a 'url' field."
-            )
-        return entries
--- a/src/specify_cli/commands/init.py
+++ b/src/specify_cli/commands/init.py
@@ -1,7 +0,0 @@
-"""CLI command groups extracted from the main application.
-
-Implemented command modules expose a ``register(app)`` function. Placeholder
-modules are import-only anchors for command groups that still live in the main
-application module.
-"""
-from __future__ import annotations
--- a/src/specify_cli/commands/extension.py
+++ b/src/specify_cli/commands/extension.py
@@ -1,2 +0,0 @@
-"""specify extension * commands — placeholder for future extraction."""
-from __future__ import annotations
--- a/src/specify_cli/commands/init.py
+++ b/src/specify_cli/commands/init.py
@@ -1,743 +0,0 @@
-"""specify init command."""
-from __future__ import annotations
-
-import os
-import shlex
-import shutil
-import sys
-from pathlib import Path
-from typing import Any
-
-import typer
-from rich.live import Live
-from rich.panel import Panel
-
-from .._agent_config import (
-    AGENT_CONFIG,
-    AI_ASSISTANT_ALIASES,
-    AI_ASSISTANT_HELP,
-    DEFAULT_INIT_INTEGRATION,
-    SCRIPT_TYPE_CHOICES,
-)
-from .._assets import (
-    _locate_bundled_extension,
-    _locate_bundled_preset,
-    _locate_bundled_workflow,
-    get_speckit_version,
-)
-from .._console import StepTracker, console, select_with_arrows, show_banner
-from .._utils import check_tool, init_git_repo, is_git_repo
-
-def _build_integration_equivalent(
-    integration_key: str,
-    ai_commands_dir: str | None = None,
-) -> str:
-    parts = [f"--integration {integration_key}"]
-    if integration_key == "generic" and ai_commands_dir:
-        parts.append(
-            f'--integration-options="--commands-dir {shlex.quote(ai_commands_dir)}"'
-        )
-    return " ".join(parts)
-
-
-def _build_ai_deprecation_warning(
-    integration_key: str,
-    ai_commands_dir: str | None = None,
-) -> str:
-    replacement = _build_integration_equivalent(
-        integration_key,
-        ai_commands_dir=ai_commands_dir,
-    )
-    return (
-        "[bold]--ai[/bold] is deprecated and will no longer be available in version 0.10.0 or later.\n\n"
-        f"Use [bold]{replacement}[/bold] instead."
-    )
-
-
-def _stdin_is_interactive() -> bool:
-    return sys.stdin.isatty()
-
-
-def ensure_constitution_from_template(
-    project_path: Path, tracker: StepTracker | None = None
-) -> None:
-    """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:
-            tracker.add("constitution", "Constitution setup")
-            tracker.skip("constitution", "existing file preserved")
-        return
-
-    if not template_constitution.exists():
-        if tracker:
-            tracker.add("constitution", "Constitution setup")
-            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:
-        if tracker:
-            tracker.add("constitution", "Constitution setup")
-            tracker.error("constitution", str(e))
-        else:
-            console.print(f"[yellow]Warning: Could not initialize constitution: {e}[/yellow]")
-
-
-def register(app: typer.Typer) -> None:
-    @app.command()
-    def init(
-        project_name: str = typer.Argument(None, help="Name for your new project directory (optional if using --here, or use '.' for current directory)"),
-        ai_assistant: str = typer.Option(None, "--ai", help=AI_ASSISTANT_HELP),
-        ai_commands_dir: str = typer.Option(None, "--ai-commands-dir", help="Directory for agent command files (required with --ai generic, e.g. .myagent/commands/)"),
-        script_type: str = typer.Option(None, "--script", help="Script type to use: sh or ps"),
-        ignore_agent_tools: bool = typer.Option(False, "--ignore-agent-tools", help="Skip checks for coding agent tools like Claude Code"),
-        no_git: bool = typer.Option(False, "--no-git", help="Skip git repository initialization"),
-        here: bool = typer.Option(False, "--here", help="Initialize project in the current directory instead of creating a new one"),
-        force: bool = typer.Option(False, "--force", help="Force merge/overwrite when using --here (skip confirmation)"),
-        skip_tls: bool = typer.Option(False, "--skip-tls", help="Deprecated (no-op). Previously: skip SSL/TLS verification.", hidden=True),
-        debug: bool = typer.Option(False, "--debug", help="Deprecated. Previously: show verbose diagnostic output; currently only prints additional diagnostic details on failure.", hidden=True),
-        github_token: str = typer.Option(None, "--github-token", help="Deprecated (no-op). Previously: GitHub token for API requests.", hidden=True),
-        ai_skills: bool = typer.Option(False, "--ai-skills", help="Install Prompt.MD templates as agent skills (requires --ai)"),
-        offline: bool = typer.Option(False, "--offline", help="Deprecated (no-op). All scaffolding now uses bundled assets.", hidden=True),
-        preset: str = typer.Option(None, "--preset", help="Install a preset during initialization (by preset ID)"),
-        branch_numbering: str = typer.Option(None, "--branch-numbering", help="Branch numbering strategy: 'sequential' (001, 002, …, 1000, … — expands past 999 automatically) or 'timestamp' (YYYYMMDD-HHMMSS)"),
-        integration: str = typer.Option(None, "--integration", help="Use the new integration system (e.g. --integration copilot). Mutually exclusive with --ai."),
-        integration_options: str = typer.Option(None, "--integration-options", help='Options for the integration (e.g. --integration-options="--commands-dir .myagent/cmds")'),
-    ):
-        """
-        Initialize a new Specify project.
-
-        Project files are scaffolded from assets bundled inside the specify-cli
-        package, so initialization does not need network access and templates
-        match the installed CLI version.
-
-        This command will:
-        1. Check that required tools are installed (git is optional)
-        2. Let you choose your coding agent integration, or default to Copilot
-           in non-interactive sessions
-        3. Install bundled Spec Kit templates, scripts, workflow, and shared
-           project infrastructure
-        4. Initialize a fresh git repository (if not --no-git and no existing repo)
-        5. Set up coding agent integration commands and optional presets
-
-        Examples:
-            specify init my-project
-            specify init my-project --integration claude
-            specify init my-project --integration copilot --no-git
-            specify init --ignore-agent-tools my-project
-            specify init . --integration claude         # Initialize in current directory
-            specify init .                     # Initialize in current directory (interactive integration selection)
-            specify init --here --integration claude    # Alternative syntax for current directory
-            specify init --here --integration codex --integration-options="--skills"
-            specify init --here --integration codebuddy
-            specify init --here --integration vibe      # Initialize with Mistral Vibe support
-            specify init --here
-            specify init --here --force  # Skip confirmation when current directory not empty
-            specify init my-project --integration claude   # Claude installs skills by default
-            specify init --here --integration gemini
-            specify init my-project --integration generic --integration-options="--commands-dir .myagent/commands/"  # Bring your own agent; requires --commands-dir
-            specify init my-project --integration claude --preset healthcare-compliance  # With preset
-        """
-        # Lazy imports to avoid circular dependency — __init__.py imports this module
-        from .. import (
-            _install_shared_infra_or_exit,
-            _parse_integration_options,
-            _print_cli_warning,
-            _write_integration_json,
-            ensure_executable_scripts,
-            save_init_options,
-        )
-        from ..integration_runtime import with_integration_setting as _with_integration_setting
-
-        show_banner()
-        ai_deprecation_warning: str | None = None
-
-        if ai_assistant and ai_assistant.startswith("--"):
-            console.print(f"[red]Error:[/red] Invalid value for --ai: '{ai_assistant}'")
-            console.print("[yellow]Hint:[/yellow] Did you forget to provide a value for --ai?")
-            console.print("[yellow]Example:[/yellow] specify init --integration claude --here")
-            console.print(f"[yellow]Available agents:[/yellow] {', '.join(AGENT_CONFIG.keys())}")
-            raise typer.Exit(1)
-
-        if ai_commands_dir and ai_commands_dir.startswith("--"):
-            console.print(f"[red]Error:[/red] Invalid value for --ai-commands-dir: '{ai_commands_dir}'")
-            console.print("[yellow]Hint:[/yellow] Did you forget to provide a value for --ai-commands-dir?")
-            console.print("[yellow]Example:[/yellow] specify init --integration generic --integration-options=\"--commands-dir .myagent/commands/\"")
-            raise typer.Exit(1)
-
-        if ai_assistant:
-            ai_assistant = AI_ASSISTANT_ALIASES.get(ai_assistant, ai_assistant)
-
-        if integration and ai_assistant:
-            console.print("[red]Error:[/red] --integration and --ai are mutually exclusive")
-            raise typer.Exit(1)
-
-        from ..integrations import INTEGRATION_REGISTRY, get_integration
-        if integration:
-            resolved_integration = get_integration(integration)
-            if not resolved_integration:
-                console.print(f"[red]Error:[/red] Unknown integration: '{integration}'")
-                available = ", ".join(sorted(INTEGRATION_REGISTRY))
-                console.print(f"[yellow]Available integrations:[/yellow] {available}")
-                raise typer.Exit(1)
-            ai_assistant = integration
-        elif ai_assistant:
-            resolved_integration = get_integration(ai_assistant)
-            if not resolved_integration:
-                console.print(f"[red]Error:[/red] Unknown agent '{ai_assistant}'. Choose from: {', '.join(sorted(INTEGRATION_REGISTRY))}")
-                raise typer.Exit(1)
-            ai_deprecation_warning = _build_ai_deprecation_warning(
-                resolved_integration.key,
-                ai_commands_dir=ai_commands_dir,
-            )
-
-        if ai_assistant or integration:
-            if ai_skills:
-                from ..integrations.base import SkillsIntegration as _SkillsCheck
-                if isinstance(resolved_integration, _SkillsCheck):
-                    console.print(
-                        "[dim]Note: --ai-skills is not needed; "
-                        "skills are the default for this integration.[/dim]"
-                    )
-                else:
-                    console.print(
-                        "[dim]Note: --ai-skills has no effect with "
-                        f"{resolved_integration.key}; this integration uses commands, not skills.[/dim]"
-                    )
-            if ai_commands_dir and resolved_integration.key != "generic":
-                console.print(
-                    "[dim]Note: --ai-commands-dir is deprecated; "
-                    'use [bold]--integration generic --integration-options="--commands-dir <dir>"[/bold] instead.[/dim]'
-                )
-
-        if no_git:
-            console.print(
-                "[yellow]⚠️  --no-git is deprecated and will be removed in v0.10.0.[/yellow]\n"
-                "[yellow]The git extension will no longer be enabled by default "
-                "— use the [bold]specify extension[/bold] commands to install or enable the git extension if needed.[/yellow]"
-            )
-
-        if project_name == ".":
-            here = True
-            project_name = None
-
-        if here and project_name:
-            console.print("[red]Error:[/red] Cannot specify both project name and --here flag")
-            raise typer.Exit(1)
-
-        if not here and not project_name:
-            console.print("[red]Error:[/red] Must specify either a project name, use '.' for current directory, or use --here flag")
-            raise typer.Exit(1)
-
-        if ai_skills and not ai_assistant:
-            console.print("[red]Error:[/red] --ai-skills requires --ai to be specified")
-            console.print("[yellow]Usage:[/yellow] specify init <project> --ai <agent> --ai-skills")
-            raise typer.Exit(1)
-
-        BRANCH_NUMBERING_CHOICES = {"sequential", "timestamp"}
-        if branch_numbering and branch_numbering not in BRANCH_NUMBERING_CHOICES:
-            console.print(f"[red]Error:[/red] Invalid --branch-numbering value '{branch_numbering}'. Choose from: {', '.join(sorted(BRANCH_NUMBERING_CHOICES))}")
-            raise typer.Exit(1)
-
-        dir_existed_before = False
-        if here:
-            project_name = Path.cwd().name
-            project_path = Path.cwd()
-            dir_existed_before = True
-
-            existing_items = list(project_path.iterdir())
-            if existing_items:
-                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:
-                    console.print("[cyan]--force supplied: skipping confirmation and proceeding with merge[/cyan]")
-                else:
-                    response = typer.confirm("Do you want to continue?")
-                    if not response:
-                        console.print("[yellow]Operation cancelled[/yellow]")
-                        raise typer.Exit(0)
-        else:
-            project_path = Path(project_name).resolve()
-            dir_existed_before = project_path.exists()
-            if project_path.exists():
-                if not project_path.is_dir():
-                    console.print(f"[red]Error:[/red] '{project_name}' exists but is not a directory.")
-                    raise typer.Exit(1)
-                existing_items = list(project_path.iterdir())
-                if force:
-                    if existing_items:
-                        console.print(f"[yellow]Warning:[/yellow] Directory '{project_name}' is not empty ({len(existing_items)} items)")
-                        console.print("[yellow]Template files will be merged with existing content and may overwrite existing files[/yellow]")
-                    console.print(f"[cyan]--force supplied: merging into existing directory '[cyan]{project_name}[/cyan]'[/cyan]")
-                else:
-                    error_panel = Panel(
-                        f"Directory already exists: '[cyan]{project_name}[/cyan]'\n"
-                        "Please choose a different project name or remove the existing directory.\n"
-                        "Use [bold]--force[/bold] to merge into the existing directory.",
-                        title="[red]Directory Conflict[/red]",
-                        border_style="red",
-                        padding=(1, 2)
-                    )
-                    console.print()
-                    console.print(error_panel)
-                    raise typer.Exit(1)
-
-        if ai_assistant:
-            if ai_assistant not in AGENT_CONFIG:
-                console.print(f"[red]Error:[/red] Invalid AI assistant '{ai_assistant}'. Choose from: {', '.join(AGENT_CONFIG.keys())}")
-                raise typer.Exit(1)
-            selected_ai = ai_assistant
-        elif not _stdin_is_interactive():
-            console.print(
-                f"[dim]Non-interactive session detected: defaulting to '{DEFAULT_INIT_INTEGRATION}'. "
-                "Use --integration to choose a different agent.[/dim]"
-            )
-            selected_ai = DEFAULT_INIT_INTEGRATION
-        else:
-            ai_choices = {key: config["name"] for key, config in AGENT_CONFIG.items()}
-            selected_ai = select_with_arrows(
-                ai_choices,
-                "Choose your coding agent integration:",
-                DEFAULT_INIT_INTEGRATION,
-            )
-
-        if not ai_assistant:
-            resolved_integration = get_integration(selected_ai)
-            if not resolved_integration:
-                console.print(f"[red]Error:[/red] Unknown agent '{selected_ai}'")
-                raise typer.Exit(1)
-
-        if selected_ai == "generic" and not integration_options:
-            if not ai_commands_dir:
-                console.print("[red]Error:[/red] --ai-commands-dir is required when using --ai generic or --integration generic")
-                console.print('[dim]Example: specify init my-project --integration generic --integration-options="--commands-dir .myagent/commands/"[/dim]')
-                raise typer.Exit(1)
-
-        current_dir = Path.cwd()
-
-        setup_lines = [
-            "[cyan]Specify Project Setup[/cyan]",
-            "",
-            f"{'Project':<15} [green]{project_path.name}[/green]",
-            f"{'Working Path':<15} [dim]{current_dir}[/dim]",
-        ]
-
-        if not here:
-            setup_lines.append(f"{'Target Path':<15} [dim]{project_path}[/dim]")
-
-        console.print(Panel("\n".join(setup_lines), border_style="cyan", padding=(1, 2)))
-
-        should_init_git = False
-        if not no_git:
-            should_init_git = check_tool("git")
-            if not should_init_git:
-                console.print("[yellow]Git not found - will skip repository initialization[/yellow]")
-
-        if not ignore_agent_tools:
-            agent_config = AGENT_CONFIG.get(selected_ai)
-            if agent_config and agent_config["requires_cli"]:
-                install_url = agent_config["install_url"]
-                if not check_tool(selected_ai):
-                    error_panel = Panel(
-                        f"[cyan]{selected_ai}[/cyan] not found\n"
-                        f"Install from: [cyan]{install_url}[/cyan]\n"
-                        f"{agent_config['name']} is required to continue with this project type.\n\n"
-                        "Tip: Use [cyan]--ignore-agent-tools[/cyan] to skip this check",
-                        title="[red]Agent Detection Error[/red]",
-                        border_style="red",
-                        padding=(1, 2)
-                    )
-                    console.print()
-                    console.print(error_panel)
-                    raise typer.Exit(1)
-
-        if script_type:
-            if script_type not in SCRIPT_TYPE_CHOICES:
-                console.print(f"[red]Error:[/red] Invalid script type '{script_type}'. Choose from: {', '.join(SCRIPT_TYPE_CHOICES.keys())}")
-                raise typer.Exit(1)
-            selected_script = script_type
-        else:
-            default_script = "ps" if os.name == "nt" else "sh"
-
-            if _stdin_is_interactive():
-                selected_script = select_with_arrows(SCRIPT_TYPE_CHOICES, "Choose script type (or press Enter)", default_script)
-            else:
-                selected_script = default_script
-
-        console.print(f"[cyan]Selected coding agent integration:[/cyan] {selected_ai}")
-        console.print(f"[cyan]Selected script type:[/cyan] {selected_script}")
-
-        tracker = StepTracker("Initialize Specify Project")
-
-        tracker.add("precheck", "Check required tools")
-        tracker.complete("precheck", "ok")
-        tracker.add("ai-select", "Select coding agent integration")
-        tracker.complete("ai-select", f"{selected_ai}")
-        tracker.add("script-select", "Select script type")
-        tracker.complete("script-select", selected_script)
-
-        tracker.add("integration", "Install integration")
-        tracker.add("shared-infra", "Install shared infrastructure")
-
-        for key, label in [
-            ("chmod", "Ensure scripts executable"),
-            ("constitution", "Constitution setup"),
-            ("git", "Install git extension"),
-            ("workflow", "Install bundled workflow"),
-            ("final", "Finalize"),
-        ]:
-            tracker.add(key, label)
-
-        git_default_notice = False
-
-        with Live(tracker.render(), console=console, refresh_per_second=8, transient=True) as live:
-            tracker.attach_refresh(lambda: live.update(tracker.render()))
-            try:
-                from ..integrations.manifest import IntegrationManifest
-                tracker.start("integration")
-                manifest = IntegrationManifest(
-                    resolved_integration.key, project_path, version=get_speckit_version()
-                )
-
-                integration_parsed_options: dict[str, Any] = {}
-                if ai_commands_dir:
-                    integration_parsed_options["commands_dir"] = ai_commands_dir
-                if ai_skills:
-                    integration_parsed_options["skills"] = True
-                if integration_options:
-                    extra = _parse_integration_options(resolved_integration, integration_options)
-                    if extra:
-                        integration_parsed_options.update(extra)
-
-                resolved_integration.setup(
-                    project_path, manifest,
-                    parsed_options=integration_parsed_options or None,
-                    script_type=selected_script,
-                    raw_options=integration_options,
-                )
-                manifest.save()
-
-                integration_settings = _with_integration_setting(
-                    {},
-                    resolved_integration.key,
-                    resolved_integration,
-                    script_type=selected_script,
-                    raw_options=integration_options,
-                    parsed_options=integration_parsed_options or None,
-                )
-                _write_integration_json(
-                    project_path,
-                    resolved_integration.key,
-                    [resolved_integration.key],
-                    integration_settings,
-                )
-
-                tracker.complete("integration", resolved_integration.config.get("name", resolved_integration.key))
-
-                tracker.start("shared-infra")
-                _install_shared_infra_or_exit(
-                    project_path,
-                    selected_script,
-                    tracker=tracker,
-                    force=force,
-                    invoke_separator=resolved_integration.effective_invoke_separator(integration_parsed_options),
-                )
-                tracker.complete("shared-infra", f"scripts ({selected_script}) + templates")
-
-                ensure_constitution_from_template(project_path, tracker=tracker)
-
-                if not no_git:
-                    tracker.start("git")
-                    git_messages = []
-                    git_has_error = False
-                    if is_git_repo(project_path):
-                        git_messages.append("existing repo detected")
-                    elif should_init_git:
-                        success, error_msg = init_git_repo(project_path, quiet=True)
-                        if success:
-                            git_messages.append("initialized")
-                        else:
-                            git_has_error = True
-                            if error_msg:
-                                sanitized = error_msg.replace('\n', ' ').strip()
-                                git_messages.append(f"init failed: {sanitized[:120]}")
-                            else:
-                                git_messages.append("init failed")
-                    else:
-                        git_messages.append("git not available")
-                    try:
-                        from ..extensions import ExtensionManager
-                        bundled_path = _locate_bundled_extension("git")
-                        if bundled_path:
-                            manager = ExtensionManager(project_path)
-                            if manager.registry.is_installed("git"):
-                                git_messages.append("extension already installed")
-                            else:
-                                manager.install_from_directory(
-                                    bundled_path, get_speckit_version()
-                                )
-                                git_default_notice = True
-                                git_messages.append("extension installed")
-                        else:
-                            git_has_error = True
-                            git_messages.append("bundled extension not found")
-                    except Exception as ext_err:
-                        git_has_error = True
-                        sanitized_ext = str(ext_err).replace('\n', ' ').strip()
-                        git_messages.append(
-                            f"extension install failed: {sanitized_ext[:120]}"
-                        )
-                    summary = "; ".join(git_messages)
-                    if git_has_error:
-                        tracker.error("git", summary)
-                    else:
-                        tracker.complete("git", summary)
-                else:
-                    tracker.skip("git", "--no-git flag")
-
-                try:
-                    bundled_wf = _locate_bundled_workflow("speckit")
-                    if bundled_wf:
-                        from ..workflows.catalog import WorkflowRegistry
-                        from ..workflows.engine import WorkflowDefinition
-                        wf_registry = WorkflowRegistry(project_path)
-                        if wf_registry.is_installed("speckit"):
-                            tracker.complete("workflow", "already installed")
-                        else:
-                            import shutil as _shutil
-                            dest_wf = project_path / ".specify" / "workflows" / "speckit"
-                            dest_wf.mkdir(parents=True, exist_ok=True)
-                            _shutil.copy2(
-                                bundled_wf / "workflow.yml",
-                                dest_wf / "workflow.yml",
-                            )
-                            definition = WorkflowDefinition.from_yaml(dest_wf / "workflow.yml")
-                            wf_registry.add("speckit", {
-                                "name": definition.name,
-                                "version": definition.version,
-                                "description": definition.description,
-                                "source": "bundled",
-                            })
-                            tracker.complete("workflow", "speckit installed")
-                    else:
-                        tracker.skip("workflow", "bundled workflow not found")
-                except Exception as wf_err:
-                    sanitized_wf = str(wf_err).replace('\n', ' ').strip()
-                    tracker.error("workflow", f"install failed: {sanitized_wf[:120]}")
-
-                ensure_executable_scripts(project_path, tracker=tracker)
-
-                init_opts = {
-                    "ai": selected_ai,
-                    "integration": resolved_integration.key,
-                    "branch_numbering": branch_numbering or "sequential",
-                    "context_file": resolved_integration.context_file,
-                    "here": here,
-                    "script": selected_script,
-                    "speckit_version": get_speckit_version(),
-                }
-                from ..integrations.base import SkillsIntegration as _SkillsPersist
-                if isinstance(resolved_integration, _SkillsPersist) or getattr(resolved_integration, "_skills_mode", False):
-                    init_opts["ai_skills"] = True
-                save_init_options(project_path, init_opts)
-
-                if preset:
-                    try:
-                        from ..presets import PresetManager, PresetCatalog, PresetError
-                        preset_manager = PresetManager(project_path)
-                        speckit_ver = get_speckit_version()
-
-                        local_path = Path(preset).resolve()
-                        if local_path.is_dir() and (local_path / "preset.yml").exists():
-                            preset_manager.install_from_directory(local_path, speckit_ver)
-                        else:
-                            bundled_path = _locate_bundled_preset(preset)
-                            if bundled_path:
-                                preset_manager.install_from_directory(bundled_path, speckit_ver)
-                            else:
-                                preset_catalog = PresetCatalog(project_path)
-                                pack_info = preset_catalog.get_pack_info(preset)
-                                if not pack_info:
-                                    console.print(f"[yellow]Warning:[/yellow] Preset '{preset}' not found in catalog. Skipping.")
-                                elif pack_info.get("bundled") and not pack_info.get("download_url"):
-                                    from ..extensions import REINSTALL_COMMAND
-                                    console.print(
-                                        f"[yellow]Warning:[/yellow] Preset '{preset}' is bundled with spec-kit "
-                                        f"but could not be found in the installed package."
-                                    )
-                                    console.print(
-                                        "This usually means the spec-kit installation is incomplete or corrupted."
-                                    )
-                                    console.print(f"Try reinstalling: {REINSTALL_COMMAND}")
-                                else:
-                                    zip_path = None
-                                    try:
-                                        zip_path = preset_catalog.download_pack(preset)
-                                        preset_manager.install_from_zip(zip_path, speckit_ver)
-                                    except PresetError as preset_err:
-                                        _print_cli_warning(
-                                            "install",
-                                            "preset",
-                                            preset,
-                                            preset_err,
-                                            continuing="Continuing without the optional preset.",
-                                        )
-                                    finally:
-                                        if zip_path is not None:
-                                            try:
-                                                zip_path.unlink(missing_ok=True)
-                                            except OSError:
-                                                pass
-                    except Exception as preset_err:
-                        _print_cli_warning(
-                            "install",
-                            "preset",
-                            preset,
-                            preset_err,
-                            continuing="Continuing without the optional preset.",
-                        )
-
-                tracker.complete("final", "project ready")
-            except (typer.Exit, SystemExit):
-                raise
-            except Exception as e:
-                tracker.error("final", str(e))
-                console.print(Panel(f"Initialization failed: {e}", title="Failure", border_style="red"))
-                if debug:
-                    _env_pairs = [
-                        ("Python", sys.version.split()[0]),
-                        ("Platform", sys.platform),
-                        ("CWD", str(Path.cwd())),
-                    ]
-                    _label_width = max(len(k) for k, _ in _env_pairs)
-                    env_lines = [f"{k.ljust(_label_width)} → [bright_black]{v}[/bright_black]" for k, v in _env_pairs]
-                    console.print(Panel("\n".join(env_lines), title="Debug Environment", border_style="magenta"))
-                if not here and project_path.exists() and not dir_existed_before:
-                    shutil.rmtree(project_path)
-                raise typer.Exit(1)
-            finally:
-                pass
-
-        console.print(tracker.render())
-        console.print("\n[bold green]Project ready.[/bold green]")
-
-        agent_config = AGENT_CONFIG.get(selected_ai)
-        if agent_config:
-            agent_folder = ai_commands_dir if selected_ai == "generic" else agent_config["folder"]
-            if agent_folder:
-                security_notice = Panel(
-                    f"Some agents may store credentials, auth tokens, or other identifying and private artifacts in the agent folder within your project.\n"
-                    f"Consider adding [cyan]{agent_folder}[/cyan] (or parts of it) to [cyan].gitignore[/cyan] to prevent accidental credential leakage.",
-                    title="[yellow]Agent Folder Security[/yellow]",
-                    border_style="yellow",
-                    padding=(1, 2)
-                )
-                console.print()
-                console.print(security_notice)
-
-        if ai_deprecation_warning:
-            deprecation_notice = Panel(
-                ai_deprecation_warning,
-                title="[bold red]Deprecation Warning[/bold red]",
-                border_style="red",
-                padding=(1, 2),
-            )
-            console.print()
-            console.print(deprecation_notice)
-
-        if git_default_notice:
-            default_change_notice = Panel(
-                "The git extension is currently enabled by default during [bold]specify init[/bold].\n"
-                "Starting in [bold]v0.10.0[/bold], this will require explicit opt-in.\n"
-                "Use [bold]specify extension add git[/bold] after init when needed.",
-                title="[yellow]Notice: Git Default Changing[/yellow]",
-                border_style="yellow",
-                padding=(1, 2),
-            )
-            console.print()
-            console.print(default_change_notice)
-
-        steps_lines = []
-        if not here:
-            steps_lines.append(f"1. Go to the project folder: [cyan]cd {project_name}[/cyan]")
-            step_num = 2
-        else:
-            steps_lines.append("1. You're already in the project directory!")
-            step_num = 2
-
-        from ..integrations.base import SkillsIntegration as _SkillsInt
-        _is_skills_integration = isinstance(resolved_integration, _SkillsInt) or getattr(resolved_integration, "_skills_mode", False)
-
-        codex_skill_mode = selected_ai == "codex" and (ai_skills or _is_skills_integration)
-        claude_skill_mode = selected_ai == "claude" and (ai_skills or _is_skills_integration)
-        kimi_skill_mode = selected_ai == "kimi"
-        agy_skill_mode = selected_ai == "agy" and _is_skills_integration
-        trae_skill_mode = selected_ai == "trae"
-        cursor_agent_skill_mode = selected_ai == "cursor-agent" and (ai_skills or _is_skills_integration)
-        copilot_skill_mode = selected_ai == "copilot" and _is_skills_integration
-        devin_skill_mode = selected_ai == "devin"
-        native_skill_mode = codex_skill_mode or claude_skill_mode or kimi_skill_mode or agy_skill_mode or trae_skill_mode or cursor_agent_skill_mode or copilot_skill_mode or devin_skill_mode
-
-        if codex_skill_mode and not ai_skills:
-            steps_lines.append(f"{step_num}. Start Codex in this project directory; spec-kit skills were installed to [cyan].agents/skills[/cyan]")
-            step_num += 1
-        if claude_skill_mode and not ai_skills:
-            steps_lines.append(f"{step_num}. Start Claude in this project directory; spec-kit skills were installed to [cyan].claude/skills[/cyan]")
-            step_num += 1
-        if cursor_agent_skill_mode and not ai_skills:
-            steps_lines.append(f"{step_num}. Start Cursor Agent in this project directory; spec-kit skills were installed to [cyan].cursor/skills[/cyan]")
-            step_num += 1
-        if devin_skill_mode:
-            steps_lines.append(f"{step_num}. Start Devin in this project directory; spec-kit skills were installed to [cyan].devin/skills[/cyan]")
-            step_num += 1
-        usage_label = "skills" if native_skill_mode else "slash commands"
-
-        def _display_cmd(name: str) -> str:
-            if codex_skill_mode or agy_skill_mode or trae_skill_mode:
-                return f"$speckit-{name}"
-            if claude_skill_mode:
-                return f"/speckit-{name}"
-            if kimi_skill_mode:
-                return f"/skill:speckit-{name}"
-            if cursor_agent_skill_mode or copilot_skill_mode or devin_skill_mode:
-                return f"/speckit-{name}"
-            return f"/speckit.{name}"
-
-        steps_lines.append(f"{step_num}. Start using {usage_label} with your coding agent:")
-
-        steps_lines.append(f"   {step_num}.1 [cyan]{_display_cmd('constitution')}[/] - Establish project principles")
-        steps_lines.append(f"   {step_num}.2 [cyan]{_display_cmd('specify')}[/] - Create baseline specification")
-        steps_lines.append(f"   {step_num}.3 [cyan]{_display_cmd('plan')}[/] - Create implementation plan")
-        steps_lines.append(f"   {step_num}.4 [cyan]{_display_cmd('tasks')}[/] - Generate actionable tasks")
-        steps_lines.append(f"   {step_num}.5 [cyan]{_display_cmd('implement')}[/] - Execute implementation")
-
-        steps_panel = Panel("\n".join(steps_lines), title="Next Steps", border_style="cyan", padding=(1, 2))
-        console.print()
-        console.print(steps_panel)
-
-        enhancement_intro = (
-            "Optional skills that you can use for your specs [bright_black](improve quality & confidence)[/bright_black]"
-            if native_skill_mode
-            else "Optional commands that you can use for your specs [bright_black](improve quality & confidence)[/bright_black]"
-        )
-        enhancement_lines = [
-            enhancement_intro,
-            "",
-            f"○ [cyan]{_display_cmd('clarify')}[/] [bright_black](optional)[/bright_black] - Ask structured questions to de-risk ambiguous areas before planning (run before [cyan]{_display_cmd('plan')}[/] if used)",
-            f"○ [cyan]{_display_cmd('analyze')}[/] [bright_black](optional)[/bright_black] - Cross-artifact consistency & alignment report (after [cyan]{_display_cmd('tasks')}[/], before [cyan]{_display_cmd('implement')}[/])",
-            f"○ [cyan]{_display_cmd('checklist')}[/] [bright_black](optional)[/bright_black] - Generate quality checklists to validate requirements completeness, clarity, and consistency (after [cyan]{_display_cmd('plan')}[/])"
-        ]
-        enhancements_title = "Enhancement Skills" if native_skill_mode else "Enhancement Commands"
-        enhancements_panel = Panel("\n".join(enhancement_lines), title=enhancements_title, border_style="cyan", padding=(1, 2))
-        console.print()
-        console.print(enhancements_panel)
--- a/src/specify_cli/commands/integration.py
+++ b/src/specify_cli/commands/integration.py
@@ -1,2 +0,0 @@
-"""specify integration * commands — placeholder for future extraction."""
-from __future__ import annotations
--- a/src/specify_cli/commands/preset.py
+++ b/src/specify_cli/commands/preset.py
@@ -1,2 +0,0 @@
-"""specify preset * commands — placeholder for future extraction."""
-from __future__ import annotations
--- a/src/specify_cli/commands/workflow.py
+++ b/src/specify_cli/commands/workflow.py
@@ -1,2 +0,0 @@
-"""specify workflow * commands — placeholder for future extraction."""
-from __future__ import annotations
--- a/src/specify_cli/extensions.py
+++ b/src/specify_cli/extensions.py
@@ -25,8 +25,6 @@ import yaml
 from packaging import version as pkg_version
 from packaging.specifiers import SpecifierSet, InvalidSpecifier

-from .catalogs import CatalogEntry as BaseCatalogEntry, CatalogStackBase
-
 _FALLBACK_CORE_COMMAND_NAMES = frozenset({
    "analyze",
    "checklist",
@@ -109,8 +107,13 @@ def normalize_priority(value: Any, default: int = 10) -> int:


@dataclass
-class CatalogEntry(BaseCatalogEntry):
+class CatalogEntry:
    """Represents a single catalog entry in the catalog stack."""
+    url: str
+    name: str
+    priority: int
+    install_allowed: bool
+    description: str = ""


 class ExtensionManifest:
@@ -801,29 +804,42 @@ class ExtensionManager:
    def _get_skills_dir(self) -> Optional[Path]:
        """Return the active skills directory for extension skill registration.

-        Delegates to :func:`resolve_active_skills_dir` which reads
-        init-options, applies the Kimi native-skills fallback, and
-        safely creates the directory when ``ai_skills`` is enabled.
+        Reads ``.specify/init-options.json`` to determine whether skills
+        are enabled and which agent was selected, then delegates to
+        the module-level ``_get_skills_dir()`` helper for the concrete path.

-        Returns ``None`` (instead of raising) when the directory cannot
-        be created due to symlink, containment, or permission issues so
-        that callers can fall back gracefully.
+        Kimi is treated as a native-skills agent: if ``ai == "kimi"`` and
+        ``.kimi/skills`` exists, extension installs should still propagate
+        command skills even when ``ai_skills`` is false.
+
+        Returns:
+            The skills directory ``Path``, or ``None`` if skills were not
+            enabled and no native-skills fallback applies.
        """
-        from . import resolve_active_skills_dir, _print_cli_warning
-        try:
-            return resolve_active_skills_dir(self.project_root)
-        except (ValueError, OSError) as exc:
-            _print_cli_warning(
-                "resolve", "skills directory", None, exc,
-                continuing="Continuing without skill registration.",
-            )
+        from . import load_init_options, _get_skills_dir as resolve_skills_dir
+
+        opts = load_init_options(self.project_root)
+        if not isinstance(opts, dict):
+            opts = {}
+
+        agent = opts.get("ai")
+        if not isinstance(agent, str) or not agent:
            return None

+        ai_skills_enabled = bool(opts.get("ai_skills"))
+        if not ai_skills_enabled and agent != "kimi":
+            return None
+
+        skills_dir = resolve_skills_dir(self.project_root, agent)
+        if not skills_dir.is_dir():
+            return None
+
+        return skills_dir
+
    def _register_extension_skills(
        self,
        manifest: ExtensionManifest,
        extension_dir: Path,
-        link_outputs: bool = False,
    ) -> List[str]:
        """Generate SKILL.md files for extension commands as agent skills.

@@ -835,8 +851,6 @@ class ExtensionManager:
        Args:
            manifest: Extension manifest.
            extension_dir: Installed extension directory.
-            link_outputs: If True, create dev-mode symlinks for rendered
-                skill files when supported by the OS.

        Returns:
            List of skill names that were created (for registry storage).
@@ -889,18 +903,9 @@ class ExtensionManager:
            # Check if skill already exists before creating the directory
            skill_subdir = skills_dir / skill_name
            skill_file = skill_subdir / "SKILL.md"
-            cache_root = extension_dir / ".specify-dev" / "extension-skills"
-            cache_file = cache_root / skill_name / "SKILL.md"
-            CommandRegistrar._ensure_inside(cache_file, cache_root)
-            if skill_file.exists() or skill_file.is_symlink():
-                # Do not overwrite user-customized skills, but allow dev-mode
-                # symlinks that point back to this extension's generated cache
-                # to be refreshed on a subsequent dev install.
-                if not (
-                    link_outputs
-                    and self._is_expected_dev_symlink(skill_file, cache_file)
-                ):
-                    continue
+            if skill_file.exists():
+                # Do not overwrite user-customized skills
+                continue

            # Create skill directory; track whether we created it so we can clean
            # up safely if reading the source file subsequently fails.
@@ -952,35 +957,11 @@ class ExtensionManager:
                    skill_content
                )

-            if link_outputs:
-                try:
-                    cache_file.parent.mkdir(parents=True, exist_ok=True)
-                    cache_file.write_text(skill_content, encoding="utf-8")
-                    if skill_file.exists() or skill_file.is_symlink():
-                        skill_file.unlink()
-                    target = os.path.relpath(cache_file, skill_file.parent)
-                    os.symlink(target, skill_file)
-                except (OSError, ValueError):
-                    if skill_file.is_symlink():
-                        skill_file.unlink()
-                    skill_file.write_text(skill_content, encoding="utf-8")
-            else:
-                skill_file.write_text(skill_content, encoding="utf-8")
+            skill_file.write_text(skill_content, encoding="utf-8")
            written.append(skill_name)

        return written

-    @staticmethod
-    def _is_expected_dev_symlink(skill_file: Path, cache_file: Path) -> bool:
-        """Return True when an existing skill file links to its dev cache."""
-        if not skill_file.is_symlink():
-            return False
-
-        try:
-            return skill_file.resolve(strict=False) == cache_file.resolve(strict=False)
-        except OSError:
-            return False
-
    def _unregister_extension_skills(
        self,
        skill_names: List[str],
@@ -1151,7 +1132,6 @@ class ExtensionManager:
        speckit_version: str,
        register_commands: bool = True,
        priority: int = 10,
-        link_commands: bool = False,
    ) -> ExtensionManifest:
        """Install extension from a local directory.

@@ -1160,8 +1140,6 @@ class ExtensionManager:
            speckit_version: Current spec-kit version
            register_commands: If True, register commands with AI agents
            priority: Resolution priority (lower = higher precedence, default 10)
-            link_commands: If True, register rendered agent artifacts as
-                symlinks to a dev cache when supported by the OS.

        Returns:
            Installed extension manifest
@@ -1205,16 +1183,14 @@ class ExtensionManager:
            registrar = CommandRegistrar()
            # Register for all detected agents
            registered_commands = registrar.register_commands_for_all_agents(
-                manifest, dest_dir, self.project_root, link_outputs=link_commands
+                manifest, dest_dir, self.project_root
            )

        # Auto-register extension commands as agent skills when --ai-skills
        # was used during project initialisation (feature parity).
-        registered_skills = self._register_extension_skills(
-            manifest, dest_dir, link_outputs=link_commands
-        )
+        registered_skills = self._register_extension_skills(manifest, dest_dir)

-        # Register hooks and update installed list in extensions.yml
+        # Register hooks
        hook_executor = HookExecutor(self.project_root)
        hook_executor.register_hooks(manifest)

@@ -1648,8 +1624,7 @@ class CommandRegistrar:
        agent_name: str,
        manifest: ExtensionManifest,
        extension_dir: Path,
-        project_root: Path,
-        link_outputs: bool = False,
+        project_root: Path
    ) -> List[str]:
        """Register extension commands for a specific agent."""
        if agent_name not in self.AGENT_CONFIGS:
@@ -1657,23 +1632,20 @@ class CommandRegistrar:
        context_note = f"\n<!-- Extension: {manifest.id} -->\n<!-- Config: .specify/extensions/{manifest.id}/ -->\n"
        return self._registrar.register_commands(
            agent_name, manifest.commands, manifest.id, extension_dir, project_root,
-            context_note=context_note,
-            link_outputs=link_outputs,
+            context_note=context_note
        )

    def register_commands_for_all_agents(
        self,
        manifest: ExtensionManifest,
        extension_dir: Path,
-        project_root: Path,
-        link_outputs: bool = False,
+        project_root: Path
    ) -> Dict[str, List[str]]:
        """Register extension commands for all detected agents."""
        context_note = f"\n<!-- Extension: {manifest.id} -->\n<!-- Config: .specify/extensions/{manifest.id}/ -->\n"
        return self._registrar.register_commands_for_all_agents(
            manifest.commands, manifest.id, extension_dir, project_root,
-            context_note=context_note,
-            link_outputs=link_outputs,
+            context_note=context_note
        )

    def unregister_commands(
@@ -1688,25 +1660,18 @@ class CommandRegistrar:
        self,
        manifest: ExtensionManifest,
        extension_dir: Path,
-        project_root: Path,
-        link_outputs: bool = False,
+        project_root: Path
    ) -> List[str]:
        """Register extension commands for Claude Code agent."""
-        return self.register_commands_for_agent(
-            "claude", manifest, extension_dir, project_root, link_outputs=link_outputs
-        )
+        return self.register_commands_for_agent("claude", manifest, extension_dir, project_root)


-class ExtensionCatalog(CatalogStackBase):
+class ExtensionCatalog:
    """Manages extension catalog fetching, caching, and searching."""

    DEFAULT_CATALOG_URL = "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.json"
    COMMUNITY_CATALOG_URL = "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.community.json"
    CACHE_DURATION = 3600  # 1 hour in seconds
-    CONFIG_FILENAME = "extension-catalogs.yml"
-    ENTRY_CLASS = CatalogEntry
-    ERROR_TYPE = ValidationError
-    VALIDATION_ERROR_TYPE = ValidationError

    def __init__(self, project_root: Path):
        """Initialize extension catalog manager.
@@ -1720,21 +1685,117 @@ class ExtensionCatalog(CatalogStackBase):
        self.cache_file = self.cache_dir / "catalog.json"
        self.cache_metadata_file = self.cache_dir / "catalog-metadata.json"

-    def _make_request(self, url: str):
-        """Build a urllib Request, adding auth headers when a provider matches.
+    def _validate_catalog_url(self, url: str) -> None:
+        """Validate that a catalog URL uses HTTPS (localhost HTTP allowed).

-        Delegates to :func:`specify_cli.authentication.http.build_request`.
+        Args:
+            url: URL to validate
+
+        Raises:
+            ValidationError: If URL is invalid or uses non-HTTPS scheme
        """
-        from specify_cli.authentication.http import build_request
-        return build_request(url)
+        from urllib.parse import urlparse
+
+        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 ValidationError(
+                f"Catalog URL must use HTTPS (got {parsed.scheme}://). "
+                "HTTP is only allowed for localhost."
+            )
+        if not parsed.netloc:
+            raise ValidationError("Catalog URL must be a valid URL with a host.")
+
+    def _make_request(self, url: str):
+        """Build a urllib Request, adding a GitHub auth header when available.
+
+        Delegates to :func:`specify_cli._github_http.build_github_request`.
+        """
+        from specify_cli._github_http import build_github_request
+        return build_github_request(url)

    def _open_url(self, url: str, timeout: int = 10):
-        """Open a URL with provider-based auth, trying each configured provider.
+        """Open a URL with GitHub auth, stripping the header on cross-host redirects.

-        Delegates to :func:`specify_cli.authentication.http.open_url`.
+        Delegates to :func:`specify_cli._github_http.open_github_url`.
        """
-        from specify_cli.authentication.http import open_url
-        return open_url(url, timeout)
+        from specify_cli._github_http import open_github_url
+        return open_github_url(url, timeout)
+
+    def _load_catalog_config(self, config_path: Path) -> Optional[List[CatalogEntry]]:
+        """Load catalog stack configuration from a YAML file.
+
+        Args:
+            config_path: Path to extension-catalogs.yml
+
+        Returns:
+            Ordered list of CatalogEntry objects, or None if file doesn't exist.
+
+        Raises:
+            ValidationError: If any catalog entry has an invalid URL,
+                the file cannot be parsed, a priority value is invalid,
+                or the file exists but contains no valid catalog entries
+                (fail-closed for security).
+        """
+        if not config_path.exists():
+            return None
+        try:
+            data = yaml.safe_load(config_path.read_text(encoding="utf-8")) or {}
+        except (yaml.YAMLError, OSError, UnicodeError) as e:
+            raise ValidationError(
+                f"Failed to read catalog config {config_path}: {e}"
+            )
+        catalogs_data = data.get("catalogs", [])
+        if not catalogs_data:
+            # File exists but has no catalogs key or empty list - fail closed
+            raise ValidationError(
+                f"Catalog config {config_path} exists but contains no 'catalogs' entries. "
+                f"Remove the file to use built-in defaults, or add valid catalog entries."
+            )
+        if not isinstance(catalogs_data, list):
+            raise ValidationError(
+                f"Invalid catalog config: 'catalogs' must be a list, got {type(catalogs_data).__name__}"
+            )
+        entries: List[CatalogEntry] = []
+        skipped_entries: List[int] = []
+        for idx, item in enumerate(catalogs_data):
+            if not isinstance(item, dict):
+                raise ValidationError(
+                    f"Invalid catalog entry at index {idx}: expected a mapping, got {type(item).__name__}"
+                )
+            url = str(item.get("url", "")).strip()
+            if not url:
+                skipped_entries.append(idx)
+                continue
+            self._validate_catalog_url(url)
+            try:
+                priority = int(item.get("priority", idx + 1))
+            except (TypeError, ValueError):
+                raise ValidationError(
+                    f"Invalid priority for catalog '{item.get('name', idx + 1)}': "
+                    f"expected integer, got {item.get('priority')!r}"
+                )
+            raw_install = item.get("install_allowed", False)
+            if isinstance(raw_install, str):
+                install_allowed = raw_install.strip().lower() in ("true", "yes", "1")
+            else:
+                install_allowed = bool(raw_install)
+            entries.append(CatalogEntry(
+                url=url,
+                name=str(item.get("name", f"catalog-{idx + 1}")),
+                priority=priority,
+                install_allowed=install_allowed,
+                description=str(item.get("description", "")),
+            ))
+        entries.sort(key=lambda e: e.priority)
+        if not entries:
+            # All entries were invalid (missing URLs) - fail closed for security
+            raise ValidationError(
+                f"Catalog config {config_path} contains {len(catalogs_data)} entries but none have valid URLs "
+                f"(entries at indices {skipped_entries} were skipped). "
+                f"Each catalog entry must have a 'url' field."
+            )
+        return entries

    def get_active_catalogs(self) -> List[CatalogEntry]:
        """Get the ordered list of active catalogs.
@@ -1765,44 +1826,24 @@ class ExtensionCatalog(CatalogStackBase):
                        file=sys.stderr,
                    )
                    self._non_default_catalog_warning_shown = True
-            return [
-                self._entry(
-                    url=catalog_url,
-                    name="custom",
-                    priority=1,
-                    install_allowed=True,
-                    description="Custom catalog via SPECKIT_CATALOG_URL",
-                )
-            ]
+            return [CatalogEntry(url=catalog_url, name="custom", priority=1, install_allowed=True, description="Custom catalog via SPECKIT_CATALOG_URL")]

        # 2. Project-level config overrides all defaults
-        project_config_path = self.project_root / ".specify" / self.CONFIG_FILENAME
+        project_config_path = self.project_root / ".specify" / "extension-catalogs.yml"
        catalogs = self._load_catalog_config(project_config_path)
        if catalogs is not None:
            return catalogs

        # 3. User-level config
-        user_config_path = Path.home() / ".specify" / self.CONFIG_FILENAME
+        user_config_path = Path.home() / ".specify" / "extension-catalogs.yml"
        catalogs = self._load_catalog_config(user_config_path)
        if catalogs is not None:
            return catalogs

        # 4. Built-in default stack
        return [
-            self._entry(
-                url=self.DEFAULT_CATALOG_URL,
-                name="default",
-                priority=1,
-                install_allowed=True,
-                description="Built-in catalog of installable extensions",
-            ),
-            self._entry(
-                url=self.COMMUNITY_CATALOG_URL,
-                name="community",
-                priority=2,
-                install_allowed=False,
-                description="Community-contributed extensions (discovery only)",
-            ),
+            CatalogEntry(url=self.DEFAULT_CATALOG_URL, name="default", priority=1, install_allowed=True, description="Built-in catalog of installable extensions"),
+            CatalogEntry(url=self.COMMUNITY_CATALOG_URL, name="community", priority=2, install_allowed=False, description="Community-contributed extensions (discovery only)"),
        ]

    def get_catalog_url(self) -> str:
@@ -2440,32 +2481,7 @@ class HookExecutor:
            }

        try:
-            result = yaml.safe_load(self.config_file.read_text(encoding="utf-8"))
-            # Coerce non-dict root (including None for an empty file) to the
-            # fully-normalized default so callers always get guaranteed fields.
-            if not isinstance(result, dict):
-                return {
-                    "installed": [],
-                    "settings": {"auto_execute_hooks": True},
-                    "hooks": {},
-                }
-            # Normalize nested fields so read-only callers like get_hooks_for_event()
-            # never see non-dict hooks or non-list installed (Feedback)
-            if not isinstance(result.get("hooks"), dict):
-                result["hooks"] = {}
-            if not isinstance(result.get("installed"), list):
-                result["installed"] = []
-            if not isinstance(result.get("settings"), dict):
-                result["settings"] = {"auto_execute_hooks": True}
-            # Sanitize hook event values: coerce non-list values to [] and filter
-            # non-dict items so get_hooks_for_event() can safely call .get() (Feedback)
-            for event_key in list(result["hooks"]):
-                event_val = result["hooks"][event_key]
-                if not isinstance(event_val, list):
-                    result["hooks"][event_key] = []
-                else:
-                    result["hooks"][event_key] = [h for h in event_val if isinstance(h, dict)]
-            return result
+            return yaml.safe_load(self.config_file.read_text(encoding="utf-8")) or {}
        except (yaml.YAMLError, OSError, UnicodeError):
            return {
                "installed": [],
@@ -2485,141 +2501,25 @@ class HookExecutor:
            encoding="utf-8",
        )

-    def register_extension(self, extension_id: str):
-        """Add extension to the installed list in project config.
-
-        Args:
-            extension_id: ID of extension to register
-        """
-        config = self.get_project_config()
-
-        # Ensure config is a dict (defensive)
-        if not isinstance(config, dict):
-            config = {}
-
-        raw_installed = config.get("installed")
-        sanitized = self._sanitize_installed_list(raw_installed, add_id=extension_id)
-
-        if sanitized != raw_installed:
-            config["installed"] = sanitized
-            self.save_project_config(config)
-
-    def unregister_extension(self, extension_id: str):
-        """Remove extension from the installed list in project config.
-
-        Args:
-            extension_id: ID of extension to unregister
-        """
-        config = self.get_project_config()
-
-        if not isinstance(config, dict):
-            config = {}
-
-        raw_installed = config.get("installed")
-        sanitized = self._sanitize_installed_list(raw_installed, remove_id=extension_id)
-
-        # Always persist if sanitized state differs from raw config (ensures normalization)
-        if sanitized != raw_installed:
-            config["installed"] = sanitized
-            self.save_project_config(config)
-
-    @staticmethod
-    def _sanitize_installed_list(
-        raw: object,
-        *,
-        add_id: str = "",
-        remove_id: str = "",
-    ) -> list:
-        """Normalize, deduplicate, and optionally add/remove an extension id.
-
-        Shared by register_extension() and unregister_extension() to prevent
-        the two paths from drifting.
-
-        Args:
-            raw: The raw value from config["installed"] (may be non-list).
-            add_id: If non-empty, ensure this id is present (plain-string fallback).
-            remove_id: If non-empty, remove this id from the list.
-
-        Returns:
-            A sanitized, deduplicated, alphabetically-sorted list.
-        """
-        _VALID_ID = re.compile(r'^[a-z0-9-]+$')
-
-        installed = raw if isinstance(raw, list) else []
-
-        # Keep only entries whose resolved id is a non-empty string matching
-        # the extension-id format (^[a-z0-9-]+$), same rule ExtensionManifest enforces.
-        def _valid_entry(x: object) -> bool:
-            if isinstance(x, str):
-                return bool(_VALID_ID.match(x.strip()))
-            if isinstance(x, dict):
-                eid = x.get("id")
-                return isinstance(eid, str) and bool(_VALID_ID.match(eid.strip()))
-            return False
-
-        valid = [x for x in installed if _valid_entry(x)]
-
-        # Deduplicate by id: prefer dict (richer metadata) over plain string
-        seen: dict = {}  # id -> entry (dict preferred over str)
-        for x in valid:
-            eid = x.strip() if isinstance(x, str) else x.get("id", "").strip()
-            if eid not in seen or isinstance(x, dict):
-                seen[eid] = x
-
-        # Validate add_id against the same regex before inserting
-        if add_id and _VALID_ID.match(add_id.strip()) and add_id not in seen:
-            seen[add_id] = add_id
-
-        if remove_id:
-            seen.pop(remove_id, None)
-
-        def _sort_key(x: object) -> str:
-            return x if isinstance(x, str) else x.get("id", "")  # type: ignore[return-value]
-
-        return sorted(seen.values(), key=_sort_key)
-
    def register_hooks(self, manifest: ExtensionManifest):
        """Register extension hooks in project config.

        Args:
            manifest: Extension manifest with hooks to register
        """
-        # Always ensure the extension is in the installed list
-        self.register_extension(manifest.id)
-
        if not hasattr(manifest, "hooks") or not manifest.hooks:
            return

        config = self.get_project_config()

-        # Ensure config is a dict (defensive)
-        changed = False
-        if not isinstance(config, dict):
-            config = {}
-            changed = True
-
-        # Ensure hooks dict exists and is a mapping
-        if "hooks" not in config or not isinstance(config["hooks"], dict):
+        # Ensure hooks dict exists
+        if "hooks" not in config:
            config["hooks"] = {}
-            changed = True
-        else:
-            # Sanitize existing hook lists to prevent crashes in downstream code (Feedback)
-            for h_name in list(config["hooks"].keys()):
-                h_list = config["hooks"][h_name]
-                if not isinstance(h_list, list):
-                    config["hooks"][h_name] = []
-                    changed = True
-                else:
-                    sanitized_h_list = [h for h in h_list if isinstance(h, dict)]
-                    if len(sanitized_h_list) != len(h_list):
-                        config["hooks"][h_name] = sanitized_h_list
-                        changed = True

        # Register each hook
        for hook_name, hook_config in manifest.hooks.items():
-            if hook_name not in config["hooks"] or not isinstance(config["hooks"][hook_name], list):
+            if hook_name not in config["hooks"]:
                config["hooks"][hook_name] = []
-                changed = True

            # Add hook entry
            hook_entry = {
@@ -2634,22 +2534,22 @@ class HookExecutor:
                "condition": hook_config.get("condition"),
            }

-            # Deduplicate: remove all existing entries for this extension on this
-            # hook event, then append the single canonical entry. This prevents
-            # multiple hooks firing when hand-edited or older versions leave
-            # duplicate entries behind. (Feedback from review)
-            original_list = config["hooks"][hook_name]
-            deduped = [
-                h for h in original_list
-                if not (isinstance(h, dict) and h.get("extension") == manifest.id)
+            # Check if already registered
+            existing = [
+                h
+                for h in config["hooks"][hook_name]
+                if h.get("extension") == manifest.id
            ]
-            deduped.append(hook_entry)
-            if deduped != original_list:
-                config["hooks"][hook_name] = deduped
-                changed = True

-        if changed:
-            self.save_project_config(config)
+            if not existing:
+                config["hooks"][hook_name].append(hook_entry)
+            else:
+                # Update existing
+                for i, h in enumerate(config["hooks"][hook_name]):
+                    if h.get("extension") == manifest.id:
+                        config["hooks"][hook_name][i] = hook_entry
+
+        self.save_project_config(config)

    def unregister_hooks(self, extension_id: str):
        """Remove extension hooks from project config.
@@ -2657,30 +2557,17 @@ class HookExecutor:
        Args:
            extension_id: ID of extension to unregister
        """
-        # Always remove from installed list (Feedback from review)
-        self.unregister_extension(extension_id)
-
        config = self.get_project_config()

-        if not isinstance(config, dict):
-            config = {}
-            # We don't save yet, as there are no hooks to unregister, 
-            # but unregister_extension above might have already saved a normalized config.
-            return
-
-        if "hooks" not in config or not isinstance(config["hooks"], dict):
+        if "hooks" not in config:
            return

        # Remove hooks for this extension
-        for hook_name in list(config["hooks"].keys()):
-            hook_list = config["hooks"][hook_name]
-            if not isinstance(hook_list, list):
-                config["hooks"][hook_name] = []
-                continue
+        for hook_name in config["hooks"]:
            config["hooks"][hook_name] = [
                h
-                for h in hook_list
-                if isinstance(h, dict) and h.get("extension") != extension_id
+                for h in config["hooks"][hook_name]
+                if h.get("extension") != extension_id
            ]

        # Clean up empty hook arrays
--- a/src/specify_cli/integration_state.py
+++ b/src/specify_cli/integration_state.py
@@ -3,7 +3,6 @@
 from __future__ import annotations

 import json
-from dataclasses import dataclass
 from pathlib import Path
 from typing import Any

@@ -12,67 +11,6 @@ INTEGRATION_JSON = ".specify/integration.json"
 INTEGRATION_STATE_SCHEMA = 1


-@dataclass(frozen=True)
-class IntegrationReadError:
-    """Structured failure from :func:`try_read_integration_json`.
-
-    Callers map ``kind`` to whatever surface they need (loud CLI error,
-    silent fallback, etc.) without re-implementing the parse/validation logic.
-    """
-
-    kind: str  # "decode", "os", "not_object", "schema_too_new"
-    detail: str = ""
-    schema: int | None = None
-
-
-def try_read_integration_json(
-    project_root: Path,
-) -> tuple[dict[str, Any] | None, IntegrationReadError | None]:
-    """Parse ``.specify/integration.json`` without raising.
-
-    Returns ``(normalized_state, None)`` on success, ``(None, None)`` when the
-    file does not exist, or ``(None, error)`` for any parse / validation
-    failure. This is the single low-level reader; both the CLI's loud
-    ``_read_integration_json`` and the workflow engine's silent
-    ``_load_project_integration`` consume it so the schema guard and parse
-    logic cannot drift between them.
-    """
-    path = project_root / INTEGRATION_JSON
-    # Avoid Path.exists() / Path.is_file() as a pre-check: both return False
-    # on some OSErrors (e.g. permission errors during stat), which would
-    # silently treat an unreadable-but-present file as missing. Attempt the
-    # read directly and distinguish FileNotFoundError (genuinely absent) from
-    # other OSErrors (which become loud errors via the IntegrationReadError
-    # path).
-    try:
-        raw = path.read_text(encoding="utf-8")
-    except FileNotFoundError:
-        return None, None
-    except IsADirectoryError as exc:
-        return None, IntegrationReadError(
-            kind="os",
-            detail=f"{path} exists but is not a regular file: {exc}",
-        )
-    except UnicodeDecodeError as exc:
-        return None, IntegrationReadError(kind="decode", detail=str(exc))
-    except OSError as exc:
-        return None, IntegrationReadError(kind="os", detail=str(exc))
-    try:
-        data = json.loads(raw)
-    except json.JSONDecodeError as exc:
-        return None, IntegrationReadError(kind="decode", detail=str(exc))
-    if not isinstance(data, dict):
-        return None, IntegrationReadError(kind="not_object", detail=type(data).__name__)
-    schema = data.get("integration_state_schema")
-    if (
-        isinstance(schema, int)
-        and not isinstance(schema, bool)
-        and schema > INTEGRATION_STATE_SCHEMA
-    ):
-        return None, IntegrationReadError(kind="schema_too_new", schema=schema)
-    return normalize_integration_state(data), None
-
-
 def clean_integration_key(key: Any) -> str | None:
    """Return a stripped integration key, or None for empty/non-string values."""
    if not isinstance(key, str) or not key.strip():
--- a/src/specify_cli/integrations/init.py
+++ b/src/specify_cli/integrations/init.py
@@ -61,7 +61,6 @@ def _register_builtins() -> None:
    from .gemini import GeminiIntegration
    from .generic import GenericIntegration
    from .goose import GooseIntegration
-    from .hermes import HermesIntegration
    from .iflow import IflowIntegration
    from .junie import JunieIntegration
    from .kilocode import KilocodeIntegration
@@ -94,7 +93,6 @@ def _register_builtins() -> None:
    _register(GeminiIntegration())
    _register(GenericIntegration())
    _register(GooseIntegration())
-    _register(HermesIntegration())
    _register(IflowIntegration())
    _register(JunieIntegration())
    _register(KilocodeIntegration())
--- a/src/specify_cli/integrations/agy/init.py
+++ b/src/specify_cli/integrations/agy/init.py
@@ -5,7 +5,6 @@ Antigravity uses ``.agents/skills/speckit-<name>/SKILL.md`` layout (enforced sin

 from __future__ import annotations

-import re
 from pathlib import Path
 from typing import TYPE_CHECKING, Any

@@ -14,15 +13,6 @@ from ..base import SkillsIntegration
 if TYPE_CHECKING:
    from ..manifest import IntegrationManifest

-# Note injected into hook sections so agy maps dot-notation command
-# names (from extensions.yml) to the hyphenated skill names it uses.
-# Without this, agy emits ``/speckit.git.commit`` (which does not
-# resolve) instead of ``/speckit-git-commit``.
-_HOOK_COMMAND_NOTE = (
-    "- When constructing slash commands from hook command names, "
-    "replace dots (`.`) with hyphens (`-`). "
-    "For example, `speckit.git.commit` → `/speckit-git-commit`.\n"
-)


 class AgyIntegration(SkillsIntegration):
@@ -33,8 +23,8 @@ class AgyIntegration(SkillsIntegration):
        "name": "Antigravity",
        "folder": ".agents/",
        "commands_subdir": "skills",
-        "install_url": "https://antigravity.google/",
-        "requires_cli": True,
+        "install_url": None,
+        "requires_cli": False,
    }
    registrar_config = {
        "dir": ".agents/skills",
@@ -44,54 +34,6 @@ class AgyIntegration(SkillsIntegration):
    }
    context_file = "AGENTS.md"

-    @staticmethod
-    def _inject_hook_command_note(content: str) -> str:
-        """Insert a dot-to-hyphen note before each hook output instruction.
-
-        Targets the line ``- For each executable hook, output the following``
-        and inserts the note on the line before it, matching its indentation.
-        Skips if the note is already present.
-        """
-        if "replace dots" in content:
-            return content
-
-        def repl(m: re.Match[str]) -> str:
-            indent = m.group(1)
-            instruction = m.group(2)
-            # ``eol`` is empty when the regex matched via ``$`` because the
-            # instruction was the final line of a file with no trailing
-            # newline. Default to ``\n`` so the note never collapses onto
-            # the same line as the instruction.
-            eol = m.group(3) or "\n"
-            return (
-                indent
-                + _HOOK_COMMAND_NOTE.rstrip("\n")
-                + eol
-                + indent
-                + instruction
-                + eol
-            )
-
-        return re.sub(
-            r"(?m)^(\s*)(- For each executable hook, output the following[^\r\n]*)(\r\n|\n|$)",
-            repl,
-            content,
-        )
-
-    def post_process_skill_content(self, content: str) -> str:
-        """Inject the dot-to-hyphen hook command note."""
-        return self._inject_hook_command_note(content)
-
-    def build_exec_args(
-        self,
-        prompt: str,
-        *,
-        model: str | None = None,
-        output_json: bool = True,
-    ) -> list[str] | None:
-        # agy does not support --model or JSON output; both params are ignored
-        return ["agy", "--print", prompt]
-
    def setup(
        self,
        project_root: Path,
@@ -107,21 +49,4 @@ class AgyIntegration(SkillsIntegration):
            fg="yellow",
            err=True,
        )
-        created = super().setup(project_root, manifest, parsed_options=parsed_options, **opts)
-
-        skills_dir = self.skills_dest(project_root).resolve()
-        for path in created:
-            try:
-                path.resolve().relative_to(skills_dir)
-            except ValueError:
-                continue
-            if path.name != "SKILL.md":
-                continue
-
-            content = path.read_bytes().decode("utf-8")
-            updated = self.post_process_skill_content(content)
-            if updated != content:
-                path.write_bytes(updated.encode("utf-8"))
-                self.record_file_in_manifest(path, project_root, manifest)
-
-        return created
+        return super().setup(project_root, manifest, parsed_options=parsed_options, **opts)
--- a/src/specify_cli/integrations/base.py
+++ b/src/specify_cli/integrations/base.py
@@ -25,12 +25,6 @@ import yaml
 if TYPE_CHECKING:
    from .manifest import IntegrationManifest

-_HOOK_COMMAND_NOTE = (
-    "- When constructing slash commands from hook command names, "
-    "replace dots (`.`) with hyphens (`-`). "
-    "For example, `speckit.git.commit` → `/speckit-git-commit`.\n"
-)
-

 # ---------------------------------------------------------------------------
 # IntegrationOption
@@ -1397,53 +1391,15 @@ class SkillsIntegration(IntegrationBase):
            invocation = f"{invocation} {args}"
        return invocation

-    @staticmethod
-    def _inject_hook_command_note(content: str) -> str:
-        """Insert a dot-to-hyphen note before each hook output instruction.
-
-        Targets the line ``- For each executable hook, output the following``
-        and inserts the note on the line before it, matching its indentation.
-        Skips individual instructions that already have the note immediately
-        above them.
-        """
-        note = _HOOK_COMMAND_NOTE.rstrip("\n")
-
-        def repl(m: re.Match[str]) -> str:
-            indent = m.group(1)
-            instruction = m.group(2)
-            previous_lines = content[:m.start()].splitlines()
-            if previous_lines and previous_lines[-1] == indent + note:
-                return m.group(0)
-            # ``eol`` is empty when the regex matched via ``$`` because the
-            # instruction was the final line of a file with no trailing
-            # newline. Default to ``\n`` so the note never collapses onto
-            # the same line as the instruction.
-            eol = m.group(3) or "\n"
-            return (
-                indent
-                + note
-                + eol
-                + indent
-                + instruction
-                + eol
-            )
-
-        return re.sub(
-            r"(?m)^([ \t]*)(- For each executable hook, output the following[^\r\n]*)(\r\n|\n|$)",
-            repl,
-            content,
-        )
-
    def post_process_skill_content(self, content: str) -> str:
        """Post-process a SKILL.md file's content after generation.

        Called by external skill generators (presets, extensions) to let
        the integration inject agent-specific frontmatter or body
-        transformations.  The base implementation injects shared skills
-        guidance for converting dotted hook command names to hyphenated
-        slash commands.  Subclasses may override — see ``ClaudeIntegration``.
+        transformations.  The default implementation returns *content*
+        unchanged.  Subclasses may override — see ``ClaudeIntegration``.
        """
-        return self._inject_hook_command_note(content)
+        return content

    def setup(
        self,
@@ -1546,8 +1502,6 @@ class SkillsIntegration(IntegrationBase):
                f"{processed_body}"
            )

-            skill_content = self.post_process_skill_content(skill_content)
-
            # Write speckit-<name>/SKILL.md
            skill_dir = skills_dir / skill_name
            skill_file = skill_dir / "SKILL.md"
--- a/src/specify_cli/integrations/catalog.py
+++ b/src/specify_cli/integrations/catalog.py
@@ -21,8 +21,6 @@ from typing import Any, Dict, List, Optional, Tuple
 import yaml
 from packaging import version as pkg_version

-from ..catalogs import CatalogEntry, CatalogStackBase
-

 # ---------------------------------------------------------------------------
 # Errors
@@ -45,15 +43,21 @@ class IntegrationDescriptorError(Exception):
 # ---------------------------------------------------------------------------

@dataclass
-class IntegrationCatalogEntry(CatalogEntry):
+class IntegrationCatalogEntry:
    """Represents a single catalog source in the catalog stack."""

+    url: str
+    name: str
+    priority: int
+    install_allowed: bool
+    description: str = ""
+

 # ---------------------------------------------------------------------------
 # IntegrationCatalog
 # ---------------------------------------------------------------------------

-class IntegrationCatalog(CatalogStackBase):
+class IntegrationCatalog:
    """Manages integration catalog fetching, caching, and searching."""

    DEFAULT_CATALOG_URL = (
@@ -63,15 +67,136 @@ class IntegrationCatalog(CatalogStackBase):
        "https://raw.githubusercontent.com/github/spec-kit/main/integrations/catalog.community.json"
    )
    CACHE_DURATION = 3600  # 1 hour
-    CONFIG_FILENAME = "integration-catalogs.yml"
-    ENTRY_CLASS = IntegrationCatalogEntry
-    ERROR_TYPE = IntegrationCatalogError
-    VALIDATION_ERROR_TYPE = IntegrationValidationError

    def __init__(self, project_root: Path) -> None:
        self.project_root = project_root
        self.cache_dir = project_root / ".specify" / "integrations" / ".cache"

+    # -- URL validation ---------------------------------------------------
+
+    @staticmethod
+    def _validate_catalog_url(url: str) -> None:
+        from urllib.parse import urlparse
+
+        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 IntegrationCatalogError(
+                f"Catalog URL must use HTTPS (got {parsed.scheme}://). "
+                "HTTP is only allowed for localhost."
+            )
+        if not parsed.netloc:
+            raise IntegrationCatalogError(
+                "Catalog URL must be a valid URL with a host."
+            )
+
+    # -- Catalog stack ----------------------------------------------------
+
+    def _load_catalog_config(
+        self, config_path: Path
+    ) -> Optional[List[IntegrationCatalogEntry]]:
+        """Load catalog stack from a YAML file.
+
+        Returns None when the file does not exist.
+
+        Raises:
+            IntegrationValidationError: on any local-config / YAML problem
+                (parse failures, wrong shape, missing/invalid fields,
+                invalid catalog URLs, etc.). This is a subclass of
+                :class:`IntegrationCatalogError`, so any caller that already
+                catches ``IntegrationCatalogError`` keeps working — but
+                callers that want to distinguish *local config* problems
+                from *remote/network* problems can match the subclass.
+        """
+        if not config_path.exists():
+            return None
+        try:
+            data = yaml.safe_load(config_path.read_text(encoding="utf-8"))
+        except (yaml.YAMLError, OSError, UnicodeError) as exc:
+            raise IntegrationValidationError(
+                f"Failed to read catalog config {config_path}: {exc}"
+            ) from exc
+        if data is None:
+            data = {}
+        if not isinstance(data, dict):
+            raise IntegrationValidationError(
+                f"Invalid catalog config {config_path}: expected a YAML mapping at the root"
+            )
+        catalogs_data = data.get("catalogs", [])
+        if not isinstance(catalogs_data, list):
+            raise IntegrationValidationError(
+                f"Invalid catalog config {config_path}: 'catalogs' must be a list, "
+                f"got {type(catalogs_data).__name__}"
+            )
+        if not catalogs_data:
+            raise IntegrationValidationError(
+                f"Catalog config {config_path} exists but contains no 'catalogs' entries. "
+                f"Remove the file to use built-in defaults, or add valid catalog entries."
+            )
+        entries: List[IntegrationCatalogEntry] = []
+        skipped: List[int] = []
+        for idx, item in enumerate(catalogs_data):
+            if not isinstance(item, dict):
+                raise IntegrationValidationError(
+                    f"Invalid catalog config {config_path}: catalog entry at index {idx}: "
+                    f"expected a mapping, got {type(item).__name__}"
+                )
+            url = str(item.get("url", "")).strip()
+            if not url:
+                skipped.append(idx)
+                continue
+            try:
+                self._validate_catalog_url(url)
+            except IntegrationCatalogError as exc:
+                # ``_validate_catalog_url`` raises the base class for direct
+                # callers (e.g. ``add_catalog`` validating user input); when
+                # the bad URL came from a local config file, surface it as a
+                # validation error so CLI handlers can route it accordingly.
+                raise IntegrationValidationError(
+                    f"Invalid catalog URL in {config_path} at index {idx}: {exc}"
+                ) from exc
+            raw_priority = item.get("priority", idx + 1)
+            if isinstance(raw_priority, bool):
+                raise IntegrationValidationError(
+                    f"Invalid catalog config {config_path}: "
+                    f"Invalid priority for catalog '{item.get('name', idx + 1)}': "
+                    f"expected integer, got {raw_priority!r}"
+                )
+            try:
+                priority = int(raw_priority)
+            except (TypeError, ValueError):
+                raise IntegrationValidationError(
+                    f"Invalid catalog config {config_path}: "
+                    f"Invalid priority for catalog '{item.get('name', idx + 1)}': "
+                    f"expected integer, got {raw_priority!r}"
+                )
+            raw_install = item.get("install_allowed", False)
+            if isinstance(raw_install, str):
+                install_allowed = raw_install.strip().lower() in ("true", "yes", "1")
+            else:
+                install_allowed = bool(raw_install)
+            raw_name = item.get("name")
+            name = str(raw_name).strip() if raw_name is not None else ""
+            if not name:
+                name = f"catalog-{len(entries) + 1}"
+            entries.append(
+                IntegrationCatalogEntry(
+                    url=url,
+                    name=name,
+                    priority=priority,
+                    install_allowed=install_allowed,
+                    description=str(item.get("description", "")),
+                )
+            )
+        entries.sort(key=lambda e: e.priority)
+        if not entries:
+            raise IntegrationValidationError(
+                f"Catalog config {config_path} contains {len(catalogs_data)} "
+                f"entries but none have valid URLs (entries at indices {skipped} "
+                f"were skipped). Each catalog entry must have a 'url' field."
+            )
+        return entries
+
    def get_active_catalogs(self) -> List[IntegrationCatalogEntry]:
        """Return the ordered list of active integration catalogs.

@@ -140,6 +265,7 @@ class IntegrationCatalog(CatalogStackBase):
    ) -> Dict[str, Any]:
        """Fetch one catalog, with per-URL caching."""
        import urllib.error
+        import urllib.request

        url_hash = hashlib.sha256(entry.url.encode()).hexdigest()[:16]
        cache_file = self.cache_dir / f"catalog-{url_hash}.json"
@@ -163,9 +289,7 @@ class IntegrationCatalog(CatalogStackBase):
                    pass  # Cache cleanup is best-effort; ignore deletion failures.

        try:
-            from specify_cli.authentication.http import open_url
-
-            with open_url(entry.url, timeout=10) as resp:
+            with urllib.request.urlopen(entry.url, timeout=10) as resp:
                # Validate final URL after redirects
                final_url = resp.geturl()
                if final_url != entry.url:
@@ -319,6 +443,8 @@ class IntegrationCatalog(CatalogStackBase):

    # -- Catalog-source management ----------------------------------------

+    CONFIG_FILENAME = "integration-catalogs.yml"
+
    def get_catalog_configs(self) -> List[Dict[str, Any]]:
        """Return the active catalog stack as a list of dicts.

--- a/src/specify_cli/integrations/claude/init.py
+++ b/src/specify_cli/integrations/claude/init.py
@@ -5,11 +5,21 @@ from __future__ import annotations
 from pathlib import Path
 from typing import Any

+import re
+
 import yaml

 from ..base import SkillsIntegration
 from ..manifest import IntegrationManifest

+# Note injected into hook sections so Claude maps dot-notation command
+# names (from extensions.yml) to the hyphenated skill names it uses.
+_HOOK_COMMAND_NOTE = (
+    "- When constructing slash commands from hook command names, "
+    "replace dots (`.`) with hyphens (`-`). "
+    "For example, `speckit.git.commit` → `/speckit-git-commit`.\n"
+)
+
 # Mapping of command template stem → argument-hint text shown inline
 # when a user invokes the slash command in Claude Code.
 ARGUMENT_HINTS: dict[str, str] = {
@@ -149,11 +159,41 @@ class ClaudeIntegration(SkillsIntegration):
            out.append(line)
        return "".join(out)

+    @staticmethod
+    def _inject_hook_command_note(content: str) -> str:
+        """Insert a dot-to-hyphen note before each hook output instruction.
+
+        Targets the line ``- For each executable hook, output the following``
+        and inserts the note on the line before it, matching its indentation.
+        Skips if the note is already present.
+        """
+        if "replace dots" in content:
+            return content
+
+        def repl(m: re.Match[str]) -> str:
+            indent = m.group(1)
+            instruction = m.group(2)
+            eol = m.group(3)
+            return (
+                indent
+                + _HOOK_COMMAND_NOTE.rstrip("\n")
+                + eol
+                + indent
+                + instruction
+                + eol
+            )
+
+        return re.sub(
+            r"(?m)^(\s*)(- For each executable hook, output the following[^\r\n]*)(\r\n|\n|$)",
+            repl,
+            content,
+        )
+
    def post_process_skill_content(self, content: str) -> str:
        """Inject Claude-specific frontmatter flags and hook notes."""
-        updated = super().post_process_skill_content(content)
-        updated = self._inject_frontmatter_flag(updated, "user-invocable")
+        updated = self._inject_frontmatter_flag(content, "user-invocable")
        updated = self._inject_frontmatter_flag(updated, "disable-model-invocation", "false")
+        updated = self._inject_hook_command_note(updated)
        return updated

    def setup(
@@ -163,9 +203,10 @@ class ClaudeIntegration(SkillsIntegration):
        parsed_options: dict[str, Any] | None = None,
        **opts: Any,
    ) -> list[Path]:
-        """Install Claude skills, then inject argument-hints."""
+        """Install Claude skills, then inject Claude-specific flags and argument-hints."""
        created = super().setup(project_root, manifest, parsed_options, **opts)

+        # Post-process generated skill files
        skills_dir = self.skills_dest(project_root).resolve()

        for path in created:
@@ -180,7 +221,7 @@ class ClaudeIntegration(SkillsIntegration):
            content_bytes = path.read_bytes()
            content = content_bytes.decode("utf-8")

-            updated = content
+            updated = self.post_process_skill_content(content)

            # Inject argument-hint if available for this skill
            skill_dir_name = path.parent.name  # e.g. "speckit-plan"
--- a/src/specify_cli/integrations/copilot/init.py
+++ b/src/specify_cli/integrations/copilot/init.py
@@ -24,16 +24,6 @@ from ..base import IntegrationBase, IntegrationOption, SkillsIntegration
 from ..manifest import IntegrationManifest


-def _copilot_executable() -> str:
-    """Return the executable name for Copilot CLI on this platform.
-
-    On Windows, subprocess invocation is reliable with `copilot.cmd`.
-    """
-    if os.name == "nt":
-        return "copilot.cmd"
-    return "copilot"
-
-
 def _allow_all() -> bool:
    """Return True if the Copilot CLI should run with full permissions.

@@ -148,7 +138,7 @@ class CopilotIntegration(IntegrationBase):
        # Controlled by SPECKIT_COPILOT_ALLOW_ALL_TOOLS env var
        # (default: enabled).  The deprecated SPECKIT_ALLOW_ALL_TOOLS
        # is also honoured as a fallback.
-        args = [_copilot_executable(), "-p", prompt]
+        args = ["copilot", "-p", prompt]
        if _allow_all():
            args.append("--yolo")
        if model:
@@ -216,7 +206,7 @@ class CopilotIntegration(IntegrationBase):
            agent_name = f"speckit.{stem}"
            prompt = args or ""

-        cli_args = [_copilot_executable(), "-p", prompt]
+        cli_args = ["copilot", "-p", prompt]
        if not skills_mode:
            cli_args.extend(["--agent", agent_name])
        if _allow_all():
@@ -265,13 +255,12 @@ class CopilotIntegration(IntegrationBase):
        return f"speckit.{template_name}.agent.md"

    def post_process_skill_content(self, content: str) -> str:
-        """Inject shared hook guidance and Copilot ``mode:`` frontmatter.
+        """Inject Copilot-specific ``mode:`` field into SKILL.md frontmatter.

        Inserts ``mode: speckit.<stem>`` before the closing ``---`` so
        Copilot can associate the skill with its agent mode.
        """
-        updated = _CopilotSkillsHelper().post_process_skill_content(content)
-        lines = updated.splitlines(keepends=True)
+        lines = content.splitlines(keepends=True)

        # Extract skill name from frontmatter to derive the mode value
        dash_count = 0
@@ -285,7 +274,7 @@ class CopilotIntegration(IntegrationBase):
                continue
            if dash_count == 1:
                if stripped.startswith("mode:"):
-                    return updated  # already present
+                    return content  # already present
                if stripped.startswith("name:"):
                    # Parse: name: "speckit-plan" → speckit.plan
                    val = stripped.split(":", 1)[1].strip().strip('"').strip("'")
@@ -296,7 +285,7 @@ class CopilotIntegration(IntegrationBase):
                        skill_name = val

        if not skill_name:
-            return updated
+            return content

        # Inject mode: before the closing --- of frontmatter
        out: list[str] = []
--- a/src/specify_cli/integrations/hermes/init.py
+++ b/src/specify_cli/integrations/hermes/init.py
@@ -1,280 +0,0 @@
-"""Hermes Agent integration — skills-based agent.
-
-Hermes Agent (https://github.com/NousResearch/hermes-agent) is an open-source
-AI agent framework by Nous Research.  It stores skills in
-``~/.hermes/skills/`` (user-global) rather than a project-local directory.
-
-Usage::
-
-    specify init my-project --integration hermes
-    specify init --here --ai hermes
-"""
-
-from __future__ import annotations
-
-from pathlib import Path
-from shutil import rmtree
-from typing import Any
-
-import yaml
-
-from ..base import IntegrationOption, SkillsIntegration
-from ..manifest import IntegrationManifest
-
-
-class HermesIntegration(SkillsIntegration):
-    """Integration for Hermes Agent skills.
-
-    Hermes loads skills from ``~/.hermes/skills/`` (user home directory)
-    rather than a project-local path.  Skills are installed directly to
-    the global directory — no project-local copies are created since
-    Hermes discovers them globally.  A project-local marker directory
-    (``.hermes/skills/`` empty) is created so extension commands (e.g.
-    git) can detect Hermes as an active integration.  Uninstall removes
-    both the marker and all global ``speckit-*`` skills, matching the
-    standard integration teardown behaviour.
-    """
-
-    key = "hermes"
-    config = {
-        "name": "Hermes Agent",
-        "folder": ".hermes/",
-        "commands_subdir": "skills",
-        "install_url": "https://github.com/NousResearch/hermes-agent",
-        "requires_cli": True,
-    }
-    registrar_config = {
-        "dir": "~/.hermes/skills",
-        "detect_dir": ".hermes/skills",
-        "format": "markdown",
-        "args": "$ARGUMENTS",
-        "extension": "/SKILL.md",
-    }
-    context_file = "AGENTS.md"
-
-    # -- Helpers -----------------------------------------------------------
-
-    @staticmethod
-    def _hermes_home_skills_dir() -> Path:
-        """Return ``~/.hermes/skills/`` — the global skills directory."""
-        return Path.home() / ".hermes" / "skills"
-
-    # -- Options -----------------------------------------------------------
-
-    @classmethod
-    def options(cls) -> list[IntegrationOption]:
-        return [
-            IntegrationOption(
-                "--skills",
-                is_flag=True,
-                default=True,
-                help="Install as agent skills (default for Hermes Agent)",
-            ),
-        ]
-
-    # -- Setup -------------------------------------------------------------
-
-    def setup(
-        self,
-        project_root: Path,
-        manifest: IntegrationManifest,
-        parsed_options: dict[str, Any] | None = None,
-        **opts: Any,
-    ) -> list[Path]:
-        """Install command templates as global Hermes skills.
-
-        Writes each skill directly to
-        ``~/.hermes/skills/speckit-<name>/SKILL.md`` where Hermes
-        discovers them at runtime.  No project-local SKILL.md copies are
-        created — the global directory is the single source of truth.
-        A project-local marker (``.hermes/skills/`` empty) is created
-        so extension commands (e.g. git) can detect Hermes as an active
-        integration.
-        """
-        templates = self.list_command_templates()
-        if not templates:
-            return []
-
-        # Safety check: verify manifest project_root matches (standard pattern)
-        project_root_resolved = project_root.resolve()
-        if manifest.project_root != project_root_resolved:
-            raise ValueError(
-                f"manifest.project_root ({manifest.project_root}) does not match "
-                f"project_root ({project_root_resolved})"
-            )
-
-        script_type = opts.get("script_type", "sh")
-        arg_placeholder = (
-            self.registrar_config.get("args", "$ARGUMENTS")
-            if self.registrar_config
-            else "$ARGUMENTS"
-        )
-
-        global_skills_dir = self._hermes_home_skills_dir()
-        global_skills_dir.mkdir(parents=True, exist_ok=True)
-
-        created: list[Path] = []
-
-        for src_file in templates:
-            raw = src_file.read_text(encoding="utf-8")
-
-            # Derive the skill name from the template stem
-            command_name = src_file.stem  # e.g. "plan"
-            skill_name = f"speckit-{command_name.replace('.', '-')}"
-
-            # Parse frontmatter for description
-            frontmatter: dict[str, Any] = {}
-            if raw.startswith("---"):
-                parts = raw.split("---", 2)
-                if len(parts) >= 3:
-                    try:
-                        fm = yaml.safe_load(parts[1])
-                        if isinstance(fm, dict):
-                            frontmatter = fm
-                    except yaml.YAMLError:
-                        pass
-
-            # Process body through the standard template pipeline
-            processed_body = self.process_template(
-                raw,
-                self.key,
-                script_type,
-                arg_placeholder,
-                context_file=self.context_file or "",
-                invoke_separator=self.invoke_separator,
-            )
-            # Strip the processed frontmatter — we rebuild it for skills.
-            if processed_body.startswith("---"):
-                parts = processed_body.split("---", 2)
-                if len(parts) >= 3:
-                    processed_body = parts[2]
-
-            # Select description
-            description = frontmatter.get("description", "")
-            if not description:
-                description = f"Spec Kit: {command_name} workflow"
-
-            # 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: {_quote(skill_name)}\n"
-                f"description: {_quote(description)}\n"
-                f"compatibility: "
-                f"{_quote('Requires spec-kit project structure with .specify/ directory')}\n"
-                f"metadata:\n"
-                f"  author: {_quote('github-spec-kit')}\n"
-                f"  source: {_quote('templates/commands/' + src_file.name)}\n"
-                f"---\n"
-                f"{processed_body}"
-            )
-
-            skill_content = self.post_process_skill_content(skill_content)
-
-            # Write directly to global ~/.hermes/skills/speckit-<name>/SKILL.md
-            skill_dir = global_skills_dir / skill_name
-            skill_dir.mkdir(parents=True, exist_ok=True)
-            skill_file = skill_dir / "SKILL.md"
-            normalized = skill_content.replace("\r\n", "\n")
-            skill_file.write_bytes(normalized.encode("utf-8"))
-            created.append(skill_file)
-
-        # Upsert managed context section into the agent context file
-        self.upsert_context_section(project_root)
-
-        # Create project-local marker directory so extension commands
-        # (e.g. git) can detect Hermes as an active integration.
-        # Hermes itself ignores this directory — skills live globally.
-        (project_root / ".hermes" / "skills").mkdir(parents=True, exist_ok=True)
-
-        return created
-
-    # -- Uninstall ---------------------------------------------------------
-
-    def teardown(
-        self,
-        project_root: Path,
-        manifest: IntegrationManifest,
-        *,
-        force: bool = False,
-    ) -> tuple[list[Path], list[Path]]:
-        """Uninstall integration files including global Hermes skills.
-
-        Removes the managed context section from AGENTS.md, removes the
-        project-local marker directory (if empty), delegates to
-        ``manifest.uninstall()`` for project-local tracked files, and
-        removes all ``speckit-*`` skills under ``~/.hermes/skills/``.
-
-        Global skills are always removed on teardown — this matches the
-        standard integration behaviour where all files created by the
-        integration are removed on ``specify integration uninstall``.
-        """
-        # Remove managed context section from AGENTS.md
-        self.remove_context_section(project_root)
-
-        # Delegate to manifest for project-local tracked files (scripts,
-        # templates, context entries tracked in the manifest).
-        removed, skipped = manifest.uninstall(project_root, force=force)
-
-        # Remove project-local marker directory if empty
-        local_skills_dir = project_root / ".hermes" / "skills"
-        if local_skills_dir.is_dir() and not any(local_skills_dir.iterdir()):
-            local_skills_dir.rmdir()
-            hermes_dir = project_root / ".hermes"
-            if hermes_dir.is_dir() and not any(hermes_dir.iterdir()):
-                hermes_dir.rmdir()
-
-        # Remove all global Hermes skills for speckit — these are always
-        # removed on uninstall regardless of the force flag, matching the
-        # standard behaviour where all integration files are cleaned up.
-        global_skills_dir = self._hermes_home_skills_dir()
-        if global_skills_dir.is_dir():
-            for skill_dir in sorted(global_skills_dir.iterdir()):
-                if skill_dir.is_dir() and skill_dir.name.startswith("speckit-"):
-                    try:
-                        rmtree(skill_dir)
-                        removed.append(skill_dir)
-                    except OSError:
-                        skipped.append(skill_dir)
-
-        return removed, skipped
-
-    # -- CLI dispatch ------------------------------------------------------
-
-    def build_exec_args(
-        self,
-        prompt: str,
-        *,
-        model: str | None = None,
-        output_json: bool = True,
-    ) -> list[str] | None:
-        """Build Hermes CLI invocation for programmatic dispatch.
-
-        Uses ``hermes chat -Q -q`` for one-shot queries in quiet mode,
-        mapping slash-command invocations to the appropriate skill-based
-        dispatch.
-        """
-        args = [self.key, "chat", "-Q"]
-
-        if model:
-            args.extend(["-m", model])
-        if output_json:
-            args.append("--json")
-
-        # If prompt starts with a slash command, pass it directly
-        # so Hermes can dispatch to the appropriate skill.
-        if prompt.startswith("/"):
-            command, _, remainder = prompt[1:].partition(" ")
-            if command:
-                args.extend(["-s", command])
-                if remainder:
-                    args.extend(["-q", remainder])
-            else:
-                args.extend(["-q", prompt])
-        else:
-            args.extend(["-q", prompt])
-
-        return args
--- a/src/specify_cli/integrations/kiro_cli/init.py
+++ b/src/specify_cli/integrations/kiro_cli/init.py
@@ -3,14 +3,6 @@
 from ..base import MarkdownIntegration


-# Kiro CLI file-based prompts do NOT support any argument-substitution syntax,
-# so a raw "$ARGUMENTS" token would reach the model verbatim and break the
-# prompt (issue #1926, kirodotdev/Kiro#4141). Use a prose fallback so the
-# rendered prompt instructs the model to take its argument from the user's
-# next message.
-_KIRO_ARG_FALLBACK = "(the user will provide the argument in this conversation)"
-
-
 class KiroCliIntegration(MarkdownIntegration):
    key = "kiro-cli"
    config = {
@@ -23,7 +15,7 @@ class KiroCliIntegration(MarkdownIntegration):
    registrar_config = {
        "dir": ".kiro/prompts",
        "format": "markdown",
-        "args": _KIRO_ARG_FALLBACK,
+        "args": "$ARGUMENTS",
        "extension": ".md",
    }
    context_file = "AGENTS.md"
--- a/src/specify_cli/integrations/opencode/init.py
+++ b/src/specify_cli/integrations/opencode/init.py
@@ -8,13 +8,12 @@ class OpencodeIntegration(MarkdownIntegration):
    config = {
        "name": "opencode",
        "folder": ".opencode/",
-        "commands_subdir": "commands",
+        "commands_subdir": "command",
        "install_url": "https://opencode.ai",
        "requires_cli": True,
    }
    registrar_config = {
-        "dir": ".opencode/commands",
-        "legacy_dir": ".opencode/command",
+        "dir": ".opencode/command",
        "format": "markdown",
        "args": "$ARGUMENTS",
        "extension": ".md",
--- a/src/specify_cli/integrations/vibe/init.py
+++ b/src/specify_cli/integrations/vibe/init.py
@@ -81,13 +81,13 @@ class VibeIntegration(SkillsIntegration):
            out.append(line)
        return "".join(out)

+
    def post_process_skill_content(self, content: str) -> str:
        """
-        Inject shared hook guidance and Vibe-specific frontmatter flags:
+        Inject Vibe-specific frontmatter flags:
        - user-invocable: allows the skill to be invoked by the user (not just other agents)
        """
-        updated = super().post_process_skill_content(content)
-        updated = self._inject_frontmatter_flag(updated, "user-invocable")
+        updated = self._inject_frontmatter_flag(content, "user-invocable")
        return updated

    def setup(
@@ -107,4 +107,27 @@ class VibeIntegration(SkillsIntegration):
            err=True,
        )

-        return super().setup(project_root, manifest, parsed_options=parsed_options, **opts)
+        created = super().setup(project_root, manifest, parsed_options=parsed_options, **opts)
+
+        # Post-process generated skill files
+        skills_dir = self.skills_dest(project_root).resolve()
+
+        for path in created:
+            # Only touch SKILL.md files under the skills directory
+            try:
+                path.resolve().relative_to(skills_dir)
+            except ValueError:
+                continue
+            if path.name != "SKILL.md":
+                continue
+
+            content_bytes = path.read_bytes()
+            content = content_bytes.decode("utf-8")
+
+            updated = self.post_process_skill_content(content)
+
+            if updated != content:
+                path.write_bytes(updated.encode("utf-8"))
+                self.record_file_in_manifest(path, project_root, manifest)
+
+        return created
--- a/src/specify_cli/presets.py
+++ b/src/specify_cli/presets.py
@@ -28,7 +28,6 @@ from packaging import version as pkg_version
 from packaging.specifiers import SpecifierSet, InvalidSpecifier

 from .extensions import REINSTALL_COMMAND, ExtensionRegistry, normalize_priority
-from .integrations.base import IntegrationBase


 def _substitute_core_template(
@@ -1049,9 +1048,9 @@ class PresetManager:
                    short_name = cmd_name
                    if short_name.startswith("speckit."):
                        short_name = short_name[len("speckit."):]
-                    desc = fm.get("description", "") or SKILL_DESCRIPTIONS.get(
+                    desc = SKILL_DESCRIPTIONS.get(
                        short_name.replace(".", "-"),
-                        f"Command: {short_name}",
+                        fm.get("description", f"Command: {short_name}"),
                    )
                    init_opts = load_init_options(self.project_root)
                    selected_ai = init_opts.get("ai") if isinstance(init_opts, dict) else ""
@@ -1059,9 +1058,6 @@ class PresetManager:
                        body = registrar.resolve_skill_placeholders(
                            selected_ai, fm, body, self.project_root
                        )
-                        body = self._resolve_skill_command_refs(
-                            body, registrar, selected_ai
-                        )
                    fm_data = registrar.build_skill_frontmatter(
                        selected_ai if isinstance(selected_ai, str) else "",
                        skill_name, desc,
@@ -1101,24 +1097,37 @@ class PresetManager:
    def _get_skills_dir(self) -> Optional[Path]:
        """Return the active skills directory for preset skill overrides.

-        Delegates to :func:`resolve_active_skills_dir` which reads
-        init-options, applies the Kimi native-skills fallback, and
-        safely creates the directory when ``ai_skills`` is enabled.
+        Reads ``.specify/init-options.json`` to determine whether skills
+        are enabled and which agent was selected, then delegates to
+        the module-level ``_get_skills_dir()`` helper for the concrete path.

-        Returns ``None`` (instead of raising) when the directory cannot
-        be created due to symlink, containment, or permission issues so
-        that callers can fall back gracefully.
+        Kimi is treated as a native-skills agent: if ``ai == "kimi"`` and
+        ``.kimi/skills`` exists, presets should still propagate command
+        overrides to skills even when ``ai_skills`` is false.
+
+        Returns:
+            The skills directory ``Path``, or ``None`` if skills were not
+            enabled and no native-skills fallback applies.
        """
-        from . import resolve_active_skills_dir, _print_cli_warning
-        try:
-            return resolve_active_skills_dir(self.project_root)
-        except (ValueError, OSError) as exc:
-            _print_cli_warning(
-                "resolve", "skills directory", None, exc,
-                continuing="Continuing without skill registration.",
-            )
+        from . import load_init_options, _get_skills_dir
+
+        opts = load_init_options(self.project_root)
+        if not isinstance(opts, dict):
+            opts = {}
+        agent = opts.get("ai")
+        if not isinstance(agent, str) or not agent:
            return None

+        ai_skills_enabled = bool(opts.get("ai_skills"))
+        if not ai_skills_enabled and agent != "kimi":
+            return None
+
+        skills_dir = _get_skills_dir(self.project_root, agent)
+        if not skills_dir.is_dir():
+            return None
+
+        return skills_dir
+
    @staticmethod
    def _skill_names_for_command(cmd_name: str) -> tuple[str, str]:
        """Return the modern and legacy skill directory names for a command."""
@@ -1138,23 +1147,6 @@ class PresetManager:
            title_name = title_name[len("speckit."):]
        return title_name.replace(".", " ").replace("-", " ").title()

-    @staticmethod
-    def _resolve_skill_command_refs(
-        body: str, registrar: "CommandRegistrar", selected_ai: str
-    ) -> str:
-        """Render ``__SPECKIT_COMMAND_*__`` tokens in a skill body as invocations.
-
-        Looks up the agent's invoke separator and rewrites each
-        ``__SPECKIT_COMMAND_<NAME>__`` placeholder into the matching
-        slash-command invocation — ``/speckit-<cmd>`` for a ``-`` separator,
-        ``/speckit.<cmd>`` for ``.`` — the same rendering the command layer
-        applies via ``CommandRegistrar.register_commands()``.
-        """
-        separator = registrar.AGENT_CONFIGS.get(selected_ai, {}).get(
-            "invoke_separator", "."
-        )
-        return IntegrationBase.resolve_command_refs(body, separator)
-
    def _build_extension_skill_restore_index(self) -> Dict[str, Dict[str, Any]]:
        """Index extension-backed skill restore data by skill directory name."""
        from .extensions import ExtensionManifest, ValidationError
@@ -1322,16 +1314,15 @@ class PresetManager:
                        frontmatter[key] = core_frontmatter[key]

            original_desc = frontmatter.get("description", "")
-            enhanced_desc = original_desc or SKILL_DESCRIPTIONS.get(
+            enhanced_desc = SKILL_DESCRIPTIONS.get(
                short_name,
-                f"Spec-kit workflow command: {short_name}",
+                original_desc or f"Spec-kit workflow command: {short_name}",
            )
            frontmatter = dict(frontmatter)
            frontmatter["description"] = enhanced_desc
            body = registrar.resolve_skill_placeholders(
                selected_ai, frontmatter, body, self.project_root
            )
-            body = self._resolve_skill_command_refs(body, registrar, selected_ai)

            for target_skill_name in target_skill_names:
                skill_subdir = skills_dir / target_skill_name
@@ -1424,14 +1415,11 @@ class PresetManager:
                    body = registrar.resolve_skill_placeholders(
                        selected_ai, frontmatter, body, self.project_root
                    )
-                    body = self._resolve_skill_command_refs(
-                        body, registrar, selected_ai
-                    )

                original_desc = frontmatter.get("description", "")
-                enhanced_desc = original_desc or SKILL_DESCRIPTIONS.get(
+                enhanced_desc = SKILL_DESCRIPTIONS.get(
                    short_name,
-                    f"Spec-kit workflow command: {short_name}",
+                    original_desc or f"Spec-kit workflow command: {short_name}",
                )

                frontmatter_data = registrar.build_skill_frontmatter(
@@ -1464,9 +1452,6 @@ class PresetManager:
                    body = registrar.resolve_skill_placeholders(
                        selected_ai, frontmatter, body, self.project_root
                    )
-                    body = self._resolve_skill_command_refs(
-                        body, registrar, selected_ai
-                    )

                command_name = extension_restore["command_name"]
                title_name = self._skill_title_from_command(command_name)
@@ -1860,20 +1845,20 @@ class PresetCatalog:
            )

    def _make_request(self, url: str):
-        """Build a urllib Request, adding auth headers when a provider matches.
+        """Build a urllib Request, adding a GitHub auth header when available.

-        Delegates to :func:`specify_cli.authentication.http.build_request`.
+        Delegates to :func:`specify_cli._github_http.build_github_request`.
        """
-        from specify_cli.authentication.http import build_request
-        return build_request(url)
+        from specify_cli._github_http import build_github_request
+        return build_github_request(url)

    def _open_url(self, url: str, timeout: int = 10):
-        """Open a URL with provider-based auth, trying each configured provider.
+        """Open a URL with GitHub auth, stripping the header on cross-host redirects.

-        Delegates to :func:`specify_cli.authentication.http.open_url`.
+        Delegates to :func:`specify_cli._github_http.open_github_url`.
        """
-        from specify_cli.authentication.http import open_url
-        return open_url(url, timeout)
+        from specify_cli._github_http import open_github_url
+        return open_github_url(url, timeout)

    def _load_catalog_config(self, config_path: Path) -> Optional[List[PresetCatalogEntry]]:
        """Load catalog stack configuration from a YAML file.
@@ -1918,24 +1903,12 @@ class PresetCatalog:
            if not url:
                continue
            self._validate_catalog_url(url)
-            raw_priority = item.get("priority", idx + 1)
-            # Reject bools explicitly: ``bool`` is a subclass of ``int`` so
-            # ``int(True)`` silently returns 1, which would let a YAML
-            # ``priority: true`` slip through as a valid priority of 1. The
-            # sibling integration-catalog reader in ``catalogs.py`` already
-            # guards this; mirror the check here so the three catalog
-            # validators stay consistent.
-            if isinstance(raw_priority, bool):
-                raise PresetValidationError(
-                    f"Invalid priority for catalog '{item.get('name', idx + 1)}': "
-                    f"expected integer, got {raw_priority!r}"
-                )
            try:
-                priority = int(raw_priority)
+                priority = int(item.get("priority", idx + 1))
            except (TypeError, ValueError):
                raise PresetValidationError(
                    f"Invalid priority for catalog '{item.get('name', idx + 1)}': "
-                    f"expected integer, got {raw_priority!r}"
+                    f"expected integer, got {item.get('priority')!r}"
                )
            raw_install = item.get("install_allowed", False)
            if isinstance(raw_install, str):
--- a/src/specify_cli/shared_infra.py
+++ b/src/specify_cli/shared_infra.py
@@ -11,15 +11,6 @@ from .integrations.base import IntegrationBase
 from .integrations.manifest import IntegrationManifest


-class SymlinkedSharedPathError(ValueError):
-    """Raised when a shared infrastructure path or ancestor is a symlink.
-
-    Distinct from other unsafe-path errors so callers can preserve symlinked
-    destinations as customizations while still letting genuine safety errors
-    (e.g. path escape, not-a-directory) propagate and abort the operation.
-    """
-
-
 def load_speckit_manifest(
    project_path: Path,
    *,
@@ -88,13 +79,7 @@ def _shared_relative_path(project_path: Path, dest: Path) -> Path:
    return rel


-def _ensure_safe_shared_directory(
-    project_path: Path,
-    directory: Path,
-    *,
-    create: bool = True,
-    context: str = "shared infrastructure directory",
-) -> None:
+def _ensure_safe_shared_directory(project_path: Path, directory: Path, *, create: bool = True) -> None:
    """Create a shared infra directory without following symlinked parents."""
    root = project_path.resolve()
    rel = _shared_relative_path(project_path, directory)
@@ -104,24 +89,24 @@ def _ensure_safe_shared_directory(
        current = current / part
        label = _shared_destination_label(project_path, current)
        if current.is_symlink():
-            raise SymlinkedSharedPathError(f"Refusing to use symlinked {context}: {label}")
+            raise ValueError(f"Refusing to use symlinked shared infrastructure directory: {label}")
        if current.exists():
            if not current.is_dir():
-                raise ValueError(f"{context.capitalize()} path is not a directory: {label}")
+                raise ValueError(f"Shared infrastructure directory path is not a directory: {label}")
            try:
                current.resolve().relative_to(root)
            except (OSError, ValueError):
-                raise ValueError(f"{context.capitalize()} escapes project root: {label}") from None
+                raise ValueError(f"Shared infrastructure directory escapes project root: {label}") from None
            continue
        if not create:
-            raise ValueError(f"{context.capitalize()} does not exist: {label}")
+            raise ValueError(f"Shared infrastructure directory does not exist: {label}")
        current.mkdir()
        if current.is_symlink():
-            raise SymlinkedSharedPathError(f"Refusing to use symlinked {context}: {label}")
+            raise ValueError(f"Refusing to use symlinked shared infrastructure directory: {label}")
        try:
            current.resolve().relative_to(root)
        except (OSError, ValueError):
-            raise ValueError(f"{context.capitalize()} escapes project root: {label}") from None
+            raise ValueError(f"Shared infrastructure directory escapes project root: {label}") from None


 def _validate_safe_shared_directory(project_path: Path, directory: Path) -> None:
@@ -134,7 +119,7 @@ def _validate_safe_shared_directory(project_path: Path, directory: Path) -> None
        current = current / part
        label = _shared_destination_label(project_path, current)
        if current.is_symlink():
-            raise SymlinkedSharedPathError(f"Refusing to use symlinked shared infrastructure directory: {label}")
+            raise ValueError(f"Refusing to use symlinked shared infrastructure directory: {label}")
        if not current.exists():
            continue
        if not current.is_dir():
@@ -160,7 +145,7 @@ def _ensure_safe_shared_destination(
        _validate_safe_shared_directory(project_path, dest.parent)
    label = _shared_destination_label(project_path, dest)
    if dest.is_symlink():
-        raise SymlinkedSharedPathError(f"Refusing to overwrite symlinked shared infrastructure path: {label}")
+        raise ValueError(f"Refusing to overwrite symlinked shared infrastructure path: {label}")

    if dest.exists():
        try:
@@ -257,156 +242,58 @@ def install_shared_infra(
    console: Any,
    force: bool = False,
    invoke_separator: str = ".",
-    refresh_managed: bool = False,
-    refresh_hint: str | None = None,
 ) -> bool:
-    """Install shared scripts and templates into *project_path*.
-
-    When ``refresh_managed`` is True, files whose on-disk hash still matches
-    the previously recorded manifest hash are overwritten with the bundled
-    version. Files whose hash diverges are treated as user customizations and
-    preserved with a warning. ``force=True`` overwrites every regular file
-    (symlinks and symlinked-parent destinations are always preserved with a
-    warning — the safe-destination check refuses to follow them so writes
-    cannot escape the project root). ``refresh_hint`` is shown after the
-    customization warning to tell the user which flag would overwrite their
-    customizations.
-    """
-    from .integrations.manifest import _sha256
-
+    """Install shared scripts and templates into *project_path*."""
    manifest = load_speckit_manifest(project_path, version=version, console=console)
-    prior_hashes = dict(manifest.files)
-
-    def _is_managed(rel: str, dst: Path) -> bool:
-        expected = prior_hashes.get(rel)
-        if not expected or not dst.is_file() or dst.is_symlink():
-            return False
-        try:
-            return _sha256(dst) == expected
-        except OSError:
-            return False
-
    skipped_files: list[str] = []
-    preserved_user_files: list[str] = []
-    symlinked_files: list[str] = []
    planned_copies: list[tuple[Path, str, bytes, int]] = []
    planned_templates: list[tuple[Path, str, str]] = []

-    def _decide_overwrite(rel: str, dst: Path) -> tuple[bool, str | None]:
-        """Return (write, bucket) where bucket is 'skip', 'preserved', or None."""
-        if not dst.exists():
-            return True, None
-        if force:
-            return True, None
-        if refresh_managed:
-            if _is_managed(rel, dst):
-                return True, None
-            if rel in prior_hashes:
-                return False, "preserved"
-            return False, "skip"
-        return False, "skip"
-
-    def _safe_dest_or_bucket(dst: Path, rel: str, *, parent_must_exist: bool = True) -> bool:
-        """Run the safe-destination check and bucket symlinked paths.
-
-        Returns True when the destination is safe to consider (write or skip).
-        Returns False (and records *rel* under ``symlinked_files``) when the
-        destination or any of its ancestors is a symlink — those paths can't
-        be written to safely, but they shouldn't abort the whole switch
-        either. They're surfaced as a separate "symlinked" warning bucket.
-
-        Other unsafe-path errors (e.g. path escape, parent-not-a-directory)
-        are NOT caught here: they re-raise so the operation aborts, since
-        treating them as "symlinked" would mask security-relevant failures.
-        """
-        try:
-            _ensure_safe_shared_destination(project_path, dst, parent_must_exist=parent_must_exist)
-        except SymlinkedSharedPathError:
-            symlinked_files.append(rel)
-            return False
-        return True
-
-    def _ensure_or_bucket_dir(directory: Path) -> bool:
-        """Create *directory* unless an ancestor is symlinked.
-
-        Returns True when the directory is safe to use. Returns False (and
-        records the path under ``symlinked_files``) when a symlink ancestor
-        forces us to skip the whole subtree. Other unsafe-path errors
-        (escape, not-a-directory) re-raise so the operation aborts.
-        """
-        try:
-            _ensure_safe_shared_directory(project_path, directory)
-        except SymlinkedSharedPathError:
-            symlinked_files.append(directory.relative_to(project_path).as_posix())
-            return False
-        return True
-
    scripts_src = shared_scripts_source(core_pack=core_pack, repo_root=repo_root)
    if scripts_src.is_dir():
        dest_scripts = project_path / ".specify" / "scripts"
-        if _ensure_or_bucket_dir(dest_scripts):
-            variant_dir = "bash" if script_type == "sh" else "powershell"
-            variant_src = scripts_src / variant_dir
-            if variant_src.is_dir():
-                dest_variant = dest_scripts / variant_dir
-                if _ensure_or_bucket_dir(dest_variant):
-                    for src_path in variant_src.rglob("*"):
-                        if not src_path.is_file():
-                            continue
+        _ensure_safe_shared_directory(project_path, dest_scripts)
+        variant_dir = "bash" if script_type == "sh" else "powershell"
+        variant_src = scripts_src / variant_dir
+        if variant_src.is_dir():
+            dest_variant = dest_scripts / variant_dir
+            _ensure_safe_shared_directory(project_path, dest_variant)
+            for src_path in variant_src.rglob("*"):
+                if not src_path.is_file():
+                    continue

-                        rel_path = src_path.relative_to(variant_src)
-                        dst_path = dest_variant / rel_path
-                        rel = dst_path.relative_to(project_path).as_posix()
-                        if not _safe_dest_or_bucket(dst_path, rel, parent_must_exist=False):
-                            continue
-                        write, bucket = _decide_overwrite(rel, dst_path)
-                        if not write:
-                            if bucket == "preserved":
-                                preserved_user_files.append(rel)
-                            else:
-                                skipped_files.append(rel)
-                            continue
+                rel_path = src_path.relative_to(variant_src)
+                dst_path = dest_variant / rel_path
+                _ensure_safe_shared_destination(project_path, dst_path, parent_must_exist=False)
+                if dst_path.exists() and not force:
+                    skipped_files.append(dst_path.relative_to(project_path).as_posix())
+                    continue

-                        if not _ensure_or_bucket_dir(dst_path.parent):
-                            continue
-                        content = src_path.read_text(encoding="utf-8")
-                        content = IntegrationBase.resolve_command_refs(content, invoke_separator)
-                        planned_copies.append(
-                            (
-                                dst_path,
-                                rel,
-                                content.encode("utf-8"),
-                                src_path.stat().st_mode & 0o777,
-                            )
-                        )
+                _ensure_safe_shared_directory(project_path, dst_path.parent)
+                rel = dst_path.relative_to(project_path).as_posix()
+                planned_copies.append((dst_path, rel, src_path.read_bytes(), src_path.stat().st_mode & 0o777))

    templates_src = shared_templates_source(core_pack=core_pack, repo_root=repo_root)
    if templates_src.is_dir():
        dest_templates = project_path / ".specify" / "templates"
-        if _ensure_or_bucket_dir(dest_templates):
-            for src in templates_src.iterdir():
-                if not src.is_file() or src.name == "vscode-settings.json" or src.name.startswith("."):
-                    continue
+        _ensure_safe_shared_directory(project_path, dest_templates)
+        for src in templates_src.iterdir():
+            if not src.is_file() or src.name == "vscode-settings.json" or src.name.startswith("."):
+                continue

-                dst = dest_templates / src.name
-                rel = dst.relative_to(project_path).as_posix()
-                if not _safe_dest_or_bucket(dst, rel):
-                    continue
-                write, bucket = _decide_overwrite(rel, dst)
-                if not write:
-                    if bucket == "preserved":
-                        preserved_user_files.append(rel)
-                    else:
-                        skipped_files.append(rel)
-                    continue
+            dst = dest_templates / src.name
+            _ensure_safe_shared_destination(project_path, dst)
+            if dst.exists() and not force:
+                skipped_files.append(dst.relative_to(project_path).as_posix())
+                continue

-                content = src.read_text(encoding="utf-8")
-                content = IntegrationBase.resolve_command_refs(content, invoke_separator)
-                planned_templates.append((dst, rel, content))
+            content = src.read_text(encoding="utf-8")
+            content = IntegrationBase.resolve_command_refs(content, invoke_separator)
+            rel = dst.relative_to(project_path).as_posix()
+            planned_templates.append((dst, rel, content))

    for dst_path, rel, content, mode in planned_copies:
-        if not _ensure_or_bucket_dir(dst_path.parent):
-            continue
+        _ensure_safe_shared_directory(project_path, dst_path.parent)
        _write_shared_bytes(project_path, dst_path, content, mode=mode)
        manifest.record_existing(rel)

@@ -420,37 +307,11 @@ def install_shared_infra(
        )
        for path in skipped_files:
            console.print(f"    {path}")
-        if refresh_managed and refresh_hint:
-            console.print(refresh_hint)
-        else:
-            console.print(
-                "To refresh shared infrastructure, run "
-                "[cyan]specify init --here --force[/cyan] or "
-                "[cyan]specify integration upgrade --force[/cyan]."
-            )
-
-    if symlinked_files:
        console.print(
-            f"[yellow]⚠[/yellow]  Skipped {len(symlinked_files)} symlinked shared "
-            "infrastructure path(s) — symlinks are never overwritten because they "
-            "may resolve outside the project root:"
+            "To refresh shared infrastructure, run "
+            "[cyan]specify init --here --force[/cyan] or "
+            "[cyan]specify integration upgrade --force[/cyan]."
        )
-        for path in symlinked_files:
-            console.print(f"    {path}")
-        console.print(
-            "To restore the bundled version, remove or replace the symlink manually, "
-            "then re-run the command."
-        )
-
-    if preserved_user_files:
-        console.print(
-            f"[yellow]⚠[/yellow]  Preserved {len(preserved_user_files)} customized shared "
-            "infrastructure file(s) (hash differs from previous install):"
-        )
-        for path in preserved_user_files:
-            console.print(f"    {path}")
-        if refresh_hint:
-            console.print(refresh_hint)

    manifest.save()
    return True
--- a/src/specify_cli/workflows/catalog.py
+++ b/src/specify_cli/workflows/catalog.py
@@ -322,7 +322,7 @@ class WorkflowCatalog:

        # Fetch from URL — validate scheme before opening and after redirects
        from urllib.parse import urlparse
-        from specify_cli.authentication.http import open_url as _open_url
+        from urllib.request import urlopen

        def _validate_catalog_url(url: str) -> None:
            parsed = urlparse(url)
@@ -337,7 +337,7 @@ class WorkflowCatalog:
        _validate_catalog_url(entry.url)

        try:
-            with _open_url(entry.url, timeout=30) as resp:
+            with urlopen(entry.url, timeout=30) as resp:  # noqa: S310
                _validate_catalog_url(resp.geturl())
                data = json.loads(resp.read().decode("utf-8"))
        except Exception as exc:
--- a/src/specify_cli/workflows/engine.py
+++ b/src/specify_cli/workflows/engine.py
@@ -19,10 +19,6 @@ from typing import Any

 import yaml

-from ..integration_state import (
-    default_integration_key,
-    try_read_integration_json,
-)
 from .base import RunStatus, StepContext, StepResult, StepStatus


@@ -147,35 +143,6 @@ def validate_workflow(definition: WorkflowDefinition) -> list[str]:
                    f"Must be 'string', 'number', or 'boolean'."
                )

-            # Validate the default eagerly so authoring mistakes (e.g. a
-            # default not in the declared enum, or a non-numeric default for
-            # a number input) surface at install/validation time instead of
-            # at workflow-execution time. ``"auto"`` for the integration
-            # input is a runtime-resolved sentinel, so only the
-            # enum-membership check is exempted for that exact case — the
-            # declared type is still enforced (e.g. ``type: number`` paired
-            # with ``default: "auto"`` is still rejected).
-            if "default" in input_def:
-                default_value = input_def["default"]
-                is_auto_integration = (
-                    input_name == "integration" and default_value == "auto"
-                )
-                validation_input_def: dict[str, Any] = input_def
-                if is_auto_integration and "enum" in input_def:
-                    validation_input_def = {
-                        key: value
-                        for key, value in input_def.items()
-                        if key != "enum"
-                    }
-                try:
-                    WorkflowEngine._coerce_input(
-                        input_name, default_value, validation_input_def
-                    )
-                except ValueError as exc:
-                    errors.append(
-                        f"Input {input_name!r} has invalid default: {exc}"
-                    )
-
    # -- Steps ------------------------------------------------------------
    if not isinstance(definition.steps, list):
        errors.append("'steps' must be a list.")
@@ -673,29 +640,22 @@ class WorkflowEngine:
                        if not evaluate_condition(condition, context):
                            break
                        # Namespace nested step IDs per iteration
-                        # so logs and state keys are unique.
-                        # Execute one step at a time and alias each
-                        # result back to the unprefixed key so that
-                        # later steps in the same body and the loop
-                        # condition see the latest values.
-                        for ns_idx, ns in enumerate(result.next_steps):
+                        iter_steps = []
+                        for ns in result.next_steps:
                            ns_copy = dict(ns)
-                            orig = ns_copy.get("id")
-                            base_id = orig or f"step-{ns_idx}"
-                            ns_copy["id"] = f"{step_id}:{base_id}:{_loop_iter + 1}"
-                            self._execute_steps(
-                                [ns_copy], context, state, registry,
-                                step_offset=-1,
-                            )
-                            if state.status in (
-                                RunStatus.PAUSED,
-                                RunStatus.FAILED,
-                                RunStatus.ABORTED,
-                            ):
-                                return
-                            if orig and ns_copy["id"] in context.steps:
-                                context.steps[orig] = context.steps[ns_copy["id"]]
-                                state.step_results[orig] = context.steps[ns_copy["id"]]
+                            if "id" in ns_copy:
+                                ns_copy["id"] = f"{step_id}:{ns_copy['id']}:{_loop_iter + 1}"
+                            iter_steps.append(ns_copy)
+                        self._execute_steps(
+                            iter_steps, context, state, registry,
+                            step_offset=-1,
+                        )
+                        if state.status in (
+                            RunStatus.PAUSED,
+                            RunStatus.FAILED,
+                            RunStatus.ABORTED,
+                        ):
+                            return

            # Fan-out: execute nested step template per item with unique IDs
            if step_type == "fan-out":
@@ -751,73 +711,16 @@ class WorkflowEngine:
            if not isinstance(input_def, dict):
                continue
            if name in provided:
-                # Resolve sentinels for explicitly-provided values too: a
-                # caller passing ``{"integration": "auto"}`` (which the
-                # workflow prompt advertises as a valid value) must be
-                # treated identically to omitting the input and letting the
-                # default flow through, so dispatch never sees the literal
-                # sentinel.
-                value = self._resolve_default(name, provided[name])
+                resolved[name] = self._coerce_input(
+                    name, provided[name], input_def
+                )
            elif "default" in input_def:
-                value = self._resolve_default(name, input_def["default"])
+                resolved[name] = input_def["default"]
            elif input_def.get("required", False):
                msg = f"Required input {name!r} not provided."
                raise ValueError(msg)
-            else:
-                continue
-
-            # When the ``integration`` default could not be resolved against
-            # project state and falls back to the literal ``"auto"``
-            # sentinel, strip ``enum`` from the input definition before
-            # coercion so a workflow that lists specific integrations in
-            # ``enum`` does not crash at runtime on the sentinel value.
-            # NOTE: only enum-membership is skipped; ``_coerce_input``
-            # still enforces the declared ``type`` against the filtered
-            # definition (``string`` rejects non-strings, ``number`` rejects
-            # bools and uncoercible values, ``boolean`` rejects non-bools),
-            # so ill-typed values still fail fast here.
-            coerce_input_def = input_def
-            if (
-                name == "integration"
-                and value == "auto"
-                and "enum" in input_def
-            ):
-                coerce_input_def = {
-                    key: val
-                    for key, val in input_def.items()
-                    if key != "enum"
-                }
-            resolved[name] = self._coerce_input(name, value, coerce_input_def)
        return resolved

-    def _resolve_default(self, name: str, default: Any) -> Any:
-        """Resolve special default sentinels against project state.
-
-        For the ``integration`` input, ``"auto"`` resolves to the integration
-        recorded in ``.specify/integration.json`` so workflows dispatch to the
-        AI the project was actually initialized with, instead of a hardcoded
-        value baked into the workflow YAML.
-        """
-        if name == "integration" and default == "auto":
-            resolved = self._load_project_integration()
-            if resolved is not None:
-                return resolved
-        return default
-
-    def _load_project_integration(self) -> str | None:
-        """Read the default integration key from ``.specify/integration.json``.
-
-        Delegates parsing and schema validation to
-        :func:`try_read_integration_json` — the same low-level helper used by
-        the CLI — so the engine cannot drift from CLI behavior on the parse
-        path. Returns ``None`` when the file is missing, malformed, or
-        written by a newer CLI; callers fall back to the literal default.
-        """
-        state, error = try_read_integration_json(self.project_root)
-        if state is None or error is not None:
-            return None
-        return default_integration_key(state)
-
    @staticmethod
    def _coerce_input(
        name: str, value: Any, input_def: dict[str, Any]
@@ -827,13 +730,6 @@ class WorkflowEngine:
        enum_values = input_def.get("enum")

        if input_type == "number":
-            # Reject bools explicitly: ``bool`` is a subclass of ``int`` so
-            # ``float(True)`` succeeds and would silently coerce a YAML
-            # authoring mistake like ``type: number`` + ``default: true``
-            # into ``1``. Fail fast instead.
-            if isinstance(value, bool):
-                msg = f"Input {name!r} expected a number, got {value!r}."
-                raise ValueError(msg)
            try:
                value = float(value)
                if value == int(value):
@@ -850,17 +746,6 @@ class WorkflowEngine:
                else:
                    msg = f"Input {name!r} expected a boolean, got {value!r}."
                    raise ValueError(msg)
-            elif not isinstance(value, bool):
-                msg = f"Input {name!r} expected a boolean, got {value!r}."
-                raise ValueError(msg)
-        elif input_type == "string":
-            # Without this, ``type: string`` accepts any Python value
-            # (numbers, lists, dicts) because nothing else rejects it —
-            # YAML ``default: 5`` would slip through. Require an actual
-            # string so authoring mistakes fail at resolve time.
-            if not isinstance(value, str):
-                msg = f"Input {name!r} expected a string, got {value!r}."
-                raise ValueError(msg)

        if enum_values is not None and value not in enum_values:
            msg = (
--- a/src/specify_cli/workflows/expressions.py
+++ b/src/specify_cli/workflows/expressions.py
@@ -102,15 +102,6 @@ def _build_namespace(context: Any) -> dict[str, Any]:
        ns["item"] = context.item
    if hasattr(context, "fan_in"):
        ns["fan_in"] = context.fan_in or {}
-    # Engine-managed runtime metadata. Always present (even outside a
-    # run) so templates referencing it never error: `run_id` falls back
-    # to an empty string when no run is active (dry-run, validation,
-    # ad-hoc evaluator usage). The value is the same one Spec Kit
-    # prints as `Run ID:` at the end of `workflow run` — auto-generated
-    # runs use an 8-character uuid4 hex; operator-supplied ids may be
-    # any alphanumeric string with hyphens or underscores.
-    run_id = getattr(context, "run_id", None) or ""
-    ns["context"] = {"run_id": run_id}
    return ns


--- a/templates/commands/clarify.md
+++ b/templates/commands/clarify.md
@@ -197,24 +197,13 @@ Execution steps:

 7. Write the updated spec back to `FEATURE_SPEC`.

-8. **Re-validate Spec Quality Checklist** (if it exists):
-   - Check if `FEATURE_DIR/checklists/requirements.md` exists.
-   - If it does NOT exist, skip this step silently.
-   - If it exists:
-     1. Read the checklist file.
-     2. Identify all GitHub task-list checkbox lines — lines matching `- [ ]`, `- [x]`, or `- [X]` (case-insensitive, tolerant of leading whitespace for nested items) outside of code fences. Ignore all other content (headings, notes, non-checkbox bullets, metadata).
-     3. For each checkbox line, record its current marker state (checked or unchecked) and item text into a before-snapshot list.
-     4. Re-evaluate each checkbox item against the **updated** spec (the version just saved in step 7).
-     5. For each checkbox item, update only if the checked/unchecked state actually changes:
-        - If the item now passes and was unchecked: change `[ ]` to `[x]`.
-        - If the item now fails and was checked: change `[x]`/`[X]` to `[ ]`.
-        - If the state is unchanged: leave the marker as-is (preserve existing case to avoid cosmetic diffs).
-     6. Save the updated checklist file. **Only toggle the `[ ]`/`[x]` marker portion of checkbox lines whose state changed.** All other file content — headings, metadata, notes, line ordering, whitespace — must remain unchanged to avoid noisy diffs.
-     7. Compare the before-snapshot with the current state to compute three lists for the Completion Report:
-        - **Newly passing**: items that changed from unchecked to checked.
-        - **Regressions**: items that changed from checked to unchecked.
-        - **Still unchecked**: items that remain unchecked.
-     8. Record the before/after pass counts as checked/total checkbox items (e.g., "12/16 → 15/16 items passing").
+8. Report completion (after questioning loop ends or early termination):
+   - Number of questions asked & answered.
+   - Path to updated spec.
+   - Sections touched (list names).
+   - Coverage summary table listing each taxonomy category with Status: Resolved (was Partial/Missing and addressed), Deferred (exceeds question quota or better suited for planning), Clear (already sufficient), Outstanding (still Partial/Missing but low impact).
+   - If any Outstanding or Deferred remain, recommend whether to proceed to `__SPECKIT_COMMAND_PLAN__` or run `__SPECKIT_COMMAND_CLARIFY__` again later post-plan.
+   - Suggested next command.

 Behavior rules:

@@ -228,27 +217,17 @@ Behavior rules:

 Context for prioritization: {ARGS}

-## Mandatory Post-Execution Hooks
-
-**You MUST complete this section before reporting completion to the user.**
+## Post-Execution Checks

+**Check for extension hooks (after clarification)**:
 Check if `.specify/extensions.yml` exists in the project root.
- If it does not exist, or no hooks are registered under `hooks.after_clarify`, skip to the Completion Report.
- If it exists, read it and look for entries under the `hooks.after_clarify` key.
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue to the Completion Report.
+- If it exists, read it and look for entries under the `hooks.after_clarify` key
+- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
 - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
 - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
  - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
 - For each executable hook, output the following based on its `optional` flag:
-  - **Mandatory hook** (`optional: false`) — **You MUST emit `EXECUTE_COMMAND:` for each mandatory hook**:
-    ```
-    ## Extension Hooks
-
-    **Automatic Hook**: {extension}
-    Executing: `/{command}`
-    EXECUTE_COMMAND: {command}
-    ```
  - **Optional hook** (`optional: true`):
    ```
    ## Extension Hooks
@@ -260,21 +239,12 @@ Check if `.specify/extensions.yml` exists in the project root.
    Prompt: {prompt}
    To execute: `/{command}`
    ```
+  - **Mandatory hook** (`optional: false`):
+    ```
+    ## Extension Hooks

-## Completion Report
-
-Report completion (after questioning loop ends or early termination):
- Number of questions asked & answered.
- Path to updated spec.
- Sections touched (list names).
- Spec quality checklist status (if `FEATURE_DIR/checklists/requirements.md` was re-validated): show before/after pass counts (e.g., "Spec Quality Checklist: 12/16 → 15/16 items passing") and list any items that changed state — both newly checked (unchecked → checked) and any regressions (checked → unchecked). If any items remain unchecked, list them as areas needing attention.
- Coverage summary table listing each taxonomy category with Status: Resolved (was Partial/Missing and addressed), Deferred (exceeds question quota or better suited for planning), Clear (already sufficient), Outstanding (still Partial/Missing but low impact).
- If any Outstanding or Deferred remain, recommend whether to proceed to `__SPECKIT_COMMAND_PLAN__` or run `__SPECKIT_COMMAND_CLARIFY__` again later post-plan.
- Suggested next command.
-
-## Done When
-
- [ ] Spec ambiguities identified and clarifications integrated into spec file
- [ ] Spec quality checklist re-validated against updated spec (if `FEATURE_DIR/checklists/requirements.md` exists)
- [ ] Extension hooks dispatched or skipped according to the rules in Mandatory Post-Execution Hooks above
- [ ] Completion reported to user with questions answered, sections touched, checklist status, and coverage summary
+    **Automatic Hook**: {extension}
+    Executing: `/{command}`
+    EXECUTE_COMMAND: {command}
+    ```
+- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
--- a/templates/commands/implement.md
+++ b/templates/commands/implement.md
@@ -168,49 +168,35 @@ You **MUST** consider the user input before proceeding (if not empty).
   - Check that implemented features match the original specification
   - Validate that tests pass and coverage meets requirements
   - Confirm the implementation follows the technical plan
+   - Report final status with summary of completed work

 Note: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, suggest running `__SPECKIT_COMMAND_TASKS__` first to regenerate the task list.

-## Mandatory Post-Execution Hooks
+10. **Check for extension hooks**: After completion validation, check if `.specify/extensions.yml` exists in the project root.
+    - If it exists, read it and look for entries under the `hooks.after_implement` key
+    - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
+    - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
+    - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
+      - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
+      - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
+    - For each executable hook, output the following based on its `optional` flag:
+      - **Optional hook** (`optional: true`):
+        ```
+        ## Extension Hooks

-**You MUST complete this section before reporting completion to the user.**
+        **Optional Hook**: {extension}
+        Command: `/{command}`
+        Description: {description}

-Check if `.specify/extensions.yml` exists in the project root.
- If it does not exist, or no hooks are registered under `hooks.after_implement`, skip to the Completion Report.
- If it exists, read it and look for entries under the `hooks.after_implement` key.
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue to the Completion Report.
- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
-  - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
-  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
- For each executable hook, output the following based on its `optional` flag:
-  - **Mandatory hook** (`optional: false`) — **You MUST emit `EXECUTE_COMMAND:` for each mandatory hook**:
-    ```
-    ## Extension Hooks
+        Prompt: {prompt}
+        To execute: `/{command}`
+        ```
+      - **Mandatory hook** (`optional: false`):
+        ```
+        ## Extension Hooks

-    **Automatic Hook**: {extension}
-    Executing: `/{command}`
-    EXECUTE_COMMAND: {command}
-    ```
-  - **Optional hook** (`optional: true`):
-    ```
-    ## Extension Hooks
-
-    **Optional Hook**: {extension}
-    Command: `/{command}`
-    Description: {description}
-
-    Prompt: {prompt}
-    To execute: `/{command}`
-    ```
-
-## Completion Report
-
-Report final status with summary of completed work.
-
-## Done When
-
- [ ] All tasks in tasks.md completed and marked `[X]`
- [ ] Implementation validated against specification, plan, and test coverage
- [ ] Extension hooks dispatched or skipped according to the rules in Mandatory Post-Execution Hooks above
- [ ] Completion reported to user with summary of completed work
+        **Automatic Hook**: {extension}
+        Executing: `/{command}`
+        EXECUTE_COMMAND: {command}
+        ```
+    - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
--- a/templates/commands/plan.md
+++ b/templates/commands/plan.md
@@ -70,42 +70,36 @@ You **MUST** consider the user input before proceeding (if not empty).
   - Phase 1: Update agent context by running the agent script
   - Re-evaluate Constitution Check post-design

-## Mandatory Post-Execution Hooks
+4. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.

-**You MUST complete this section before reporting completion to the user.**
+5. **Check for extension hooks**: After reporting, check if `.specify/extensions.yml` exists in the project root.
+   - If it exists, read it and look for entries under the `hooks.after_plan` key
+   - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
+   - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
+   - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
+     - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
+     - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
+   - For each executable hook, output the following based on its `optional` flag:
+     - **Optional hook** (`optional: true`):
+       ```
+       ## Extension Hooks

-Check if `.specify/extensions.yml` exists in the project root.
- If it does not exist, or no hooks are registered under `hooks.after_plan`, skip to the Completion Report.
- If it exists, read it and look for entries under the `hooks.after_plan` key.
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue to the Completion Report.
- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
-  - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
-  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
- For each executable hook, output the following based on its `optional` flag:
-  - **Mandatory hook** (`optional: false`) — **You MUST emit `EXECUTE_COMMAND:` for each mandatory hook**:
-    ```
-    ## Extension Hooks
+       **Optional Hook**: {extension}
+       Command: `/{command}`
+       Description: {description}

-    **Automatic Hook**: {extension}
-    Executing: `/{command}`
-    EXECUTE_COMMAND: {command}
-    ```
-  - **Optional hook** (`optional: true`):
-    ```
-    ## Extension Hooks
+       Prompt: {prompt}
+       To execute: `/{command}`
+       ```
+     - **Mandatory hook** (`optional: false`):
+       ```
+       ## Extension Hooks

-    **Optional Hook**: {extension}
-    Command: `/{command}`
-    Description: {description}
-
-    Prompt: {prompt}
-    To execute: `/{command}`
-    ```
-
-## Completion Report
-
-Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
+       **Automatic Hook**: {extension}
+       Executing: `/{command}`
+       EXECUTE_COMMAND: {command}
+       ```
+   - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently

 ## Phases

@@ -156,9 +150,3 @@ Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generate

 - Use absolute paths for filesystem operations; use project-relative paths for references in documentation and agent context files
 - ERROR on gate failures or unresolved clarifications
-
-## Done When
-
- [ ] Plan workflow executed and design artifacts generated
- [ ] Extension hooks dispatched or skipped according to the rules in Mandatory Post-Execution Hooks above
- [ ] Completion reported to user with branch, plan path, and generated artifacts
--- a/templates/commands/specify.md
+++ b/templates/commands/specify.md
@@ -183,7 +183,7 @@ Given that feature description, do this:

   c. **Handle Validation Results**:

-      - **If all items pass**: Mark checklist complete and proceed to the Mandatory Post-Execution Hooks section
+      - **If all items pass**: Mark checklist complete and proceed to step 8

      - **If items fail (excluding [NEEDS CLARIFICATION])**:
        1. List the failing items and specific issues
@@ -228,46 +228,40 @@ Given that feature description, do this:

   d. **Update Checklist**: After each validation iteration, update the checklist file with current pass/fail status

-## Mandatory Post-Execution Hooks
+8. **Report completion** to the user with:
+   - `SPECIFY_FEATURE_DIRECTORY` — the feature directory path
+   - `SPEC_FILE` — the spec file path
+   - Checklist results summary
+   - Readiness for the next phase (`__SPECKIT_COMMAND_CLARIFY__` or `__SPECKIT_COMMAND_PLAN__`)

-**You MUST complete this section before reporting completion to the user.**
+9. **Check for extension hooks**: After reporting completion, check if `.specify/extensions.yml` exists in the project root.
+   - If it exists, read it and look for entries under the `hooks.after_specify` key
+   - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
+   - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
+   - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
+     - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
+     - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
+   - For each executable hook, output the following based on its `optional` flag:
+     - **Optional hook** (`optional: true`):
+       ```
+       ## Extension Hooks

-Check if `.specify/extensions.yml` exists in the project root.
- If it does not exist, or no hooks are registered under `hooks.after_specify`, skip to the Completion Report.
- If it exists, read it and look for entries under the `hooks.after_specify` key.
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue to the Completion Report.
- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
-  - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
-  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
- For each executable hook, output the following based on its `optional` flag:
-  - **Mandatory hook** (`optional: false`) — **You MUST emit `EXECUTE_COMMAND:` for each mandatory hook**:
-    ```
-    ## Extension Hooks
+       **Optional Hook**: {extension}
+       Command: `/{command}`
+       Description: {description}

-    **Automatic Hook**: {extension}
-    Executing: `/{command}`
-    EXECUTE_COMMAND: {command}
-    ```
-  - **Optional hook** (`optional: true`):
-    ```
-    ## Extension Hooks
+       Prompt: {prompt}
+       To execute: `/{command}`
+       ```
+     - **Mandatory hook** (`optional: false`):
+       ```
+       ## Extension Hooks

-    **Optional Hook**: {extension}
-    Command: `/{command}`
-    Description: {description}
-
-    Prompt: {prompt}
-    To execute: `/{command}`
-    ```
-
-## Completion Report
-
-Report completion to the user with:
- `SPECIFY_FEATURE_DIRECTORY` — the feature directory path
- `SPEC_FILE` — the spec file path
- Checklist results summary
- Readiness for the next phase (`__SPECKIT_COMMAND_CLARIFY__` or `__SPECKIT_COMMAND_PLAN__`)
+       **Automatic Hook**: {extension}
+       Executing: `/{command}`
+       EXECUTE_COMMAND: {command}
+       ```
+   - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently

 **NOTE:** Branch creation is handled by the `before_specify` hook (git extension). Spec directory and file creation are always handled by this core command.

@@ -331,9 +325,3 @@ Success criteria must be:
 - "Database can handle 1000 TPS" (implementation detail, use user-facing metric)
 - "React components render efficiently" (framework-specific)
 - "Redis cache hit rate above 80%" (technology-specific)
-
-## Done When
-
- [ ] Specification written to `SPEC_FILE` and validated against quality checklist
- [ ] Extension hooks dispatched or skipped according to the rules in Mandatory Post-Execution Hooks above
- [ ] Completion reported to user with feature directory, spec file path, and checklist results
--- a/templates/commands/tasks.md
+++ b/templates/commands/tasks.md
@@ -89,48 +89,42 @@ You **MUST** consider the user input before proceeding (if not empty).
   - Parallel execution examples per story
   - Implementation strategy section (MVP first, incremental delivery)

-## Mandatory Post-Execution Hooks
+5. **Report**: Output path to generated tasks.md and summary:
+   - Total task count
+   - Task count per user story
+   - Parallel opportunities identified
+   - Independent test criteria for each story
+   - Suggested MVP scope (typically just User Story 1)
+   - Format validation: Confirm ALL tasks follow the checklist format (checkbox, ID, labels, file paths)

-**You MUST complete this section before reporting completion to the user.**
+6. **Check for extension hooks**: After tasks.md is generated, check if `.specify/extensions.yml` exists in the project root.
+   - If it exists, read it and look for entries under the `hooks.after_tasks` key
+   - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
+   - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
+   - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
+     - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
+     - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
+   - For each executable hook, output the following based on its `optional` flag:
+     - **Optional hook** (`optional: true`):
+       ```
+       ## Extension Hooks

-Check if `.specify/extensions.yml` exists in the project root.
- If it does not exist, or no hooks are registered under `hooks.after_tasks`, skip to the Completion Report.
- If it exists, read it and look for entries under the `hooks.after_tasks` key.
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue to the Completion Report.
- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
-  - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
-  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
- For each executable hook, output the following based on its `optional` flag:
-  - **Mandatory hook** (`optional: false`) — **You MUST emit `EXECUTE_COMMAND:` for each mandatory hook**:
-    ```
-    ## Extension Hooks
+       **Optional Hook**: {extension}
+       Command: `/{command}`
+       Description: {description}

-    **Automatic Hook**: {extension}
-    Executing: `/{command}`
-    EXECUTE_COMMAND: {command}
-    ```
-  - **Optional hook** (`optional: true`):
-    ```
-    ## Extension Hooks
+       Prompt: {prompt}
+       To execute: `/{command}`
+       ```
+     - **Mandatory hook** (`optional: false`):
+       ```
+       ## Extension Hooks

-    **Optional Hook**: {extension}
-    Command: `/{command}`
-    Description: {description}
-
-    Prompt: {prompt}
-    To execute: `/{command}`
-    ```
-
-## Completion Report
-
-Output path to generated tasks.md and summary:
- Total task count
- Task count per user story
- Parallel opportunities identified
- Independent test criteria for each story
- Suggested MVP scope (typically just User Story 1)
- Format validation: Confirm ALL tasks follow the checklist format (checkbox, ID, labels, file paths)
+       **Automatic Hook**: {extension}
+       Executing: `/{command}`
+       EXECUTE_COMMAND: {command}
+       ```
+   - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently

 Context for task generation: {ARGS}

@@ -207,9 +201,3 @@ Every task MUST strictly follow this format:
  - Within each story: Tests (if requested) → Models → Services → Endpoints → Integration
  - Each phase should be a complete, independently testable increment
 - **Final Phase**: Polish & Cross-Cutting Concerns
-
-## Done When
-
- [ ] tasks.md generated with all phases, task IDs, and file paths
- [ ] Extension hooks dispatched or skipped according to the rules in Mandatory Post-Execution Hooks above
- [ ] Completion reported to user with task count, story breakdown, and MVP scope
--- a/templates/plan-template.md
+++ b/templates/plan-template.md
@@ -1,7 +1,6 @@
 # Implementation Plan: [FEATURE]

 **Branch**: `[###-feature-name]` | **Date**: [DATE] | **Spec**: [link]
-
 **Input**: Feature specification from `/specs/[###-feature-name]/spec.md`

 **Note**: This template is filled in by the `__SPECKIT_COMMAND_PLAN__` command. See `.specify/templates/plan-template.md` for the execution workflow.
@@ -18,22 +17,14 @@
  the iteration process.
 -->

-**Language/Version**: [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION]
-
-**Primary Dependencies**: [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]
-
-**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]
-
-**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]
-
+**Language/Version**: [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION]  
+**Primary Dependencies**: [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]  
+**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]  
+**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]  
 **Target Platform**: [e.g., Linux server, iOS 15+, WASM or NEEDS CLARIFICATION]
-
-**Project Type**: [e.g., library/cli/web-service/mobile-app/compiler/desktop-app or NEEDS CLARIFICATION]
-
-**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps or NEEDS CLARIFICATION]
-
-**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory, offline-capable or NEEDS CLARIFICATION]
-
+**Project Type**: [e.g., library/cli/web-service/mobile-app/compiler/desktop-app or NEEDS CLARIFICATION]  
+**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps or NEEDS CLARIFICATION]  
+**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory, offline-capable or NEEDS CLARIFICATION]  
 **Scale/Scope**: [domain-specific, e.g., 10k users, 1M LOC, 50 screens or NEEDS CLARIFICATION]

 ## Constitution Check
--- a/templates/spec-template.md
+++ b/templates/spec-template.md
@@ -1,11 +1,8 @@
 # Feature Specification: [FEATURE NAME]

-**Feature Branch**: `[###-feature-name]`
-
-**Created**: [DATE]
-
-**Status**: Draft
-
+**Feature Branch**: `[###-feature-name]`  
+**Created**: [DATE]  
+**Status**: Draft  
 **Input**: User description: "$ARGUMENTS"

 ## User Scenarios & Testing *(mandatory)*
@@ -14,7 +11,7 @@
  IMPORTANT: User stories should be PRIORITIZED as user journeys ordered by importance.
  Each user story/journey must be INDEPENDENTLY TESTABLE - meaning if you implement just ONE of them,
  you should still have a viable MVP (Minimum Viable Product) that delivers value.
-
+  
  Assign priorities (P1, P2, P3, etc.) to each story, where P1 is the most critical.
  Think of each story as a standalone slice of functionality that can be:
  - Developed independently
@@ -88,7 +85,7 @@
 ### Functional Requirements

 - **FR-001**: System MUST [specific capability, e.g., "allow users to create accounts"]
- **FR-002**: System MUST [specific capability, e.g., "validate email addresses"]
+- **FR-002**: System MUST [specific capability, e.g., "validate email addresses"]  
 - **FR-003**: Users MUST be able to [key interaction, e.g., "reset their password"]
 - **FR-004**: System MUST [data requirement, e.g., "persist user preferences"]
 - **FR-005**: System MUST [behavior, e.g., "log all security events"]
--- a/templates/tasks-template.md
+++ b/templates/tasks-template.md
@@ -6,7 +6,6 @@ description: "Task list template for feature implementation"
 # Tasks: [FEATURE NAME]

 **Input**: Design documents from `/specs/[###-feature-name]/`
-
 **Prerequisites**: plan.md (required), spec.md (required for user stories), research.md, data-model.md, contracts/

 **Tests**: The examples below include test tasks. Tests are OPTIONAL - only include them if explicitly requested in the feature specification.
@@ -26,21 +25,21 @@ description: "Task list template for feature implementation"
 - **Mobile**: `api/src/`, `ios/src/` or `android/src/`
 - Paths shown below assume single project - adjust based on plan.md structure

-<!--
+<!-- 
  ============================================================================
  IMPORTANT: The tasks below are SAMPLE TASKS for illustration purposes only.
-
+  
  The __SPECKIT_COMMAND_TASKS__ command MUST replace these with actual tasks based on:
  - User stories from spec.md (with their priorities P1, P2, P3...)
  - Feature requirements from plan.md
  - Entities from data-model.md
  - Endpoints from contracts/
-
+  
  Tasks MUST be organized by user story so each story can be:
  - Implemented independently
  - Tested independently
  - Delivered as an MVP increment
-
+  
  DO NOT keep these sample tasks in the generated tasks.md file.
  ============================================================================
 -->
--- a/tests/auth_helpers.py
+++ b/tests/auth_helpers.py
@@ -1,21 +0,0 @@
-"""Shared test helpers for authentication config injection."""
-
-from __future__ import annotations
-
-from specify_cli.authentication.config import AuthConfigEntry
-
-
-def make_github_auth_entry(token_env: str = "GH_TOKEN") -> AuthConfigEntry:
-    """Build a GitHub ``AuthConfigEntry`` for testing."""
-    return AuthConfigEntry(
-        hosts=("github.com", "api.github.com", "raw.githubusercontent.com", "codeload.github.com"),
-        provider="github",
-        auth="bearer",
-        token_env=token_env,
-    )
-
-
-def inject_github_config(monkeypatch, token_env: str = "GH_TOKEN") -> None:
-    """Inject a GitHub auth.json config entry into the auth HTTP module."""
-    from specify_cli.authentication import http as _auth_http
-    monkeypatch.setattr(_auth_http, "_config_override", [make_github_auth_entry(token_env)])
--- a/Show More
+++ b/Show More