Add apm_cli to pyproject.toml and fix apm module url validation

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

.devcontainer/devcontainer.json

@@ -1,75 +0,0 @@
-// For format details, see https://aka.ms/devcontainer.json. For config options, see the
-// README at: https://github.com/devcontainers/templates/tree/main/src/python
-{
-	"name": "SpecKitDevContainer",
-	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
-	"image": "mcr.microsoft.com/devcontainers/python:3.13-trixie", // based on Debian "Trixie" (13)
-	"features": {
-		"ghcr.io/devcontainers/features/common-utils:2": {
-			"installZsh": true,
-			"installOhMyZsh": true,
-			"installOhMyZshConfig": true,
-			"upgradePackages": true,
-			"username": "devcontainer",
-			"userUid": "automatic",
-			"userGid": "automatic"
-		},
-		"ghcr.io/devcontainers/features/dotnet:2": {
-			"version": "lts"
-		},
-		"ghcr.io/devcontainers/features/git:1": {
-			"ppa": true,
-			"version": "latest"
-		},
-		"ghcr.io/devcontainers/features/node": {
-			"version": "lts"
-		}
-	},
-
-	// Use 'forwardPorts' to make a list of ports inside the container available locally.
-  "forwardPorts": [
-	8080 // for Spec-Kit documentation site
-  ],
-  "containerUser": "devcontainer",
-  "updateRemoteUserUID": true,
-  "postCreateCommand": "chmod +x ./.devcontainer/post-create.sh && ./.devcontainer/post-create.sh",
-  "postStartCommand": "git config --global --add safe.directory ${containerWorkspaceFolder}",
-  "customizations": {
-    "vscode": {
-      "extensions": [
-		"mhutchie.git-graph",
-		"eamodio.gitlens",
-		"anweber.reveal-button",
-		"chrisdias.promptboost",
-		// Github Copilot
-		"GitHub.copilot",
-		"GitHub.copilot-chat",
-		// Codex
-		"openai.chatgpt",
-		// Kilo Code
-		"kilocode.Kilo-Code",
-		// Roo Code
-		"RooVeterinaryInc.roo-cline",
-		// Claude Code
-		"anthropic.claude-code"
-	],
-      "settings": {
-		"debug.javascript.autoAttachFilter": "disabled", // fix running commands in integrated terminal
-
-		// Specify settings for Github Copilot
-		"git.autofetch": true,
-		"chat.promptFilesRecommendations": {
-			"speckit.constitution": true,
-			"speckit.specify": true,
-			"speckit.plan": true,
-			"speckit.tasks": true,
-			"speckit.implement": true
-		},
-		"chat.tools.terminal.autoApprove": {
-			".specify/scripts/bash/": true,
-			".specify/scripts/powershell/": true
-		}
-      }
-    }
-  }
-}

.devcontainer/post-create.sh

@@ -1,101 +0,0 @@
-#!/bin/bash
-
-# Exit immediately on error, treat unset variables as an error, and fail if any command in a pipeline fails.
-set -euo pipefail
-
-# Function to run a command and show logs only on error
-run_command() {
-    local command_to_run="$*"
-    local output
-    local exit_code
-    
-    # Capture all output (stdout and stderr)
-    output=$(eval "$command_to_run" 2>&1) || exit_code=$?
-    exit_code=${exit_code:-0}
-    
-    if [ $exit_code -ne 0 ]; then
-        echo -e "\033[0;31m[ERROR] Command failed (Exit Code $exit_code): $command_to_run\033[0m" >&2
-        echo -e "\033[0;31m$output\033[0m" >&2
-        
-        exit $exit_code
-    fi
-}
-
-# Installing CLI-based AI Agents
-
-echo -e "\n🤖 Installing Copilot CLI..."
-run_command "npm install -g @github/copilot@latest"
-echo "✅ Done"
-
-echo -e "\n🤖 Installing Claude CLI..."
-run_command "npm install -g @anthropic-ai/claude-code@latest"
-echo "✅ Done"
-
-echo -e "\n🤖 Installing Codex CLI..."
-run_command "npm install -g @openai/codex@latest"
-echo "✅ Done"
-
-echo -e "\n🤖 Installing Gemini CLI..."
-run_command "npm install -g @google/gemini-cli@latest"
-echo "✅ Done"
-
-echo -e "\n🤖 Installing Augie CLI..."
-run_command "npm install -g @augmentcode/auggie@latest"
-echo "✅ Done"
-
-echo -e "\n🤖 Installing Qwen Code CLI..."
-run_command "npm install -g @qwen-code/qwen-code@latest"
-echo "✅ Done"
-
-echo -e "\n🤖 Installing OpenCode CLI..."
-run_command "npm install -g opencode-ai@latest"
-echo "✅ Done"
-
-echo -e "\n🤖 Installing Kiro CLI..."
-# https://kiro.dev/docs/cli/
-KIRO_INSTALLER_URL="https://cli.kiro.dev/install"
-KIRO_INSTALLER_SHA256="7487a65cf310b7fb59b357c4b5e6e3f3259d383f4394ecedb39acf70f307cffb"
-KIRO_INSTALLER_PATH="$(mktemp)"
-
-cleanup_kiro_installer() {
-  rm -f "$KIRO_INSTALLER_PATH"
-}
-trap cleanup_kiro_installer EXIT
-
-run_command "curl -fsSL \"$KIRO_INSTALLER_URL\" -o \"$KIRO_INSTALLER_PATH\""
-run_command "echo \"$KIRO_INSTALLER_SHA256  $KIRO_INSTALLER_PATH\" | sha256sum -c -"
-
-run_command "bash \"$KIRO_INSTALLER_PATH\""
-
-kiro_binary=""
-if command -v kiro-cli >/dev/null 2>&1; then
-  kiro_binary="kiro-cli"
-elif command -v kiro >/dev/null 2>&1; then
-  kiro_binary="kiro"
-else
-  echo -e "\033[0;31m[ERROR] Kiro CLI installation did not create 'kiro-cli' or 'kiro' in PATH.\033[0m" >&2
-  exit 1
-fi
-
-run_command "$kiro_binary --help > /dev/null"
-echo "✅ Done"
-
-echo -e "\n🤖 Installing CodeBuddy CLI..."
-run_command "npm install -g @tencent-ai/codebuddy-code@latest"
-echo "✅ Done"
-
-# Installing UV (Python package manager)
-echo -e "\n🐍 Installing UV - Python Package Manager..."
-run_command "pipx install uv"
-echo "✅ Done"
-
-# Installing DocFx (for documentation site)
-echo -e "\n📚 Installing DocFx..."
-run_command "dotnet tool update -g docfx"
-echo "✅ Done"
-
-echo -e "\n🧹 Cleaning cache..."
-run_command "sudo apt-get autoclean"
-run_command "sudo apt-get clean"
-
-echo "✅ Setup completed. Happy coding! 🚀"

.gitattributes

@@ -1 +0,0 @@
-* text=auto eol=lf

.github/CODEOWNERS

@@ -1,3 +1,7 @@
 # Global code owner
-* @mnriem
+* @localden
 
+# APM CLI code owner
+src/apm_cli/ @danielmeppiel
+templates/apm/ @danielmeppiel
+docs/context-management.md @danielmeppiel

.github/ISSUE_TEMPLATE/agent_request.yml

@@ -1,141 +0,0 @@
-name: Agent Request
-description: Request support for a new AI agent/assistant in Spec Kit
-title: "[Agent]: Add support for "
-labels: ["agent-request", "enhancement", "needs-triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for requesting a new agent! Before submitting, please check if the agent is already supported.
-        
-        **Currently supported agents**: Claude Code, Gemini CLI, GitHub Copilot, Cursor, Qwen Code, opencode, Codex CLI, Windsurf, Kilo Code, Auggie CLI, Roo Code, CodeBuddy, Qoder CLI, Kiro CLI, Amp, SHAI, IBM Bob, Antigravity
-
-  - type: input
-    id: agent-name
-    attributes:
-      label: Agent Name
-      description: What is the name of the AI agent/assistant?
-      placeholder: "e.g., SuperCoder AI"
-    validations:
-      required: true
-
-  - type: input
-    id: website
-    attributes:
-      label: Official Website
-      description: Link to the agent's official website or documentation
-      placeholder: "https://..."
-    validations:
-      required: true
-
-  - type: dropdown
-    id: agent-type
-    attributes:
-      label: Agent Type
-      description: How is the agent accessed?
-      options:
-        - CLI tool (command-line interface)
-        - IDE extension/plugin
-        - Both CLI and IDE
-        - Other
-    validations:
-      required: true
-
-  - type: input
-    id: cli-command
-    attributes:
-      label: CLI Command (if applicable)
-      description: What command is used to invoke the agent from terminal?
-      placeholder: "e.g., supercode, ai-assistant"
-
-  - type: input
-    id: install-method
-    attributes:
-      label: Installation Method
-      description: How is the agent installed?
-      placeholder: "e.g., npm install -g supercode, pip install supercode, IDE marketplace"
-    validations:
-      required: true
-
-  - type: textarea
-    id: command-structure
-    attributes:
-      label: Command/Workflow Structure
-      description: How does the agent define custom commands or workflows?
-      placeholder: |
-        - Command file format (Markdown, YAML, TOML, etc.)
-        - Directory location (e.g., .supercode/commands/)
-        - Example command file structure
-    validations:
-      required: true
-
-  - type: textarea
-    id: argument-pattern
-    attributes:
-      label: Argument Passing Pattern
-      description: How does the agent handle arguments in commands?
-      placeholder: |
-        e.g., Uses {{args}}, $ARGUMENTS, %ARGS%, or other placeholder format
-        Example: "Run test suite with {{args}}"
-
-  - type: dropdown
-    id: popularity
-    attributes:
-      label: Popularity/Usage
-      description: How widely is this agent used?
-      options:
-        - Widely used (thousands+ of users)
-        - Growing adoption (hundreds of users)
-        - New/emerging (less than 100 users)
-        - Unknown
-    validations:
-      required: true
-
-  - type: textarea
-    id: documentation
-    attributes:
-      label: Documentation Links
-      description: Links to relevant documentation for custom commands/workflows
-      placeholder: |
-        - Command documentation: https://...
-        - API/CLI reference: https://...
-        - Examples: https://...
-
-  - type: textarea
-    id: use-case
-    attributes:
-      label: Use Case
-      description: Why do you want this agent supported in Spec Kit?
-      placeholder: Explain your workflow and how this agent fits into your development process
-    validations:
-      required: true
-
-  - type: textarea
-    id: example-command
-    attributes:
-      label: Example Command File
-      description: If possible, provide an example of a command file for this agent
-      render: markdown
-      placeholder: |
-        ```toml
-        description = "Example command"
-        prompt = "Do something with {{args}}"
-        ```
-
-  - type: checkboxes
-    id: contribution
-    attributes:
-      label: Contribution
-      description: Are you willing to help implement support for this agent?
-      options:
-        - label: I can help test the integration
-        - label: I can provide example command files
-        - label: I can help with documentation
-        - label: I can submit a pull request for the integration
-
-  - type: textarea
-    id: context
-    attributes:
-      label: Additional Context
-      description: Any other relevant information about this agent
-      placeholder: Screenshots, community links, comparison to existing agents, etc.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,118 +0,0 @@
-name: Bug Report
-description: Report a bug or unexpected behavior in Specify CLI or Spec Kit
-title: "[Bug]: "
-labels: ["bug", "needs-triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to report a bug! Please fill out the sections below to help us diagnose and fix the issue.
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Bug Description
-      description: A clear and concise description of what the bug is.
-      placeholder: What went wrong?
-    validations:
-      required: true
-
-  - type: textarea
-    id: reproduce
-    attributes:
-      label: Steps to Reproduce
-      description: Steps to reproduce the behavior
-      placeholder: |
-        1. Run command '...'
-        2. Execute script '...'
-        3. See error
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected
-    attributes:
-      label: Expected Behavior
-      description: What did you expect to happen?
-      placeholder: Describe the expected outcome
-    validations:
-      required: true
-
-  - type: textarea
-    id: actual
-    attributes:
-      label: Actual Behavior
-      description: What actually happened?
-      placeholder: Describe what happened instead
-    validations:
-      required: true
-
-  - type: input
-    id: version
-    attributes:
-      label: Specify CLI Version
-      description: "Run `specify version` or `pip show spec-kit`"
-      placeholder: "e.g., 1.3.0"
-    validations:
-      required: true
-
-  - type: dropdown
-    id: ai-agent
-    attributes:
-      label: AI Agent
-      description: Which AI agent are you using?
-      options:
-        - Claude Code
-        - Gemini CLI
-        - GitHub Copilot
-        - Cursor
-        - Qwen Code
-        - opencode
-        - Codex CLI
-        - Windsurf
-        - Kilo Code
-        - Auggie CLI
-        - Roo Code
-        - CodeBuddy
-        - Qoder CLI
-        - Kiro CLI
-        - Amp
-        - SHAI
-        - IBM Bob
-        - Antigravity
-        - Not applicable
-    validations:
-      required: true
-
-  - type: input
-    id: os
-    attributes:
-      label: Operating System
-      description: Your operating system and version
-      placeholder: "e.g., macOS 14.2, Ubuntu 22.04, Windows 11"
-    validations:
-      required: true
-
-  - type: input
-    id: python
-    attributes:
-      label: Python Version
-      description: "Run `python --version` or `python3 --version`"
-      placeholder: "e.g., Python 3.11.5"
-    validations:
-      required: true
-
-  - type: textarea
-    id: logs
-    attributes:
-      label: Error Logs
-      description: Please paste any relevant error messages or logs
-      render: shell
-      placeholder: Paste error output here
-
-  - type: textarea
-    id: context
-    attributes:
-      label: Additional Context
-      description: Add any other context about the problem
-      placeholder: Screenshots, related issues, workarounds attempted, etc.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,17 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: 💬 General Discussion
-    url: https://github.com/github/spec-kit/discussions
-    about: Ask questions, share ideas, or discuss Spec-Driven Development
-  - name: 📖 Documentation
-    url: https://github.com/github/spec-kit/blob/main/README.md
-    about: Read the Spec Kit documentation and guides
-  - name: 🛠️ Extension Development Guide
-    url: https://github.com/manfredseee/spec-kit/blob/main/extensions/EXTENSION-DEVELOPMENT-GUIDE.md
-    about: Learn how to develop and publish Spec Kit extensions
-  - name: 🤝 Contributing Guide
-    url: https://github.com/github/spec-kit/blob/main/CONTRIBUTING.md
-    about: Learn how to contribute to Spec Kit
-  - name: 🔒 Security Issues
-    url: https://github.com/github/spec-kit/blob/main/SECURITY.md
-    about: Report security vulnerabilities privately

.github/ISSUE_TEMPLATE/extension_submission.yml

@@ -1,280 +0,0 @@
-name: Extension Submission
-description: Submit your extension to the Spec Kit catalog
-title: "[Extension]: Add "
-labels: ["extension-submission", "enhancement", "needs-triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for contributing an extension! This template helps you submit your extension to the community catalog.
-        
-        **Before submitting:**
-        - Review the [Extension Publishing Guide](https://github.com/github/spec-kit/blob/main/extensions/EXTENSION-PUBLISHING-GUIDE.md)
-        - Ensure your extension has a valid `extension.yml` manifest
-        - Create a GitHub release with a version tag (e.g., v1.0.0)
-        - Test installation: `specify extension add --from <your-release-url>`
-
-  - type: input
-    id: extension-id
-    attributes:
-      label: Extension ID
-      description: Unique extension identifier (lowercase with hyphens only)
-      placeholder: "e.g., jira-integration"
-    validations:
-      required: true
-
-  - type: input
-    id: extension-name
-    attributes:
-      label: Extension Name
-      description: Human-readable extension name
-      placeholder: "e.g., Jira Integration"
-    validations:
-      required: true
-
-  - type: input
-    id: version
-    attributes:
-      label: Version
-      description: Semantic version number
-      placeholder: "e.g., 1.0.0"
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-      description: Brief description of what your extension does (under 200 characters)
-      placeholder: Integrates Jira issue tracking with Spec Kit workflows for seamless task management
-    validations:
-      required: true
-
-  - type: input
-    id: author
-    attributes:
-      label: Author
-      description: Your name or organization
-      placeholder: "e.g., John Doe or Acme Corp"
-    validations:
-      required: true
-
-  - type: input
-    id: repository
-    attributes:
-      label: Repository URL
-      description: GitHub repository URL for your extension
-      placeholder: "https://github.com/your-org/spec-kit-your-extension"
-    validations:
-      required: true
-
-  - type: input
-    id: download-url
-    attributes:
-      label: Download URL
-      description: URL to the GitHub release archive (e.g., v1.0.0.zip)
-      placeholder: "https://github.com/your-org/spec-kit-your-extension/archive/refs/tags/v1.0.0.zip"
-    validations:
-      required: true
-
-  - type: input
-    id: license
-    attributes:
-      label: License
-      description: Open source license type
-      placeholder: "e.g., MIT, Apache-2.0"
-    validations:
-      required: true
-
-  - type: input
-    id: homepage
-    attributes:
-      label: Homepage (optional)
-      description: Link to extension homepage or documentation site
-      placeholder: "https://..."
-
-  - type: input
-    id: documentation
-    attributes:
-      label: Documentation URL (optional)
-      description: Link to detailed documentation
-      placeholder: "https://github.com/your-org/spec-kit-your-extension/blob/main/docs/"
-
-  - type: input
-    id: changelog
-    attributes:
-      label: Changelog URL (optional)
-      description: Link to changelog file
-      placeholder: "https://github.com/your-org/spec-kit-your-extension/blob/main/CHANGELOG.md"
-
-  - type: input
-    id: speckit-version
-    attributes:
-      label: Required Spec Kit Version
-      description: Minimum Spec Kit version required
-      placeholder: "e.g., >=0.1.0"
-    validations:
-      required: true
-
-  - type: textarea
-    id: required-tools
-    attributes:
-      label: Required Tools (optional)
-      description: List any external tools or dependencies required
-      placeholder: |
-        - jira-cli (>=1.0.0) - required
-        - python (>=3.8) - optional
-      render: markdown
-
-  - type: input
-    id: commands-count
-    attributes:
-      label: Number of Commands
-      description: How many commands does your extension provide?
-      placeholder: "e.g., 3"
-    validations:
-      required: true
-
-  - type: input
-    id: hooks-count
-    attributes:
-      label: Number of Hooks (optional)
-      description: How many hooks does your extension provide?
-      placeholder: "e.g., 0"
-
-  - type: textarea
-    id: tags
-    attributes:
-      label: Tags
-      description: 2-5 relevant tags (lowercase, separated by commas)
-      placeholder: "issue-tracking, jira, atlassian, automation"
-    validations:
-      required: true
-
-  - type: textarea
-    id: features
-    attributes:
-      label: Key Features
-      description: List the main features and capabilities of your extension
-      placeholder: |
-        - Create Jira issues from specs
-        - Sync task status with Jira
-        - Link specs to existing issues
-        - Generate Jira reports
-    validations:
-      required: true
-
-  - type: checkboxes
-    id: testing
-    attributes:
-      label: Testing Checklist
-      description: Confirm that your extension has been tested
-      options:
-        - label: Extension installs successfully via download URL
-          required: true
-        - label: All commands execute without errors
-          required: true
-        - label: Documentation is complete and accurate
-          required: true
-        - label: No security vulnerabilities identified
-          required: true
-        - label: Tested on at least one real project
-          required: true
-
-  - type: checkboxes
-    id: requirements
-    attributes:
-      label: Submission Requirements
-      description: Verify your extension meets all requirements
-      options:
-        - label: Valid `extension.yml` manifest included
-          required: true
-        - label: README.md with installation and usage instructions
-          required: true
-        - label: LICENSE file included
-          required: true
-        - label: GitHub release created with version tag
-          required: true
-        - label: All command files exist and are properly formatted
-          required: true
-        - label: Extension ID follows naming conventions (lowercase-with-hyphens)
-          required: true
-
-  - type: textarea
-    id: testing-details
-    attributes:
-      label: Testing Details
-      description: Describe how you tested your extension
-      placeholder: |
-        **Tested on:**
-        - macOS 14.0 with Spec Kit v0.1.0
-        - Linux Ubuntu 22.04 with Spec Kit v0.1.0
-        
-        **Test project:** [Link or description]
-        
-        **Test scenarios:**
-        1. Installed extension
-        2. Configured settings
-        3. Ran all commands
-        4. Verified outputs
-    validations:
-      required: true
-
-  - type: textarea
-    id: example-usage
-    attributes:
-      label: Example Usage
-      description: Provide a simple example of using your extension
-      render: markdown
-      placeholder: |
-        ```bash
-        # Install extension
-        specify extension add --from https://github.com/your-org/spec-kit-your-extension/archive/refs/tags/v1.0.0.zip
-        
-        # Use a command
-        /speckit.your-extension.command-name arg1 arg2
-        ```
-    validations:
-      required: true
-
-  - type: textarea
-    id: catalog-entry
-    attributes:
-      label: Proposed Catalog Entry
-      description: Provide the JSON entry for catalog.json (helps reviewers)
-      render: json
-      placeholder: |
-        {
-          "your-extension": {
-            "name": "Your Extension",
-            "id": "your-extension",
-            "description": "Brief description",
-            "author": "Your Name",
-            "version": "1.0.0",
-            "download_url": "https://github.com/your-org/spec-kit-your-extension/archive/refs/tags/v1.0.0.zip",
-            "repository": "https://github.com/your-org/spec-kit-your-extension",
-            "homepage": "https://github.com/your-org/spec-kit-your-extension",
-            "license": "MIT",
-            "requires": {
-              "speckit_version": ">=0.1.0"
-            },
-            "provides": {
-              "commands": 3
-            },
-            "tags": ["category", "tool"],
-            "verified": false,
-            "downloads": 0,
-            "stars": 0,
-            "created_at": "2026-02-20T00:00:00Z",
-            "updated_at": "2026-02-20T00:00:00Z"
-          }
-        }
-    validations:
-      required: true
-
-  - type: textarea
-    id: additional-context
-    attributes:
-      label: Additional Context
-      description: Any other information that would help reviewers
-      placeholder: Screenshots, demo videos, links to related projects, etc.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,104 +0,0 @@
-name: Feature Request
-description: Suggest a new feature or enhancement for Specify CLI or Spec Kit
-title: "[Feature]: "
-labels: ["enhancement", "needs-triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for suggesting a feature! Please provide details below to help us understand and evaluate your request.
-
-  - type: textarea
-    id: problem
-    attributes:
-      label: Problem Statement
-      description: Is your feature request related to a problem? Please describe.
-      placeholder: "I'm frustrated when..."
-    validations:
-      required: true
-
-  - type: textarea
-    id: solution
-    attributes:
-      label: Proposed Solution
-      description: Describe the solution you'd like
-      placeholder: What would you like to happen?
-    validations:
-      required: true
-
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: Alternatives Considered
-      description: Have you considered any alternative solutions or workarounds?
-      placeholder: What other approaches might work?
-
-  - type: dropdown
-    id: component
-    attributes:
-      label: Component
-      description: Which component does this feature relate to?
-      options:
-        - Specify CLI (initialization, commands)
-        - Spec templates (BDD, Testing Strategy, etc.)
-        - Agent integrations (command files, workflows)
-        - Scripts (Bash/PowerShell utilities)
-        - Documentation
-        - CI/CD workflows
-        - Other
-    validations:
-      required: true
-
-  - type: dropdown
-    id: ai-agent
-    attributes:
-      label: AI Agent (if applicable)
-      description: Does this feature relate to a specific AI agent?
-      options:
-        - All agents
-        - Claude Code
-        - Gemini CLI
-        - GitHub Copilot
-        - Cursor
-        - Qwen Code
-        - opencode
-        - Codex CLI
-        - Windsurf
-        - Kilo Code
-        - Auggie CLI
-        - Roo Code
-        - CodeBuddy
-        - Qoder CLI
-        - Kiro CLI
-        - Amp
-        - SHAI
-        - IBM Bob
-        - Antigravity
-        - Not applicable
-
-  - type: textarea
-    id: use-cases
-    attributes:
-      label: Use Cases
-      description: Describe specific use cases where this feature would be valuable
-      placeholder: |
-        1. When working on large projects...
-        2. During spec review...
-        3. When integrating with CI/CD...
-
-  - type: textarea
-    id: acceptance
-    attributes:
-      label: Acceptance Criteria
-      description: How would you know this feature is complete and working?
-      placeholder: |
-        - [ ] Feature does X
-        - [ ] Documentation is updated
-        - [ ] Works with all supported agents
-
-  - type: textarea
-    id: context
-    attributes:
-      label: Additional Context
-      description: Add any other context, screenshots, or examples
-      placeholder: Links to similar features, mockups, related discussions, etc.

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,22 +0,0 @@
-## Description
-
-<!-- What does this PR do? Why is it needed? -->
-
-## Testing
-
-<!-- How did you test your changes? -->
-
-- [ ] Tested locally with `uv run specify --help`
-- [ ] Ran existing tests with `uv sync && uv run pytest`
-- [ ] Tested with a sample project (if applicable)
-
-## AI Disclosure
-
-<!-- Per our Contributing guidelines, AI assistance must be disclosed. -->
-<!-- See: https://github.com/github/spec-kit/blob/main/CONTRIBUTING.md#ai-contributions-in-spec-kit -->
-
-- [ ] I **did not** use AI assistance for this contribution
-- [ ] I **did** use AI assistance (describe below)
-
-<!-- If you used AI, briefly describe how (e.g., "Code generated by Copilot", "Consulted ChatGPT for approach"): -->
-

.github/dependabot.yml

@@ -1,11 +0,0 @@
-version: 2
-updates:
-  - package-ecosystem: "pip"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    schedule:
-      interval: "weekly"

.github/workflows/RELEASE-PROCESS.md

@@ -1,191 +0,0 @@
-# Release Process
-
-This document describes the automated release process for Spec Kit.
-
-## Overview
-
-The release process is split into two workflows to ensure version consistency:
-
-1. **Release Trigger Workflow** (`release-trigger.yml`) - Manages versioning and triggers release
-2. **Release Workflow** (`release.yml`) - Builds and publishes artifacts
-
-This separation ensures that git tags always point to commits with the correct version in `pyproject.toml`.
-
-## Before Creating a Release
-
-**Important**: Write clear, descriptive commit messages!
-
-### How CHANGELOG.md Works
-
-The CHANGELOG is **automatically generated** from your git commit messages:
-
-1. **During Development**: Write clear, descriptive commit messages:
-   ```bash
-   git commit -m "feat: Add new authentication feature"
-   git commit -m "fix: Resolve timeout issue in API client (#123)"
-   git commit -m "docs: Update installation instructions"
-   ```
-
-2. **When Releasing**: The release trigger workflow automatically:
-   - Finds all commits since the last release tag
-   - Formats them as changelog entries
-   - Inserts them into CHANGELOG.md
-   - Commits the updated changelog before creating the new tag
-
-### Commit Message Best Practices
-
-Good commit messages make good changelogs:
-- **Be descriptive**: "Add user authentication" not "Update files"
-- **Reference issues/PRs**: Include `(#123)` for automated linking
-- **Use conventional commits** (optional): `feat:`, `fix:`, `docs:`, `chore:`
-- **Keep it concise**: One line is ideal, details go in commit body
-
-**Example commits that become good changelog entries:**
-```
-fix: prepend YAML frontmatter to Cursor .mdc files (#1699)
-feat: add generic agent support with customizable command directories (#1639)
-docs: document dual-catalog system for extensions (#1689)
-```
-
-## Creating a Release
-
-### Option 1: Auto-Increment (Recommended for patches)
-
-1. Go to **Actions** → **Release Trigger**
-2. Click **Run workflow**
-3. Leave the version field **empty**
-4. Click **Run workflow**
-
-The workflow will:
-- Auto-increment the patch version (e.g., `0.1.10` → `0.1.11`)
-- Update `pyproject.toml`
-- Update `CHANGELOG.md` by adding a new section for the release based on commits since the last tag
-- Commit changes to a `chore/release-vX.Y.Z` branch
-- Create and push the git tag from that branch
-- Open a PR to merge the version bump into `main`
-- Trigger the release workflow automatically via the tag push
-
-### Option 2: Manual Version (For major/minor bumps)
-
-1. Go to **Actions** → **Release Trigger**
-2. Click **Run workflow**
-3. Enter the desired version (e.g., `0.2.0` or `v0.2.0`)
-4. Click **Run workflow**
-
-The workflow will:
-- Use your specified version
-- Update `pyproject.toml`
-- Update `CHANGELOG.md` by adding a new section for the release based on commits since the last tag
-- Commit changes to a `chore/release-vX.Y.Z` branch
-- Create and push the git tag from that branch
-- Open a PR to merge the version bump into `main`
-- Trigger the release workflow automatically via the tag push
-
-## What Happens Next
-
-Once the release trigger workflow completes:
-
-1. A `chore/release-vX.Y.Z` branch is pushed with the version bump commit
-2. The git tag is pushed, pointing to that commit
-3. The **Release Workflow** is automatically triggered by the tag push
-4. Release artifacts are built for all supported agents
-5. A GitHub Release is created with all assets
-6. A PR is opened to merge the version bump branch into `main`
-
-> **Note**: Merge the auto-opened PR after the release is published to keep `main` in sync.
-
-## Workflow Details
-
-### Release Trigger Workflow
-
-**File**: `.github/workflows/release-trigger.yml`
-
-**Trigger**: Manual (`workflow_dispatch`)
-
-**Permissions Required**: `contents: write`
-
-**Steps**:
-1. Checkout repository
-2. Determine version (manual or auto-increment)
-3. Check if tag already exists (prevents duplicates)
-4. Create `chore/release-vX.Y.Z` branch
-5. Update `pyproject.toml`
-6. Update `CHANGELOG.md` from git commits
-7. Commit changes
-8. Push branch and tag
-9. Open PR to merge version bump into `main`
-
-### Release Workflow
-
-**File**: `.github/workflows/release.yml`
-
-**Trigger**: Tag push (`v*`)
-
-**Permissions Required**: `contents: write`
-
-**Steps**:
-1. Checkout repository at tag
-2. Extract version from tag name
-3. Check if release already exists
-4. Build release package variants (all agents × shell/powershell)
-5. Generate release notes from commits
-6. Create GitHub Release with all assets
-
-## Version Constraints
-
-- Tags must follow format: `v{MAJOR}.{MINOR}.{PATCH}`
-- Example valid versions: `v0.1.11`, `v0.2.0`, `v1.0.0`
-- Auto-increment only bumps patch version
-- Cannot create duplicate tags (workflow will fail)
-
-## Benefits of This Approach
-
-✅ **Version Consistency**: Git tags point to commits with matching `pyproject.toml` version
-
-✅ **Single Source of Truth**: Version set once, used everywhere
-
-✅ **Prevents Drift**: No more manual version synchronization needed
-
-✅ **Clean Separation**: Versioning logic separate from artifact building
-
-✅ **Flexibility**: Supports both auto-increment and manual versioning
-
-## Troubleshooting
-
-### No Commits Since Last Release
-
-If you run the release trigger workflow when there are no new commits since the last tag:
-- The workflow will still succeed
-- The CHANGELOG will show "- Initial release" if it's the first release
-- Or it will be empty if there are no commits
-- Consider adding meaningful commits before releasing
-
-**Best Practice**: Use descriptive commit messages - they become your changelog!
-
-### Tag Already Exists
-
-If you see "Error: Tag vX.Y.Z already exists!", you need to:
-- Choose a different version number, or
-- Delete the existing tag if it was created in error
-
-### Release Workflow Didn't Trigger
-
-Check that:
-- The release trigger workflow completed successfully
-- The tag was pushed (check repository tags)
-- The release workflow is enabled in Actions settings
-
-### Version Mismatch
-
-If `pyproject.toml` doesn't match the latest tag:
-- Run the release trigger workflow to sync versions
-- Or manually update `pyproject.toml` and push changes before running the release trigger
-
-## Legacy Behavior (Pre-v0.1.10)
-
-Before this change, the release workflow:
-- Created tags automatically on main branch pushes
-- Updated `pyproject.toml` AFTER creating the tag
-- Resulted in tags pointing to commits with outdated versions
-
-This has been fixed in v0.1.10+.

.github/workflows/codeql.yml

@@ -1,32 +0,0 @@
-name: "CodeQL"
-
-on:
-  push:
-    branches: [ main ]
-  pull_request:
-    branches: [ main ]
-
-jobs:
-  analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-    permissions:
-      security-events: write
-      contents: read
-    strategy:
-      fail-fast: false
-      matrix:
-        language: [ 'actions', 'python' ]
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Initialize CodeQL
-        uses: github/codeql-action/init@v4
-        with:
-          languages: ${{ matrix.language }}
-
-      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v4
-        with:
-          category: "/language:${{ matrix.language }}"

.github/workflows/docs.yml

@@ -29,7 +29,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v6
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0 # Fetch all history for git info
 
@@ -65,4 +65,3 @@ jobs:
       - name: Deploy to GitHub Pages
         id: deployment
         uses: actions/deploy-pages@v4
-

.github/workflows/lint.yml

@@ -1,22 +0,0 @@
-name: Lint
-permissions:
-  contents: read
-
-on:
-  push:
-    branches: ["main"]
-  pull_request:
-
-jobs:
-  markdownlint:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v6
-
-      - name: Run markdownlint-cli2
-        uses: DavidAnson/markdownlint-cli2-action@v19
-        with:
-          globs: |
-            '**/*.md'
-            !extensions/**/*.md

.github/workflows/release-trigger.yml

@@ -1,161 +0,0 @@
-name: Release Trigger
-
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: 'Version to release (e.g., 0.1.11). Leave empty to auto-increment patch version.'
-        required: false
-        type: string
-
-jobs:
-  bump-version:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.RELEASE_PAT }}
-
-      - name: Configure Git
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
-
-      - name: Determine version
-        id: version
-        env:
-          INPUT_VERSION: ${{ github.event.inputs.version }}
-        run: |
-          if [[ -n "$INPUT_VERSION" ]]; then
-            # Manual version specified - strip optional v prefix
-            VERSION="${INPUT_VERSION#v}"
-            # Validate strict semver format to prevent injection
-            if [[ ! "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
-              echo "Error: Invalid version format '$VERSION'. Must be X.Y.Z (e.g. 1.2.3 or v1.2.3)"
-              exit 1
-            fi
-            echo "version=$VERSION" >> $GITHUB_OUTPUT
-            echo "tag=v$VERSION" >> $GITHUB_OUTPUT
-            echo "Using manual version: $VERSION"
-          else
-            # Auto-increment patch version
-            LATEST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")
-            echo "Latest tag: $LATEST_TAG"
-
-            # Extract version number and increment
-            VERSION=$(echo $LATEST_TAG | sed 's/v//')
-            IFS='.' read -ra VERSION_PARTS <<< "$VERSION"
-            MAJOR=${VERSION_PARTS[0]:-0}
-            MINOR=${VERSION_PARTS[1]:-0}
-            PATCH=${VERSION_PARTS[2]:-0}
-
-            # Increment patch version
-            PATCH=$((PATCH + 1))
-            NEW_VERSION="$MAJOR.$MINOR.$PATCH"
-
-            echo "version=$NEW_VERSION" >> $GITHUB_OUTPUT
-            echo "tag=v$NEW_VERSION" >> $GITHUB_OUTPUT
-            echo "Auto-incremented version: $NEW_VERSION"
-          fi
-
-      - name: Check if tag already exists
-        run: |
-          if git rev-parse "${{ steps.version.outputs.tag }}" >/dev/null 2>&1; then
-            echo "Error: Tag ${{ steps.version.outputs.tag }} already exists!"
-            exit 1
-          fi
-
-      - name: Create release branch
-        run: |
-          BRANCH="chore/release-${{ steps.version.outputs.tag }}"
-          git checkout -b "$BRANCH"
-          echo "branch=$BRANCH" >> $GITHUB_ENV
-
-      - name: Update pyproject.toml
-        run: |
-          sed -i "s/version = \".*\"/version = \"${{ steps.version.outputs.version }}\"/" pyproject.toml
-          echo "Updated pyproject.toml to version ${{ steps.version.outputs.version }}"
-
-      - name: Update CHANGELOG.md
-        run: |
-          if [ -f "CHANGELOG.md" ]; then
-            DATE=$(date +%Y-%m-%d)
-
-            # Get the previous tag to compare commits
-            PREVIOUS_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
-
-            echo "Generating changelog from commits..."
-            if [[ -n "$PREVIOUS_TAG" ]]; then
-              echo "Changes since $PREVIOUS_TAG"
-              COMMITS=$(git log --oneline "$PREVIOUS_TAG"..HEAD --no-merges --pretty=format:"- %s" 2>/dev/null || echo "- Initial release")
-            else
-              echo "No previous tag found - this is the first release"
-              COMMITS="- Initial release"
-            fi
-
-            # Create new changelog entry
-            {
-              head -n 8 CHANGELOG.md
-              echo ""
-              echo "## [${{ steps.version.outputs.version }}] - $DATE"
-              echo ""
-              echo "### Changed"
-              echo ""
-              echo "$COMMITS"
-              echo ""
-              tail -n +9 CHANGELOG.md
-            } > CHANGELOG.md.tmp
-            mv CHANGELOG.md.tmp CHANGELOG.md
-
-            echo "✅ Updated CHANGELOG.md with commits since $PREVIOUS_TAG"
-          else
-            echo "No CHANGELOG.md found"
-          fi
-
-      - name: Commit version bump
-        run: |
-          if [ -f "CHANGELOG.md" ]; then
-            git add pyproject.toml CHANGELOG.md
-          else
-            git add pyproject.toml
-          fi
-
-          if git diff --cached --quiet; then
-            echo "No changes to commit"
-          else
-            git commit -m "chore: bump version to ${{ steps.version.outputs.version }}"
-            echo "Changes committed"
-          fi
-
-      - name: Create and push tag
-        run: |
-          git tag -a "${{ steps.version.outputs.tag }}" -m "Release ${{ steps.version.outputs.tag }}"
-          git push origin "${{ env.branch }}"
-          git push origin "${{ steps.version.outputs.tag }}"
-          echo "Branch ${{ env.branch }} and tag ${{ steps.version.outputs.tag }} pushed"
-
-      - name: Open pull request
-        env:
-          GITHUB_TOKEN: ${{ secrets.RELEASE_PAT }}
-        run: |
-          gh pr create \
-            --base main \
-            --head "${{ env.branch }}" \
-            --title "chore: bump version to ${{ steps.version.outputs.version }}" \
-            --body "Automated version bump to ${{ steps.version.outputs.version }}.
-
-          This PR was created by the Release Trigger workflow. The git tag \`${{ steps.version.outputs.tag }}\` has already been pushed and the release artifacts are being built.
-
-          Merge this PR to record the version bump and changelog update on \`main\`."
-
-      - name: Summary
-        run: |
-          echo "✅ Version bumped to ${{ steps.version.outputs.version }}"
-          echo "✅ Tag ${{ steps.version.outputs.tag }} created and pushed"
-          echo "✅ PR opened to merge version bump into main"
-          echo "🚀 Release workflow is building artifacts from the tag"

.github/workflows/release.yml

@@ -2,60 +2,130 @@ name: Create Release
 
 on:
   push:
-    tags:
-      - 'v*'
+    branches: [ main ]
+    paths:
+      - 'memory/**'
+      - 'scripts/**'
+      - 'templates/**'
+      - '.github/workflows/**'
+  workflow_dispatch:
 
 jobs:
   release:
     runs-on: ubuntu-latest
     permissions:
       contents: write
+      pull-requests: write
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0
           token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Extract version from tag
-        id: version
+      - name: Get latest tag
+        id: get_tag
         run: |
-          VERSION=${GITHUB_REF#refs/tags/}
-          echo "tag=$VERSION" >> $GITHUB_OUTPUT
-          echo "Building release for $VERSION"
-
+          # Get the latest tag, or use v0.0.0 if no tags exist
+          LATEST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")
+          echo "latest_tag=$LATEST_TAG" >> $GITHUB_OUTPUT
+          
+          # Extract version number and increment
+          VERSION=$(echo $LATEST_TAG | sed 's/v//')
+          IFS='.' read -ra VERSION_PARTS <<< "$VERSION"
+          MAJOR=${VERSION_PARTS[0]:-0}
+          MINOR=${VERSION_PARTS[1]:-0}
+          PATCH=${VERSION_PARTS[2]:-0}
+          
+          # Increment patch version
+          PATCH=$((PATCH + 1))
+          NEW_VERSION="v$MAJOR.$MINOR.$PATCH"
+          
+          echo "new_version=$NEW_VERSION" >> $GITHUB_OUTPUT
+          echo "New version will be: $NEW_VERSION"
       - name: Check if release already exists
         id: check_release
         run: |
-          chmod +x .github/workflows/scripts/check-release-exists.sh
-          .github/workflows/scripts/check-release-exists.sh ${{ steps.version.outputs.tag }}
+          if gh release view ${{ steps.get_tag.outputs.new_version }} >/dev/null 2>&1; then
+            echo "exists=true" >> $GITHUB_OUTPUT
+            echo "Release ${{ steps.get_tag.outputs.new_version }} already exists, skipping..."
+          else
+            echo "exists=false" >> $GITHUB_OUTPUT
+            echo "Release ${{ steps.get_tag.outputs.new_version }} does not exist, proceeding..."
+          fi
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
       - name: Create release package variants
         if: steps.check_release.outputs.exists == 'false'
         run: |
           chmod +x .github/workflows/scripts/create-release-packages.sh
-          .github/workflows/scripts/create-release-packages.sh ${{ steps.version.outputs.tag }}
-
+          .github/workflows/scripts/create-release-packages.sh ${{ steps.get_tag.outputs.new_version }}
       - name: Generate release notes
         if: steps.check_release.outputs.exists == 'false'
         id: release_notes
         run: |
-          chmod +x .github/workflows/scripts/generate-release-notes.sh
-          # Get the previous tag for changelog generation
-          PREVIOUS_TAG=$(git describe --tags --abbrev=0 ${{ steps.version.outputs.tag }}^ 2>/dev/null || echo "")
-          # Default to v0.0.0 if no previous tag is found (e.g., first release)
-          if [ -z "$PREVIOUS_TAG" ]; then
-            PREVIOUS_TAG="v0.0.0"
+          # Get commits since last tag
+          LAST_TAG=${{ steps.get_tag.outputs.latest_tag }}
+          if [ "$LAST_TAG" = "v0.0.0" ]; then
+            # Check how many commits we have and use that as the limit
+            COMMIT_COUNT=$(git rev-list --count HEAD)
+            if [ "$COMMIT_COUNT" -gt 10 ]; then
+              COMMITS=$(git log --oneline --pretty=format:"- %s" HEAD~10..HEAD)
+            else
+              COMMITS=$(git log --oneline --pretty=format:"- %s" HEAD~$COMMIT_COUNT..HEAD 2>/dev/null || git log --oneline --pretty=format:"- %s")
+            fi
+          else
+            COMMITS=$(git log --oneline --pretty=format:"- %s" $LAST_TAG..HEAD)
           fi
-          .github/workflows/scripts/generate-release-notes.sh ${{ steps.version.outputs.tag }} "$PREVIOUS_TAG"
+          
+          # Create release notes
+          cat > release_notes.md << EOF
+          Template release ${{ steps.get_tag.outputs.new_version }}
 
+          Updated specification-driven development templates for GitHub Copilot, Claude Code, Gemini CLI, and Cursor.
+
+          Now includes per-script variants for POSIX shell (sh) and PowerShell (ps).
+
+          Download the template for your preferred AI assistant + script type:
+          - spec-kit-template-copilot-sh-${{ steps.get_tag.outputs.new_version }}.zip
+          - spec-kit-template-copilot-ps-${{ steps.get_tag.outputs.new_version }}.zip
+          - spec-kit-template-claude-sh-${{ steps.get_tag.outputs.new_version }}.zip
+          - spec-kit-template-claude-ps-${{ steps.get_tag.outputs.new_version }}.zip
+          - spec-kit-template-gemini-sh-${{ steps.get_tag.outputs.new_version }}.zip
+          - spec-kit-template-gemini-ps-${{ steps.get_tag.outputs.new_version }}.zip
+          - spec-kit-template-cursor-sh-${{ steps.get_tag.outputs.new_version }}.zip
+          - spec-kit-template-cursor-ps-${{ steps.get_tag.outputs.new_version }}.zip
+          EOF
+          
+          echo "Generated release notes:"
+          cat release_notes.md
       - name: Create GitHub Release
         if: steps.check_release.outputs.exists == 'false'
         run: |
-          chmod +x .github/workflows/scripts/create-github-release.sh
-          .github/workflows/scripts/create-github-release.sh ${{ steps.version.outputs.tag }}
+          # Remove 'v' prefix from version for release title
+          VERSION_NO_V=${{ steps.get_tag.outputs.new_version }}
+          VERSION_NO_V=${VERSION_NO_V#v}
+          
+          gh release create ${{ steps.get_tag.outputs.new_version }} \
+            spec-kit-template-copilot-sh-${{ steps.get_tag.outputs.new_version }}.zip \
+            spec-kit-template-copilot-ps-${{ steps.get_tag.outputs.new_version }}.zip \
+            spec-kit-template-claude-sh-${{ steps.get_tag.outputs.new_version }}.zip \
+            spec-kit-template-claude-ps-${{ steps.get_tag.outputs.new_version }}.zip \
+            spec-kit-template-gemini-sh-${{ steps.get_tag.outputs.new_version }}.zip \
+            spec-kit-template-gemini-ps-${{ steps.get_tag.outputs.new_version }}.zip \
+            spec-kit-template-cursor-sh-${{ steps.get_tag.outputs.new_version }}.zip \
+            spec-kit-template-cursor-ps-${{ steps.get_tag.outputs.new_version }}.zip \
+            --title "Spec Kit Templates - $VERSION_NO_V" \
+            --notes-file release_notes.md
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
+      - name: Update version in pyproject.toml (for release artifacts only)
+        if: steps.check_release.outputs.exists == 'false'
+        run: |
+          # Update version in pyproject.toml (remove 'v' prefix for Python versioning)
+          VERSION=${{ steps.get_tag.outputs.new_version }}
+          PYTHON_VERSION=${VERSION#v}
+          
+          if [ -f "pyproject.toml" ]; then
+            sed -i "s/version = \".*\"/version = \"$PYTHON_VERSION\"/" pyproject.toml
+            echo "Updated pyproject.toml version to $PYTHON_VERSION (for release artifacts only)"
+          fi

.github/workflows/scripts/check-release-exists.sh

@@ -1,21 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# check-release-exists.sh
-# Check if a GitHub release already exists for the given version
-# Usage: check-release-exists.sh <version>
-
-if [[ $# -ne 1 ]]; then
-  echo "Usage: $0 <version>" >&2
-  exit 1
-fi
-
-VERSION="$1"
-
-if gh release view "$VERSION" >/dev/null 2>&1; then
-  echo "exists=true" >> $GITHUB_OUTPUT
-  echo "Release $VERSION already exists, skipping..."
-else
-  echo "exists=false" >> $GITHUB_OUTPUT
-  echo "Release $VERSION does not exist, proceeding..."
-fi

.github/workflows/scripts/create-github-release.sh

@@ -1,62 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# create-github-release.sh
-# Create a GitHub release with all template zip files
-# Usage: create-github-release.sh <version>
-
-if [[ $# -ne 1 ]]; then
-  echo "Usage: $0 <version>" >&2
-  exit 1
-fi
-
-VERSION="$1"
-
-# Remove 'v' prefix from version for release title
-VERSION_NO_V=${VERSION#v}
-
-gh release create "$VERSION" \
-  .genreleases/spec-kit-template-copilot-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-copilot-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-claude-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-claude-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-gemini-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-gemini-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-cursor-agent-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-cursor-agent-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-opencode-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-opencode-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-qwen-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-qwen-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-windsurf-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-windsurf-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-codex-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-codex-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-kilocode-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-kilocode-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-auggie-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-auggie-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-roo-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-roo-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-codebuddy-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-codebuddy-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-qodercli-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-qodercli-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-amp-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-amp-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-shai-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-shai-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-tabnine-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-tabnine-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-kiro-cli-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-kiro-cli-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-agy-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-agy-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-bob-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-bob-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-vibe-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-vibe-ps-"$VERSION".zip \
-  .genreleases/spec-kit-template-generic-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-generic-ps-"$VERSION".zip \
-  --title "Spec Kit Templates - $VERSION_NO_V" \
-  --notes-file release_notes.md

.github/workflows/scripts/create-release-packages.ps1

@@ -1,449 +0,0 @@
-#!/usr/bin/env pwsh
-#requires -Version 7.0
-
-<#
-.SYNOPSIS
-    Build Spec Kit template release archives for each supported AI assistant and script type.
-
-.DESCRIPTION
-    create-release-packages.ps1 (workflow-local)
-    Build Spec Kit template release archives for each supported AI assistant and script type.
-    
-.PARAMETER Version
-    Version string with leading 'v' (e.g., v0.2.0)
-
-.PARAMETER Agents
-    Comma or space separated subset of agents to build (default: all)
-    Valid agents: claude, gemini, copilot, cursor-agent, qwen, opencode, windsurf, codex, kilocode, auggie, roo, codebuddy, amp, kiro-cli, bob, qodercli, shai, tabnine, agy, vibe, generic
-
-.PARAMETER Scripts
-    Comma or space separated subset of script types to build (default: both)
-    Valid scripts: sh, ps
-
-.EXAMPLE
-    .\create-release-packages.ps1 -Version v0.2.0
-
-.EXAMPLE
-    .\create-release-packages.ps1 -Version v0.2.0 -Agents claude,copilot -Scripts sh
-
-.EXAMPLE
-    .\create-release-packages.ps1 -Version v0.2.0 -Agents claude -Scripts ps
-#>
-
-param(
-    [Parameter(Mandatory=$true, Position=0)]
-    [string]$Version,
-    
-    [Parameter(Mandatory=$false)]
-    [string]$Agents = "",
-    
-    [Parameter(Mandatory=$false)]
-    [string]$Scripts = ""
-)
-
-$ErrorActionPreference = "Stop"
-
-# Validate version format
-if ($Version -notmatch '^v\d+\.\d+\.\d+$') {
-    Write-Error "Version must look like v0.0.0"
-    exit 1
-}
-
-Write-Host "Building release packages for $Version"
-
-# Create and use .genreleases directory for all build artifacts
-$GenReleasesDir = ".genreleases"
-if (Test-Path $GenReleasesDir) {
-    Remove-Item -Path $GenReleasesDir -Recurse -Force -ErrorAction SilentlyContinue
-}
-New-Item -ItemType Directory -Path $GenReleasesDir -Force | Out-Null
-
-function Rewrite-Paths {
-    param([string]$Content)
-    
-    $Content = $Content -replace '(/?)\bmemory/', '.specify/memory/'
-    $Content = $Content -replace '(/?)\bscripts/', '.specify/scripts/'
-    $Content = $Content -replace '(/?)\btemplates/', '.specify/templates/'
-    return $Content
-}
-
-function Generate-Commands {
-    param(
-        [string]$Agent,
-        [string]$Extension,
-        [string]$ArgFormat,
-        [string]$OutputDir,
-        [string]$ScriptVariant
-    )
-    
-    New-Item -ItemType Directory -Path $OutputDir -Force | Out-Null
-    
-    $templates = Get-ChildItem -Path "templates/commands/*.md" -File -ErrorAction SilentlyContinue
-    
-    foreach ($template in $templates) {
-        $name = [System.IO.Path]::GetFileNameWithoutExtension($template.Name)
-        
-        # Read file content and normalize line endings
-        $fileContent = (Get-Content -Path $template.FullName -Raw) -replace "`r`n", "`n"
-        
-        # Extract description from YAML frontmatter
-        $description = ""
-        if ($fileContent -match '(?m)^description:\s*(.+)$') {
-            $description = $matches[1]
-        }
-        
-        # Extract script command from YAML frontmatter
-        $scriptCommand = ""
-        if ($fileContent -match "(?m)^\s*${ScriptVariant}:\s*(.+)$") {
-            $scriptCommand = $matches[1]
-        }
-        
-        if ([string]::IsNullOrEmpty($scriptCommand)) {
-            Write-Warning "No script command found for $ScriptVariant in $($template.Name)"
-            $scriptCommand = "(Missing script command for $ScriptVariant)"
-        }
-        
-        # Extract agent_script command from YAML frontmatter if present
-        $agentScriptCommand = ""
-        if ($fileContent -match "(?ms)agent_scripts:.*?^\s*${ScriptVariant}:\s*(.+?)$") {
-            $agentScriptCommand = $matches[1].Trim()
-        }
-        
-        # Replace {SCRIPT} placeholder with the script command
-        $body = $fileContent -replace '\{SCRIPT\}', $scriptCommand
-        
-        # Replace {AGENT_SCRIPT} placeholder with the agent script command if found
-        if (-not [string]::IsNullOrEmpty($agentScriptCommand)) {
-            $body = $body -replace '\{AGENT_SCRIPT\}', $agentScriptCommand
-        }
-        
-        # Remove the scripts: and agent_scripts: sections from frontmatter
-        $lines = $body -split "`n"
-        $outputLines = @()
-        $inFrontmatter = $false
-        $skipScripts = $false
-        $dashCount = 0
-        
-        foreach ($line in $lines) {
-            if ($line -match '^---$') {
-                $outputLines += $line
-                $dashCount++
-                if ($dashCount -eq 1) {
-                    $inFrontmatter = $true
-                } else {
-                    $inFrontmatter = $false
-                }
-                continue
-            }
-            
-            if ($inFrontmatter) {
-                if ($line -match '^(scripts|agent_scripts):$') {
-                    $skipScripts = $true
-                    continue
-                }
-                if ($line -match '^[a-zA-Z].*:' -and $skipScripts) {
-                    $skipScripts = $false
-                }
-                if ($skipScripts -and $line -match '^\s+') {
-                    continue
-                }
-            }
-            
-            $outputLines += $line
-        }
-        
-        $body = $outputLines -join "`n"
-        
-        # Apply other substitutions
-        $body = $body -replace '\{ARGS\}', $ArgFormat
-        $body = $body -replace '__AGENT__', $Agent
-        $body = Rewrite-Paths -Content $body
-        
-        # Generate output file based on extension
-        $outputFile = Join-Path $OutputDir "speckit.$name.$Extension"
-        
-        switch ($Extension) {
-            'toml' {
-                $body = $body -replace '\\', '\\'
-                $output = "description = `"$description`"`n`nprompt = `"`"`"`n$body`n`"`"`""
-                Set-Content -Path $outputFile -Value $output -NoNewline
-            }
-            'md' {
-                Set-Content -Path $outputFile -Value $body -NoNewline
-            }
-            'agent.md' {
-                Set-Content -Path $outputFile -Value $body -NoNewline
-            }
-        }
-    }
-}
-
-function Generate-CopilotPrompts {
-    param(
-        [string]$AgentsDir,
-        [string]$PromptsDir
-    )
-    
-    New-Item -ItemType Directory -Path $PromptsDir -Force | Out-Null
-    
-    $agentFiles = Get-ChildItem -Path "$AgentsDir/speckit.*.agent.md" -File -ErrorAction SilentlyContinue
-    
-    foreach ($agentFile in $agentFiles) {
-        $basename = $agentFile.Name -replace '\.agent\.md$', ''
-        $promptFile = Join-Path $PromptsDir "$basename.prompt.md"
-        
-        $content = @"
----
-agent: $basename
----
-"@
-        Set-Content -Path $promptFile -Value $content
-    }
-}
-
-function Build-Variant {
-    param(
-        [string]$Agent,
-        [string]$Script
-    )
-    
-    $baseDir = Join-Path $GenReleasesDir "sdd-${Agent}-package-${Script}"
-    Write-Host "Building $Agent ($Script) package..."
-    New-Item -ItemType Directory -Path $baseDir -Force | Out-Null
-    
-    # Copy base structure but filter scripts by variant
-    $specDir = Join-Path $baseDir ".specify"
-    New-Item -ItemType Directory -Path $specDir -Force | Out-Null
-    
-    # Copy memory directory
-    if (Test-Path "memory") {
-        Copy-Item -Path "memory" -Destination $specDir -Recurse -Force
-        Write-Host "Copied memory -> .specify"
-    }
-    
-    # Only copy the relevant script variant directory
-    if (Test-Path "scripts") {
-        $scriptsDestDir = Join-Path $specDir "scripts"
-        New-Item -ItemType Directory -Path $scriptsDestDir -Force | Out-Null
-        
-        switch ($Script) {
-            'sh' {
-                if (Test-Path "scripts/bash") {
-                    Copy-Item -Path "scripts/bash" -Destination $scriptsDestDir -Recurse -Force
-                    Write-Host "Copied scripts/bash -> .specify/scripts"
-                }
-            }
-            'ps' {
-                if (Test-Path "scripts/powershell") {
-                    Copy-Item -Path "scripts/powershell" -Destination $scriptsDestDir -Recurse -Force
-                    Write-Host "Copied scripts/powershell -> .specify/scripts"
-                }
-            }
-        }
-        
-        # Copy any script files that aren't in variant-specific directories
-        Get-ChildItem -Path "scripts" -File -ErrorAction SilentlyContinue | ForEach-Object {
-            Copy-Item -Path $_.FullName -Destination $scriptsDestDir -Force
-        }
-    }
-    
-    # Copy templates (excluding commands directory and vscode-settings.json)
-    if (Test-Path "templates") {
-        $templatesDestDir = Join-Path $specDir "templates"
-        New-Item -ItemType Directory -Path $templatesDestDir -Force | Out-Null
-        
-        Get-ChildItem -Path "templates" -Recurse -File | Where-Object {
-            $_.FullName -notmatch 'templates[/\\]commands[/\\]' -and $_.Name -ne 'vscode-settings.json'
-        } | ForEach-Object {
-            $relativePath = $_.FullName.Substring((Resolve-Path "templates").Path.Length + 1)
-            $destFile = Join-Path $templatesDestDir $relativePath
-            $destFileDir = Split-Path $destFile -Parent
-            New-Item -ItemType Directory -Path $destFileDir -Force | Out-Null
-            Copy-Item -Path $_.FullName -Destination $destFile -Force
-        }
-        Write-Host "Copied templates -> .specify/templates"
-    }
-    
-    # Generate agent-specific command files
-    switch ($Agent) {
-        'claude' {
-            $cmdDir = Join-Path $baseDir ".claude/commands"
-            Generate-Commands -Agent 'claude' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'gemini' {
-            $cmdDir = Join-Path $baseDir ".gemini/commands"
-            Generate-Commands -Agent 'gemini' -Extension 'toml' -ArgFormat '{{args}}' -OutputDir $cmdDir -ScriptVariant $Script
-            if (Test-Path "agent_templates/gemini/GEMINI.md") {
-                Copy-Item -Path "agent_templates/gemini/GEMINI.md" -Destination (Join-Path $baseDir "GEMINI.md")
-            }
-        }
-        'copilot' {
-            $agentsDir = Join-Path $baseDir ".github/agents"
-            Generate-Commands -Agent 'copilot' -Extension 'agent.md' -ArgFormat '$ARGUMENTS' -OutputDir $agentsDir -ScriptVariant $Script
-            
-            # Generate companion prompt files
-            $promptsDir = Join-Path $baseDir ".github/prompts"
-            Generate-CopilotPrompts -AgentsDir $agentsDir -PromptsDir $promptsDir
-            
-            # Create VS Code workspace settings
-            $vscodeDir = Join-Path $baseDir ".vscode"
-            New-Item -ItemType Directory -Path $vscodeDir -Force | Out-Null
-            if (Test-Path "templates/vscode-settings.json") {
-                Copy-Item -Path "templates/vscode-settings.json" -Destination (Join-Path $vscodeDir "settings.json")
-            }
-        }
-        'cursor-agent' {
-            $cmdDir = Join-Path $baseDir ".cursor/commands"
-            Generate-Commands -Agent 'cursor-agent' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'qwen' {
-            $cmdDir = Join-Path $baseDir ".qwen/commands"
-            Generate-Commands -Agent 'qwen' -Extension 'toml' -ArgFormat '{{args}}' -OutputDir $cmdDir -ScriptVariant $Script
-            if (Test-Path "agent_templates/qwen/QWEN.md") {
-                Copy-Item -Path "agent_templates/qwen/QWEN.md" -Destination (Join-Path $baseDir "QWEN.md")
-            }
-        }
-        'opencode' {
-            $cmdDir = Join-Path $baseDir ".opencode/command"
-            Generate-Commands -Agent 'opencode' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'windsurf' {
-            $cmdDir = Join-Path $baseDir ".windsurf/workflows"
-            Generate-Commands -Agent 'windsurf' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'codex' {
-            $cmdDir = Join-Path $baseDir ".codex/prompts"
-            Generate-Commands -Agent 'codex' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'kilocode' {
-            $cmdDir = Join-Path $baseDir ".kilocode/workflows"
-            Generate-Commands -Agent 'kilocode' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'auggie' {
-            $cmdDir = Join-Path $baseDir ".augment/commands"
-            Generate-Commands -Agent 'auggie' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'roo' {
-            $cmdDir = Join-Path $baseDir ".roo/commands"
-            Generate-Commands -Agent 'roo' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'codebuddy' {
-            $cmdDir = Join-Path $baseDir ".codebuddy/commands"
-            Generate-Commands -Agent 'codebuddy' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'amp' {
-            $cmdDir = Join-Path $baseDir ".agents/commands"
-            Generate-Commands -Agent 'amp' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'kiro-cli' {
-            $cmdDir = Join-Path $baseDir ".kiro/prompts"
-            Generate-Commands -Agent 'kiro-cli' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'bob' {
-            $cmdDir = Join-Path $baseDir ".bob/commands"
-            Generate-Commands -Agent 'bob' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'qodercli' {
-            $cmdDir = Join-Path $baseDir ".qoder/commands"
-            Generate-Commands -Agent 'qodercli' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'shai' {
-            $cmdDir = Join-Path $baseDir ".shai/commands"
-            Generate-Commands -Agent 'shai' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'tabnine' {
-            $cmdDir = Join-Path $baseDir ".tabnine/agent/commands"
-            Generate-Commands -Agent 'tabnine' -Extension 'toml' -ArgFormat '{{args}}' -OutputDir $cmdDir -ScriptVariant $Script
-            $tabnineTemplate = Join-Path 'agent_templates' 'tabnine/TABNINE.md'
-            if (Test-Path $tabnineTemplate) { Copy-Item $tabnineTemplate (Join-Path $baseDir 'TABNINE.md') }
-        }
-        'agy' {
-            $cmdDir = Join-Path $baseDir ".agent/workflows"
-            Generate-Commands -Agent 'agy' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'generic' {
-            $cmdDir = Join-Path $baseDir ".speckit/commands"
-            Generate-Commands -Agent 'generic' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        'vibe' {
-            $cmdDir = Join-Path $baseDir ".vibe/prompts"
-            Generate-Commands -Agent 'vibe' -Extension 'md' -ArgFormat '$ARGUMENTS' -OutputDir $cmdDir -ScriptVariant $Script
-        }
-        default {
-            throw "Unsupported agent '$Agent'."
-        }
-    }
-    
-    # Create zip archive
-    $zipFile = Join-Path $GenReleasesDir "spec-kit-template-${Agent}-${Script}-${Version}.zip"
-    Compress-Archive -Path "$baseDir/*" -DestinationPath $zipFile -Force
-    Write-Host "Created $zipFile"
-}
-
-# Define all agents and scripts
-$AllAgents = @('claude', 'gemini', 'copilot', 'cursor-agent', 'qwen', 'opencode', 'windsurf', 'codex', 'kilocode', 'auggie', 'roo', 'codebuddy', 'amp', 'kiro-cli', 'bob', 'qodercli', 'shai', 'tabnine', 'agy', 'vibe', 'generic')
-$AllScripts = @('sh', 'ps')
-
-function Normalize-List {
-    param([string]$Input)
-    
-    if ([string]::IsNullOrEmpty($Input)) {
-        return @()
-    }
-    
-    # Split by comma or space and remove duplicates while preserving order
-    $items = $Input -split '[,\s]+' | Where-Object { $_ } | Select-Object -Unique
-    return $items
-}
-
-function Validate-Subset {
-    param(
-        [string]$Type,
-        [string[]]$Allowed,
-        [string[]]$Items
-    )
-    
-    $ok = $true
-    foreach ($item in $Items) {
-        if ($item -notin $Allowed) {
-            Write-Error "Unknown $Type '$item' (allowed: $($Allowed -join ', '))"
-            $ok = $false
-        }
-    }
-    return $ok
-}
-
-# Determine agent list
-if (-not [string]::IsNullOrEmpty($Agents)) {
-    $AgentList = Normalize-List -Input $Agents
-    if (-not (Validate-Subset -Type 'agent' -Allowed $AllAgents -Items $AgentList)) {
-        exit 1
-    }
-} else {
-    $AgentList = $AllAgents
-}
-
-# Determine script list
-if (-not [string]::IsNullOrEmpty($Scripts)) {
-    $ScriptList = Normalize-List -Input $Scripts
-    if (-not (Validate-Subset -Type 'script' -Allowed $AllScripts -Items $ScriptList)) {
-        exit 1
-    }
-} else {
-    $ScriptList = $AllScripts
-}
-
-Write-Host "Agents: $($AgentList -join ', ')"
-Write-Host "Scripts: $($ScriptList -join ', ')"
-
-# Build all variants
-foreach ($agent in $AgentList) {
-    foreach ($script in $ScriptList) {
-        Build-Variant -Agent $agent -Script $script
-    }
-}
-
-Write-Host "`nArchives in ${GenReleasesDir}:"
-Get-ChildItem -Path $GenReleasesDir -Filter "spec-kit-template-*-${Version}.zip" | ForEach-Object {
-    Write-Host "  $($_.Name)"
-}

.github/workflows/scripts/create-release-packages.sh

@@ -6,7 +6,7 @@ set -euo pipefail
 # Usage: .github/workflows/scripts/create-release-packages.sh <version>
 #   Version argument should include leading 'v'.
 #   Optionally set AGENTS and/or SCRIPTS env vars to limit what gets built.
-#     AGENTS  : space or comma separated subset of: claude gemini copilot cursor-agent qwen opencode windsurf codex kilocode auggie roo codebuddy amp shai tabnine kiro-cli agy bob vibe qodercli generic (default: all)
+#     AGENTS  : space or comma separated subset of: claude gemini copilot (default: all)
 #     SCRIPTS : space or comma separated subset of: sh ps (default: both)
 #   Examples:
 #     AGENTS=claude SCRIPTS=sh $0 v0.2.0
@@ -25,17 +25,13 @@ fi
 
 echo "Building release packages for $NEW_VERSION"
 
-# Create and use .genreleases directory for all build artifacts
-GENRELEASES_DIR=".genreleases"
-mkdir -p "$GENRELEASES_DIR"
-rm -rf "$GENRELEASES_DIR"/* || true
+rm -rf sdd-package-base* sdd-*-package-* spec-kit-template-*-${NEW_VERSION}.zip || true
 
 rewrite_paths() {
   sed -E \
     -e 's@(/?)memory/@.specify/memory/@g' \
     -e 's@(/?)scripts/@.specify/scripts/@g' \
-    -e 's@(/?)templates/@.specify/templates/@g' \
-    -e 's@\.specify\.specify/@.specify/@g'
+    -e 's@(/?)templates/@.specify/templates/@g'
 }
 
 generate_commands() {
@@ -43,7 +39,7 @@ generate_commands() {
   mkdir -p "$output_dir"
   for template in templates/commands/*.md; do
     [[ -f "$template" ]] || continue
-    local name description script_command agent_script_command body
+    local name description script_command body
     name=$(basename "$template" .md)
     
     # Normalize line endings
@@ -58,30 +54,13 @@ generate_commands() {
       script_command="(Missing script command for $script_variant)"
     fi
     
-    # Extract agent_script command from YAML frontmatter if present
-    agent_script_command=$(printf '%s\n' "$file_content" | awk '
-      /^agent_scripts:$/ { in_agent_scripts=1; next }
-      in_agent_scripts && /^[[:space:]]*'"$script_variant"':[[:space:]]*/ {
-        sub(/^[[:space:]]*'"$script_variant"':[[:space:]]*/, "")
-        print
-        exit
-      }
-      in_agent_scripts && /^[a-zA-Z]/ { in_agent_scripts=0 }
-    ')
-    
     # Replace {SCRIPT} placeholder with the script command
     body=$(printf '%s\n' "$file_content" | sed "s|{SCRIPT}|${script_command}|g")
     
-    # Replace {AGENT_SCRIPT} placeholder with the agent script command if found
-    if [[ -n $agent_script_command ]]; then
-      body=$(printf '%s\n' "$body" | sed "s|{AGENT_SCRIPT}|${agent_script_command}|g")
-    fi
-    
-    # Remove the scripts: and agent_scripts: sections from frontmatter while preserving YAML structure
+    # Remove the scripts: section from frontmatter while preserving YAML structure
     body=$(printf '%s\n' "$body" | awk '
       /^---$/ { print; if (++dash_count == 1) in_frontmatter=1; else in_frontmatter=0; next }
       in_frontmatter && /^scripts:$/ { skip_scripts=1; next }
-      in_frontmatter && /^agent_scripts:$/ { skip_scripts=1; next }
       in_frontmatter && /^[a-zA-Z].*:/ && skip_scripts { skip_scripts=0 }
       in_frontmatter && skip_scripts && /^[[:space:]]/ { next }
       { print }
@@ -92,39 +71,18 @@ generate_commands() {
     
     case $ext in
       toml)
-        body=$(printf '%s\n' "$body" | sed 's/\\/\\\\/g')
-        { echo "description = \"$description\""; echo; echo "prompt = \"\"\""; echo "$body"; echo "\"\"\""; } > "$output_dir/speckit.$name.$ext" ;;
+        { echo "description = \"$description\""; echo; echo "prompt = \"\"\""; echo "$body"; echo "\"\"\""; } > "$output_dir/$name.$ext" ;;
       md)
-        echo "$body" > "$output_dir/speckit.$name.$ext" ;;
-      agent.md)
-        echo "$body" > "$output_dir/speckit.$name.$ext" ;;
+        echo "$body" > "$output_dir/$name.$ext" ;;
+      prompt.md)
+        echo "$body" > "$output_dir/$name.$ext" ;;
     esac
   done
 }
 
-generate_copilot_prompts() {
-  local agents_dir=$1 prompts_dir=$2
-  mkdir -p "$prompts_dir"
-  
-  # Generate a .prompt.md file for each .agent.md file
-  for agent_file in "$agents_dir"/speckit.*.agent.md; do
-    [[ -f "$agent_file" ]] || continue
-    
-    local basename=$(basename "$agent_file" .agent.md)
-    local prompt_file="$prompts_dir/${basename}.prompt.md"
-    
-    # Create prompt file with agent frontmatter
-    cat > "$prompt_file" <<EOF
----
-agent: ${basename}
----
-EOF
-  done
-}
-
 build_variant() {
   local agent=$1 script=$2
-  local base_dir="$GENRELEASES_DIR/sdd-${agent}-package-${script}"
+  local base_dir="sdd-${agent}-package-${script}"
   echo "Building $agent ($script) package..."
   mkdir -p "$base_dir"
   
@@ -151,13 +109,19 @@ build_variant() {
     esac
   fi
   
-  [[ -d templates ]] && { mkdir -p "$SPEC_DIR/templates"; find templates -type f -not -path "templates/commands/*" -not -name "vscode-settings.json" -exec cp --parents {} "$SPEC_DIR"/ \; ; echo "Copied templates -> .specify/templates"; }
-  
-  # NOTE: We substitute {ARGS} internally. Outward tokens differ intentionally:
-  #   * Markdown/prompt (claude, copilot, cursor-agent, opencode): $ARGUMENTS
-  #   * TOML (gemini, qwen, tabnine): {{args}}
-  # This keeps formats readable without extra abstraction.
-
+  [[ -d templates ]] && { mkdir -p "$SPEC_DIR/templates"; find templates -type f -not -path "templates/commands/*" -exec cp --parents {} "$SPEC_DIR"/ \; ; echo "Copied templates -> .specify/templates"; }
+  # Inject variant into plan-template.md within .specify/templates if present
+  local plan_tpl="$base_dir/.specify/templates/plan-template.md"
+  if [[ -f "$plan_tpl" ]]; then
+    plan_norm=$(tr -d '\r' < "$plan_tpl")
+    variant_line=$(printf '%s\n' "$plan_norm" | grep -E "<!--[[:space:]]*VARIANT:$script" | head -1 | sed -E "s/.*VARIANT:$script[[:space:]]+//; s/-->.*//; s/^[[:space:]]+//; s/[[:space:]]+$//")
+    if [[ -n $variant_line ]]; then
+      tmp_file=$(mktemp)
+      sed "s|VARIANT-INJECT|${variant_line}|" "$plan_tpl" | tr -d '\r' | sed "s|__AGENT__|${agent}|g" | sed '/<!--[[:space:]]*VARIANT:sh/d' | sed '/<!--[[:space:]]*VARIANT:ps/d' > "$tmp_file" && mv "$tmp_file" "$plan_tpl"
+    else
+      echo "Warning: no plan-template variant for $script (pattern not matched)" >&2
+    fi
+  fi
   case $agent in
     claude)
       mkdir -p "$base_dir/.claude/commands"
@@ -167,110 +131,51 @@ build_variant() {
       generate_commands gemini toml "{{args}}" "$base_dir/.gemini/commands" "$script"
       [[ -f agent_templates/gemini/GEMINI.md ]] && cp agent_templates/gemini/GEMINI.md "$base_dir/GEMINI.md" ;;
     copilot)
-      mkdir -p "$base_dir/.github/agents"
-      generate_commands copilot agent.md "\$ARGUMENTS" "$base_dir/.github/agents" "$script"
-      # Generate companion prompt files
-      generate_copilot_prompts "$base_dir/.github/agents" "$base_dir/.github/prompts"
-      # Create VS Code workspace settings
-      mkdir -p "$base_dir/.vscode"
-      [[ -f templates/vscode-settings.json ]] && cp templates/vscode-settings.json "$base_dir/.vscode/settings.json"
-      ;;
-    cursor-agent)
+      mkdir -p "$base_dir/.github/prompts"
+      generate_commands copilot prompt.md "\$ARGUMENTS" "$base_dir/.github/prompts" "$script" ;;
+    cursor)
       mkdir -p "$base_dir/.cursor/commands"
-      generate_commands cursor-agent md "\$ARGUMENTS" "$base_dir/.cursor/commands" "$script" ;;
-    qwen)
-      mkdir -p "$base_dir/.qwen/commands"
-      generate_commands qwen toml "{{args}}" "$base_dir/.qwen/commands" "$script"
-      [[ -f agent_templates/qwen/QWEN.md ]] && cp agent_templates/qwen/QWEN.md "$base_dir/QWEN.md" ;;
-    opencode)
-      mkdir -p "$base_dir/.opencode/command"
-      generate_commands opencode md "\$ARGUMENTS" "$base_dir/.opencode/command" "$script" ;;
-    windsurf)
-      mkdir -p "$base_dir/.windsurf/workflows"
-      generate_commands windsurf md "\$ARGUMENTS" "$base_dir/.windsurf/workflows" "$script" ;;
-    codex)
-      mkdir -p "$base_dir/.codex/prompts"
-      generate_commands codex md "\$ARGUMENTS" "$base_dir/.codex/prompts" "$script" ;;
-    kilocode)
-      mkdir -p "$base_dir/.kilocode/workflows"
-      generate_commands kilocode md "\$ARGUMENTS" "$base_dir/.kilocode/workflows" "$script" ;;
-    auggie)
-      mkdir -p "$base_dir/.augment/commands"
-      generate_commands auggie md "\$ARGUMENTS" "$base_dir/.augment/commands" "$script" ;;
-    roo)
-      mkdir -p "$base_dir/.roo/commands"
-      generate_commands roo md "\$ARGUMENTS" "$base_dir/.roo/commands" "$script" ;;
-    codebuddy)
-      mkdir -p "$base_dir/.codebuddy/commands"
-      generate_commands codebuddy md "\$ARGUMENTS" "$base_dir/.codebuddy/commands" "$script" ;;
-    qodercli)
-      mkdir -p "$base_dir/.qoder/commands"
-      generate_commands qodercli md "\$ARGUMENTS" "$base_dir/.qoder/commands" "$script" ;;
-    amp)
-      mkdir -p "$base_dir/.agents/commands"
-      generate_commands amp md "\$ARGUMENTS" "$base_dir/.agents/commands" "$script" ;;
-    shai)
-      mkdir -p "$base_dir/.shai/commands"
-      generate_commands shai md "\$ARGUMENTS" "$base_dir/.shai/commands" "$script" ;;
-    tabnine)
-      mkdir -p "$base_dir/.tabnine/agent/commands"
-      generate_commands tabnine toml "{{args}}" "$base_dir/.tabnine/agent/commands" "$script"
-      [[ -f agent_templates/tabnine/TABNINE.md ]] && cp agent_templates/tabnine/TABNINE.md "$base_dir/TABNINE.md" ;;
-    kiro-cli)
-      mkdir -p "$base_dir/.kiro/prompts"
-      generate_commands kiro-cli md "\$ARGUMENTS" "$base_dir/.kiro/prompts" "$script" ;;
-    agy)
-      mkdir -p "$base_dir/.agent/workflows"
-      generate_commands agy md "\$ARGUMENTS" "$base_dir/.agent/workflows" "$script" ;;
-    bob)
-      mkdir -p "$base_dir/.bob/commands"
-      generate_commands bob md "\$ARGUMENTS" "$base_dir/.bob/commands" "$script" ;;
-    vibe)
-      mkdir -p "$base_dir/.vibe/prompts"
-      generate_commands vibe md "\$ARGUMENTS" "$base_dir/.vibe/prompts" "$script" ;;
-    generic)
-      mkdir -p "$base_dir/.speckit/commands"
-      generate_commands generic md "\$ARGUMENTS" "$base_dir/.speckit/commands" "$script" ;;
+      generate_commands cursor md "\$ARGUMENTS" "$base_dir/.cursor/commands" "$script" ;;
   esac
   ( cd "$base_dir" && zip -r "../spec-kit-template-${agent}-${script}-${NEW_VERSION}.zip" . )
-  echo "Created $GENRELEASES_DIR/spec-kit-template-${agent}-${script}-${NEW_VERSION}.zip"
+  echo "Created spec-kit-template-${agent}-${script}-${NEW_VERSION}.zip"
 }
 
 # Determine agent list
-ALL_AGENTS=(claude gemini copilot cursor-agent qwen opencode windsurf codex kilocode auggie roo codebuddy amp shai tabnine kiro-cli agy bob vibe qodercli generic)
+ALL_AGENTS=(claude gemini copilot cursor)
 ALL_SCRIPTS=(sh ps)
 
 norm_list() {
-  # convert comma+space separated -> line separated unique while preserving order of first occurrence
-  tr ',\n' '  ' | awk '{for(i=1;i<=NF;i++){if(!seen[$i]++){printf((out?"\n":"") $i);out=1}}}END{printf("\n")}'
+  # convert comma+space separated -> space separated unique while preserving order of first occurrence
+  tr ',\n' '  ' | awk '{for(i=1;i<=NF;i++){if(!seen[$i]++){printf((out?" ":"") $i)}}}END{printf("\n")}'
 }
 
 validate_subset() {
-  local type=$1; shift; local -n allowed=$1; shift; local items=("$@")
-  local invalid=0
+  local type=$1; shift; local -n allowed=$1; shift; local items=($@)
+  local ok=1
   for it in "${items[@]}"; do
     local found=0
-    for a in "${allowed[@]}"; do [[ $it == "$a" ]] && { found=1; break; }; done
+    for a in "${allowed[@]}"; do [[ $it == $a ]] && { found=1; break; }; done
     if [[ $found -eq 0 ]]; then
       echo "Error: unknown $type '$it' (allowed: ${allowed[*]})" >&2
-      invalid=1
+      ok=0
     fi
   done
-  return $invalid
+  return $ok
 }
 
 if [[ -n ${AGENTS:-} ]]; then
-  mapfile -t AGENT_LIST < <(printf '%s' "$AGENTS" | norm_list)
+  AGENT_LIST=($(printf '%s' "$AGENTS" | norm_list))
   validate_subset agent ALL_AGENTS "${AGENT_LIST[@]}" || exit 1
 else
-  AGENT_LIST=("${ALL_AGENTS[@]}")
+  AGENT_LIST=(${ALL_AGENTS[@]})
 fi
 
 if [[ -n ${SCRIPTS:-} ]]; then
-  mapfile -t SCRIPT_LIST < <(printf '%s' "$SCRIPTS" | norm_list)
+  SCRIPT_LIST=($(printf '%s' "$SCRIPTS" | norm_list))
   validate_subset script ALL_SCRIPTS "${SCRIPT_LIST[@]}" || exit 1
 else
-  SCRIPT_LIST=("${ALL_SCRIPTS[@]}")
+  SCRIPT_LIST=(${ALL_SCRIPTS[@]})
 fi
 
 echo "Agents: ${AGENT_LIST[*]}"
@@ -282,5 +187,5 @@ for agent in "${AGENT_LIST[@]}"; do
   done
 done
 
-echo "Archives in $GENRELEASES_DIR:"
-ls -1 "$GENRELEASES_DIR"/spec-kit-template-*-"${NEW_VERSION}".zip
+echo "Archives:"
+ls -1 spec-kit-template-*-${NEW_VERSION}.zip

.github/workflows/scripts/generate-release-notes.sh

@@ -1,40 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# generate-release-notes.sh
-# Generate release notes from git history
-# Usage: generate-release-notes.sh <new_version> <last_tag>
-
-if [[ $# -ne 2 ]]; then
-  echo "Usage: $0 <new_version> <last_tag>" >&2
-  exit 1
-fi
-
-NEW_VERSION="$1"
-LAST_TAG="$2"
-
-# Get commits since last tag
-if [ "$LAST_TAG" = "v0.0.0" ]; then
-  # Check how many commits we have and use that as the limit
-  COMMIT_COUNT=$(git rev-list --count HEAD)
-  if [ "$COMMIT_COUNT" -gt 10 ]; then
-    COMMITS=$(git log --oneline --pretty=format:"- %s" HEAD~10..HEAD)
-  else
-    COMMITS=$(git log --oneline --pretty=format:"- %s" HEAD~$COMMIT_COUNT..HEAD 2>/dev/null || git log --oneline --pretty=format:"- %s")
-  fi
-else
-  COMMITS=$(git log --oneline --pretty=format:"- %s" $LAST_TAG..HEAD)
-fi
-
-# Create release notes
-cat > release_notes.md << EOF
-This is the latest set of releases that you can use with your agent of choice. We recommend using the Specify CLI to scaffold your projects, however you can download these independently and manage them yourself.
-
-## Changelog
-
-$COMMITS
-
-EOF
-
-echo "Generated release notes:"
-cat release_notes.md

.github/workflows/scripts/get-next-version.sh

@@ -1,24 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# get-next-version.sh
-# Calculate the next version based on the latest git tag and output GitHub Actions variables
-# Usage: get-next-version.sh
-
-# Get the latest tag, or use v0.0.0 if no tags exist
-LATEST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")
-echo "latest_tag=$LATEST_TAG" >> $GITHUB_OUTPUT
-
-# Extract version number and increment
-VERSION=$(echo $LATEST_TAG | sed 's/v//')
-IFS='.' read -ra VERSION_PARTS <<< "$VERSION"
-MAJOR=${VERSION_PARTS[0]:-0}
-MINOR=${VERSION_PARTS[1]:-0}
-PATCH=${VERSION_PARTS[2]:-0}
-
-# Increment patch version
-PATCH=$((PATCH + 1))
-NEW_VERSION="v$MAJOR.$MINOR.$PATCH"
-
-echo "new_version=$NEW_VERSION" >> $GITHUB_OUTPUT
-echo "New version will be: $NEW_VERSION"

.github/workflows/scripts/simulate-release.sh

@@ -1,161 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# simulate-release.sh
-# Simulate the release process locally without pushing to GitHub
-# Usage: simulate-release.sh [version]
-#   If version is omitted, auto-increments patch version
-
-# Colors for output
-GREEN='\033[0;32m'
-BLUE='\033[0;34m'
-YELLOW='\033[1;33m'
-RED='\033[0;31m'
-NC='\033[0m' # No Color
-
-echo -e "${BLUE}🧪 Simulating Release Process Locally${NC}"
-echo "======================================"
-echo ""
-
-# Step 1: Determine version
-if [[ -n "${1:-}" ]]; then
-  VERSION="${1#v}"
-  TAG="v$VERSION"
-  echo -e "${GREEN}📝 Using manual version: $VERSION${NC}"
-else
-  LATEST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")
-  echo -e "${BLUE}Latest tag: $LATEST_TAG${NC}"
-  
-  VERSION=$(echo $LATEST_TAG | sed 's/v//')
-  IFS='.' read -ra VERSION_PARTS <<< "$VERSION"
-  MAJOR=${VERSION_PARTS[0]:-0}
-  MINOR=${VERSION_PARTS[1]:-0}
-  PATCH=${VERSION_PARTS[2]:-0}
-  
-  PATCH=$((PATCH + 1))
-  VERSION="$MAJOR.$MINOR.$PATCH"
-  TAG="v$VERSION"
-  echo -e "${GREEN}📝 Auto-incremented to: $VERSION${NC}"
-fi
-
-echo ""
-
-# Step 2: Check if tag exists
-if git rev-parse "$TAG" >/dev/null 2>&1; then
-  echo -e "${RED}❌ Error: Tag $TAG already exists!${NC}"
-  echo "   Please use a different version or delete the tag first."
-  exit 1
-fi
-echo -e "${GREEN}✓ Tag $TAG is available${NC}"
-
-# Step 3: Backup current state
-echo ""
-echo -e "${YELLOW}💾 Creating backup of current state...${NC}"
-BACKUP_DIR=$(mktemp -d)
-cp pyproject.toml "$BACKUP_DIR/pyproject.toml.bak"
-cp CHANGELOG.md "$BACKUP_DIR/CHANGELOG.md.bak"
-echo -e "${GREEN}✓ Backup created at: $BACKUP_DIR${NC}"
-
-# Step 4: Update pyproject.toml
-echo ""
-echo -e "${YELLOW}📝 Updating pyproject.toml...${NC}"
-sed -i.tmp "s/version = \".*\"/version = \"$VERSION\"/" pyproject.toml
-rm -f pyproject.toml.tmp
-echo -e "${GREEN}✓ Updated pyproject.toml to version $VERSION${NC}"
-
-# Step 5: Update CHANGELOG.md
-echo ""
-echo -e "${YELLOW}📝 Updating CHANGELOG.md...${NC}"
-DATE=$(date +%Y-%m-%d)
-
-# Get the previous tag to compare commits
-PREVIOUS_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
-
-if [[ -n "$PREVIOUS_TAG" ]]; then
-  echo "   Generating changelog from commits since $PREVIOUS_TAG"
-  # Get commits since last tag, format as bullet points
-  COMMITS=$(git log --oneline "$PREVIOUS_TAG"..HEAD --no-merges --pretty=format:"- %s" 2>/dev/null || echo "- Initial release")
-else
-  echo "   No previous tag found - this is the first release"
-  COMMITS="- Initial release"
-fi
-
-# Create temp file with new entry
-{
-  head -n 8 CHANGELOG.md
-  echo ""
-  echo "## [$VERSION] - $DATE"
-  echo ""
-  echo "### Changed"
-  echo ""
-  echo "$COMMITS"
-  echo ""
-  tail -n +9 CHANGELOG.md
-} > CHANGELOG.md.tmp
-mv CHANGELOG.md.tmp CHANGELOG.md
-echo -e "${GREEN}✓ Updated CHANGELOG.md with commits since $PREVIOUS_TAG${NC}"
-
-# Step 6: Show what would be committed
-echo ""
-echo -e "${YELLOW}📋 Changes that would be committed:${NC}"
-git diff pyproject.toml CHANGELOG.md
-
-# Step 7: Create temporary tag (no push)
-echo ""
-echo -e "${YELLOW}🏷️  Creating temporary local tag...${NC}"
-git tag -a "$TAG" -m "Simulated release $TAG" 2>/dev/null || true
-echo -e "${GREEN}✓ Tag $TAG created locally${NC}"
-
-# Step 8: Simulate release artifact creation
-echo ""
-echo -e "${YELLOW}📦 Simulating release package creation...${NC}"
-echo "   (High-level simulation only; packaging script is not executed)"
-echo ""
-
-# Check if script exists and is executable
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-if [[ -x "$SCRIPT_DIR/create-release-packages.sh" ]]; then
-  echo -e "${BLUE}In a real release, the following command would be run to create packages:${NC}"
-  echo "  $SCRIPT_DIR/create-release-packages.sh \"$TAG\""
-  echo ""
-  echo "This simulation does not enumerate individual package files to avoid"
-  echo "drifting from the actual behavior of create-release-packages.sh."
-else
-  echo -e "${RED}⚠️  create-release-packages.sh not found or not executable${NC}"
-fi
-
-# Step 9: Simulate release notes generation
-echo ""
-echo -e "${YELLOW}📄 Simulating release notes generation...${NC}"
-echo ""
-PREVIOUS_TAG=$(git describe --tags --abbrev=0 $TAG^ 2>/dev/null || echo "")
-if [[ -n "$PREVIOUS_TAG" ]]; then
-  echo -e "${BLUE}Changes since $PREVIOUS_TAG:${NC}"
-  git log --oneline "$PREVIOUS_TAG".."$TAG" | head -n 10
-  echo ""
-else
-  echo -e "${BLUE}No previous tag found - this would be the first release${NC}"
-fi
-
-# Step 10: Summary
-echo ""
-echo -e "${GREEN}🎉 Simulation Complete!${NC}"
-echo "======================================"
-echo ""
-echo -e "${BLUE}Summary:${NC}"
-echo "  Version: $VERSION"
-echo "  Tag: $TAG"
-echo "  Backup: $BACKUP_DIR"
-echo ""
-echo -e "${YELLOW}⚠️  SIMULATION ONLY - NO CHANGES PUSHED${NC}"
-echo ""
-echo -e "${BLUE}Next steps:${NC}"
-echo "  1. Review the changes above"
-echo "  2. To keep changes: git add pyproject.toml CHANGELOG.md && git commit"
-echo "  3. To discard changes: git checkout pyproject.toml CHANGELOG.md && git tag -d $TAG"
-echo "  4. To restore from backup: cp $BACKUP_DIR/* ."
-echo ""
-echo -e "${BLUE}To run the actual release:${NC}"
-echo "  Go to: https://github.com/github/spec-kit/actions/workflows/release-trigger.yml"
-echo "  Click 'Run workflow' and enter version: $VERSION"
-echo ""

.github/workflows/scripts/update-version.sh

@@ -1,23 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# update-version.sh
-# Update version in pyproject.toml (for release artifacts only)
-# Usage: update-version.sh <version>
-
-if [[ $# -ne 1 ]]; then
-  echo "Usage: $0 <version>" >&2
-  exit 1
-fi
-
-VERSION="$1"
-
-# Remove 'v' prefix for Python versioning
-PYTHON_VERSION=${VERSION#v}
-
-if [ -f "pyproject.toml" ]; then
-  sed -i "s/version = \".*\"/version = \"$PYTHON_VERSION\"/" pyproject.toml
-  echo "Updated pyproject.toml version to $PYTHON_VERSION (for release artifacts only)"
-else
-  echo "Warning: pyproject.toml not found, skipping version update"
-fi

.github/workflows/stale.yml

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

.github/workflows/test.yml

@@ -1,50 +0,0 @@
-name: Test & Lint Python
-
-permissions:
-  contents: read
-
-on:
-  push:
-    branches: ["main"]
-  pull_request:
-
-jobs:
-  ruff:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Install uv
-        uses: astral-sh/setup-uv@v7
-
-      - name: Set up Python
-        uses: actions/setup-python@v6
-        with:
-          python-version: "3.13"
-
-      - name: Run ruff check
-        run: uvx ruff check src/
-
-  pytest:
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        python-version: ["3.11", "3.12", "3.13"]
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Install uv
-        uses: astral-sh/setup-uv@v7
-
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v6
-        with:
-          python-version: ${{ matrix.python-version }}
-
-      - name: Install dependencies
-        run: uv sync --extra test
-
-      - name: Run tests
-        run: uv run pytest

.gitignore

@@ -32,21 +32,9 @@ env/
 *.swp
 *.swo
 .DS_Store
-*.tmp
 
 # Project specific
 *.log
 .env
 .env.local
 *.lock
-
-# Spec Kit-specific files
-.genreleases/
-*.zip
-sdd-*/
-docs/dev
-
-# Extension system
-.specify/extensions/.cache/
-.specify/extensions/.backup/
-.specify/extensions/*/local-config.yml

.markdownlint-cli2.jsonc

@@ -1,29 +0,0 @@
-{
-  // https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md
-  "config": {
-    "default": true,
-    "MD003": {
-      "style": "atx"
-    },
-    "MD007": {
-      "indent": 2
-    },
-    "MD013": false,
-    "MD024": {
-      "siblings_only": true
-    },
-    "MD033": false,
-    "MD041": false,
-    "MD049": {
-      "style": "asterisk"
-    },
-    "MD050": {
-      "style": "asterisk"
-    },
-    "MD036": false,
-    "MD060": false
-  },
-  "ignores": [
-    ".genreleases/"
-  ]
-}

AGENTS.md

@@ -1,421 +0,0 @@
-# AGENTS.md
-
-## About Spec Kit and Specify
-
-**GitHub Spec Kit** is a comprehensive toolkit for implementing Spec-Driven Development (SDD) - a methodology that emphasizes creating clear specifications before implementation. The toolkit includes templates, scripts, and workflows that guide development teams through a structured approach to building software.
-
-**Specify CLI** is the command-line interface that bootstraps projects with the Spec Kit framework. It sets up the necessary directory structures, templates, and AI agent integrations to support the Spec-Driven Development workflow.
-
-The toolkit supports multiple AI coding assistants, allowing teams to use their preferred tools while maintaining consistent project structure and development practices.
-
----
-
-## General practices
-
-- Any changes to `__init__.py` for the Specify CLI require a version rev in `pyproject.toml` and addition of entries to `CHANGELOG.md`.
-
-## Adding New Agent Support
-
-This section explains how to add support for new AI agents/assistants to the Specify CLI. Use this guide as a reference when integrating new AI tools into the Spec-Driven Development workflow.
-
-### Overview
-
-Specify supports multiple AI agents by generating agent-specific command files and directory structures when initializing projects. Each agent has its own conventions for:
-
-- **Command file formats** (Markdown, TOML, etc.)
-- **Directory structures** (`.claude/commands/`, `.windsurf/workflows/`, etc.)
-- **Command invocation patterns** (slash commands, CLI tools, etc.)
-- **Argument passing conventions** (`$ARGUMENTS`, `{{args}}`, etc.)
-
-### Current Supported Agents
-
-| Agent                      | Directory              | Format   | CLI Tool        | Description                 |
-| -------------------------- | ---------------------- | -------- | --------------- | --------------------------- |
-| **Claude Code**            | `.claude/commands/`    | Markdown | `claude`        | Anthropic's Claude Code CLI |
-| **Gemini CLI**             | `.gemini/commands/`    | TOML     | `gemini`        | Google's Gemini CLI         |
-| **GitHub Copilot**         | `.github/agents/`      | Markdown | N/A (IDE-based) | GitHub Copilot in VS Code   |
-| **Cursor**                 | `.cursor/commands/`    | Markdown | `cursor-agent`  | Cursor CLI                  |
-| **Qwen Code**              | `.qwen/commands/`      | TOML     | `qwen`          | Alibaba's Qwen Code CLI     |
-| **opencode**               | `.opencode/command/`   | Markdown | `opencode`      | opencode CLI                |
-| **Codex CLI**              | `.codex/commands/`     | Markdown | `codex`         | Codex CLI                   |
-| **Windsurf**               | `.windsurf/workflows/` | Markdown | N/A (IDE-based) | Windsurf IDE workflows      |
-| **Kilo Code**              | `.kilocode/rules/`     | Markdown | N/A (IDE-based) | Kilo Code IDE               |
-| **Auggie CLI**             | `.augment/rules/`      | Markdown | `auggie`        | Auggie CLI                  |
-| **Roo Code**               | `.roo/rules/`          | Markdown | N/A (IDE-based) | Roo Code IDE                |
-| **CodeBuddy CLI**          | `.codebuddy/commands/` | Markdown | `codebuddy`     | CodeBuddy CLI               |
-| **Qoder CLI**              | `.qoder/commands/`     | Markdown | `qodercli`      | Qoder CLI                   |
-| **Kiro CLI**               | `.kiro/prompts/`       | Markdown | `kiro-cli`      | Kiro CLI                    |
-| **Amp**                    | `.agents/commands/`    | Markdown | `amp`           | Amp CLI                     |
-| **SHAI**                   | `.shai/commands/`      | Markdown | `shai`          | SHAI CLI                    |
-| **Tabnine CLI**            | `.tabnine/agent/commands/` | TOML | `tabnine`       | Tabnine CLI                 |
-| **IBM Bob**                | `.bob/commands/`       | Markdown | N/A (IDE-based) | IBM Bob IDE                 |
-| **Generic**                | User-specified via `--ai-commands-dir` | Markdown | N/A | Bring your own agent        |
-
-### Step-by-Step Integration Guide
-
-Follow these steps to add a new agent (using a hypothetical new agent as an example):
-
-#### 1. Add to AGENT_CONFIG
-
-**IMPORTANT**: Use the actual CLI tool name as the key, not a shortened version.
-
-Add the new agent to the `AGENT_CONFIG` dictionary in `src/specify_cli/__init__.py`. This is the **single source of truth** for all agent metadata:
-
-```python
-AGENT_CONFIG = {
-    # ... existing agents ...
-    "new-agent-cli": {  # Use the ACTUAL CLI tool name (what users type in terminal)
-        "name": "New Agent Display Name",
-        "folder": ".newagent/",  # Directory for agent files
-        "commands_subdir": "commands",  # Subdirectory name for command files (default: "commands")
-        "install_url": "https://example.com/install",  # URL for installation docs (or None if IDE-based)
-        "requires_cli": True,  # True if CLI tool required, False for IDE-based agents
-    },
-}
-```
-
-**Key Design Principle**: The dictionary key should match the actual executable name that users install. For example:
-
-- ✅ Use `"cursor-agent"` because the CLI tool is literally called `cursor-agent`
-- ❌ Don't use `"cursor"` as a shortcut if the tool is `cursor-agent`
-
-This eliminates the need for special-case mappings throughout the codebase.
-
-**Field Explanations**:
-
-- `name`: Human-readable display name shown to users
-- `folder`: Directory where agent-specific files are stored (relative to project root)
-- `commands_subdir`: Subdirectory name within the agent folder where command/prompt files are stored (default: `"commands"`)
-  - Most agents use `"commands"` (e.g., `.claude/commands/`)
-  - Some agents use alternative names: `"agents"` (copilot), `"workflows"` (windsurf, kilocode, agy), `"prompts"` (codex, kiro-cli), `"command"` (opencode - singular)
-  - This field enables `--ai-skills` to locate command templates correctly for skill generation
-- `install_url`: Installation documentation URL (set to `None` for IDE-based agents)
-- `requires_cli`: Whether the agent requires a CLI tool check during initialization
-
-#### 2. Update CLI Help Text
-
-Update the `--ai` parameter help text in the `init()` command to include the new agent:
-
-```python
-ai_assistant: str = typer.Option(None, "--ai", help="AI assistant to use: claude, gemini, copilot, cursor-agent, qwen, opencode, codex, windsurf, kilocode, auggie, codebuddy, new-agent-cli, or kiro-cli"),
-```
-
-Also update any function docstrings, examples, and error messages that list available agents.
-
-#### 3. Update README Documentation
-
-Update the **Supported AI Agents** section in `README.md` to include the new agent:
-
-- Add the new agent to the table with appropriate support level (Full/Partial)
-- Include the agent's official website link
-- Add any relevant notes about the agent's implementation
-- Ensure the table formatting remains aligned and consistent
-
-#### 4. Update Release Package Script
-
-Modify `.github/workflows/scripts/create-release-packages.sh`:
-
-##### Add to ALL_AGENTS array
-
-```bash
-ALL_AGENTS=(claude gemini copilot cursor-agent qwen opencode windsurf kiro-cli)
-```
-
-##### Add case statement for directory structure
-
-```bash
-case $agent in
-  # ... existing cases ...
-  windsurf)
-    mkdir -p "$base_dir/.windsurf/workflows"
-    generate_commands windsurf md "\$ARGUMENTS" "$base_dir/.windsurf/workflows" "$script" ;;
-esac
-```
-
-#### 4. Update GitHub Release Script
-
-Modify `.github/workflows/scripts/create-github-release.sh` to include the new agent's packages:
-
-```bash
-gh release create "$VERSION" \
-  # ... existing packages ...
-  .genreleases/spec-kit-template-windsurf-sh-"$VERSION".zip \
-  .genreleases/spec-kit-template-windsurf-ps-"$VERSION".zip \
-  # Add new agent packages here
-```
-
-#### 5. Update Agent Context Scripts
-
-##### Bash script (`scripts/bash/update-agent-context.sh`)
-
-Add file variable:
-
-```bash
-WINDSURF_FILE="$REPO_ROOT/.windsurf/rules/specify-rules.md"
-```
-
-Add to case statement:
-
-```bash
-case "$AGENT_TYPE" in
-  # ... existing cases ...
-  windsurf) update_agent_file "$WINDSURF_FILE" "Windsurf" ;;
-  "")
-    # ... existing checks ...
-    [ -f "$WINDSURF_FILE" ] && update_agent_file "$WINDSURF_FILE" "Windsurf";
-    # Update default creation condition
-    ;;
-esac
-```
-
-##### PowerShell script (`scripts/powershell/update-agent-context.ps1`)
-
-Add file variable:
-
-```powershell
-$windsurfFile = Join-Path $repoRoot '.windsurf/rules/specify-rules.md'
-```
-
-Add to switch statement:
-
-```powershell
-switch ($AgentType) {
-    # ... existing cases ...
-    'windsurf' { Update-AgentFile $windsurfFile 'Windsurf' }
-    '' {
-        foreach ($pair in @(
-            # ... existing pairs ...
-            @{file=$windsurfFile; name='Windsurf'}
-        )) {
-            if (Test-Path $pair.file) { Update-AgentFile $pair.file $pair.name }
-        }
-        # Update default creation condition
-    }
-}
-```
-
-#### 6. Update CLI Tool Checks (Optional)
-
-For agents that require CLI tools, add checks in the `check()` command and agent validation:
-
-```python
-# In check() command
-tracker.add("windsurf", "Windsurf IDE (optional)")
-windsurf_ok = check_tool_for_tracker("windsurf", "https://windsurf.com/", tracker)
-
-# In init validation (only if CLI tool required)
-elif selected_ai == "windsurf":
-    if not check_tool("windsurf", "Install from: https://windsurf.com/"):
-        console.print("[red]Error:[/red] Windsurf CLI is required for Windsurf projects")
-        agent_tool_missing = True
-```
-
-**Note**: CLI tool checks are now handled automatically based on the `requires_cli` field in AGENT_CONFIG. No additional code changes needed in the `check()` or `init()` commands - they automatically loop through AGENT_CONFIG and check tools as needed.
-
-## Important Design Decisions
-
-### Using Actual CLI Tool Names as Keys
-
-**CRITICAL**: When adding a new agent to AGENT_CONFIG, always use the **actual executable name** as the dictionary key, not a shortened or convenient version.
-
-**Why this matters:**
-
-- The `check_tool()` function uses `shutil.which(tool)` to find executables in the system PATH
-- If the key doesn't match the actual CLI tool name, you'll need special-case mappings throughout the codebase
-- This creates unnecessary complexity and maintenance burden
-
-**Example - The Cursor Lesson:**
-
-❌ **Wrong approach** (requires special-case mapping):
-
-```python
-AGENT_CONFIG = {
-    "cursor": {  # Shorthand that doesn't match the actual tool
-        "name": "Cursor",
-        # ...
-    }
-}
-
-# Then you need special cases everywhere:
-cli_tool = agent_key
-if agent_key == "cursor":
-    cli_tool = "cursor-agent"  # Map to the real tool name
-```
-
-✅ **Correct approach** (no mapping needed):
-
-```python
-AGENT_CONFIG = {
-    "cursor-agent": {  # Matches the actual executable name
-        "name": "Cursor",
-        # ...
-    }
-}
-
-# No special cases needed - just use agent_key directly!
-```
-
-**Benefits of this approach:**
-
-- Eliminates special-case logic scattered throughout the codebase
-- Makes the code more maintainable and easier to understand
-- Reduces the chance of bugs when adding new agents
-- Tool checking "just works" without additional mappings
-
-#### 7. Update Devcontainer files (Optional)
-
-For agents that have VS Code extensions or require CLI installation, update the devcontainer configuration files:
-
-##### VS Code Extension-based Agents
-
-For agents available as VS Code extensions, add them to `.devcontainer/devcontainer.json`:
-
-```json
-{
-  "customizations": {
-    "vscode": {
-      "extensions": [
-        // ... existing extensions ...
-        // [New Agent Name]
-        "[New Agent Extension ID]"
-      ]
-    }
-  }
-}
-```
-
-##### CLI-based Agents
-
-For agents that require CLI tools, add installation commands to `.devcontainer/post-create.sh`:
-
-```bash
-#!/bin/bash
-
-# Existing installations...
-
-echo -e "\n🤖 Installing [New Agent Name] CLI..."
-# run_command "npm install -g [agent-cli-package]@latest" # Example for node-based CLI
-# or other installation instructions (must be non-interactive and compatible with Linux Debian "Trixie" or later)...
-echo "✅ Done"
-
-```
-
-**Quick Tips:**
-
-- **Extension-based agents**: Add to the `extensions` array in `devcontainer.json`
-- **CLI-based agents**: Add installation scripts to `post-create.sh`
-- **Hybrid agents**: May require both extension and CLI installation
-- **Test thoroughly**: Ensure installations work in the devcontainer environment
-
-## Agent Categories
-
-### CLI-Based Agents
-
-Require a command-line tool to be installed:
-
-- **Claude Code**: `claude` CLI
-- **Gemini CLI**: `gemini` CLI
-- **Cursor**: `cursor-agent` CLI
-- **Qwen Code**: `qwen` CLI
-- **opencode**: `opencode` CLI
-- **Kiro CLI**: `kiro-cli` CLI
-- **CodeBuddy CLI**: `codebuddy` CLI
-- **Qoder CLI**: `qodercli` CLI
-- **Amp**: `amp` CLI
-- **SHAI**: `shai` CLI
-- **Tabnine CLI**: `tabnine` CLI
-
-### IDE-Based Agents
-
-Work within integrated development environments:
-
-- **GitHub Copilot**: Built into VS Code/compatible editors
-- **Windsurf**: Built into Windsurf IDE
-- **IBM Bob**: Built into IBM Bob IDE
-
-## Command File Formats
-
-### Markdown Format
-
-Used by: Claude, Cursor, opencode, Windsurf, Kiro CLI, Amp, SHAI, IBM Bob
-
-**Standard format:**
-
-```markdown
----
-description: "Command description"
----
-
-Command content with {SCRIPT} and $ARGUMENTS placeholders.
-```
-
-**GitHub Copilot Chat Mode format:**
-
-```markdown
----
-description: "Command description"
-mode: speckit.command-name
----
-
-Command content with {SCRIPT} and $ARGUMENTS placeholders.
-```
-
-### TOML Format
-
-Used by: Gemini, Qwen, Tabnine
-
-```toml
-description = "Command description"
-
-prompt = """
-Command content with {SCRIPT} and {{args}} placeholders.
-"""
-```
-
-## Directory Conventions
-
-- **CLI agents**: Usually `.<agent-name>/commands/`
-- **IDE agents**: Follow IDE-specific patterns:
-  - Copilot: `.github/agents/`
-  - Cursor: `.cursor/commands/`
-  - Windsurf: `.windsurf/workflows/`
-
-## Argument Patterns
-
-Different agents use different argument placeholders:
-
-- **Markdown/prompt-based**: `$ARGUMENTS`
-- **TOML-based**: `{{args}}`
-- **Script placeholders**: `{SCRIPT}` (replaced with actual script path)
-- **Agent placeholders**: `__AGENT__` (replaced with agent name)
-
-## Testing New Agent Integration
-
-1. **Build test**: Run package creation script locally
-2. **CLI test**: Test `specify init --ai <agent>` command
-3. **File generation**: Verify correct directory structure and files
-4. **Command validation**: Ensure generated commands work with the agent
-5. **Context update**: Test agent context update scripts
-
-## Common Pitfalls
-
-1. **Using shorthand keys instead of actual CLI tool names**: Always use the actual executable name as the AGENT_CONFIG key (e.g., `"cursor-agent"` not `"cursor"`). This prevents the need for special-case mappings throughout the codebase.
-2. **Forgetting update scripts**: Both bash and PowerShell scripts must be updated when adding new agents.
-3. **Incorrect `requires_cli` value**: Set to `True` only for agents that actually have CLI tools to check; set to `False` for IDE-based agents.
-4. **Wrong argument format**: Use correct placeholder format for each agent type (`$ARGUMENTS` for Markdown, `{{args}}` for TOML).
-5. **Directory naming**: Follow agent-specific conventions exactly (check existing agents for patterns).
-6. **Help text inconsistency**: Update all user-facing text consistently (help strings, docstrings, README, error messages).
-
-## Future Considerations
-
-When adding new agents:
-
-- Consider the agent's native command/workflow patterns
-- Ensure compatibility with the Spec-Driven Development process
-- Document any special requirements or limitations
-- Update this guide with lessons learned
-- Verify the actual CLI tool name before adding to AGENT_CONFIG
-
----
-
-*This documentation should be updated whenever new agents are added to maintain accuracy and completeness.*

CHANGELOG.md

@@ -1,235 +1,22 @@
 # Changelog
 
-<!-- markdownlint-disable MD024 -->
-
-Recent changes to the Specify CLI and templates are documented here.
+All notable changes to the Specify CLI will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [0.2.1] - 2026-03-10
+## [Unreleased]
+
+## [0.0.4] - 2025-09-14
 
 ### Added
 
-- feat(presets): Pluggable preset system with preset catalog and template resolver
-- Preset manifest (`preset.yml`) with validation for artifact, command, and script types
-- `PresetManifest`, `PresetRegistry`, `PresetManager`, `PresetCatalog`, `PresetResolver` classes in `src/specify_cli/presets.py`
-- CLI commands: `specify preset search`, `specify preset add`, `specify preset list`, `specify preset remove`, `specify preset resolve`, `specify preset info`
-- CLI commands: `specify preset catalog list`, `specify preset catalog add`, `specify preset catalog remove` for multi-catalog management
-- `PresetCatalogEntry` dataclass and multi-catalog support mirroring the extension catalog system
-- `--preset` option for `specify init` to install presets during initialization
-- Priority-based preset resolution: presets with lower priority number win (`--priority` flag)
-- `resolve_template()` / `Resolve-Template` helpers in bash and PowerShell common scripts
-- Template resolution priority stack: overrides → presets → extensions → core
-- Preset catalog files (`presets/catalog.json`, `presets/catalog.community.json`)
-- Preset scaffold directory (`presets/scaffold/`)
-- Scripts updated to use template resolution instead of hardcoded paths
-- feat(presets): Preset command overrides now propagate to agent skills when `--ai-skills` was used during init
-- feat: `specify init` persists CLI options to `.specify/init-options.json` for downstream operations
-- feat(extensions): support `.extensionignore` to exclude files/folders during `specify extension add` (#1781)
-
-## [0.2.0] - 2026-03-09
-
-### Changed
-
-- fix: sync agent list comments with actual supported agents (#1785)
-- feat(extensions): support multiple active catalogs simultaneously (#1720)
-- Pavel/add tabnine cli support (#1503)
-- Add Understanding extension to community catalog (#1778)
-- Add ralph extension to community catalog (#1780)
-- Update README with project initialization instructions (#1772)
-- feat: add review extension to community catalog (#1775)
-- Add fleet extension to community catalog (#1771)
-- Integration of Mistral vibe support into speckit (#1725)
-- fix: Remove duplicate options in specify.md (#1765)
-- fix: use global branch numbering instead of per-short-name detection (#1757)
-- Add Community Walkthroughs section to README (#1766)
-- feat(extensions): add Jira Integration to community catalog (#1764)
-- Add Azure DevOps Integration extension to community catalog (#1734)
-- Fix docs: update Antigravity link and add initialization example (#1748)
-- fix: wire after_tasks and after_implement hook events into command templates (#1702)
-- make c ignores consistent with c++ (#1747)
-- chore: bump version to 0.1.13 (#1746)
-- feat: add kiro-cli and AGENT_CONFIG consistency coverage (#1690)
-- feat: add verify extension to community catalog (#1726)
-- Add Retrospective Extension to community catalog README table (#1741)
-- fix(scripts): add empty description validation and branch checkout error handling (#1559)
-- fix: correct Copilot extension command registration (#1724)
-- fix(implement): remove Makefile from C ignore patterns (#1558)
-- Add sync extension to community catalog (#1728)
-- fix(checklist): clarify file handling behavior for append vs create (#1556)
-- fix(clarify): correct conflicting question limit from 10 to 5 (#1557)
-- chore: bump version to 0.1.12 (#1737)
-- fix: use RELEASE_PAT so tag push triggers release workflow (#1736)
-- fix: release-trigger uses release branch + PR instead of direct push to main (#1733)
-- fix: Split release process to sync pyproject.toml version with git tags (#1732)
-
-## [0.1.14] - 2026-03-09
-
-### Added
-
-- feat: add Tabnine CLI agent support
-- **Multi-Catalog Support (#1707)**: Extension catalog system now supports multiple active catalogs simultaneously via a catalog stack
-  - New `specify extension catalog list` command lists all active catalogs with name, URL, priority, and `install_allowed` status
-  - New `specify extension catalog add` and `specify extension catalog remove` commands for project-scoped catalog management
-  - Default built-in stack includes `catalog.json` (default, installable) and `catalog.community.json` (community, discovery only) — community extensions are now surfaced in search results out of the box
-  - `specify extension search` aggregates results across all active catalogs, annotating each result with source catalog
-  - `specify extension add` enforces `install_allowed` policy — extensions from discovery-only catalogs cannot be installed directly
-  - Project-level `.specify/extension-catalogs.yml` and user-level `~/.specify/extension-catalogs.yml` config files supported, with project-level taking precedence
-  - `SPECKIT_CATALOG_URL` environment variable still works for backward compatibility (replaces full stack with single catalog)
-  - All catalog URLs require HTTPS (HTTP allowed for localhost development)
-  - New `CatalogEntry` dataclass in `extensions.py` for catalog stack representation
-  - Per-URL hash-based caching for non-default catalogs; legacy cache preserved for default catalog
-  - Higher-priority catalogs win on merge conflicts (same extension id in multiple catalogs)
-  - 13 new tests covering catalog stack resolution, merge conflicts, URL validation, and `install_allowed` enforcement
-  - Updated RFC, Extension User Guide, and Extension API Reference documentation
-
-## [0.1.13] - 2026-03-03
-
-### Changed
-
-- feat: add kiro-cli and AGENT_CONFIG consistency coverage (#1690)
-- feat: add verify extension to community catalog (#1726)
-- Add Retrospective Extension to community catalog README table (#1741)
-- fix(scripts): add empty description validation and branch checkout error handling (#1559)
-- fix: correct Copilot extension command registration (#1724)
-- fix(implement): remove Makefile from C ignore patterns (#1558)
-- Add sync extension to community catalog (#1728)
-- fix(checklist): clarify file handling behavior for append vs create (#1556)
-- fix(clarify): correct conflicting question limit from 10 to 5 (#1557)
-- chore: bump version to 0.1.12 (#1737)
-- fix: use RELEASE_PAT so tag push triggers release workflow (#1736)
-- fix: release-trigger uses release branch + PR instead of direct push to main (#1733)
-- fix: Split release process to sync pyproject.toml version with git tags (#1732)
-
-
-## [0.1.13] - 2026-03-03
+- SOCKS proxy support for corporate environments via `httpx[socks]` dependency
 
 ### Fixed
 
-- **Copilot Extension Commands Not Visible**: Fixed extension commands not appearing in GitHub Copilot when installed via `specify extension add --dev`
-  - Changed Copilot file extension from `.md` to `.agent.md` in `CommandRegistrar.AGENT_CONFIGS` so Copilot recognizes agent files
-  - Added generation of companion `.prompt.md` files in `.github/prompts/` during extension command registration, matching the release packaging behavior
-  - Added cleanup of `.prompt.md` companion files when removing extensions via `specify extension remove`
-- Fixed a syntax regression in `src/specify_cli/__init__.py` in `_build_ai_assistant_help()` that broke `ruff` and `pytest` collection in CI.
-## [0.1.12] - 2026-03-02
+N/A
 
 ### Changed
 
-- fix: use RELEASE_PAT so tag push triggers release workflow (#1736)
-- fix: release-trigger uses release branch + PR instead of direct push to main (#1733)
-- fix: Split release process to sync pyproject.toml version with git tags (#1732)
-
-
-## [0.1.10] - 2026-03-02
-
-### Fixed
-
-- **Version Sync Issue (#1721)**: Fixed version mismatch between `pyproject.toml` and git release tags
-  - Split release process into two workflows: `release-trigger.yml` for version management and `release.yml` for artifact building
-  - Version bump now happens BEFORE tag creation, ensuring tags point to commits with correct version
-  - Supports both manual version specification and auto-increment (patch version)
-  - Git tags now accurately reflect the version in `pyproject.toml` at that commit
-  - Prevents confusion when installing from source
-
-## [0.1.9] - 2026-02-28
-
-### Changed
-
-- Updated dependency: bumped astral-sh/setup-uv from 6 to 7
-
-## [0.1.8] - 2026-02-28
-
-### Changed
-
-- Updated dependency: bumped actions/setup-python from 5 to 6
-
-## [0.1.7] - 2026-02-27
-
-### Changed
-
-- Updated outdated GitHub Actions versions
-- Documented dual-catalog system for extensions
-
-### Fixed
-
-- Fixed version command in documentation
-
-### Added
-
-- Added Cleanup Extension to README
-- Added retrospective extension to community catalog
-
-## [0.1.6] - 2026-02-23
-
-### Fixed
-
-- **Parameter Ordering Issues (#1641)**: Fixed CLI parameter parsing issue where option flags were incorrectly consumed as values for preceding options
-  - Added validation to detect when `--ai` or `--ai-commands-dir` incorrectly consume following flags like `--here` or `--ai-skills`
-  - Now provides clear error messages: "Invalid value for --ai: '--here'"
-  - Includes helpful hints suggesting proper usage and listing available agents
-  - Commands like `specify init --ai-skills --ai --here` now fail with actionable feedback instead of confusing "Must specify project name" errors
-  - Added comprehensive test suite (5 new tests) to prevent regressions
-
-## [0.1.5] - 2026-02-21
-
-### Fixed
-
-- **AI Skills Installation Bug (#1658)**: Fixed `--ai-skills` flag not generating skill files for GitHub Copilot and other agents with non-standard command directory structures
-  - Added `commands_subdir` field to `AGENT_CONFIG` to explicitly specify the subdirectory name for each agent
-  - Affected agents now work correctly: copilot (`.github/agents/`), opencode (`.opencode/command/`), windsurf (`.windsurf/workflows/`), codex (`.codex/prompts/`), kilocode (`.kilocode/workflows/`), q (`.amazonq/prompts/`), and agy (`.agent/workflows/`)
-  - The `install_ai_skills()` function now uses the correct path for all agents instead of assuming `commands/` for everyone
-
-## [0.1.4] - 2026-02-20
-
-### Fixed
-
-- **Qoder CLI detection**: Renamed `AGENT_CONFIG` key from `"qoder"` to `"qodercli"` to match the actual executable name, fixing `specify check` and `specify init --ai` detection failures
-
-## [0.1.3] - 2026-02-20
-
-### Added
-
-- **Generic Agent Support**: Added `--ai generic` option for unsupported AI agents ("bring your own agent")
-  - Requires `--ai-commands-dir <path>` to specify where the agent reads commands from
-  - Generates Markdown commands with `$ARGUMENTS` format (compatible with most agents)
-  - Example: `specify init my-project --ai generic --ai-commands-dir .myagent/commands/`
-  - Enables users to start with Spec Kit immediately while their agent awaits formal support
-
-## [0.0.102] - 2026-02-20
-
-- fix: include 'src/**' path in release workflow triggers (#1646)
-
-## [0.0.101] - 2026-02-19
-
-- chore(deps): bump github/codeql-action from 3 to 4 (#1635)
-
-## [0.0.100] - 2026-02-19
-
-- Add pytest and Python linting (ruff) to CI (#1637)
-- feat: add pull request template for better contribution guidelines (#1634)
-
-## [0.0.99] - 2026-02-19
-
-- Feat/ai skills (#1632)
-
-## [0.0.98] - 2026-02-19
-
-- chore(deps): bump actions/stale from 9 to 10 (#1623)
-- feat: add dependabot configuration for pip and GitHub Actions updates (#1622)
-
-## [0.0.97] - 2026-02-18
-
-- Remove Maintainers section from README.md (#1618)
-
-## [0.0.96] - 2026-02-17
-
-- fix: typo in plan-template.md (#1446)
-
-## [0.0.95] - 2026-02-12
-
-- Feat: add a new agent: Google Anti Gravity (#1220)
-
-## [0.0.94] - 2026-02-11
-
-- Add stale workflow for 180-day inactive issues and PRs (#1594)
+N/A

CODE_OF_CONDUCT.md

@@ -14,21 +14,21 @@ orientation.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-- The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
   address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
+* Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Our Responsibilities
@@ -71,4 +71,4 @@ This Code of Conduct is adapted from the [Contributor Covenant][homepage], versi
 available at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to Spec Kit
+## Contributing to Spec Kit
 
 Hi there! We're thrilled that you'd like to contribute to Spec Kit. Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
 
@@ -11,29 +11,12 @@ These are one time installations required to be able to test your changes locall
 1. Install [Python 3.11+](https://www.python.org/downloads/)
 1. Install [uv](https://docs.astral.sh/uv/) for package management
 1. Install [Git](https://git-scm.com/downloads)
-1. Have an [AI coding agent available](README.md#-supported-ai-agents)
-
-<details>
-<summary><b>💡 Hint if you are using <code>VSCode</code> or <code>GitHub Codespaces</code> as your IDE</b></summary>
-
-<br>
-
-Provided you have [Docker](https://docker.com) installed on your machine, you can leverage [Dev Containers](https://containers.dev) through this [VSCode extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers), to easily set up your development environment, with aforementioned tools already installed and configured, thanks to the `.devcontainer/devcontainer.json` file (located at the root of the project).
-
-To do so, simply:
-
-- Checkout the repo
-- Open it with VSCode
-- Open the [Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette) and select "Dev Containers: Open Folder in Container..."
-
-On [GitHub Codespaces](https://github.com/features/codespaces) it's even simpler, as it leverages the `.devcontainer/devcontainer.json` automatically upon opening the codespace.
-
-</details>
+1. Have an AI coding agent available: [Claude Code](https://www.anthropic.com/claude-code), [GitHub Copilot](https://code.visualstudio.com/), or [Gemini CLI](https://github.com/google-gemini/gemini-cli) are recommended, but we're working on adding support for other agents as well.
 
 ## Submitting a pull request
 
-> [!NOTE]
-> If your pull request introduces a large change that materially impacts the work of the CLI or the rest of the repository (e.g., you're introducing new templates, arguments, or otherwise major changes), make sure that it was **discussed and agreed upon** by the project maintainers. Pull requests with large changes that did not have a prior conversation and agreement will be closed.
+>[!NOTE]
+>If your pull request introduces a large change that materially impacts the work of the CLI or the rest of the repository (e.g., you're introducing new templates, arguments, or otherwise major changes), make sure that it was **discussed and agreed upon** by the project maintainers. Pull requests with large changes that did not have a prior conversation and agreement will be closed.
 
 1. Fork and clone the repository
 1. Configure and install the dependencies: `uv sync`
@@ -48,7 +31,7 @@ Here are a few things you can do that will increase the likelihood of your pull
 
 - Follow the project's coding conventions.
 - Write tests for new functionality.
-- Update documentation (`README.md`, `spec-driven.md`) if your changes affect user-facing features.
+- Update documentation (`README.md,` `spec-driven.md`) if your changes affect user-facing features.
 - Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
 - 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.
@@ -57,91 +40,11 @@ Here are a few things you can do that will increase the likelihood of your pull
 
 When working on spec-kit:
 
-1. Test changes with the `specify` CLI commands (`/speckit.specify`, `/speckit.plan`, `/speckit.tasks`) in your coding agent of choice
+1. Test changes with the `specify` CLI commands (`/specify`, `/plan`, `/tasks`) in your coding agent of choice
 2. Verify templates are working correctly in `templates/` directory
 3. Test script functionality in the `scripts/` directory
 4. Ensure memory files (`memory/constitution.md`) are updated if major process changes are made
 
-### Testing template and command changes locally
-
-Running `uv run specify init` pulls released packages, which won’t include your local changes.  
-To test your templates, commands, and other changes locally, follow these steps:
-
-1. **Create release packages**
-
-   Run the following command to generate the local packages:
-
-   ```bash
-   ./.github/workflows/scripts/create-release-packages.sh v1.0.0
-   ```
-
-2. **Copy the relevant package to your test project**
-
-   ```bash
-   cp -r .genreleases/sdd-copilot-package-sh/. <path-to-test-project>/
-   ```
-
-3. **Open and test the agent**
-
-   Navigate to your test project folder and open the agent to verify your implementation.
-
-## AI contributions in Spec Kit
-
-> [!IMPORTANT]
->
-> If you are using **any kind of AI assistance** to contribute to Spec Kit,
-> it must be disclosed in the pull request or issue.
-
-We welcome and encourage the use of AI tools to help improve Spec Kit! Many valuable contributions have been enhanced with AI assistance for code generation, issue detection, and feature definition.
-
-That being said, if you are using any kind of AI assistance (e.g., agents, ChatGPT) while contributing to Spec Kit,
-**this must be disclosed in the pull request or issue**, along with the extent to which AI assistance was used (e.g., documentation comments vs. code generation).
-
-If your PR responses or comments are being generated by an AI, disclose that as well.
-
-As an exception, trivial spacing or typo fixes don't need to be disclosed, so long as the changes are limited to small parts of the code or short phrases.
-
-An example disclosure:
-
-> This PR was written primarily by GitHub Copilot.
-
-Or a more detailed disclosure:
-
-> I consulted ChatGPT to understand the codebase but the solution
-> was fully authored manually by myself.
-
-Failure to disclose this is first and foremost rude to the human operators on the other end of the pull request, but it also makes it difficult to
-determine how much scrutiny to apply to the contribution.
-
-In a perfect world, AI assistance would produce equal or higher quality work than any human. That isn't the world we live in today, and in most cases
-where human supervision or expertise is not in the loop, it's generating code that cannot be reasonably maintained or evolved.
-
-### What we're looking for
-
-When submitting AI-assisted contributions, please ensure they include:
-
-- **Clear disclosure of AI use** - You are transparent about AI use and degree to which you're using it for the contribution
-- **Human understanding and testing** - You've personally tested the changes and understand what they do
-- **Clear rationale** - You can explain why the change is needed and how it fits within Spec Kit's goals
-- **Concrete evidence** - Include test cases, scenarios, or examples that demonstrate the improvement
-- **Your own analysis** - Share your thoughts on the end-to-end developer experience
-
-### What we'll close
-
-We reserve the right to close contributions that appear to be:
-
-- Untested changes submitted without verification
-- Generic suggestions that don't address specific Spec Kit needs
-- Bulk submissions that show no human review or understanding
-
-### Guidelines for success
-
-The key is demonstrating that you understand and have validated your proposed changes. If a maintainer can easily tell that a contribution was generated entirely by AI without human input or testing, it likely needs more work before submission.
-
-Contributors who consistently submit low-effort AI-generated changes may be restricted from further contributions at the maintainers' discretion.
-
-Please be respectful to maintainers and disclose AI assistance.
-
 ## Resources
 
 - [Spec-Driven Development Methodology](./spec-driven.md)

LICENSE

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

README.md

@@ -1,37 +1,32 @@
 <div align="center">
-    <img src="./media/logo_large.webp" alt="Spec Kit Logo" width="200" height="200"/>
+    <img src="./media/logo_small.webp"/>
     <h1>🌱 Spec Kit</h1>
     <h3><em>Build high-quality software faster.</em></h3>
 </div>
 
 <p align="center">
-    <strong>An open source toolkit that allows you to focus on product scenarios and predictable outcomes instead of vibe coding every piece from scratch.</strong>
+    <strong>An effort to allow organizations to focus on product scenarios rather than writing undifferentiated code with the help of Spec-Driven Development.</strong>
 </p>
 
-<p align="center">
-    <a href="https://github.com/github/spec-kit/actions/workflows/release.yml"><img src="https://github.com/github/spec-kit/actions/workflows/release.yml/badge.svg" alt="Release"/></a>
-    <a href="https://github.com/github/spec-kit/stargazers"><img src="https://img.shields.io/github/stars/github/spec-kit?style=social" alt="GitHub stars"/></a>
-    <a href="https://github.com/github/spec-kit/blob/main/LICENSE"><img src="https://img.shields.io/github/license/github/spec-kit" alt="License"/></a>
-    <a href="https://github.github.io/spec-kit/"><img src="https://img.shields.io/badge/docs-GitHub_Pages-blue" alt="Documentation"/></a>
-</p>
+[![Release](https://github.com/github/spec-kit/actions/workflows/release.yml/badge.svg)](https://github.com/github/spec-kit/actions/workflows/release.yml)
 
 ---
 
 ## Table of Contents
 
 - [🤔 What is Spec-Driven Development?](#-what-is-spec-driven-development)
-- [⚡ Get Started](#-get-started)
+- [⚡ Get started](#-get-started)
 - [📽️ Video Overview](#️-video-overview)
-- [🚶 Community Walkthroughs](#-community-walkthroughs)
-- [🤖 Supported AI Agents](#-supported-ai-agents)
 - [🔧 Specify CLI Reference](#-specify-cli-reference)
-- [📚 Core Philosophy](#-core-philosophy)
-- [🌟 Development Phases](#-development-phases)
-- [🎯 Experimental Goals](#-experimental-goals)
+- [<EFBFBD> APM Integration](#-apm-integration)
+- [<EFBFBD>📚 Core philosophy](#-core-philosophy)
+- [🌟 Development phases](#-development-phases)
+- [🎯 Experimental goals](#-experimental-goals)
 - [🔧 Prerequisites](#-prerequisites)
-- [📖 Learn More](#-learn-more)
-- [📋 Detailed Process](#-detailed-process)
+- [📖 Learn more](#-learn-more)
+- [📋 Detailed process](#-detailed-process)
 - [🔍 Troubleshooting](#-troubleshooting)
+- [👥 Maintainers](#-maintainers)
 - [💬 Support](#-support)
 - [🙏 Acknowledgements](#-acknowledgements)
 - [📄 License](#-license)
@@ -40,103 +35,35 @@
 
 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.
 
-## ⚡ Get Started
+## ⚡ Get started
 
-### 1. Install Specify CLI
+### 1. Install Specify
 
-Choose your preferred installation method:
-
-#### Option 1: Persistent Installation (Recommended)
-
-Install once and use everywhere:
+Initialize your project depending on the coding agent you're using:
 
 ```bash
-uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
-```
-
-Then use the tool directly:
-
-```bash
-# Create new project
-specify init <PROJECT_NAME>
-
-# Or initialize in existing project
-specify init . --ai claude
-# or
-specify init --here --ai claude
-
-# 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
-```
-
-#### Option 2: One-time Usage
-
-Run directly without installing:
-
-```bash
-# Create new project
 uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME>
-
-# Or initialize in existing project
-uvx --from git+https://github.com/github/spec-kit.git specify init . --ai claude
-# or
-uvx --from git+https://github.com/github/spec-kit.git specify init --here --ai claude
 ```
 
-**Benefits of persistent installation:**
+### 2. Create the spec
 
-- 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
-
-### 2. Establish project principles
-
-Launch your AI assistant in the project directory. The `/speckit.*` commands are available in the assistant.
-
-Use the **`/speckit.constitution`** command to create your project's governing principles and development guidelines that will guide all subsequent development.
+Use the **`/specify`** command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
 
 ```bash
-/speckit.constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements
+/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.
 ```
 
-### 3. Create the spec
+### 3. Create a technical implementation plan
 
-Use the **`/speckit.specify`** command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
+Use the **`/plan`** command to provide your tech stack and architecture choices.
 
 ```bash
-/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.
+/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.
 ```
 
-### 4. Create a technical implementation plan
+### 4. Break down and implement
 
-Use the **`/speckit.plan`** command to provide your tech stack and architecture choices.
-
-```bash
-/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.
-```
-
-### 5. Break down into tasks
-
-Use **`/speckit.tasks`** to create an actionable task list from your implementation plan.
-
-```bash
-/speckit.tasks
-```
-
-### 6. Execute implementation
-
-Use **`/speckit.implement`** to execute all tasks and build your feature according to the plan.
-
-```bash
-/speckit.implement
-```
+Use **`/tasks`** to create an actionable task list, then ask your agent to implement the feature.
 
 For detailed step-by-step instructions, see our [comprehensive guide](./spec-driven.md).
 
@@ -146,70 +73,31 @@ 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 Walkthroughs
-
-See Spec-Driven Development in action across different scenarios with these community-contributed walkthroughs:
-
-- **[Greenfield .NET CLI tool](https://github.com/mnriem/spec-kit-dotnet-cli-demo)** — Builds a Timezone Utility as a .NET single-binary CLI tool from a blank directory, covering the full spec-kit workflow: constitution, specify, plan, tasks, and multi-pass implement using GitHub Copilot agents.
-
-- **[Greenfield Spring Boot + React platform](https://github.com/mnriem/spec-kit-spring-react-demo)** — Builds an LLM performance analytics platform (REST API, graphs, iteration tracking) from scratch using Spring Boot, embedded React, PostgreSQL, and Docker Compose, with a clarify step and a cross-artifact consistency analysis pass included.
-
-- **[Brownfield ASP.NET CMS extension](https://github.com/mnriem/spec-kit-aspnet-brownfield-demo)** — Extends an existing open-source .NET CMS (CarrotCakeCMS-Core) with two new features — cross-platform Docker Compose infrastructure and a token-authenticated headless REST API — demonstrating how spec-kit fits into existing codebases without prior specs or a constitution.
-
-## 🤖 Supported AI Agents
-
-| Agent                                                                                | Support | Notes                                                                                                                                     |
-| ------------------------------------------------------------------------------------ | ------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| [Qoder CLI](https://qoder.com/cli)                                                   | ✅      |                                                                                                                                           |
-| [Kiro CLI](https://kiro.dev/docs/cli/)                                               | ✅      | Use `--ai kiro-cli` (alias: `--ai kiro`)                                                                                                 |
-| [Amp](https://ampcode.com/)                                                          | ✅      |                                                                                                                                           |
-| [Auggie CLI](https://docs.augmentcode.com/cli/overview)                              | ✅      |                                                                                                                                           |
-| [Claude Code](https://www.anthropic.com/claude-code)                                 | ✅      |                                                                                                                                           |
-| [CodeBuddy CLI](https://www.codebuddy.ai/cli)                                        | ✅      |                                                                                                                                           |
-| [Codex CLI](https://github.com/openai/codex)                                         | ✅      |                                                                                                                                           |
-| [Cursor](https://cursor.sh/)                                                         | ✅      |                                                                                                                                           |
-| [Gemini CLI](https://github.com/google-gemini/gemini-cli)                            | ✅      |                                                                                                                                           |
-| [GitHub Copilot](https://code.visualstudio.com/)                                     | ✅      |                                                                                                                                           |
-| [IBM Bob](https://www.ibm.com/products/bob)                                          | ✅      | IDE-based agent with slash command support                                                                                                |
-| [Jules](https://jules.google.com/)                                                   | ✅      |                                                                                                                                           |
-| [Kilo Code](https://github.com/Kilo-Org/kilocode)                                    | ✅      |                                                                                                                                           |
-| [opencode](https://opencode.ai/)                                                     | ✅      |                                                                                                                                           |
-| [Qwen Code](https://github.com/QwenLM/qwen-code)                                     | ✅      |                                                                                                                                           |
-| [Roo Code](https://roocode.com/)                                                     | ✅      |                                                                                                                                           |
-| [SHAI (OVHcloud)](https://github.com/ovh/shai)                                       | ✅      |                                                                                                                                           |
-| [Tabnine CLI](https://docs.tabnine.com/main/getting-started/tabnine-cli)             | ✅      |                                                                                                                                           |
-| [Mistral Vibe](https://github.com/mistralai/mistral-vibe)                            | ✅      |                                                                                                                                           |
-| [Windsurf](https://windsurf.com/)                                                    | ✅      |                                                                                                                                           |
-| [Antigravity (agy)](https://antigravity.google/)                                     | ✅      |                                                                                                                                           |
-| Generic                                                                              | ✅      | Bring your own agent — use `--ai generic --ai-commands-dir <path>` for unsupported agents                                                 |
-
 ## 🔧 Specify CLI Reference
 
 The `specify` command supports the following options:
 
 ### Commands
 
-| Command | Description                                                                                                                                             |
-| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `init`  | Initialize a new Specify project from the latest template                                                                                               |
-| `check` | Check for installed tools (`git`, `claude`, `gemini`, `code`/`code-insiders`, `cursor-agent`, `windsurf`, `qwen`, `opencode`, `codex`, `kiro-cli`, `shai`, `qodercli`, `vibe`) |
+| Command     | Description                                                    |
+|-------------|----------------------------------------------------------------|
+| `init`      | Initialize a new Specify project from the latest template      |
+| `check`     | Check for installed tools (`git`, `claude`, `gemini`, `code`/`code-insiders`, `cursor-agent`) |
+| `apm`       | APM - Agent Package Manager commands for Context management   |
 
 ### `specify init` Arguments & Options
 
-| Argument/Option        | Type     | Description                                                                                                                                                                                  |
-| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `<project-name>`       | Argument | Name for your new project directory (optional if using `--here`, or use `.` for current directory)                                                                                           |
-| `--ai`                 | Option   | AI assistant to use: `claude`, `gemini`, `copilot`, `cursor-agent`, `qwen`, `opencode`, `codex`, `windsurf`, `kilocode`, `auggie`, `roo`, `codebuddy`, `amp`, `shai`, `kiro-cli` (`kiro` alias), `agy`, `bob`, `qodercli`, `vibe`, or `generic` (requires `--ai-commands-dir`) |
-| `--ai-commands-dir`    | Option   | Directory for agent command files (required with `--ai generic`, e.g. `.myagent/commands/`)                                                                                                  |
-| `--script`             | Option   | Script variant to use: `sh` (bash/zsh) or `ps` (PowerShell)                                                                                                                                  |
-| `--ignore-agent-tools` | Flag     | Skip checks for AI agent tools like Claude Code                                                                                                                                              |
-| `--no-git`             | Flag     | Skip git repository initialization                                                                                                                                                           |
-| `--here`               | Flag     | Initialize project in the current directory instead of creating a new one                                                                                                                    |
-| `--force`              | Flag     | Force merge/overwrite when initializing in current directory (skip confirmation)                                                                                                             |
-| `--skip-tls`           | Flag     | Skip SSL/TLS verification (not recommended)                                                                                                                                                  |
-| `--debug`              | Flag     | Enable detailed debug output for troubleshooting                                                                                                                                             |
-| `--github-token`       | Option   | GitHub token for API requests (or set GH_TOKEN/GITHUB_TOKEN env variable)                                                                                                                    |
-| `--ai-skills`          | Flag     | Install Prompt.MD templates as agent skills in agent-specific `skills/` directory (requires `--ai`)                                                                                          |
+| Argument/Option        | Type     | Description                                                                  |
+|------------------------|----------|------------------------------------------------------------------------------|
+| `<project-name>`       | Argument | Name for your new project directory (optional if using `--here`)            |
+| `--ai`                 | Option   | AI assistant to use: `claude`, `gemini`, `copilot`, or `cursor`             |
+| `--script`             | Option   | Script variant to use: `sh` (bash/zsh) or `ps` (PowerShell)                 |
+| `--ignore-agent-tools` | Flag     | Skip checks for AI agent tools like Claude Code                             |
+| `--no-git`             | Flag     | Skip git repository initialization                                          |
+| `--here`               | Flag     | Initialize project in the current directory instead of creating a new one   |
+| `--skip-tls`           | Flag     | Skip SSL/TLS verification (not recommended)                                 |
+| `--debug`              | Flag     | Enable detailed debug output for troubleshooting                            |
+| `--use-apm`            | Flag     | Include APM (Agent Package Manager) structure for context management       |
 
 ### Examples
 
@@ -220,48 +108,17 @@ specify init my-project
 # Initialize with specific AI assistant
 specify init my-project --ai claude
 
+# Initialize with APM support
+specify init my-project --ai claude --use-apm
+
 # Initialize with Cursor support
-specify init my-project --ai cursor-agent
-
-# Initialize with Qoder support
-specify init my-project --ai qodercli
-
-# Initialize with Windsurf support
-specify init my-project --ai windsurf
-
-# Initialize with Kiro CLI support
-specify init my-project --ai kiro-cli
-
-# Initialize with Amp support
-specify init my-project --ai amp
-
-# Initialize with SHAI support
-specify init my-project --ai shai
-
-# Initialize with Mistral Vibe support
-specify init my-project --ai vibe
-
-# Initialize with IBM Bob support
-specify init my-project --ai bob
-
-# Initialize with Antigravity support
-specify init my-project --ai agy
-
-# Initialize with an unsupported agent (generic / bring your own agent)
-specify init my-project --ai generic --ai-commands-dir .myagent/commands/
+specify init my-project --ai cursor
 
 # Initialize with PowerShell scripts (Windows/cross-platform)
 specify init my-project --ai copilot --script ps
 
-# Initialize in current directory
-specify init . --ai copilot
-# or use the --here flag
-specify init --here --ai copilot
-
-# Force merge into current (non-empty) directory without confirmation
-specify init . --force --ai copilot
-# or
-specify init --here --force --ai copilot
+# Initialize in current directory with APM
+specify init --here --ai copilot --use-apm
 
 # Skip git initialization
 specify init my-project --ai gemini --no-git
@@ -269,69 +126,70 @@ specify init my-project --ai gemini --no-git
 # Enable debug output for troubleshooting
 specify init my-project --ai claude --debug
 
-# Use GitHub token for API requests (helpful for corporate environments)
-specify init my-project --ai claude --github-token ghp_your_token_here
-
-# Install agent skills with the project
-specify init my-project --ai claude --ai-skills
-
-# Initialize in current directory with agent skills
-specify init --here --ai gemini --ai-skills
-
 # Check system requirements
 specify check
 ```
 
-### Available Slash Commands
+## 📦 APM Integration - NPM for Agent Context
 
-After running `specify init`, your AI coding agent will have access to these slash commands for structured development:
+**Context as Code Packages**: Package and share agent intelligence like npm packages. With APM, your agents get:
 
-#### Core Commands
+- **Team knowledge** from reusable context packages
+- **Optimized context** through mathematical relevance scoring  
+- **Universal compatibility** via dynamically generated Agents.md files
 
-Essential commands for the Spec-Driven Development workflow:
+[Complete Context Management Guide →](docs/context-management.md)
 
-| Command                 | Description                                                              |
-| ----------------------- | ------------------------------------------------------------------------ |
-| `/speckit.constitution` | Create or update project governing principles and development guidelines |
-| `/speckit.specify`      | Define what you want to build (requirements and user stories)            |
-| `/speckit.plan`         | Create technical implementation plans with your chosen tech stack        |
-| `/speckit.tasks`        | Generate actionable task lists for implementation                        |
-| `/speckit.implement`    | Execute all tasks to build the feature according to the plan             |
+Spec Kit includes full APM (Agent Package Manager) functionality for managing modular context packages and files:
 
-#### Optional Commands
+### Unified Initialization
+```bash
+# The --use-apm flag creates both SDD and APM structures 
+specify init my-project --ai claude --use-apm
+```
 
-Additional commands for enhanced quality and validation:
+### APM Commands
+```bash
+# Core APM commands available under 'apm' subcommand
 
-| Command              | Description                                                                                                                          |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `/speckit.clarify`   | Clarify underspecified areas (recommended before `/speckit.plan`; formerly `/quizme`)                                                |
-| `/speckit.analyze`   | Cross-artifact consistency & coverage analysis (run after `/speckit.tasks`, before `/speckit.implement`)                             |
-| `/speckit.checklist` | Generate custom quality checklists that validate requirements completeness, clarity, and consistency (like "unit tests for English") |
+# Install APM packages from apm.yml
+specify apm install       
 
-### Environment Variables
+# Add APM package to apm.yml and install                      
+specify apm install org/repo   
 
-| Variable          | Description                                                                                                                                                                                                                                                                                            |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `SPECIFY_FEATURE` | Override feature detection for non-Git repositories. Set to the feature directory name (e.g., `001-photo-albums`) to work on a specific feature when not using Git branches.<br/>\*\*Must be set in the context of the agent you're working with prior to using `/speckit.plan` or follow-up commands. |
+# Remove package from apm.yml and apm_modules
+specify apm uninstall org/repo              
 
-## 📚 Core Philosophy
+# Remove orphaned packages not in apm.yml
+specify apm prune   
+
+# List installed APM packages
+specify apm deps list    
+
+# Generate nested optimal AGENTS.md tree
+# Uses installed APM packages and local context files
+specify apm compile                                
+```
+
+## <20>📚 Core philosophy
 
 Spec-Driven Development is a structured process that emphasizes:
 
-- **Intent-driven development** where specifications define the "*what*" before the "*how*"
+- **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
+## 🌟 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>                                                                |
+| 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
+## 🎯 Experimental goals
 
 Our research and experimentation focus on:
 
@@ -359,22 +217,20 @@ Our research and experimentation focus on:
 
 ## 🔧 Prerequisites
 
-- **Linux/macOS/Windows**
-- [Supported](#-supported-ai-agents) AI coding agent.
+- **Linux/macOS** (or WSL2 on Windows)
+- AI coding agent: [Claude Code](https://www.anthropic.com/claude-code), [GitHub Copilot](https://code.visualstudio.com/), [Gemini CLI](https://github.com/google-gemini/gemini-cli), or [Cursor](https://cursor.sh/)
 - [uv](https://docs.astral.sh/uv/) for package management
 - [Python 3.11+](https://www.python.org/downloads/)
 - [Git](https://git-scm.com/downloads)
 
-If you encounter issues with an agent, please open an issue so we can refine the integration.
-
-## 📖 Learn More
+## 📖 Learn more
 
 - **[Complete Spec-Driven Development Methodology](./spec-driven.md)** - Deep dive into the full process
 - **[Detailed Walkthrough](#-detailed-process)** - Step-by-step implementation guide
 
 ---
 
-## 📋 Detailed Process
+## 📋 Detailed process
 
 <details>
 <summary>Click to expand the detailed step-by-step walkthrough</summary>
@@ -388,13 +244,7 @@ specify init <project_name>
 Or initialize in the current directory:
 
 ```bash
-specify init .
-# or use the --here flag
 specify init --here
-# Skip confirmation when the directory already has files
-specify init . --force
-# or
-specify init --here --force
 ```
 
 ![Specify CLI bootstrapping a new project in the terminal](./media/specify_cli.gif)
@@ -405,50 +255,28 @@ You will be prompted to select the AI agent you are using. You can also proactiv
 specify init <project_name> --ai claude
 specify init <project_name> --ai gemini
 specify init <project_name> --ai copilot
-
 # Or in current directory:
-specify init . --ai claude
-specify init . --ai codex
-
-# or use --here flag
 specify init --here --ai claude
-specify init --here --ai codex
-
-# Force merge into a non-empty current directory
-specify init . --force --ai claude
-
-# or
-specify init --here --force --ai claude
 ```
 
-The CLI will check if you have Claude Code, Gemini CLI, Cursor CLI, Qwen CLI, opencode, Codex CLI, Qoder CLI, Tabnine CLI, Kiro CLI, or Mistral Vibe installed. If you do not, or you prefer to get the templates without checking for the right tools, use `--ignore-agent-tools` with your command:
+The CLI will check if you have Claude Code or Gemini CLI installed. If you do not, or you prefer to get the templates without checking for the right tools, use `--ignore-agent-tools` with your command:
 
 ```bash
 specify init <project_name> --ai claude --ignore-agent-tools
 ```
 
-### **STEP 1:** Establish project principles
+### **STEP 1:** Bootstrap the project
 
 Go to the project folder and run your AI agent. In our example, we're using `claude`.
 
 ![Bootstrapping Claude Code environment](./media/bootstrap-claude-code.gif)
 
-You will know that things are configured correctly if you see the `/speckit.constitution`, `/speckit.specify`, `/speckit.plan`, `/speckit.tasks`, and `/speckit.implement` commands available.
+You will know that things are configured correctly if you see the `/specify`, `/plan`, and `/tasks` commands available.
 
-The first step should be establishing your project's governing principles using the `/speckit.constitution` command. This helps ensure consistent decision-making throughout all subsequent development phases:
+The first step should be creating a new project scaffolding. Use `/specify` command and then provide the concrete requirements for the project you want to develop.
 
-```text
-/speckit.constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements. Include governance for how these principles should guide technical decisions and implementation choices.
-```
-
-This step creates or updates the `.specify/memory/constitution.md` file with your project's foundational guidelines that the AI agent will reference during specification, planning, and implementation phases.
-
-### **STEP 2:** Create project specifications
-
-With your project principles established, you can now create the functional specifications. Use the `/speckit.specify` command and then provide the concrete requirements for the project you want to develop.
-
-> [!IMPORTANT]
-> Be as explicit as possible about *what* you are trying to build and *why*. **Do not focus on the tech stack at this point**.
+>[!IMPORTANT]
+>Be as explicit as possible about _what_ you are trying to build and _why_. **Do not focus on the tech stack at this point**.
 
 An example prompt:
 
@@ -480,38 +308,28 @@ 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
-    │  ├── 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
+├── memory
+│	 ├── constitution.md
+│	 └── constitution_update_checklist.md
+├── scripts
+│	 ├── check-task-prerequisites.sh
+│	 ├── common.sh
+│	 ├── create-new-feature.sh
+│	 ├── get-feature-paths.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)
+### **STEP 2:** Functional specification clarification
 
-With the baseline specification created, you can go ahead and clarify any of the requirements that were not captured properly within the first shot attempt.
-
-You should run the structured clarification workflow **before** creating a technical plan to reduce rework downstream.
-
-Preferred order:
-
-1. Use `/speckit.clarify` (structured) – sequential, coverage-based questioning that records answers in a Clarifications section.
-2. Optionally follow up with ad-hoc free-form refinement if something still feels vague.
-
-If you intentionally want to skip clarification (e.g., spike or exploratory prototype), explicitly state that so the agent doesn't block on missing clarifications.
-
-Example free-form refinement prompt (after `/speckit.clarify` if still needed):
+With the baseline specification created, you can go ahead and clarify any of the requirements that were not captured properly within the first shot attempt. For example, you could use a prompt like this within the same Claude Code session:
 
 ```text
 For each sample project or project that you create there should be a variable number of tasks between 5 and 15
@@ -527,9 +345,9 @@ Read the review and acceptance checklist, and check off each item in the checkli
 
 It's important to use the interaction with Claude Code as an opportunity to clarify and ask questions around the specification - **do not treat its first attempt as final**.
 
-### **STEP 4:** Generate a plan
+### **STEP 3:** Generate a plan
 
-You can now be specific about the tech stack and other technical requirements. You can use the `/speckit.plan` command that is built into the project template with a prompt like this:
+You can now be specific about the tech stack and other technical requirements. You can use the `/plan` command that is built into the project template with a prompt like this:
 
 ```text
 We are going to generate this using .NET Aspire, using Postgres as the database. The frontend should use
@@ -543,23 +361,25 @@ The output of this step will include a number of implementation detail documents
 .
 ├── CLAUDE.md
 ├── memory
-│  └── constitution.md
+│	 ├── constitution.md
+│	 └── constitution_update_checklist.md
 ├── scripts
-│  ├── check-prerequisites.sh
-│  ├── common.sh
-│  ├── create-new-feature.sh
-│  ├── setup-plan.sh
-│  └── update-claude-md.sh
+│	 ├── check-task-prerequisites.sh
+│	 ├── common.sh
+│	 ├── create-new-feature.sh
+│	 ├── get-feature-paths.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
+│	 └── 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
@@ -591,10 +411,10 @@ researching .NET Aspire in general and I don't think that's gonna do much for us
 That's way too untargeted research. The research needs to help you solve a specific targeted question.
 ```
 
-> [!NOTE]
-> Claude Code might be over-eager and add components that you did not ask for. Ask it to clarify the rationale and the source of the change.
+>[!NOTE]
+>Claude Code might be over-eager and add components that you did not ask for. Ask it to clarify the rationale and the source of the change.
 
-### **STEP 5:** Have Claude Code validate the plan
+### **STEP 4:** Have Claude Code validate the plan
 
 With the plan in place, you should have Claude Code run through it to make sure that there are no missing pieces. You can use a prompt like this:
 
@@ -610,48 +430,23 @@ 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](base/memory/constitution.md) as the foundational piece that it must adhere to when establishing the plan.
+>[!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](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
+### STEP 5: Implementation
 
-With the implementation plan validated, you can now break down the plan into specific, actionable tasks that can be executed in the correct order. Use the `/speckit.tasks` command to automatically generate a detailed task breakdown from your implementation plan:
+Once ready, instruct Claude Code to implement your solution (example path included):
 
 ```text
-/speckit.tasks
+implement specs/002-create-taskify/plan.md
 ```
 
-This step creates a `tasks.md` file in your feature specification directory that contains:
+Claude Code will spring into action and will start creating the implementation.
 
-- **Task breakdown organized by user story** - Each user story becomes a separate implementation phase with its own set of tasks
-- **Dependency management** - Tasks are ordered to respect dependencies between components (e.g., models before services, services before endpoints)
-- **Parallel execution markers** - Tasks that can run in parallel are marked with `[P]` to optimize development workflow
-- **File path specifications** - Each task includes the exact file paths where implementation should occur
-- **Test-driven development structure** - If tests are requested, test tasks are included and ordered to be written before implementation
-- **Checkpoint validation** - Each user story phase includes checkpoints to validate independent functionality
+>[!IMPORTANT]
+>Claude Code will execute local CLI commands (such as `dotnet`) - make sure you have them installed on your machine.
 
-The generated tasks.md provides a clear roadmap for the `/speckit.implement` command, ensuring systematic implementation that maintains code quality and allows for incremental delivery of user stories.
-
-### **STEP 7:** Implementation
-
-Once ready, use the `/speckit.implement` command to execute your implementation plan:
-
-```text
-/speckit.implement
-```
-
-The `/speckit.implement` command will:
-
-- Validate that all prerequisites are in place (constitution, spec, plan, and tasks)
-- Parse the task breakdown from `tasks.md`
-- Execute tasks in the correct order, respecting dependencies and parallel execution markers
-- Follow the TDD approach defined in your task plan
-- Provide progress updates and handle errors appropriately
-
-> [!IMPORTANT]
-> The AI agent will execute local CLI commands (such as `dotnet`, `npm`, etc.) - make sure you have the required tools installed on your machine.
-
-Once the implementation is complete, test the application and resolve any runtime errors that may not be visible in CLI logs (e.g., browser console errors). You can copy and paste such errors back to your AI agent for resolution.
+Once the implementation step is done, ask Claude Code to try to run the application and resolve any emerging build errors. If the application runs, but there are _runtime errors_ that are not directly available to Claude Code through CLI logs (e.g., errors rendered in browser logs), copy and paste the error in Claude Code and have it attempt to resolve it.
 
 </details>
 
@@ -676,6 +471,12 @@ echo "Cleaning up..."
 rm gcm-linux_amd64.2.6.1.deb
 ```
 
+## 👥 Maintainers
+
+- Den Delimarsky ([@localden](https://github.com/localden))
+- John Lam ([@jflam](https://github.com/jflam))
+- Daniel Meppiel [@danielmeppiel](https://github.com/danielmeppiel)
+
 ## 💬 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.

SECURITY.md

@@ -1,10 +1,10 @@
-# Security Policy
-
 Thanks for helping make GitHub safe for everyone.
 
+# Security
+
 GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub).
 
-Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation.
+Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation. 
 
 ## Reporting Security Issues
 
@@ -16,16 +16,16 @@ Instead, please send an email to opensource-security[@]github.com.
 
 Please include as much of the information listed below as you can to help us better understand and resolve the issue:
 
-- The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
-- Full paths of source file(s) related to the manifestation of the issue
-- The location of the affected source code (tag/branch/commit or direct URL)
-- Any special configuration required to reproduce the issue
-- Step-by-step instructions to reproduce the issue
-- Proof-of-concept or exploit code (if possible)
-- Impact of the issue, including how an attacker might exploit the issue
+  * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
 
 This information will help us triage your report more quickly.
 
 ## Policy
 
-See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms)
+See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms)

SUPPORT.md

@@ -1,4 +1,4 @@
-# Support
+# Support 
 
 ## How to file issues and get help
 

docs/.gitignore

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

docs/README.md

@@ -7,13 +7,11 @@ This folder contains the documentation source files for Spec Kit, built using [D
 To build the documentation locally:
 
 1. Install DocFX:
-
    ```bash
    dotnet tool install -g docfx
    ```
 
 2. Build the documentation:
-
    ```bash
    cd docs
    docfx docfx.json --serve

docs/context-management.md

@@ -0,0 +1,59 @@
+# Context Management with APM
+
+## NPM for Agent Context
+
+Just like npm revolutionized JavaScript by enabling package reuse, APM creates an ecosystem for sharing agent context.
+
+## Package Composition & Reuse
+
+```yaml
+# Your project inherits team knowledge via apm.yml file in the root
+dependencies:
+  apm:
+    - company/design-system     # UI patterns, brand guidelines
+    - company/security-standards # Auth patterns, data handling
+    - community/best-practices  # Industry standards
+```
+
+**Result**: Your project gets all the instructions of above packages applied via dynamically generated Agents.md files using `specify apm compile`. These files are optimally generated to minimize contextual load for Agents compatible with the Agents.md standard.
+
+**Enterprise Scenario**: Design team creates accessibility guidelines once → entire organization uses them → agents work consistently across all projects.
+
+## Mathematical Context Optimization
+
+**The Technical Foundation**: APM uses mathematical optimization to solve the context efficiency problem.
+
+```
+Context_Efficiency = Relevant_Instructions / Total_Instructions_Loaded
+```
+
+**Why This Matters**: When agents work in `/styles/` directory, they shouldn't load Python compliance rules. APM's Context Optimization Engine ensures agents get minimal, highly relevant context.
+
+**The Algorithm**: Constraint satisfaction optimization that finds placement minimizing context pollution while maximizing relevance. Each instruction gets mathematically optimal placement across the project hierarchy.
+
+## Quick Start
+
+```bash
+specify init my-project --use-apm --ai copilot
+specify apm install company/design-system  
+specify apm compile  # Mathematical optimization generates distributed AGENTS.md files
+```
+
+## Universal Agent Compatibility
+
+APM generates distributed `AGENTS.md` files compatible with the [agents.md standard](https://agents.md), working with any coding agent (GitHub Copilot, Cursor, Claude, Codex, Aider, etc.).
+
+## Authentication Setup (Optional)
+
+```bash
+export GITHUB_APM_PAT=your_fine_grained_token_here
+```
+
+Only needed for private packages. Public community packages work without authentication.
+
+## The Complete Value
+
+1. **Package Ecosystem** - Share and compose agent intelligence like code dependencies
+2. **Mathematical Optimization** - Context Optimization Engine ensures relevance without pollution  
+3. **Universal Standards** - Works with any agent via industry-standard agents.md format
+4. **Enterprise Ready** - Team knowledge scales across entire organizations

docs/docfx.json

@@ -68,4 +68,3 @@
     }
   }
 }
-

docs/index.md

@@ -12,14 +12,13 @@ Spec-Driven Development **flips the script** on traditional software development
 
 - [Installation Guide](installation.md)
 - [Quick Start Guide](quickstart.md)
-- [Upgrade Guide](upgrade.md)
 - [Local Development](local-development.md)
 
 ## Core Philosophy
 
 Spec-Driven Development is a structured process that emphasizes:
 
-- **Intent-driven development** where specifications define the "*what*" before the "*how*"
+- **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
@@ -37,31 +36,27 @@ Spec-Driven Development is a structured process that emphasizes:
 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
 
 ## Contributing
 
-Please see our [Contributing Guide](https://github.com/github/spec-kit/blob/main/CONTRIBUTING.md) for information on how to contribute to this project.
+Please see our [Contributing Guide](CONTRIBUTING.md) for information on how to contribute to this project.
 
 ## Support
 
-For support, please check our [Support Guide](https://github.com/github/spec-kit/blob/main/SUPPORT.md) or open an issue on GitHub.
+For support, please check our [Support Guide](SUPPORT.md) or open an issue on GitHub.

docs/installation.md

@@ -3,7 +3,7 @@
 ## Prerequisites
 
 - **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) or [Gemini CLI](https://github.com/google-gemini/gemini-cli)
+- AI coding agent: [Claude Code](https://www.anthropic.com/claude-code), [GitHub Copilot](https://code.visualstudio.com/), or [Gemini CLI](https://github.com/google-gemini/gemini-cli)
 - [uv](https://docs.astral.sh/uv/) for package management
 - [Python 3.11+](https://www.python.org/downloads/)
 - [Git](https://git-scm.com/downloads)
@@ -21,8 +21,6 @@ uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME
 Or initialize in the current directory:
 
 ```bash
-uvx --from git+https://github.com/github/spec-kit.git specify init .
-# or use the --here flag
 uvx --from git+https://github.com/github/spec-kit.git specify init --here
 ```
 
@@ -34,7 +32,6 @@ You can proactively specify your AI agent during initialization:
 uvx --from git+https://github.com/github/spec-kit.git specify init <project_name> --ai claude
 uvx --from git+https://github.com/github/spec-kit.git specify init <project_name> --ai gemini
 uvx --from git+https://github.com/github/spec-kit.git specify init <project_name> --ai copilot
-uvx --from git+https://github.com/github/spec-kit.git specify init <project_name> --ai codebuddy
 ```
 
 ### Specify Script Type (Shell vs PowerShell)
@@ -42,13 +39,11 @@ uvx --from git+https://github.com/github/spec-kit.git specify init <project_name
 All automation scripts now have both Bash (`.sh`) and PowerShell (`.ps1`) variants.
 
 Auto behavior:
-
 - Windows default: `ps`
 - Other OS default: `sh`
 - Interactive mode: you'll be prompted unless you pass `--script`
 
 Force a specific script type:
-
 ```bash
 uvx --from git+https://github.com/github/spec-kit.git specify init <project_name> --script sh
 uvx --from git+https://github.com/github/spec-kit.git specify init <project_name> --script ps
@@ -65,10 +60,9 @@ uvx --from git+https://github.com/github/spec-kit.git specify init <project_name
 ## Verification
 
 After initialization, you should see the following commands available in your AI agent:
-
-- `/speckit.specify` - Create specifications
-- `/speckit.plan` - Generate implementation plans  
-- `/speckit.tasks` - Break down into actionable tasks
+- `/specify` - Create specifications
+- `/plan` - Generate implementation plans  
+- `/tasks` - Break down into actionable tasks
 
 The `.specify/scripts` directory will contain both `.sh` and `.ps1` scripts.
 

docs/local-development.md

@@ -73,14 +73,12 @@ uvx --from /mnt/c/GitHub/spec-kit specify init demo-anywhere --ai copilot --igno
 ```
 
 Set an environment variable for convenience:
-
 ```bash
 export SPEC_KIT_SRC=/mnt/c/GitHub/spec-kit
 uvx --from "$SPEC_KIT_SRC" specify init demo-env --ai copilot --ignore-agent-tools --script ps
 ```
 
 (Optional) Define a shell function:
-
 ```bash
 specify-dev() { uvx --from /mnt/c/GitHub/spec-kit specify "$@"; }
 # Then
@@ -95,13 +93,11 @@ After running an `init`, check that shell scripts are executable on POSIX system
 ls -l scripts | grep .sh
 # Expect owner execute bit (e.g. -rwxr-xr-x)
 ```
-
 On Windows you will instead use the `.ps1` scripts (no chmod needed).
 
 ## 6. Run Lint / Basic Checks (Add Your Own)
 
 Currently no enforced lint config is bundled, but you can quickly sanity check importability:
-
 ```bash
 python -c "import specify_cli; print('Import OK')"
 ```
@@ -114,7 +110,6 @@ Validate packaging before publishing:
 uv build
 ls dist/
 ```
-
 Install the built artifact into a fresh throwaway environment if needed.
 
 ## 8. Using a Temporary Workspace
@@ -125,7 +120,6 @@ When testing `init --here` in a dirty directory, create a temp workspace:
 mkdir /tmp/spec-test && cd /tmp/spec-test
 python -m src.specify_cli init --here --ai claude --ignore-agent-tools --script sh  # if repo copied here
 ```
-
 Or copy only the modified CLI portion if you want a lighter sandbox.
 
 ## 9. Debug Network / TLS Skips
@@ -136,7 +130,6 @@ If you need to bypass TLS validation while experimenting:
 specify check --skip-tls
 specify init demo --skip-tls --ai gemini --ignore-agent-tools --script ps
 ```
-
 (Use only for local experimentation.)
 
 ## 10. Rapid Edit Loop Summary
@@ -153,7 +146,6 @@ specify init demo --skip-tls --ai gemini --ignore-agent-tools --script ps
 ## 11. Cleaning Up
 
 Remove build artifacts / virtual env quickly:
-
 ```bash
 rm -rf .venv dist build *.egg-info
 ```
@@ -173,3 +165,4 @@ rm -rf .venv dist build *.egg-info
 - Update docs and run through Quick Start using your modified CLI
 - Open a PR when satisfied
 - (Optional) Tag a release once changes land in `main`
+

docs/quickstart.md

@@ -2,101 +2,49 @@
 
 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`.
+> NEW: 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`.
 
-## The 6-Step Process
+## The 4-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.
+### 1. Install Specify
 
-### Step 1: Install Specify
-
-**In your terminal**, run the `specify` CLI command to initialize your project:
+Initialize your project depending on the coding agent you're using:
 
 ```bash
-# Create a new project directory
 uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME>
-
-# OR initialize in the current directory
-uvx --from git+https://github.com/github/spec-kit.git specify init .
 ```
 
 Pick script type explicitly (optional):
-
 ```bash
 uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME> --script ps  # Force PowerShell
 uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME> --script sh  # Force POSIX shell
 ```
 
-### Step 2: Define Your Constitution
+### 2. Create the Spec
 
-**In your AI Agent's chat interface**, use the `/speckit.constitution` slash command to establish the core rules and principles for your project. You should provide your project's specific principles as arguments.
-
-```markdown
-/speckit.constitution This project follows a "Library-First" approach. All features must be implemented as standalone libraries first. We use TDD strictly. We prefer functional programming patterns.
-```
-
-### Step 3: Create the Spec
-
-**In the chat**, use the `/speckit.specify` slash command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
-
-```markdown
-/speckit.specify Build an application that can help me organize my photos in separate photo albums. Albums are grouped by date and can be re-organized by dragging and dropping on the main page. Albums are never in other nested albums. Within each album, photos are previewed in a tile-like interface.
-```
-
-### Step 4: 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.
+Use the `/specify` command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
 
 ```bash
-/speckit.clarify Focus on security and performance requirements.
+/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 5: Create a Technical Implementation Plan
+### 3. Create a Technical Implementation Plan
 
-**In the chat**, use the `/speckit.plan` slash command to provide your tech stack and architecture choices.
+Use the `/plan` command to provide your tech stack and architecture choices.
 
-```markdown
-/speckit.plan The application uses Vite with minimal number of libraries. Use vanilla HTML, CSS, and JavaScript as much as possible. Images are not uploaded anywhere and metadata is stored in a local SQLite database.
+```bash
+/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 and Implement
+### 4. Break Down and Implement
 
-**In the chat**, use the `/speckit.tasks` slash command to create an actionable task list.
-
-```markdown
-/speckit.tasks
-```
-
-Optionally, validate the plan with `/speckit.analyze`:
-
-```markdown
-/speckit.analyze
-```
-
-Then, use the `/speckit.implement` slash command to execute the plan.
-
-```markdown
-/speckit.implement
-```
-
-> [!TIP]
-> **Phased Implementation**: For complex projects, implement in phases to avoid overwhelming the agent's context. Start with core functionality, validate it works, then add features incrementally.
+Use `/tasks` to create an actionable task list, then ask your agent to implement the feature.
 
 ## Detailed Example: Building Taskify
 
 Here's a complete example of building a team productivity platform:
 
-### Step 1: Define Constitution
-
-Initialize the project's constitution to set ground rules:
-
-```markdown
-/speckit.constitution Taskify is a "Security-First" application. All user inputs must be validated. We use a microservices architecture. Code must be fully documented.
-```
-
-### Step 2: Define Requirements with `/speckit.specify`
+### Step 1: Define Requirements with `/specify`
 
 ```text
 Develop Taskify, a team productivity platform. It should allow users to create projects, add team members,
@@ -105,64 +53,60 @@ let's call it "Create Taskify," let's have multiple users but the users will be
 I want five users in two different categories, one product manager and four engineers. Let's create three
 different sample projects. Let's have the standard Kanban columns for the status of each task, such as "To Do,"
 "In Progress," "In Review," and "Done." There will be no login for this application as this is just the very
-first testing thing to ensure that our basic features are set up.
+first testing thing to ensure that our basic features are set up. For each task in the UI for a task card,
+you should be able to change the current status of the task between the different columns in the Kanban work board.
+You should be able to leave an unlimited number of comments for a particular card. You should be able to, from that task
+card, assign one of the valid users. When you first launch Taskify, it's going to give you a list of the five users to pick
+from. There will be no password required. When you click on a user, you go into the main view, which displays the list of
+projects. When you click on a project, you open the Kanban board for that project. You're going to see the columns.
+You'll be able to drag and drop cards back and forth between different columns. You will see any cards that are
+assigned to you, the currently logged in user, in a different color from all the other ones, so you can quickly
+see yours. You can edit any comments that you make, but you can't edit comments that other people made. You can
+delete any comments that you made, but you can't delete comments anybody else made.
 ```
 
-### Step 3: Refine the Specification
+### Step 2: Refine the Specification
 
-Use the `/speckit.clarify` command to interactively resolve any ambiguities in your specification. You can also provide specific details you want to ensure are included.
+After the initial specification is created, clarify any missing requirements:
 
-```bash
-/speckit.clarify I want to clarify the task card details. For each task in the UI for a task card, you should be able to change the current status of the task between the different columns in the Kanban work board. You should be able to leave an unlimited number of comments for a particular card. You should be able to, from that task card, assign one of the valid users.
+```text
+For each sample project or project that you create there should be a variable number of tasks between 5 and 15
+tasks for each one randomly distributed into different states of completion. Make sure that there's at least
+one task in each stage of completion.
 ```
 
-You can continue to refine the spec with more details using `/speckit.clarify`:
+Also validate the specification checklist:
 
-```bash
-/speckit.clarify When you first launch Taskify, it's going to give you a list of the five users to pick from. There will be no password required. When you click on a user, you go into the main view, which displays the list of projects. When you click on a project, you open the Kanban board for that project. You're going to see the columns. You'll be able to drag and drop cards back and forth between different columns. You will see any cards that are assigned to you, the currently logged in user, in a different color from all the other ones, so you can quickly see yours. You can edit any comments that you make, but you can't edit comments that other people made. You can delete any comments that you made, but you can't delete comments anybody else made.
+```text
+Read the review and acceptance checklist, and check off each item in the checklist if the feature spec meets the criteria. Leave it empty if it does not.
 ```
 
-### Step 4: Validate the Spec
-
-Validate the specification checklist using the `/speckit.checklist` command:
-
-```bash
-/speckit.checklist
-```
-
-### Step 5: Generate Technical Plan with `/speckit.plan`
+### Step 3: Generate Technical Plan with `/plan`
 
 Be specific about your tech stack and technical requirements:
 
-```bash
-/speckit.plan We are going to generate this using .NET Aspire, using Postgres as the database. The frontend should use Blazor server with drag-and-drop task boards, real-time updates. There should be a REST API created with a projects API, tasks API, and a notifications API.
+```text
+We are going to generate this using .NET Aspire, using Postgres as the database. The frontend should use
+Blazor server with drag-and-drop task boards, real-time updates. There should be a REST API created with a projects API,
+tasks API, and a notifications API.
 ```
 
-### Step 6: Define Tasks
+### Step 4: Validate and Implement
 
-Generate an actionable task list using the `/speckit.tasks` command:
+Have your AI agent audit the implementation plan:
 
-```bash
-/speckit.tasks
-```
-
-### Step 7: Validate and Implement
-
-Have your AI agent audit the implementation plan using `/speckit.analyze`:
-
-```bash
-/speckit.analyze
+```text
+Now I want you to go and audit the implementation plan and the implementation detail files.
+Read through it with an eye on determining whether or not there is a sequence of tasks that you need
+to be doing that are obvious from reading this. Because I don't know if there's enough here.
 ```
 
 Finally, implement the solution:
 
-```bash
-/speckit.implement
+```text
+implement specs/002-create-taskify/plan.md
 ```
 
-> [!TIP]
-> **Phased Implementation**: For large projects like Taskify, consider implementing in phases (e.g., Phase 1: Basic project/task structure, Phase 2: Kanban functionality, Phase 3: Comments and assignments). This prevents context saturation and allows for validation at each stage.
-
 ## Key Principles
 
 - **Be explicit** about what you're building and why
@@ -173,6 +117,6 @@ Finally, implement the solution:
 
 ## Next Steps
 
-- Read the [complete methodology](../spec-driven.md) for in-depth guidance
-- Check out [more examples](../templates) in the repository
-- Explore the [source code on GitHub](https://github.com/github/spec-kit)
+- Read the complete methodology for in-depth guidance
+- Check out more examples in the repository
+- Explore the source code on GitHub

docs/toc.yml

@@ -9,8 +9,6 @@
       href: installation.md
     - name: Quick Start
       href: quickstart.md
-    - name: Upgrade
-      href: upgrade.md
 
 # Development workflows
 - name: Development

docs/upgrade.md

@@ -1,444 +0,0 @@
-# Upgrade Guide
-
-> You have Spec Kit installed and want to upgrade to the latest version to get new features, bug fixes, or updated slash commands. This guide covers both upgrading the CLI tool and updating your project files.
-
----
-
-## Quick Reference
-
-| What to Upgrade | Command | When to Use |
-|----------------|---------|-------------|
-| **CLI Tool Only** | `uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git` | Get latest CLI features without touching project files |
-| **Project Files** | `specify init --here --force --ai <your-agent>` | Update slash commands, templates, and scripts in your project |
-| **Both** | Run CLI upgrade, then project update | Recommended for major version updates |
-
----
-
-## Part 1: Upgrade the CLI Tool
-
-The CLI tool (`specify`) is separate from your project files. Upgrade it to get the latest features and bug fixes.
-
-### If you installed with `uv tool install`
-
-```bash
-uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git
-```
-
-### If you use one-shot `uvx` commands
-
-No upgrade needed—`uvx` always fetches the latest version. Just run your commands as normal:
-
-```bash
-uvx --from git+https://github.com/github/spec-kit.git specify init --here --ai copilot
-```
-
-### Verify the upgrade
-
-```bash
-specify check
-```
-
-This shows installed tools and confirms the CLI is working.
-
----
-
-## Part 2: Updating Project Files
-
-When Spec Kit releases new features (like new slash commands or updated templates), you need to refresh your project's Spec Kit files.
-
-### What gets updated?
-
-Running `specify init --here --force` will update:
-
-- ✅ **Slash command files** (`.claude/commands/`, `.github/prompts/`, etc.)
-- ✅ **Script files** (`.specify/scripts/`)
-- ✅ **Template files** (`.specify/templates/`)
-- ✅ **Shared memory files** (`.specify/memory/`) - **⚠️ See warnings below**
-
-### What stays safe?
-
-These files are **never touched** by the upgrade—the template packages don't even contain them:
-
-- ✅ **Your specifications** (`specs/001-my-feature/spec.md`, etc.) - **CONFIRMED SAFE**
-- ✅ **Your implementation plans** (`specs/001-my-feature/plan.md`, `tasks.md`, etc.) - **CONFIRMED SAFE**
-- ✅ **Your source code** - **CONFIRMED SAFE**
-- ✅ **Your git history** - **CONFIRMED SAFE**
-
-The `specs/` directory is completely excluded from template packages and will never be modified during upgrades.
-
-### Update command
-
-Run this inside your project directory:
-
-```bash
-specify init --here --force --ai <your-agent>
-```
-
-Replace `<your-agent>` with your AI assistant. Refer to this list of [Supported AI Agents](../README.md#-supported-ai-agents)
-
-**Example:**
-
-```bash
-specify init --here --force --ai copilot
-```
-
-### Understanding the `--force` flag
-
-Without `--force`, the CLI warns you and asks for confirmation:
-
-```text
-Warning: Current directory is not empty (25 items)
-Template files will be merged with existing content and may overwrite existing files
-Proceed? [y/N]
-```
-
-With `--force`, it skips the confirmation and proceeds immediately.
-
-**Important: Your `specs/` directory is always safe.** The `--force` flag only affects template files (commands, scripts, templates, memory). Your feature specifications, plans, and tasks in `specs/` are never included in upgrade packages and cannot be overwritten.
-
----
-
-## ⚠️ Important Warnings
-
-### 1. Constitution file will be overwritten
-
-**Known issue:** `specify init --here --force` currently overwrites `.specify/memory/constitution.md` with the default template, erasing any customizations you made.
-
-**Workaround:**
-
-```bash
-# 1. Back up your constitution before upgrading
-cp .specify/memory/constitution.md .specify/memory/constitution-backup.md
-
-# 2. Run the upgrade
-specify init --here --force --ai copilot
-
-# 3. Restore your customized constitution
-mv .specify/memory/constitution-backup.md .specify/memory/constitution.md
-```
-
-Or use git to restore it:
-
-```bash
-# After upgrade, restore from git history
-git restore .specify/memory/constitution.md
-```
-
-### 2. Custom template modifications
-
-If you customized any templates in `.specify/templates/`, the upgrade will overwrite them. Back them up first:
-
-```bash
-# Back up custom templates
-cp -r .specify/templates .specify/templates-backup
-
-# After upgrade, merge your changes back manually
-```
-
-### 3. Duplicate slash commands (IDE-based agents)
-
-Some IDE-based agents (like Kilo Code, Windsurf) may show **duplicate slash commands** after upgrading—both old and new versions appear.
-
-**Solution:** Manually delete the old command files from your agent's folder.
-
-**Example for Kilo Code:**
-
-```bash
-# Navigate to the agent's commands folder
-cd .kilocode/rules/
-
-# List files and identify duplicates
-ls -la
-
-# Delete old versions (example filenames - yours may differ)
-rm speckit.specify-old.md
-rm speckit.plan-v1.md
-```
-
-Restart your IDE to refresh the command list.
-
----
-
-## Common Scenarios
-
-### Scenario 1: "I just want new slash commands"
-
-```bash
-# Upgrade CLI (if using persistent install)
-uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git
-
-# Update project files to get new commands
-specify init --here --force --ai copilot
-
-# Restore your constitution if customized
-git restore .specify/memory/constitution.md
-```
-
-### Scenario 2: "I customized templates and constitution"
-
-```bash
-# 1. Back up customizations
-cp .specify/memory/constitution.md /tmp/constitution-backup.md
-cp -r .specify/templates /tmp/templates-backup
-
-# 2. Upgrade CLI
-uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git
-
-# 3. Update project
-specify init --here --force --ai copilot
-
-# 4. Restore customizations
-mv /tmp/constitution-backup.md .specify/memory/constitution.md
-# Manually merge template changes if needed
-```
-
-### Scenario 3: "I see duplicate slash commands in my IDE"
-
-This happens with IDE-based agents (Kilo Code, Windsurf, Roo Code, etc.).
-
-```bash
-# Find the agent folder (example: .kilocode/rules/)
-cd .kilocode/rules/
-
-# List all files
-ls -la
-
-# Delete old command files
-rm speckit.old-command-name.md
-
-# Restart your IDE
-```
-
-### Scenario 4: "I'm working on a project without Git"
-
-If you initialized your project with `--no-git`, you can still upgrade:
-
-```bash
-# Manually back up files you customized
-cp .specify/memory/constitution.md /tmp/constitution-backup.md
-
-# Run upgrade
-specify init --here --force --ai copilot --no-git
-
-# Restore customizations
-mv /tmp/constitution-backup.md .specify/memory/constitution.md
-```
-
-The `--no-git` flag skips git initialization but doesn't affect file updates.
-
----
-
-## Using `--no-git` Flag
-
-The `--no-git` flag tells Spec Kit to **skip git repository initialization**. This is useful when:
-
-- You manage version control differently (Mercurial, SVN, etc.)
-- Your project is part of a larger monorepo with existing git setup
-- You're experimenting and don't want version control yet
-
-**During initial setup:**
-
-```bash
-specify init my-project --ai copilot --no-git
-```
-
-**During upgrade:**
-
-```bash
-specify init --here --force --ai copilot --no-git
-```
-
-### What `--no-git` does NOT do
-
-❌ Does NOT prevent file updates
-❌ Does NOT skip slash command installation
-❌ Does NOT affect template merging
-
-It **only** skips running `git init` and creating the initial commit.
-
-### Working without Git
-
-If you use `--no-git`, you'll need to manage feature directories manually:
-
-**Set the `SPECIFY_FEATURE` environment variable** before using planning commands:
-
-```bash
-# Bash/Zsh
-export SPECIFY_FEATURE="001-my-feature"
-
-# PowerShell
-$env:SPECIFY_FEATURE = "001-my-feature"
-```
-
-This tells Spec Kit which feature directory to use when creating specs, plans, and tasks.
-
-**Why this matters:** Without git, Spec Kit can't detect your current branch name to determine the active feature. The environment variable provides that context manually.
-
----
-
-## Troubleshooting
-
-### "Slash commands not showing up after upgrade"
-
-**Cause:** Agent didn't reload the command files.
-
-**Fix:**
-
-1. **Restart your IDE/editor** completely (not just reload window)
-2. **For CLI-based agents**, verify files exist:
-
-   ```bash
-   ls -la .claude/commands/      # Claude Code
-   ls -la .gemini/commands/       # Gemini
-   ls -la .cursor/commands/       # Cursor
-   ```
-
-3. **Check agent-specific setup:**
-   - Codex requires `CODEX_HOME` environment variable
-   - Some agents need workspace restart or cache clearing
-
-### "I lost my constitution customizations"
-
-**Fix:** Restore from git or backup:
-
-```bash
-# If you committed before upgrading
-git restore .specify/memory/constitution.md
-
-# If you backed up manually
-cp /tmp/constitution-backup.md .specify/memory/constitution.md
-```
-
-**Prevention:** Always commit or back up `constitution.md` before upgrading.
-
-### "Warning: Current directory is not empty"
-
-**Full warning message:**
-
-```text
-Warning: Current directory is not empty (25 items)
-Template files will be merged with existing content and may overwrite existing files
-Do you want to continue? [y/N]
-```
-
-**What this means:**
-
-This warning appears when you run `specify init --here` (or `specify init .`) in a directory that already has files. It's telling you:
-
-1. **The directory has existing content** - In the example, 25 files/folders
-2. **Files will be merged** - New template files will be added alongside your existing files
-3. **Some files may be overwritten** - If you already have Spec Kit files (`.claude/`, `.specify/`, etc.), they'll be replaced with the new versions
-
-**What gets overwritten:**
-
-Only Spec Kit infrastructure files:
-
-- Agent command files (`.claude/commands/`, `.github/prompts/`, etc.)
-- Scripts in `.specify/scripts/`
-- Templates in `.specify/templates/`
-- Memory files in `.specify/memory/` (including constitution)
-
-**What stays untouched:**
-
-- Your `specs/` directory (specifications, plans, tasks)
-- Your source code files
-- Your `.git/` directory and git history
-- Any other files not part of Spec Kit templates
-
-**How to respond:**
-
-- **Type `y` and press Enter** - Proceed with the merge (recommended if upgrading)
-- **Type `n` and press Enter** - Cancel the operation
-- **Use `--force` flag** - Skip this confirmation entirely:
-
-  ```bash
-  specify init --here --force --ai copilot
-  ```
-
-**When you see this warning:**
-
-- ✅ **Expected** when upgrading an existing Spec Kit project
-- ✅ **Expected** when adding Spec Kit to an existing codebase
-- ⚠️ **Unexpected** if you thought you were creating a new project in an empty directory
-
-**Prevention tip:** Before upgrading, commit or back up your `.specify/memory/constitution.md` if you customized it.
-
-### "CLI upgrade doesn't seem to work"
-
-Verify the installation:
-
-```bash
-# Check installed tools
-uv tool list
-
-# Should show specify-cli
-
-# Verify path
-which specify
-
-# Should point to the uv tool installation directory
-```
-
-If not found, reinstall:
-
-```bash
-uv tool uninstall specify-cli
-uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
-```
-
-### "Do I need to run specify every time I open my project?"
-
-**Short answer:** No, you only run `specify init` once per project (or when upgrading).
-
-**Explanation:**
-
-The `specify` CLI tool is used for:
-
-- **Initial setup:** `specify init` to bootstrap Spec Kit in your project
-- **Upgrades:** `specify init --here --force` to update templates and commands
-- **Diagnostics:** `specify check` to verify tool installation
-
-Once you've run `specify init`, the slash commands (like `/speckit.specify`, `/speckit.plan`, etc.) are **permanently installed** in your project's agent folder (`.claude/`, `.github/prompts/`, etc.). Your AI assistant reads these command files directly—no need to run `specify` again.
-
-**If your agent isn't recognizing slash commands:**
-
-1. **Verify command files exist:**
-
-   ```bash
-   # For GitHub Copilot
-   ls -la .github/prompts/
-
-   # For Claude
-   ls -la .claude/commands/
-   ```
-
-2. **Restart your IDE/editor completely** (not just reload window)
-
-3. **Check you're in the correct directory** where you ran `specify init`
-
-4. **For some agents**, you may need to reload the workspace or clear cache
-
-**Related issue:** If Copilot can't open local files or uses PowerShell commands unexpectedly, this is typically an IDE context issue, not related to `specify`. Try:
-
-- Restarting VS Code
-- Checking file permissions
-- Ensuring the workspace folder is properly opened
-
----
-
-## Version Compatibility
-
-Spec Kit follows semantic versioning for major releases. The CLI and project files are designed to be compatible within the same major version.
-
-**Best practice:** Keep both CLI and project files in sync by upgrading both together during major version changes.
-
----
-
-## Next Steps
-
-After upgrading:
-
-- **Test new slash commands:** Run `/speckit.constitution` or another command to verify everything works
-- **Review release notes:** Check [GitHub Releases](https://github.com/github/spec-kit/releases) for new features and breaking changes
-- **Update workflows:** If new commands were added, update your team's development workflows
-- **Check documentation:** Visit [github.io/spec-kit](https://github.github.io/spec-kit/) for updated guides

extensions/EXTENSION-API-REFERENCE.md

@@ -1,816 +0,0 @@
-# Extension API Reference
-
-Technical reference for Spec Kit extension system APIs and manifest schema.
-
-## Table of Contents
-
-1. [Extension Manifest](#extension-manifest)
-2. [Python API](#python-api)
-3. [Command File Format](#command-file-format)
-4. [Configuration Schema](#configuration-schema)
-5. [Hook System](#hook-system)
-6. [CLI Commands](#cli-commands)
-
----
-
-## Extension Manifest
-
-### Schema Version 1.0
-
-File: `extension.yml`
-
-```yaml
-schema_version: "1.0"  # Required
-
-extension:
-  id: string           # Required, pattern: ^[a-z0-9-]+$
-  name: string         # Required, human-readable name
-  version: string      # Required, semantic version (X.Y.Z)
-  description: string  # Required, brief description (<200 chars)
-  author: string       # Required
-  repository: string   # Required, valid URL
-  license: string      # Required (e.g., "MIT", "Apache-2.0")
-  homepage: string     # Optional, valid URL
-
-requires:
-  speckit_version: string  # Required, version specifier (>=X.Y.Z)
-  tools:                   # Optional, array of tool requirements
-    - name: string         # Tool name
-      version: string      # Optional, version specifier
-      required: boolean    # Optional, default: false
-
-provides:
-  commands:              # Required, at least one command
-    - name: string       # Required, pattern: ^speckit\.[a-z0-9-]+\.[a-z0-9-]+$
-      file: string       # Required, relative path to command file
-      description: string # Required
-      aliases: [string]  # Optional, array of alternate names
-
-  config:                # Optional, array of config files
-    - name: string       # Config file name
-      template: string   # Template file path
-      description: string
-      required: boolean  # Default: false
-
-hooks:                   # Optional, event hooks
-  event_name:            # e.g., "after_tasks", "after_implement"
-    command: string      # Command to execute
-    optional: boolean    # Default: true
-    prompt: string       # Prompt text for optional hooks
-    description: string  # Hook description
-    condition: string    # Optional, condition expression
-
-tags:                    # Optional, array of tags (2-10 recommended)
-  - string
-
-defaults:                # Optional, default configuration values
-  key: value             # Any YAML structure
-```
-
-### Field Specifications
-
-#### `extension.id`
-
-- **Type**: string
-- **Pattern**: `^[a-z0-9-]+$`
-- **Description**: Unique extension identifier
-- **Examples**: `jira`, `linear`, `azure-devops`
-- **Invalid**: `Jira`, `my_extension`, `extension.id`
-
-#### `extension.version`
-
-- **Type**: string
-- **Format**: Semantic versioning (X.Y.Z)
-- **Description**: Extension version
-- **Examples**: `1.0.0`, `0.9.5`, `2.1.3`
-- **Invalid**: `v1.0`, `1.0`, `1.0.0-beta`
-
-#### `requires.speckit_version`
-
-- **Type**: string
-- **Format**: Version specifier
-- **Description**: Required spec-kit version range
-- **Examples**:
-  - `>=0.1.0` - Any version 0.1.0 or higher
-  - `>=0.1.0,<2.0.0` - Version 0.1.x or 1.x
-  - `==0.1.0` - Exactly 0.1.0
-- **Invalid**: `0.1.0`, `>= 0.1.0` (space), `latest`
-
-#### `provides.commands[].name`
-
-- **Type**: string
-- **Pattern**: `^speckit\.[a-z0-9-]+\.[a-z0-9-]+$`
-- **Description**: Namespaced command name
-- **Format**:  `speckit.{extension-id}.{command-name}`
-- **Examples**: `speckit.jira.specstoissues`, `speckit.linear.sync`
-- **Invalid**: `jira.specstoissues`, `speckit.command`, `speckit.jira.CreateIssues`
-
-#### `hooks`
-
-- **Type**: object
-- **Keys**: Event names (e.g., `after_tasks`, `after_implement`, `before_commit`)
-- **Description**: Hooks that execute at lifecycle events
-- **Events**: Defined by core spec-kit commands
-
----
-
-## Python API
-
-### ExtensionManifest
-
-**Module**: `specify_cli.extensions`
-
-```python
-from specify_cli.extensions import ExtensionManifest
-
-manifest = ExtensionManifest(Path("extension.yml"))
-```
-
-**Properties**:
-
-```python
-manifest.id                        # str: Extension ID
-manifest.name                      # str: Extension name
-manifest.version                   # str: Version
-manifest.description               # str: Description
-manifest.requires_speckit_version  # str: Required spec-kit version
-manifest.commands                  # List[Dict]: Command definitions
-manifest.hooks                     # Dict: Hook definitions
-```
-
-**Methods**:
-
-```python
-manifest.get_hash()  # str: SHA256 hash of manifest file
-```
-
-**Exceptions**:
-
-```python
-ValidationError       # Invalid manifest structure
-CompatibilityError    # Incompatible with current spec-kit version
-```
-
-### ExtensionRegistry
-
-**Module**: `specify_cli.extensions`
-
-```python
-from specify_cli.extensions import ExtensionRegistry
-
-registry = ExtensionRegistry(extensions_dir)
-```
-
-**Methods**:
-
-```python
-# Add extension to registry
-registry.add(extension_id: str, metadata: dict)
-
-# Remove extension from registry
-registry.remove(extension_id: str)
-
-# Get extension metadata
-metadata = registry.get(extension_id: str)  # Optional[dict]
-
-# List all extensions
-extensions = registry.list()  # Dict[str, dict]
-
-# Check if installed
-is_installed = registry.is_installed(extension_id: str)  # bool
-```
-
-**Registry Format**:
-
-```json
-{
-  "schema_version": "1.0",
-  "extensions": {
-    "jira": {
-      "version": "1.0.0",
-      "source": "catalog",
-      "manifest_hash": "sha256...",
-      "enabled": true,
-      "registered_commands": ["speckit.jira.specstoissues", ...],
-      "installed_at": "2026-01-28T..."
-    }
-  }
-}
-```
-
-### ExtensionManager
-
-**Module**: `specify_cli.extensions`
-
-```python
-from specify_cli.extensions import ExtensionManager
-
-manager = ExtensionManager(project_root)
-```
-
-**Methods**:
-
-```python
-# Install from directory
-manifest = manager.install_from_directory(
-    source_dir: Path,
-    speckit_version: str,
-    register_commands: bool = True
-)  # Returns: ExtensionManifest
-
-# Install from ZIP
-manifest = manager.install_from_zip(
-    zip_path: Path,
-    speckit_version: str
-)  # Returns: ExtensionManifest
-
-# Remove extension
-success = manager.remove(
-    extension_id: str,
-    keep_config: bool = False
-)  # Returns: bool
-
-# List installed extensions
-extensions = manager.list_installed()  # List[Dict]
-
-# Get extension manifest
-manifest = manager.get_extension(extension_id: str)  # Optional[ExtensionManifest]
-
-# Check compatibility
-manager.check_compatibility(
-    manifest: ExtensionManifest,
-    speckit_version: str
-)  # Raises: CompatibilityError if incompatible
-```
-
-### CatalogEntry
-
-**Module**: `specify_cli.extensions`
-
-Represents a single catalog in the active catalog stack.
-
-```python
-from specify_cli.extensions import CatalogEntry
-
-entry = CatalogEntry(
-    url="https://example.com/catalog.json",
-    name="default",
-    priority=1,
-    install_allowed=True,
-    description="Built-in catalog of installable extensions",
-)
-```
-
-**Fields**:
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `url` | `str` | Catalog URL (must use HTTPS, or HTTP for localhost) |
-| `name` | `str` | Human-readable catalog name |
-| `priority` | `int` | Sort order (lower = higher priority, wins on conflicts) |
-| `install_allowed` | `bool` | Whether extensions from this catalog can be installed |
-| `description` | `str` | Optional human-readable description of the catalog (default: empty) |
-
-### ExtensionCatalog
-
-**Module**: `specify_cli.extensions`
-
-```python
-from specify_cli.extensions import ExtensionCatalog
-
-catalog = ExtensionCatalog(project_root)
-```
-
-**Class attributes**:
-
-```python
-ExtensionCatalog.DEFAULT_CATALOG_URL    # default catalog URL
-ExtensionCatalog.COMMUNITY_CATALOG_URL  # community catalog URL
-```
-
-**Methods**:
-
-```python
-# Get the ordered list of active catalogs
-entries = catalog.get_active_catalogs()  # List[CatalogEntry]
-
-# Fetch catalog (primary catalog, backward compat)
-catalog_data = catalog.fetch_catalog(force_refresh: bool = False)  # Dict
-
-# Search extensions across all active catalogs
-# Each result includes _catalog_name and _install_allowed
-results = catalog.search(
-    query: Optional[str] = None,
-    tag: Optional[str] = None,
-    author: Optional[str] = None,
-    verified_only: bool = False
-)  # Returns: List[Dict]  — each dict includes _catalog_name, _install_allowed
-
-# Get extension info (searches all active catalogs)
-# Returns None if not found; includes _catalog_name and _install_allowed
-ext_info = catalog.get_extension_info(extension_id: str)  # Optional[Dict]
-
-# Check cache validity (primary catalog)
-is_valid = catalog.is_cache_valid()  # bool
-
-# Clear all catalog caches
-catalog.clear_cache()
-```
-
-**Result annotation fields**:
-
-Each extension dict returned by `search()` and `get_extension_info()` includes:
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `_catalog_name` | `str` | Name of the source catalog |
-| `_install_allowed` | `bool` | Whether installation is allowed from this catalog |
-
-**Catalog config file** (`.specify/extension-catalogs.yml`):
-
-```yaml
-catalogs:
-  - name: "default"
-    url: "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.json"
-    priority: 1
-    install_allowed: true
-    description: "Built-in catalog of installable extensions"
-  - name: "community"
-    url: "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.community.json"
-    priority: 2
-    install_allowed: false
-    description: "Community-contributed extensions (discovery only)"
-```
-
-### HookExecutor
-
-**Module**: `specify_cli.extensions`
-
-```python
-from specify_cli.extensions import HookExecutor
-
-hook_executor = HookExecutor(project_root)
-```
-
-**Methods**:
-
-```python
-# Get project config
-config = hook_executor.get_project_config()  # Dict
-
-# Save project config
-hook_executor.save_project_config(config: Dict)
-
-# Register hooks
-hook_executor.register_hooks(manifest: ExtensionManifest)
-
-# Unregister hooks
-hook_executor.unregister_hooks(extension_id: str)
-
-# Get hooks for event
-hooks = hook_executor.get_hooks_for_event(event_name: str)  # List[Dict]
-
-# Check if hook should execute
-should_run = hook_executor.should_execute_hook(hook: Dict)  # bool
-
-# Format hook message
-message = hook_executor.format_hook_message(
-    event_name: str,
-    hooks: List[Dict]
-)  # str
-```
-
-### CommandRegistrar
-
-**Module**: `specify_cli.extensions`
-
-```python
-from specify_cli.extensions import CommandRegistrar
-
-registrar = CommandRegistrar()
-```
-
-**Methods**:
-
-```python
-# Register commands for Claude Code
-registered = registrar.register_commands_for_claude(
-    manifest: ExtensionManifest,
-    extension_dir: Path,
-    project_root: Path
-)  # Returns: List[str] (command names)
-
-# Parse frontmatter
-frontmatter, body = registrar.parse_frontmatter(content: str)
-
-# Render frontmatter
-yaml_text = registrar.render_frontmatter(frontmatter: Dict)  # str
-```
-
----
-
-## Command File Format
-
-### Universal Command Format
-
-**File**: `commands/{command-name}.md`
-
-```markdown
----
-description: "Command description"
-tools:
-  - 'mcp-server/tool_name'
-  - 'other-mcp-server/other_tool'
----
-
-# Command Title
-
-Command documentation in Markdown.
-
-## Prerequisites
-
-1. Requirement 1
-2. Requirement 2
-
-## User Input
-
-$ARGUMENTS
-
-## Steps
-
-### Step 1: Description
-
-Instruction text...
-
-\`\`\`bash
-# Shell commands
-\`\`\`
-
-### Step 2: Another Step
-
-More instructions...
-
-## Configuration Reference
-
-Information about configuration options.
-
-## Notes
-
-Additional notes and tips.
-```
-
-### Frontmatter Fields
-
-```yaml
-description: string   # Required, brief command description
-tools: [string]       # Optional, MCP tools required
-```
-
-### Special Variables
-
-- `$ARGUMENTS` - Placeholder for user-provided arguments
-- Extension context automatically injected:
-
-  ```markdown
-  <!-- Extension: {extension-id} -->
-  <!-- Config: .specify/extensions/{extension-id}/ -->
-  ```
-
----
-
-## Configuration Schema
-
-### Extension Config File
-
-**File**: `.specify/extensions/{extension-id}/{extension-id}-config.yml`
-
-Extensions define their own config schema. Common patterns:
-
-```yaml
-# Connection settings
-connection:
-  url: string
-  api_key: string
-
-# Project settings
-project:
-  key: string
-  workspace: string
-
-# Feature flags
-features:
-  enabled: boolean
-  auto_sync: boolean
-
-# Defaults
-defaults:
-  labels: [string]
-  assignee: string
-
-# Custom fields
-field_mappings:
-  internal_name: "external_field_id"
-```
-
-### Config Layers
-
-1. **Extension Defaults** (from `extension.yml` `defaults` section)
-2. **Project Config** (`{extension-id}-config.yml`)
-3. **Local Override** (`{extension-id}-config.local.yml`, gitignored)
-4. **Environment Variables** (`SPECKIT_{EXTENSION}_*`)
-
-### Environment Variable Pattern
-
-Format: `SPECKIT_{EXTENSION}_{KEY}`
-
-Examples:
-
-- `SPECKIT_JIRA_PROJECT_KEY`
-- `SPECKIT_LINEAR_API_KEY`
-- `SPECKIT_GITHUB_TOKEN`
-
----
-
-## Hook System
-
-### Hook Definition
-
-**In extension.yml**:
-
-```yaml
-hooks:
-  after_tasks:
-    command: "speckit.jira.specstoissues"
-    optional: true
-    prompt: "Create Jira issues from tasks?"
-    description: "Automatically create Jira hierarchy"
-    condition: null
-```
-
-### Hook Events
-
-Standard events (defined by core):
-
-- `after_tasks` - After task generation
-- `after_implement` - After implementation
-- `before_commit` - Before git commit
-- `after_commit` - After git commit
-
-### Hook Configuration
-
-**In `.specify/extensions.yml`**:
-
-```yaml
-hooks:
-  after_tasks:
-    - extension: jira
-      command: speckit.jira.specstoissues
-      enabled: true
-      optional: true
-      prompt: "Create Jira issues from tasks?"
-      description: "..."
-      condition: null
-```
-
-### Hook Message Format
-
-```markdown
-## Extension Hooks
-
-**Optional Hook**: {extension}
-Command: `/{command}`
-Description: {description}
-
-Prompt: {prompt}
-To execute: `/{command}`
-```
-
-Or for mandatory hooks:
-
-```markdown
-**Automatic Hook**: {extension}
-Executing: `/{command}`
-EXECUTE_COMMAND: {command}
-```
-
----
-
-## CLI Commands
-
-### extension list
-
-**Usage**: `specify extension list [OPTIONS]`
-
-**Options**:
-
-- `--available` - Show available extensions from catalog
-- `--all` - Show both installed and available
-
-**Output**: List of installed extensions with metadata
-
-### extension catalog list
-
-**Usage**: `specify extension catalog list`
-
-Lists all active catalogs in the current catalog stack, showing name, description, URL, priority, and `install_allowed` status.
-
-### extension catalog add
-
-**Usage**: `specify extension catalog add URL [OPTIONS]`
-
-**Options**:
-
-- `--name NAME` - Catalog name (required)
-- `--priority INT` - Priority (lower = higher priority, default: 10)
-- `--install-allowed / --no-install-allowed` - Allow installs from this catalog (default: false)
-- `--description TEXT` - Optional description of the catalog
-
-**Arguments**:
-
-- `URL` - Catalog URL (must use HTTPS)
-
-Adds a catalog entry to `.specify/extension-catalogs.yml`.
-
-### extension catalog remove
-
-**Usage**: `specify extension catalog remove NAME`
-
-**Arguments**:
-
-- `NAME` - Catalog name to remove
-
-Removes a catalog entry from `.specify/extension-catalogs.yml`.
-
-### extension add
-
-**Usage**: `specify extension add EXTENSION [OPTIONS]`
-
-**Options**:
-
-- `--from URL` - Install from custom URL
-- `--dev PATH` - Install from local directory
-
-**Arguments**:
-
-- `EXTENSION` - Extension name or URL
-
-**Note**: Extensions from catalogs with `install_allowed: false` cannot be installed via this command.
-
-### extension remove
-
-**Usage**: `specify extension remove EXTENSION [OPTIONS]`
-
-**Options**:
-
-- `--keep-config` - Preserve config files
-- `--force` - Skip confirmation
-
-**Arguments**:
-
-- `EXTENSION` - Extension ID
-
-### extension search
-
-**Usage**: `specify extension search [QUERY] [OPTIONS]`
-
-Searches all active catalogs simultaneously. Results include source catalog name and install_allowed status.
-
-**Options**:
-
-- `--tag TAG` - Filter by tag
-- `--author AUTHOR` - Filter by author
-- `--verified` - Show only verified extensions
-
-**Arguments**:
-
-- `QUERY` - Optional search query
-
-### extension info
-
-**Usage**: `specify extension info EXTENSION`
-
-Shows source catalog and install_allowed status.
-
-**Arguments**:
-
-- `EXTENSION` - Extension ID
-
-### extension update
-
-**Usage**: `specify extension update [EXTENSION]`
-
-**Arguments**:
-
-- `EXTENSION` - Optional, extension ID (default: all)
-
-### extension enable
-
-**Usage**: `specify extension enable EXTENSION`
-
-**Arguments**:
-
-- `EXTENSION` - Extension ID
-
-### extension disable
-
-**Usage**: `specify extension disable EXTENSION`
-
-**Arguments**:
-
-- `EXTENSION` - Extension ID
-
----
-
-## Exceptions
-
-### ValidationError
-
-Raised when extension manifest validation fails.
-
-```python
-from specify_cli.extensions import ValidationError
-
-try:
-    manifest = ExtensionManifest(path)
-except ValidationError as e:
-    print(f"Invalid manifest: {e}")
-```
-
-### CompatibilityError
-
-Raised when extension is incompatible with current spec-kit version.
-
-```python
-from specify_cli.extensions import CompatibilityError
-
-try:
-    manager.check_compatibility(manifest, "0.1.0")
-except CompatibilityError as e:
-    print(f"Incompatible: {e}")
-```
-
-### ExtensionError
-
-Base exception for all extension-related errors.
-
-```python
-from specify_cli.extensions import ExtensionError
-
-try:
-    manager.install_from_directory(path, "0.1.0")
-except ExtensionError as e:
-    print(f"Extension error: {e}")
-```
-
----
-
-## Version Functions
-
-### version_satisfies
-
-Check if a version satisfies a specifier.
-
-```python
-from specify_cli.extensions import version_satisfies
-
-# True if 1.2.3 satisfies >=1.0.0,<2.0.0
-satisfied = version_satisfies("1.2.3", ">=1.0.0,<2.0.0")  # bool
-```
-
----
-
-## File System Layout
-
-```text
-.specify/
-├── extensions/
-│   ├── .registry               # Extension registry (JSON)
-│   ├── .cache/                 # Catalog cache
-│   │   ├── catalog.json
-│   │   └── catalog-metadata.json
-│   ├── .backup/                # Config backups
-│   │   └── {ext}-{config}.yml
-│   ├── {extension-id}/         # Extension directory
-│   │   ├── extension.yml       # Manifest
-│   │   ├── {ext}-config.yml    # User config
-│   │   ├── {ext}-config.local.yml  # Local overrides (gitignored)
-│   │   ├── {ext}-config.template.yml  # Template
-│   │   ├── commands/           # Command files
-│   │   │   └── *.md
-│   │   ├── scripts/            # Helper scripts
-│   │   │   └── *.sh
-│   │   ├── docs/               # Documentation
-│   │   └── README.md
-│   └── extensions.yml          # Project extension config
-└── scripts/                    # (existing spec-kit)
-
-.claude/
-└── commands/
-    └── speckit.{ext}.{cmd}.md  # Registered commands
-```
-
----
-
-*Last Updated: 2026-01-28*
-*API Version: 1.0*
-*Spec Kit Version: 0.1.0*

extensions/EXTENSION-DEVELOPMENT-GUIDE.md

@@ -1,712 +0,0 @@
-# Extension Development Guide
-
-A guide for creating Spec Kit extensions.
-
----
-
-## Quick Start
-
-### 1. Create Extension Directory
-
-```bash
-mkdir my-extension
-cd my-extension
-```
-
-### 2. Create `extension.yml` Manifest
-
-```yaml
-schema_version: "1.0"
-
-extension:
-  id: "my-ext"                          # Lowercase, alphanumeric + hyphens only
-  name: "My Extension"
-  version: "1.0.0"                      # Semantic versioning
-  description: "My custom extension"
-  author: "Your Name"
-  repository: "https://github.com/you/spec-kit-my-ext"
-  license: "MIT"
-
-requires:
-  speckit_version: ">=0.1.0"            # Minimum spec-kit version
-  tools:                                # Optional: External tools required
-    - name: "my-tool"
-      required: true
-      version: ">=1.0.0"
-  commands:                             # Optional: Core commands needed
-    - "speckit.tasks"
-
-provides:
-  commands:
-    - name: "speckit.my-ext.hello"      # Must follow pattern: speckit.{ext-id}.{cmd}
-      file: "commands/hello.md"
-      description: "Say hello"
-      aliases: ["speckit.hello"]        # Optional aliases
-
-  config:                               # Optional: Config files
-    - name: "my-ext-config.yml"
-      template: "my-ext-config.template.yml"
-      description: "Extension configuration"
-      required: false
-
-hooks:                                  # Optional: Integration hooks
-  after_tasks:
-    command: "speckit.my-ext.hello"
-    optional: true
-    prompt: "Run hello command?"
-
-tags:                                   # Optional: For catalog search
-  - "example"
-  - "utility"
-```
-
-### 3. Create Commands Directory
-
-```bash
-mkdir commands
-```
-
-### 4. Create Command File
-
-**File**: `commands/hello.md`
-
-```markdown
----
-description: "Say hello command"
-tools:                              # Optional: AI tools this command uses
-  - 'some-tool/function'
-scripts:                            # Optional: Helper scripts
-  sh: ../../scripts/bash/helper.sh
-  ps: ../../scripts/powershell/helper.ps1
----
-
-# Hello Command
-
-This command says hello!
-
-## User Input
-
-$ARGUMENTS
-
-## Steps
-
-1. Greet the user
-2. Show extension is working
-
-```bash
-echo "Hello from my extension!"
-echo "Arguments: $ARGUMENTS"
-```
-
-## Extension Configuration
-
-Load extension config from `.specify/extensions/my-ext/my-ext-config.yml`.
-
-### 5. Test Locally
-
-```bash
-cd /path/to/spec-kit-project
-specify extension add --dev /path/to/my-extension
-```
-
-### 6. Verify Installation
-
-```bash
-specify extension list
-
-# Should show:
-#  ✓ My Extension (v1.0.0)
-#     My custom extension
-#     Commands: 1 | Hooks: 1 | Status: Enabled
-```
-
-### 7. Test Command
-
-If using Claude:
-
-```bash
-claude
-> /speckit.my-ext.hello world
-```
-
-The command will be available in `.claude/commands/speckit.my-ext.hello.md`.
-
----
-
-## Manifest Schema Reference
-
-### Required Fields
-
-#### `schema_version`
-
-Extension manifest schema version. Currently: `"1.0"`
-
-#### `extension`
-
-Extension metadata block.
-
-**Required sub-fields**:
-
-- `id`: Extension identifier (lowercase, alphanumeric, hyphens)
-- `name`: Human-readable name
-- `version`: Semantic version (e.g., "1.0.0")
-- `description`: Short description
-
-**Optional sub-fields**:
-
-- `author`: Extension author
-- `repository`: Source code URL
-- `license`: SPDX license identifier
-- `homepage`: Extension homepage URL
-
-#### `requires`
-
-Compatibility requirements.
-
-**Required sub-fields**:
-
-- `speckit_version`: Semantic version specifier (e.g., ">=0.1.0,<2.0.0")
-
-**Optional sub-fields**:
-
-- `tools`: External tools required (array of tool objects)
-- `commands`: Core spec-kit commands needed (array of command names)
-- `scripts`: Core scripts required (array of script names)
-
-#### `provides`
-
-What the extension provides.
-
-**Required sub-fields**:
-
-- `commands`: Array of command objects (must have at least one)
-
-**Command object**:
-
-- `name`: Command name (must match `speckit.{ext-id}.{command}`)
-- `file`: Path to command file (relative to extension root)
-- `description`: Command description (optional)
-- `aliases`: Alternative command names (optional, array)
-
-### Optional Fields
-
-#### `hooks`
-
-Integration hooks for automatic execution.
-
-Available hook points:
-
-- `after_tasks`: After `/speckit.tasks` completes
-- `after_implement`: After `/speckit.implement` completes (future)
-
-Hook object:
-
-- `command`: Command to execute (must be in `provides.commands`)
-- `optional`: If true, prompt user before executing
-- `prompt`: Prompt text for optional hooks
-- `description`: Hook description
-- `condition`: Execution condition (future)
-
-#### `tags`
-
-Array of tags for catalog discovery.
-
-#### `defaults`
-
-Default extension configuration values.
-
-#### `config_schema`
-
-JSON Schema for validating extension configuration.
-
----
-
-## Command File Format
-
-### Frontmatter (YAML)
-
-```yaml
----
-description: "Command description"          # Required
-tools:                                      # Optional
-  - 'tool-name/function'
-scripts:                                    # Optional
-  sh: ../../scripts/bash/helper.sh
-  ps: ../../scripts/powershell/helper.ps1
----
-```
-
-### Body (Markdown)
-
-Use standard Markdown with special placeholders:
-
-- `$ARGUMENTS`: User-provided arguments
-- `{SCRIPT}`: Replaced with script path during registration
-
-**Example**:
-
-````markdown
-## Steps
-
-1. Parse arguments
-2. Execute logic
-
-```bash
-args="$ARGUMENTS"
-echo "Running with args: $args"
-```
-````
-
-### Script Path Rewriting
-
-Extension commands use relative paths that get rewritten during registration:
-
-**In extension**:
-
-```yaml
-scripts:
-  sh: ../../scripts/bash/helper.sh
-```
-
-**After registration**:
-
-```yaml
-scripts:
-  sh: .specify/scripts/bash/helper.sh
-```
-
-This allows scripts to reference core spec-kit scripts.
-
----
-
-## Configuration Files
-
-### Config Template
-
-**File**: `my-ext-config.template.yml`
-
-```yaml
-# My Extension Configuration
-# Copy this to my-ext-config.yml and customize
-
-# Example configuration
-api:
-  endpoint: "https://api.example.com"
-  timeout: 30
-
-features:
-  feature_a: true
-  feature_b: false
-
-credentials:
-  # DO NOT commit credentials!
-  # Use environment variables instead
-  api_key: "${MY_EXT_API_KEY}"
-```
-
-### Config Loading
-
-In your command, load config with layered precedence:
-
-1. Extension defaults (`extension.yml` → `defaults`)
-2. Project config (`.specify/extensions/my-ext/my-ext-config.yml`)
-3. Local overrides (`.specify/extensions/my-ext/my-ext-config.local.yml` - gitignored)
-4. Environment variables (`SPECKIT_MY_EXT_*`)
-
-**Example loading script**:
-
-```bash
-#!/usr/bin/env bash
-EXT_DIR=".specify/extensions/my-ext"
-
-# Load and merge config
-config=$(yq eval '.' "$EXT_DIR/my-ext-config.yml" -o=json)
-
-# Apply env overrides
-if [ -n "${SPECKIT_MY_EXT_API_KEY:-}" ]; then
-  config=$(echo "$config" | jq ".api.api_key = \"$SPECKIT_MY_EXT_API_KEY\"")
-fi
-
-echo "$config"
-```
-
----
-
-## Excluding Files with `.extensionignore`
-
-Extension authors can create a `.extensionignore` file in the extension root to exclude files and folders from being copied when a user installs the extension with `specify extension add`. This is useful for keeping development-only files (tests, CI configs, docs source, etc.) out of the installed copy.
-
-### Format
-
-The file uses `.gitignore`-compatible patterns (one per line), powered by the [`pathspec`](https://pypi.org/project/pathspec/) library:
-
-- Blank lines are ignored
-- Lines starting with `#` are comments
-- `*` matches anything **except** `/` (does not cross directory boundaries)
-- `**` matches zero or more directories (e.g., `docs/**/*.draft.md`)
-- `?` matches any single character except `/`
-- A trailing `/` restricts a pattern to directories only
-- Patterns containing `/` (other than a trailing slash) are anchored to the extension root
-- Patterns without `/` match at any depth in the tree
-- `!` negates a previously excluded pattern (re-includes a file)
-- Backslashes in patterns are normalised to forward slashes for cross-platform compatibility
-- The `.extensionignore` file itself is always excluded automatically
-
-### Example
-
-```gitignore
-# .extensionignore
-
-# Development files
-tests/
-.github/
-.gitignore
-
-# Build artifacts
-__pycache__/
-*.pyc
-dist/
-
-# Documentation source (keep only the built README)
-docs/
-CONTRIBUTING.md
-```
-
-### Pattern Matching
-
-| Pattern | Matches | Does NOT match |
-|---------|---------|----------------|
-| `*.pyc` | Any `.pyc` file in any directory | — |
-| `tests/` | The `tests` directory (and all its contents) | A file named `tests` |
-| `docs/*.draft.md` | `docs/api.draft.md` (directly inside `docs/`) | `docs/sub/api.draft.md` (nested) |
-| `.env` | The `.env` file at any level | — |
-| `!README.md` | Re-includes `README.md` even if matched by an earlier pattern | — |
-| `docs/**/*.draft.md` | `docs/api.draft.md`, `docs/sub/api.draft.md` | — |
-
-### Unsupported Features
-
-The following `.gitignore` features are **not applicable** in this context:
-
-- **Multiple `.extensionignore` files**: Only a single file at the extension root is supported (`.gitignore` supports files in subdirectories)
-- **`$GIT_DIR/info/exclude` and `core.excludesFile`**: These are Git-specific and have no equivalent here
-- **Negation inside excluded directories**: Because file copying uses `shutil.copytree`, excluding a directory prevents recursion into it entirely. A negation pattern cannot re-include a file inside a directory that was itself excluded. For example, the combination `tests/` followed by `!tests/important.py` will **not** preserve `tests/important.py` — the `tests/` directory is skipped at the root level and its contents are never evaluated. To work around this, exclude the directory's contents individually instead of the directory itself (e.g., `tests/*.pyc` and `tests/.cache/` rather than `tests/`).
-
----
-
-## Validation Rules
-
-### Extension ID
-
-- **Pattern**: `^[a-z0-9-]+$`
-- **Valid**: `my-ext`, `tool-123`, `awesome-plugin`
-- **Invalid**: `MyExt` (uppercase), `my_ext` (underscore), `my ext` (space)
-
-### Extension Version
-
-- **Format**: Semantic versioning (MAJOR.MINOR.PATCH)
-- **Valid**: `1.0.0`, `0.1.0`, `2.5.3`
-- **Invalid**: `1.0`, `v1.0.0`, `1.0.0-beta`
-
-### Command Name
-
-- **Pattern**: `^speckit\.[a-z0-9-]+\.[a-z0-9-]+$`
-- **Valid**: `speckit.my-ext.hello`, `speckit.tool.cmd`
-- **Invalid**: `my-ext.hello` (missing prefix), `speckit.hello` (no extension namespace)
-
-### Command File Path
-
-- **Must be** relative to extension root
-- **Valid**: `commands/hello.md`, `commands/subdir/cmd.md`
-- **Invalid**: `/absolute/path.md`, `../outside.md`
-
----
-
-## Testing Extensions
-
-### Manual Testing
-
-1. **Create test extension**
-2. **Install locally**:
-
-   ```bash
-   specify extension add --dev /path/to/extension
-   ```
-
-3. **Verify installation**:
-
-   ```bash
-   specify extension list
-   ```
-
-4. **Test commands** with your AI agent
-5. **Check command registration**:
-
-   ```bash
-   ls .claude/commands/speckit.my-ext.*
-   ```
-
-6. **Remove extension**:
-
-   ```bash
-   specify extension remove my-ext
-   ```
-
-### Automated Testing
-
-Create tests for your extension:
-
-```python
-# tests/test_my_extension.py
-import pytest
-from pathlib import Path
-from specify_cli.extensions import ExtensionManifest
-
-def test_manifest_valid():
-    """Test extension manifest is valid."""
-    manifest = ExtensionManifest(Path("extension.yml"))
-    assert manifest.id == "my-ext"
-    assert len(manifest.commands) >= 1
-
-def test_command_files_exist():
-    """Test all command files exist."""
-    manifest = ExtensionManifest(Path("extension.yml"))
-    for cmd in manifest.commands:
-        cmd_file = Path(cmd["file"])
-        assert cmd_file.exists(), f"Command file not found: {cmd_file}"
-```
-
----
-
-## Distribution
-
-### Option 1: GitHub Repository
-
-1. **Create repository**: `spec-kit-my-ext`
-2. **Add files**:
-
-   ```text
-   spec-kit-my-ext/
-   ├── extension.yml
-   ├── commands/
-   ├── scripts/
-   ├── docs/
-   ├── README.md
-   ├── LICENSE
-   └── CHANGELOG.md
-   ```
-
-3. **Create release**: Tag with version (e.g., `v1.0.0`)
-4. **Install from repo**:
-
-   ```bash
-   git clone https://github.com/you/spec-kit-my-ext
-   specify extension add --dev spec-kit-my-ext/
-   ```
-
-### Option 2: ZIP Archive (Future)
-
-Create ZIP archive and host on GitHub Releases:
-
-```bash
-zip -r spec-kit-my-ext-1.0.0.zip extension.yml commands/ scripts/ docs/
-```
-
-Users install with:
-
-```bash
-specify extension add --from https://github.com/.../spec-kit-my-ext-1.0.0.zip
-```
-
-### Option 3: Community Reference Catalog
-
-Submit to the community catalog for public discovery:
-
-1. **Fork** spec-kit repository
-2. **Add entry** to `extensions/catalog.community.json`
-3. **Update** `extensions/README.md` with your extension
-4. **Create PR** following the [Extension Publishing Guide](EXTENSION-PUBLISHING-GUIDE.md)
-5. **After merge**, your extension becomes available:
-   - Users can browse `catalog.community.json` to discover your extension
-   - Users copy the entry to their own `catalog.json`
-   - Users install with: `specify extension add my-ext` (from their catalog)
-
-See the [Extension Publishing Guide](EXTENSION-PUBLISHING-GUIDE.md) for detailed submission instructions.
-
----
-
-## Best Practices
-
-### Naming Conventions
-
-- **Extension ID**: Use descriptive, hyphenated names (`jira-integration`, not `ji`)
-- **Commands**: Use verb-noun pattern (`create-issue`, `sync-status`)
-- **Config files**: Match extension ID (`jira-config.yml`)
-
-### Documentation
-
-- **README.md**: Overview, installation, usage
-- **CHANGELOG.md**: Version history
-- **docs/**: Detailed guides
-- **Command descriptions**: Clear, concise
-
-### Versioning
-
-- **Follow SemVer**: `MAJOR.MINOR.PATCH`
-- **MAJOR**: Breaking changes
-- **MINOR**: New features
-- **PATCH**: Bug fixes
-
-### Security
-
-- **Never commit secrets**: Use environment variables
-- **Validate input**: Sanitize user arguments
-- **Document permissions**: What files/APIs are accessed
-
-### Compatibility
-
-- **Specify version range**: Don't require exact version
-- **Test with multiple versions**: Ensure compatibility
-- **Graceful degradation**: Handle missing features
-
----
-
-## Example Extensions
-
-### Minimal Extension
-
-Smallest possible extension:
-
-```yaml
-# extension.yml
-schema_version: "1.0"
-extension:
-  id: "minimal"
-  name: "Minimal Extension"
-  version: "1.0.0"
-  description: "Minimal example"
-requires:
-  speckit_version: ">=0.1.0"
-provides:
-  commands:
-    - name: "speckit.minimal.hello"
-      file: "commands/hello.md"
-```
-
-````markdown
-<!-- commands/hello.md -->
----
-description: "Hello command"
----
-
-# Hello World
-
-```bash
-echo "Hello, $ARGUMENTS!"
-```
-````
-
-### Extension with Config
-
-Extension using configuration:
-
-```yaml
-# extension.yml
-# ... metadata ...
-provides:
-  config:
-    - name: "tool-config.yml"
-      template: "tool-config.template.yml"
-      required: true
-```
-
-```yaml
-# tool-config.template.yml
-api_endpoint: "https://api.example.com"
-timeout: 30
-```
-
-````markdown
-<!-- commands/use-config.md -->
-# Use Config
-
-Load config:
-```bash
-config_file=".specify/extensions/tool/tool-config.yml"
-endpoint=$(yq eval '.api_endpoint' "$config_file")
-echo "Using endpoint: $endpoint"
-```
-````
-
-### Extension with Hooks
-
-Extension that runs automatically:
-
-```yaml
-# extension.yml
-hooks:
-  after_tasks:
-    command: "speckit.auto.analyze"
-    optional: false  # Always run
-    description: "Analyze tasks after generation"
-```
-
----
-
-## Troubleshooting
-
-### Extension won't install
-
-**Error**: `Invalid extension ID`
-
-- **Fix**: Use lowercase, alphanumeric + hyphens only
-
-**Error**: `Extension requires spec-kit >=0.2.0`
-
-- **Fix**: Update spec-kit with `uv tool install specify-cli --force`
-
-**Error**: `Command file not found`
-
-- **Fix**: Ensure command files exist at paths specified in manifest
-
-### Commands not registered
-
-**Symptom**: Commands don't appear in AI agent
-
-**Check**:
-
-1. `.claude/commands/` directory exists
-2. Extension installed successfully
-3. Commands registered in registry:
-
-   ```bash
-   cat .specify/extensions/.registry
-   ```
-
-**Fix**: Reinstall extension to trigger registration
-
-### Config not loading
-
-**Check**:
-
-1. Config file exists: `.specify/extensions/{ext-id}/{ext-id}-config.yml`
-2. YAML syntax is valid: `yq eval '.' config.yml`
-3. Environment variables set correctly
-
----
-
-## Getting Help
-
-- **Issues**: Report bugs at GitHub repository
-- **Discussions**: Ask questions in GitHub Discussions
-- **Examples**: See `spec-kit-jira` for full-featured example (Phase B)
-
----
-
-## Next Steps
-
-1. **Create your extension** following this guide
-2. **Test locally** with `--dev` flag
-3. **Share with community** (GitHub, catalog)
-4. **Iterate** based on feedback
-
-Happy extending! 🚀

extensions/EXTENSION-PUBLISHING-GUIDE.md

@@ -1,548 +0,0 @@
-# Extension Publishing Guide
-
-This guide explains how to publish your extension to the Spec Kit extension catalog, making it discoverable by `specify extension search`.
-
-## Table of Contents
-
-1. [Prerequisites](#prerequisites)
-2. [Prepare Your Extension](#prepare-your-extension)
-3. [Submit to Catalog](#submit-to-catalog)
-4. [Verification Process](#verification-process)
-5. [Release Workflow](#release-workflow)
-6. [Best Practices](#best-practices)
-
----
-
-## Prerequisites
-
-Before publishing an extension, ensure you have:
-
-1. **Valid Extension**: A working extension with a valid `extension.yml` manifest
-2. **Git Repository**: Extension hosted on GitHub (or other public git hosting)
-3. **Documentation**: README.md with installation and usage instructions
-4. **License**: Open source license file (MIT, Apache 2.0, etc.)
-5. **Versioning**: Semantic versioning (e.g., 1.0.0)
-6. **Testing**: Extension tested on real projects
-
----
-
-## Prepare Your Extension
-
-### 1. Extension Structure
-
-Ensure your extension follows the standard structure:
-
-```text
-your-extension/
-├── extension.yml              # Required: Extension manifest
-├── README.md                  # Required: Documentation
-├── LICENSE                    # Required: License file
-├── CHANGELOG.md               # Recommended: Version history
-├── .gitignore                 # Recommended: Git ignore rules
-│
-├── commands/                  # Extension commands
-│   ├── command1.md
-│   └── command2.md
-│
-├── config-template.yml        # Config template (if needed)
-│
-└── docs/                      # Additional documentation
-    ├── usage.md
-    └── examples/
-```
-
-### 2. extension.yml Validation
-
-Verify your manifest is valid:
-
-```yaml
-schema_version: "1.0"
-
-extension:
-  id: "your-extension"           # Unique lowercase-hyphenated ID
-  name: "Your Extension Name"     # Human-readable name
-  version: "1.0.0"                # Semantic version
-  description: "Brief description (one sentence)"
-  author: "Your Name or Organization"
-  repository: "https://github.com/your-org/spec-kit-your-extension"
-  license: "MIT"
-  homepage: "https://github.com/your-org/spec-kit-your-extension"
-
-requires:
-  speckit_version: ">=0.1.0"    # Required spec-kit version
-
-provides:
-  commands:                       # List all commands
-    - name: "speckit.your-extension.command"
-      file: "commands/command.md"
-      description: "Command description"
-
-tags:                             # 2-5 relevant tags
-  - "category"
-  - "tool-name"
-```
-
-**Validation Checklist**:
-
-- ✅ `id` is lowercase with hyphens only (no underscores, spaces, or special characters)
-- ✅ `version` follows semantic versioning (X.Y.Z)
-- ✅ `description` is concise (under 100 characters)
-- ✅ `repository` URL is valid and public
-- ✅ All command files exist in the extension directory
-- ✅ Tags are lowercase and descriptive
-
-### 3. Create GitHub Release
-
-Create a GitHub release for your extension version:
-
-```bash
-# Tag the release
-git tag v1.0.0
-git push origin v1.0.0
-
-# Create release on GitHub
-# Go to: https://github.com/your-org/spec-kit-your-extension/releases/new
-# - Tag: v1.0.0
-# - Title: v1.0.0 - Release Name
-# - Description: Changelog/release notes
-```
-
-The release archive URL will be:
-
-```text
-https://github.com/your-org/spec-kit-your-extension/archive/refs/tags/v1.0.0.zip
-```
-
-### 4. Test Installation
-
-Test that users can install from your release:
-
-```bash
-# Test dev installation
-specify extension add --dev /path/to/your-extension
-
-# Test from GitHub archive
-specify extension add --from https://github.com/your-org/spec-kit-your-extension/archive/refs/tags/v1.0.0.zip
-```
-
----
-
-## Submit to Catalog
-
-### Understanding the Catalogs
-
-Spec Kit uses a dual-catalog system. For details about how catalogs work, see the main [Extensions README](README.md#extension-catalogs).
-
-**For extension publishing**: All community extensions should be added to `catalog.community.json`. Users browse this catalog and copy extensions they trust into their own `catalog.json`.
-
-### 1. Fork the spec-kit Repository
-
-```bash
-# Fork on GitHub
-# https://github.com/github/spec-kit/fork
-
-# Clone your fork
-git clone https://github.com/YOUR-USERNAME/spec-kit.git
-cd spec-kit
-```
-
-### 2. Add Extension to Community Catalog
-
-Edit `extensions/catalog.community.json` and add your extension:
-
-```json
-{
-  "schema_version": "1.0",
-  "updated_at": "2026-01-28T15:54:00Z",
-  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.community.json",
-  "extensions": {
-    "your-extension": {
-      "name": "Your Extension Name",
-      "id": "your-extension",
-      "description": "Brief description of your extension",
-      "author": "Your Name",
-      "version": "1.0.0",
-      "download_url": "https://github.com/your-org/spec-kit-your-extension/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/your-org/spec-kit-your-extension",
-      "homepage": "https://github.com/your-org/spec-kit-your-extension",
-      "documentation": "https://github.com/your-org/spec-kit-your-extension/blob/main/docs/",
-      "changelog": "https://github.com/your-org/spec-kit-your-extension/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          {
-            "name": "required-mcp-tool",
-            "version": ">=1.0.0",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 1
-      },
-      "tags": [
-        "category",
-        "tool-name",
-        "feature"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-01-28T00:00:00Z",
-      "updated_at": "2026-01-28T00:00:00Z"
-    }
-  }
-}
-```
-
-**Important**:
-
-- Set `verified: false` (maintainers will verify)
-- Set `downloads: 0` and `stars: 0` (auto-updated later)
-- Use current timestamp for `created_at` and `updated_at`
-- Update the top-level `updated_at` to current time
-
-### 3. Update Extensions README
-
-Add your extension to the Available Extensions table in `extensions/README.md`:
-
-```markdown
-| Your Extension Name | Brief description of what it does | [repo-name](https://github.com/your-org/spec-kit-your-extension) |
-```
-
-Insert your extension in alphabetical order in the table.
-
-### 4. Submit Pull Request
-
-```bash
-# Create a branch
-git checkout -b add-your-extension
-
-# Commit your changes
-git add extensions/catalog.community.json extensions/README.md
-git commit -m "Add your-extension to community catalog
-
-- Extension ID: your-extension
-- Version: 1.0.0
-- Author: Your Name
-- Description: Brief description
-"
-
-# Push to your fork
-git push origin add-your-extension
-
-# Create Pull Request on GitHub
-# https://github.com/github/spec-kit/compare
-```
-
-**Pull Request Template**:
-
-```markdown
-## Extension Submission
-
-**Extension Name**: Your Extension Name
-**Extension ID**: your-extension
-**Version**: 1.0.0
-**Author**: Your Name
-**Repository**: https://github.com/your-org/spec-kit-your-extension
-
-### Description
-Brief description of what your extension does.
-
-### Checklist
-- [x] Valid extension.yml manifest
-- [x] README.md with installation and usage docs
-- [x] LICENSE file included
-- [x] GitHub release created (v1.0.0)
-- [x] Extension tested on real project
-- [x] All commands working
-- [x] No security vulnerabilities
-- [x] Added to extensions/catalog.community.json
-- [x] Added to extensions/README.md Available Extensions table
-
-### Testing
-Tested on:
-- macOS 13.0+ with spec-kit 0.1.0
-- Project: [Your test project]
-
-### Additional Notes
-Any additional context or notes for reviewers.
-```
-
----
-
-## Verification Process
-
-### What Happens After Submission
-
-1. **Automated Checks** (if available):
-   - Manifest validation
-   - Download URL accessibility
-   - Repository existence
-   - License file presence
-
-2. **Manual Review**:
-   - Code quality review
-   - Security audit
-   - Functionality testing
-   - Documentation review
-
-3. **Verification**:
-   - If approved, `verified: true` is set
-   - Extension appears in `specify extension search --verified`
-
-### Verification Criteria
-
-To be verified, your extension must:
-
-✅ **Functionality**:
-
-- Works as described in documentation
-- All commands execute without errors
-- No breaking changes to user workflows
-
-✅ **Security**:
-
-- No known vulnerabilities
-- No malicious code
-- Safe handling of user data
-- Proper validation of inputs
-
-✅ **Code Quality**:
-
-- Clean, readable code
-- Follows extension best practices
-- Proper error handling
-- Helpful error messages
-
-✅ **Documentation**:
-
-- Clear installation instructions
-- Usage examples
-- Troubleshooting section
-- Accurate description
-
-✅ **Maintenance**:
-
-- Active repository
-- Responsive to issues
-- Regular updates
-- Semantic versioning followed
-
-### Typical Review Timeline
-
-- **Automated checks**: Immediate (if implemented)
-- **Manual review**: 3-7 business days
-- **Verification**: After successful review
-
----
-
-## Release Workflow
-
-### Publishing New Versions
-
-When releasing a new version:
-
-1. **Update version** in `extension.yml`:
-
-   ```yaml
-   extension:
-     version: "1.1.0"  # Updated version
-   ```
-
-2. **Update CHANGELOG.md**:
-
-   ```markdown
-   ## [1.1.0] - 2026-02-15
-
-   ### Added
-   - New feature X
-
-   ### Fixed
-   - Bug fix Y
-   ```
-
-3. **Create GitHub release**:
-
-   ```bash
-   git tag v1.1.0
-   git push origin v1.1.0
-   # Create release on GitHub
-   ```
-
-4. **Update catalog**:
-
-   ```bash
-   # Fork spec-kit repo (or update existing fork)
-   cd spec-kit
-
-   # Update extensions/catalog.json
-   jq '.extensions["your-extension"].version = "1.1.0"' extensions/catalog.json > tmp.json && mv tmp.json extensions/catalog.json
-   jq '.extensions["your-extension"].download_url = "https://github.com/your-org/spec-kit-your-extension/archive/refs/tags/v1.1.0.zip"' extensions/catalog.json > tmp.json && mv tmp.json extensions/catalog.json
-   jq '.extensions["your-extension"].updated_at = "2026-02-15T00:00:00Z"' extensions/catalog.json > tmp.json && mv tmp.json extensions/catalog.json
-   jq '.updated_at = "2026-02-15T00:00:00Z"' extensions/catalog.json > tmp.json && mv tmp.json extensions/catalog.json
-
-   # Submit PR
-   git checkout -b update-your-extension-v1.1.0
-   git add extensions/catalog.json
-   git commit -m "Update your-extension to v1.1.0"
-   git push origin update-your-extension-v1.1.0
-   ```
-
-5. **Submit update PR** with changelog in description
-
----
-
-## Best Practices
-
-### Extension Design
-
-1. **Single Responsibility**: Each extension should focus on one tool/integration
-2. **Clear Naming**: Use descriptive, unambiguous names
-3. **Minimal Dependencies**: Avoid unnecessary dependencies
-4. **Backward Compatibility**: Follow semantic versioning strictly
-
-### Documentation
-
-1. **README.md Structure**:
-   - Overview and features
-   - Installation instructions
-   - Configuration guide
-   - Usage examples
-   - Troubleshooting
-   - Contributing guidelines
-
-2. **Command Documentation**:
-   - Clear description
-   - Prerequisites listed
-   - Step-by-step instructions
-   - Error handling guidance
-   - Examples
-
-3. **Configuration**:
-   - Provide template file
-   - Document all options
-   - Include examples
-   - Explain defaults
-
-### Security
-
-1. **Input Validation**: Validate all user inputs
-2. **No Hardcoded Secrets**: Never include credentials
-3. **Safe Dependencies**: Only use trusted dependencies
-4. **Audit Regularly**: Check for vulnerabilities
-
-### Maintenance
-
-1. **Respond to Issues**: Address issues within 1-2 weeks
-2. **Regular Updates**: Keep dependencies updated
-3. **Changelog**: Maintain detailed changelog
-4. **Deprecation**: Give advance notice for breaking changes
-
-### Community
-
-1. **License**: Use permissive open-source license (MIT, Apache 2.0)
-2. **Contributing**: Welcome contributions
-3. **Code of Conduct**: Be respectful and inclusive
-4. **Support**: Provide ways to get help (issues, discussions, email)
-
----
-
-## FAQ
-
-### Q: Can I publish private/proprietary extensions?
-
-A: The main catalog is for public extensions only. For private extensions:
-
-- Host your own catalog.json file
-- Users add your catalog: `specify extension add-catalog https://your-domain.com/catalog.json`
-- Not yet implemented - coming in Phase 4
-
-### Q: How long does verification take?
-
-A: Typically 3-7 business days for initial review. Updates to verified extensions are usually faster.
-
-### Q: What if my extension is rejected?
-
-A: You'll receive feedback on what needs to be fixed. Make the changes and resubmit.
-
-### Q: Can I update my extension anytime?
-
-A: Yes, submit a PR to update the catalog with your new version. Verified status may be re-evaluated for major changes.
-
-### Q: Do I need to be verified to be in the catalog?
-
-A: No, unverified extensions are still searchable. Verification just adds trust and visibility.
-
-### Q: Can extensions have paid features?
-
-A: Extensions should be free and open-source. Commercial support/services are allowed, but core functionality must be free.
-
----
-
-## Support
-
-- **Catalog Issues**: <https://github.com/statsperform/spec-kit/issues>
-- **Extension Template**: <https://github.com/statsperform/spec-kit-extension-template> (coming soon)
-- **Development Guide**: See EXTENSION-DEVELOPMENT-GUIDE.md
-- **Community**: Discussions and Q&A
-
----
-
-## Appendix: Catalog Schema
-
-### Complete Catalog Entry Schema
-
-```json
-{
-  "name": "string (required)",
-  "id": "string (required, unique)",
-  "description": "string (required, <200 chars)",
-  "author": "string (required)",
-  "version": "string (required, semver)",
-  "download_url": "string (required, valid URL)",
-  "repository": "string (required, valid URL)",
-  "homepage": "string (optional, valid URL)",
-  "documentation": "string (optional, valid URL)",
-  "changelog": "string (optional, valid URL)",
-  "license": "string (required)",
-  "requires": {
-    "speckit_version": "string (required, version specifier)",
-    "tools": [
-      {
-        "name": "string (required)",
-        "version": "string (optional, version specifier)",
-        "required": "boolean (default: false)"
-      }
-    ]
-  },
-  "provides": {
-    "commands": "integer (optional)",
-    "hooks": "integer (optional)"
-  },
-  "tags": ["array of strings (2-10 tags)"],
-  "verified": "boolean (default: false)",
-  "downloads": "integer (auto-updated)",
-  "stars": "integer (auto-updated)",
-  "created_at": "string (ISO 8601 datetime)",
-  "updated_at": "string (ISO 8601 datetime)"
-}
-```
-
-### Valid Tags
-
-Recommended tag categories:
-
-- **Integration**: jira, linear, github, gitlab, azure-devops
-- **Category**: issue-tracking, vcs, ci-cd, documentation, testing
-- **Platform**: atlassian, microsoft, google
-- **Feature**: automation, reporting, deployment, monitoring
-
-Use 2-5 tags that best describe your extension.
-
----
-
-*Last Updated: 2026-01-28*
-*Catalog Format Version: 1.0*

extensions/EXTENSION-USER-GUIDE.md

@@ -1,970 +0,0 @@
-# Extension User Guide
-
-Complete guide for using Spec Kit extensions to enhance your workflow.
-
-## Table of Contents
-
-1. [Introduction](#introduction)
-2. [Getting Started](#getting-started)
-3. [Finding Extensions](#finding-extensions)
-4. [Installing Extensions](#installing-extensions)
-5. [Using Extensions](#using-extensions)
-6. [Managing Extensions](#managing-extensions)
-7. [Configuration](#configuration)
-8. [Troubleshooting](#troubleshooting)
-9. [Best Practices](#best-practices)
-
----
-
-## Introduction
-
-### What are Extensions?
-
-Extensions are modular packages that add new commands and functionality to Spec Kit without bloating the core framework. They allow you to:
-
-- **Integrate** with external tools (Jira, Linear, GitHub, etc.)
-- **Automate** repetitive tasks with hooks
-- **Customize** workflows for your team
-- **Share** solutions across projects
-
-### Why Use Extensions?
-
-- **Clean Core**: Keeps spec-kit lightweight and focused
-- **Optional Features**: Only install what you need
-- **Community Driven**: Anyone can create and share extensions
-- **Version Controlled**: Extensions are versioned independently
-
----
-
-## Getting Started
-
-### Prerequisites
-
-- Spec Kit version 0.1.0 or higher
-- A spec-kit project (directory with `.specify/` folder)
-
-### Check Your Version
-
-```bash
-specify version
-# Should show 0.1.0 or higher
-```
-
-### First Extension
-
-Let's install the Jira extension as an example:
-
-```bash
-# 1. Search for the extension
-specify extension search jira
-
-# 2. Get detailed information
-specify extension info jira
-
-# 3. Install it
-specify extension add jira
-
-# 4. Configure it
-vim .specify/extensions/jira/jira-config.yml
-
-# 5. Use it
-# (Commands are now available in Claude Code)
-/speckit.jira.specstoissues
-```
-
----
-
-## Finding Extensions
-
-`specify extension search` searches **all active catalogs** simultaneously, including the community catalog by default. Results are annotated with their source catalog and install status.
-
-### Browse All Extensions
-
-```bash
-specify extension search
-```
-
-Shows all extensions across all active catalogs (default and community by default).
-
-### Search by Keyword
-
-```bash
-# Search for "jira"
-specify extension search jira
-
-# Search for "issue tracking"
-specify extension search issue
-```
-
-### Filter by Tag
-
-```bash
-# Find all issue-tracking extensions
-specify extension search --tag issue-tracking
-
-# Find all Atlassian tools
-specify extension search --tag atlassian
-```
-
-### Filter by Author
-
-```bash
-# Extensions by Stats Perform
-specify extension search --author "Stats Perform"
-```
-
-### Show Verified Only
-
-```bash
-# Only show verified extensions
-specify extension search --verified
-```
-
-### Get Extension Details
-
-```bash
-# Detailed information
-specify extension info jira
-```
-
-Shows:
-
-- Description
-- Requirements
-- Commands provided
-- Hooks available
-- Links (documentation, repository, changelog)
-- Installation status
-
----
-
-## Installing Extensions
-
-### Install from Catalog
-
-```bash
-# By name (from catalog)
-specify extension add jira
-```
-
-This will:
-
-1. Download the extension from GitHub
-2. Validate the manifest
-3. Check compatibility with your spec-kit version
-4. Install to `.specify/extensions/jira/`
-5. Register commands with your AI agent
-6. Create config template
-
-### Install from URL
-
-```bash
-# From GitHub release
-specify extension add --from https://github.com/org/spec-kit-ext/archive/refs/tags/v1.0.0.zip
-```
-
-### Install from Local Directory (Development)
-
-```bash
-# For testing or development
-specify extension add --dev /path/to/extension
-```
-
-### Installation Output
-
-```text
-✓ Extension installed successfully!
-
-Jira Integration (v1.0.0)
-  Create Jira Epics, Stories, and Issues from spec-kit artifacts
-
-Provided commands:
-  • speckit.jira.specstoissues - Create Jira hierarchy from spec and tasks
-  • speckit.jira.discover-fields - Discover Jira custom fields for configuration
-  • speckit.jira.sync-status - Sync task completion status to Jira
-
-⚠  Configuration may be required
-   Check: .specify/extensions/jira/
-```
-
----
-
-## Using Extensions
-
-### Using Extension Commands
-
-Extensions add commands that appear in your AI agent (Claude Code):
-
-```text
-# In Claude Code
-> /speckit.jira.specstoissues
-
-# Or use short alias (if provided)
-> /speckit.specstoissues
-```
-
-### Extension Configuration
-
-Most extensions require configuration:
-
-```bash
-# 1. Find the config file
-ls .specify/extensions/jira/
-
-# 2. Copy template to config
-cp .specify/extensions/jira/jira-config.template.yml \
-   .specify/extensions/jira/jira-config.yml
-
-# 3. Edit configuration
-vim .specify/extensions/jira/jira-config.yml
-
-# 4. Use the extension
-# (Commands will now work with your config)
-```
-
-### Extension Hooks
-
-Some extensions provide hooks that execute after core commands:
-
-**Example**: Jira extension hooks into `/speckit.tasks`
-
-```text
-# Run core command
-> /speckit.tasks
-
-# Output includes:
-## Extension Hooks
-
-**Optional Hook**: jira
-Command: `/speckit.jira.specstoissues`
-Description: Automatically create Jira hierarchy after task generation
-
-Prompt: Create Jira issues from tasks?
-To execute: `/speckit.jira.specstoissues`
-```
-
-You can then choose to run the hook or skip it.
-
----
-
-## Managing Extensions
-
-### List Installed Extensions
-
-```bash
-specify extension list
-```
-
-Output:
-
-```text
-Installed Extensions:
-
-  ✓ Jira Integration (v1.0.0)
-     Create Jira Epics, Stories, and Issues from spec-kit artifacts
-     Commands: 3 | Hooks: 1 | Status: Enabled
-```
-
-### Update Extensions
-
-```bash
-# Check for updates (all extensions)
-specify extension update
-
-# Update specific extension
-specify extension update jira
-```
-
-Output:
-
-```text
-🔄 Checking for updates...
-
-Updates available:
-
-  • jira: 1.0.0 → 1.1.0
-
-Update these extensions? [y/N]:
-```
-
-### Disable Extension Temporarily
-
-```bash
-# Disable without removing
-specify extension disable jira
-
-✓ Extension 'jira' disabled
-
-Commands will no longer be available. Hooks will not execute.
-To re-enable: specify extension enable jira
-```
-
-### Re-enable Extension
-
-```bash
-specify extension enable jira
-
-✓ Extension 'jira' enabled
-```
-
-### Remove Extension
-
-```bash
-# Remove extension (with confirmation)
-specify extension remove jira
-
-# Keep configuration when removing
-specify extension remove jira --keep-config
-
-# Force removal (no confirmation)
-specify extension remove jira --force
-```
-
----
-
-## Configuration
-
-### Configuration Files
-
-Extensions can have multiple configuration files:
-
-```text
-.specify/extensions/jira/
-├── jira-config.yml           # Main config (version controlled)
-├── jira-config.local.yml     # Local overrides (gitignored)
-└── jira-config.template.yml  # Template (reference)
-```
-
-### Configuration Layers
-
-Configuration is merged in this order (highest priority last):
-
-1. **Extension defaults** (from `extension.yml`)
-2. **Project config** (`jira-config.yml`)
-3. **Local overrides** (`jira-config.local.yml`)
-4. **Environment variables** (`SPECKIT_JIRA_*`)
-
-### Example: Jira Configuration
-
-**Project config** (`.specify/extensions/jira/jira-config.yml`):
-
-```yaml
-project:
-  key: "MSATS"
-
-defaults:
-  epic:
-    labels: ["spec-driven"]
-```
-
-**Local override** (`.specify/extensions/jira/jira-config.local.yml`):
-
-```yaml
-project:
-  key: "MYTEST"  # Override for local development
-```
-
-**Environment variable**:
-
-```bash
-export SPECKIT_JIRA_PROJECT_KEY="DEVTEST"
-```
-
-Final resolved config uses `DEVTEST` from environment variable.
-
-### Project-Wide Extension Settings
-
-File: `.specify/extensions.yml`
-
-```yaml
-# Extensions installed in this project
-installed:
-  - jira
-  - linear
-
-# Global settings
-settings:
-  auto_execute_hooks: true
-
-# Hook configuration
-hooks:
-  after_tasks:
-    - extension: jira
-      command: speckit.jira.specstoissues
-      enabled: true
-      optional: true
-      prompt: "Create Jira issues from tasks?"
-```
-
-### Core Environment Variables
-
-In addition to extension-specific environment variables (`SPECKIT_{EXT_ID}_*`), spec-kit supports core environment variables:
-
-| Variable | Description | Default |
-|----------|-------------|---------|
-| `SPECKIT_CATALOG_URL`       | Override the full catalog stack with a single URL (backward compat) | Built-in default stack |
-| `GH_TOKEN` / `GITHUB_TOKEN` | GitHub API token for downloads     | None                  |
-
-#### Example: Using a custom catalog for testing
-
-```bash
-# Point to a local or alternative catalog (replaces the full stack)
-export SPECKIT_CATALOG_URL="http://localhost:8000/catalog.json"
-
-# Or use a staging catalog
-export SPECKIT_CATALOG_URL="https://example.com/staging/catalog.json"
-```
-
----
-
-## Extension Catalogs
-
-Spec Kit uses a **catalog stack** — an ordered list of catalogs searched simultaneously. By default, two catalogs are active:
-
-| Priority | Catalog | Install Allowed | Purpose |
-|----------|---------|-----------------|---------|
-| 1 | `catalog.json` (default) | ✅ Yes | Curated extensions available for installation |
-| 2 | `catalog.community.json` (community) | ❌ No (discovery only) | Browse community extensions |
-
-### Listing Active Catalogs
-
-```bash
-specify extension catalog list
-```
-
-### Adding a Catalog (Project-scoped)
-
-```bash
-# Add an internal catalog that allows installs
-specify extension catalog add \
-  --name "internal" \
-  --priority 2 \
-  --install-allowed \
-  https://internal.company.com/spec-kit/catalog.json
-
-# Add a discovery-only catalog
-specify extension catalog add \
-  --name "partner" \
-  --priority 5 \
-  https://partner.example.com/spec-kit/catalog.json
-```
-
-This creates or updates `.specify/extension-catalogs.yml`.
-
-### Removing a Catalog
-
-```bash
-specify extension catalog remove internal
-```
-
-### Manual Config File
-
-You can also edit `.specify/extension-catalogs.yml` directly:
-
-```yaml
-catalogs:
-  - name: "default"
-    url: "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.json"
-    priority: 1
-    install_allowed: true
-    description: "Built-in catalog of installable extensions"
-
-  - name: "internal"
-    url: "https://internal.company.com/spec-kit/catalog.json"
-    priority: 2
-    install_allowed: true
-    description: "Internal company extensions"
-
-  - name: "community"
-    url: "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.community.json"
-    priority: 3
-    install_allowed: false
-    description: "Community-contributed extensions (discovery only)"
-```
-
-A user-level equivalent lives at `~/.specify/extension-catalogs.yml`. Project-level config takes full precedence when it contains one or more catalog entries. An empty `catalogs: []` list falls back to built-in defaults.
-
-## Organization Catalog Customization
-
-### Why Customize Your Catalog
-
-Organizations customize their catalogs to:
-
-- **Control available extensions** - Curate which extensions your team can install
-- **Host private extensions** - Internal tools that shouldn't be public
-- **Customize for compliance** - Meet security/audit requirements
-- **Support air-gapped environments** - Work without internet access
-
-### Setting Up a Custom Catalog
-
-#### 1. Create Your Catalog File
-
-Create a `catalog.json` file with your extensions:
-
-```json
-{
-  "schema_version": "1.0",
-  "updated_at": "2026-02-03T00:00:00Z",
-  "catalog_url": "https://your-org.com/spec-kit/catalog.json",
-  "extensions": {
-    "jira": {
-      "name": "Jira Integration",
-      "id": "jira",
-      "description": "Create Jira issues from spec-kit artifacts",
-      "author": "Your Organization",
-      "version": "2.1.0",
-      "download_url": "https://github.com/your-org/spec-kit-jira/archive/refs/tags/v2.1.0.zip",
-      "repository": "https://github.com/your-org/spec-kit-jira",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          {"name": "atlassian-mcp-server", "required": true}
-        ]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 1
-      },
-      "tags": ["jira", "atlassian", "issue-tracking"],
-      "verified": true
-    },
-    "internal-tool": {
-      "name": "Internal Tool Integration",
-      "id": "internal-tool",
-      "description": "Connect to internal company systems",
-      "author": "Your Organization",
-      "version": "1.0.0",
-      "download_url": "https://internal.your-org.com/extensions/internal-tool-1.0.0.zip",
-      "repository": "https://github.internal.your-org.com/spec-kit-internal",
-      "license": "Proprietary",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 2
-      },
-      "tags": ["internal", "proprietary"],
-      "verified": true
-    }
-  }
-}
-```
-
-#### 2. Host the Catalog
-
-Options for hosting your catalog:
-
-| Method | URL Example | Use Case |
-| ------ | ----------- | -------- |
-| GitHub Pages | `https://your-org.github.io/spec-kit-catalog/catalog.json` | Public or org-visible |
-| Internal web server | `https://internal.company.com/spec-kit/catalog.json` | Corporate network |
-| S3/Cloud storage | `https://s3.amazonaws.com/your-bucket/catalog.json` | Cloud-hosted teams |
-| Local file server | `http://localhost:8000/catalog.json` | Development/testing |
-
-**Security requirement**: URLs must use HTTPS (except `localhost` for testing).
-
-#### 3. Configure Your Environment
-
-##### Option A: Catalog stack config file (recommended)
-
-Add to `.specify/extension-catalogs.yml` in your project:
-
-```yaml
-catalogs:
-  - name: "my-org"
-    url: "https://your-org.com/spec-kit/catalog.json"
-    priority: 1
-    install_allowed: true
-```
-
-Or use the CLI:
-
-```bash
-specify extension catalog add \
-  --name "my-org" \
-  --install-allowed \
-  https://your-org.com/spec-kit/catalog.json
-```
-
-##### Option B: Environment variable (recommended for CI/CD, single-catalog)
-
-```bash
-# In ~/.bashrc, ~/.zshrc, or CI pipeline
-export SPECKIT_CATALOG_URL="https://your-org.com/spec-kit/catalog.json"
-```
-
-#### 4. Verify Configuration
-
-```bash
-# List active catalogs
-specify extension catalog list
-
-# Search should now show your catalog's extensions
-specify extension search
-
-# Install from your catalog
-specify extension add jira
-```
-
-### Catalog JSON Schema
-
-Required fields for each extension entry:
-
-| Field | Type | Required | Description |
-| ----- | ---- | -------- | ----------- |
-| `name` | string | Yes | Human-readable name |
-| `id` | string | Yes | Unique identifier (lowercase, hyphens) |
-| `version` | string | Yes | Semantic version (X.Y.Z) |
-| `download_url` | string | Yes | URL to ZIP archive |
-| `repository` | string | Yes | Source code URL |
-| `description` | string | No | Brief description |
-| `author` | string | No | Author/organization |
-| `license` | string | No | SPDX license identifier |
-| `requires.speckit_version` | string | No | Version constraint |
-| `requires.tools` | array | No | Required external tools |
-| `provides.commands` | number | No | Number of commands |
-| `provides.hooks` | number | No | Number of hooks |
-| `tags` | array | No | Search tags |
-| `verified` | boolean | No | Verification status |
-
-### Use Cases
-
-#### Private/Internal Extensions
-
-Host proprietary extensions that integrate with internal systems:
-
-```json
-{
-  "internal-auth": {
-    "name": "Internal SSO Integration",
-    "download_url": "https://artifactory.company.com/spec-kit/internal-auth-1.0.0.zip",
-    "verified": true
-  }
-}
-```
-
-#### Curated Team Catalog
-
-Limit which extensions your team can install:
-
-```json
-{
-  "extensions": {
-    "jira": { "..." },
-    "github": { "..." }
-  }
-}
-```
-
-Only `jira` and `github` will appear in `specify extension search`.
-
-#### Air-Gapped Environments
-
-For networks without internet access:
-
-1. Download extension ZIPs to internal file server
-2. Create catalog pointing to internal URLs
-3. Host catalog on internal web server
-
-```json
-{
-  "jira": {
-    "download_url": "https://files.internal/spec-kit/jira-2.1.0.zip"
-  }
-}
-```
-
-#### Development/Testing
-
-Test new extensions before publishing:
-
-```bash
-# Start local server
-python -m http.server 8000 --directory ./my-catalog/
-
-# Point spec-kit to local catalog
-export SPECKIT_CATALOG_URL="http://localhost:8000/catalog.json"
-
-# Test installation
-specify extension add my-new-extension
-```
-
-### Combining with Direct Installation
-
-You can still install extensions not in your catalog using `--from`:
-
-```bash
-# From catalog
-specify extension add jira
-
-# Direct URL (bypasses catalog)
-specify extension add --from https://github.com/someone/spec-kit-ext/archive/v1.0.0.zip
-
-# Local development
-specify extension add --dev /path/to/extension
-```
-
-**Note**: Direct URL installation shows a security warning since the extension isn't from your configured catalog.
-
----
-
-## Troubleshooting
-
-### Extension Not Found
-
-**Error**: `Extension 'jira' not found in catalog
-
-**Solutions**:
-
-1. Check spelling: `specify extension search jira`
-2. Refresh catalog: `specify extension search --help`
-3. Check internet connection
-4. Extension may not be published yet
-
-### Configuration Not Found
-
-**Error**: `Jira configuration not found`
-
-**Solutions**:
-
-1. Check if extension is installed: `specify extension list`
-2. Create config from template:
-
-   ```bash
-   cp .specify/extensions/jira/jira-config.template.yml \
-      .specify/extensions/jira/jira-config.yml
-   ```
-
-3. Reinstall extension: `specify extension remove jira && specify extension add jira`
-
-### Command Not Available
-
-**Issue**: Extension command not appearing in AI agent
-
-**Solutions**:
-
-1. Check extension is enabled: `specify extension list`
-2. Restart AI agent (Claude Code)
-3. Check command file exists:
-
-   ```bash
-   ls .claude/commands/speckit.jira.*.md
-   ```
-
-4. Reinstall extension
-
-### Incompatible Version
-
-**Error**: `Extension requires spec-kit >=0.2.0, but you have 0.1.0`
-
-**Solutions**:
-
-1. Upgrade spec-kit:
-
-   ```bash
-   uv tool upgrade specify-cli
-   ```
-
-2. Install older version of extension:
-
-   ```bash
-   specify extension add --from https://github.com/org/ext/archive/v1.0.0.zip
-   ```
-
-### MCP Tool Not Available
-
-**Error**: `Tool 'jira-mcp-server/epic_create' not found`
-
-**Solutions**:
-
-1. Check MCP server is installed
-2. Check AI agent MCP configuration
-3. Restart AI agent
-4. Check extension requirements: `specify extension info jira`
-
-### Permission Denied
-
-**Error**: `Permission denied` when accessing Jira
-
-**Solutions**:
-
-1. Check Jira credentials in MCP server config
-2. Verify project permissions in Jira
-3. Test MCP server connection independently
-
----
-
-## Best Practices
-
-### 1. Version Control
-
-**Do commit**:
-
-- `.specify/extensions.yml` (project extension config)
-- `.specify/extensions/*/jira-config.yml` (project config)
-
-**Don't commit**:
-
-- `.specify/extensions/.cache/` (catalog cache)
-- `.specify/extensions/.backup/` (config backups)
-- `.specify/extensions/*/*.local.yml` (local overrides)
-- `.specify/extensions/.registry` (installation state)
-
-Add to `.gitignore`:
-
-```gitignore
-.specify/extensions/.cache/
-.specify/extensions/.backup/
-.specify/extensions/*/*.local.yml
-.specify/extensions/.registry
-```
-
-### 2. Team Workflows
-
-**For teams**:
-
-1. Agree on which extensions to use
-2. Commit extension configuration
-3. Document extension usage in README
-4. Keep extensions updated together
-
-**Example README section**:
-
-```markdown
-## Extensions
-
-This project uses:
-- **jira** (v1.0.0) - Jira integration
-  - Config: `.specify/extensions/jira/jira-config.yml`
-  - Requires: jira-mcp-server
-
-To install: `specify extension add jira`
-```
-
-### 3. Local Development
-
-Use local config for development:
-
-```yaml
-# .specify/extensions/jira/jira-config.local.yml
-project:
-  key: "DEVTEST"  # Your test project
-
-defaults:
-  task:
-    custom_fields:
-      customfield_10002: 1  # Lower story points for testing
-```
-
-### 4. Environment-Specific Config
-
-Use environment variables for CI/CD:
-
-```bash
-# .github/workflows/deploy.yml
-env:
-  SPECKIT_JIRA_PROJECT_KEY: ${{ secrets.JIRA_PROJECT }}
-
-- name: Create Jira Issues
-  run: specify extension add jira && ...
-```
-
-### 5. Extension Updates
-
-**Check for updates regularly**:
-
-```bash
-# Weekly or before major releases
-specify extension update
-```
-
-**Pin versions for stability**:
-
-```yaml
-# .specify/extensions.yml
-installed:
-  - id: jira
-    version: "1.0.0"  # Pin to specific version
-```
-
-### 6. Minimal Extensions
-
-Only install extensions you actively use:
-
-- Reduces complexity
-- Faster command loading
-- Less configuration
-
-### 7. Documentation
-
-Document extension usage in your project:
-
-```markdown
-# PROJECT.md
-
-## Working with Jira
-
-After creating tasks, sync to Jira:
-1. Run `/speckit.tasks` to generate tasks
-2. Run `/speckit.jira.specstoissues` to create Jira issues
-3. Run `/speckit.jira.sync-status` to update status
-```
-
----
-
-## FAQ
-
-### Q: Can I use multiple extensions at once?
-
-**A**: Yes! Extensions are designed to work together. Install as many as you need.
-
-### Q: Do extensions slow down spec-kit?
-
-**A**: No. Extensions are loaded on-demand and only when their commands are used.
-
-### Q: Can I create private extensions?
-
-**A**: Yes. Install with `--dev` or `--from` and keep private. Public catalog submission is optional.
-
-### Q: How do I know if an extension is safe?
-
-**A**: Look for the ✓ Verified badge. Verified extensions are reviewed by maintainers. Always review extension code before installing.
-
-### Q: Can extensions modify spec-kit core?
-
-**A**: No. Extensions can only add commands and hooks. They cannot modify core functionality.
-
-### Q: What happens if two extensions have the same command name?
-
-**A**: Extensions use namespaced commands (`speckit.{extension}.{command}`), so conflicts are very rare. The extension system will warn you if conflicts occur.
-
-### Q: Can I contribute to existing extensions?
-
-**A**: Yes! Most extensions are open source. Check the repository link in `specify extension info {extension}`.
-
-### Q: How do I report extension bugs?
-
-**A**: Go to the extension's repository (shown in `specify extension info`) and create an issue.
-
-### Q: Can extensions work offline?
-
-**A**: Once installed, extensions work offline. However, some extensions may require internet for their functionality (e.g., Jira requires Jira API access).
-
-### Q: How do I backup my extension configuration?
-
-**A**: Extension configs are in `.specify/extensions/{extension}/`. Back up this directory or commit configs to git.
-
----
-
-## Support
-
-- **Extension Issues**: Report to extension repository (see `specify extension info`)
-- **Spec Kit Issues**: <https://github.com/statsperform/spec-kit/issues>
-- **Extension Catalog**: <https://github.com/statsperform/spec-kit/tree/main/extensions>
-- **Documentation**: See EXTENSION-DEVELOPMENT-GUIDE.md and EXTENSION-PUBLISHING-GUIDE.md
-
----
-
-*Last Updated: 2026-01-28*
-*Spec Kit Version: 0.1.0*

extensions/README.md

@@ -1,129 +0,0 @@
-# Spec Kit Extensions
-
-Extension system for [Spec Kit](https://github.com/github/spec-kit) - add new functionality without bloating the core framework.
-
-## Extension Catalogs
-
-Spec Kit provides two catalog files with different purposes:
-
-### Your Catalog (`catalog.json`)
-
-- **Purpose**: Default upstream catalog of extensions used by the Spec Kit CLI
-- **Default State**: Empty by design in the upstream project - you or your organization populate a fork/copy with extensions you trust
-- **Location (upstream)**: `extensions/catalog.json` in the GitHub-hosted spec-kit repo
-- **CLI Default**: The `specify extension` commands use the upstream catalog URL by default, unless overridden
-- **Org Catalog**: Point `SPECKIT_CATALOG_URL` at your organization's fork or hosted catalog JSON to use it instead of the upstream default
-- **Customization**: Copy entries from the community catalog into your org catalog, or add your own extensions directly
-
-**Example override:**
-```bash
-# Override the default upstream catalog with your organization's catalog
-export SPECKIT_CATALOG_URL="https://your-org.com/spec-kit/catalog.json"
-specify extension search  # Now uses your organization's catalog instead of the upstream default
-```
-
-### Community Reference Catalog (`catalog.community.json`)
-
-- **Purpose**: Browse available community-contributed extensions
-- **Status**: Active - contains extensions submitted by the community
-- **Location**: `extensions/catalog.community.json`
-- **Usage**: Reference catalog for discovering available extensions
-- **Submission**: Open to community contributions via Pull Request
-
-**How It Works:**
-
-## Making Extensions Available
-
-You control which extensions your team can discover and install:
-
-### Option 1: Curated Catalog (Recommended for Organizations)
-
-Populate your `catalog.json` with approved extensions:
-
-1. **Discover** extensions from various sources:
-   - Browse `catalog.community.json` for community extensions
-   - Find private/internal extensions in your organization's repos
-   - Discover extensions from trusted third parties
-2. **Review** extensions and choose which ones you want to make available
-3. **Add** those extension entries to your own `catalog.json`
-4. **Team members** can now discover and install them:
-   - `specify extension search` shows your curated catalog
-   - `specify extension add <name>` installs from your catalog
-
-**Benefits**: Full control over available extensions, team consistency, organizational approval workflow
-
-**Example**: Copy an entry from `catalog.community.json` to your `catalog.json`, then your team can discover and install it by name.
-
-### Option 2: Direct URLs (For Ad-hoc Use)
-
-Skip catalog curation - team members install directly using URLs:
-
-```bash
-specify extension add --from https://github.com/org/spec-kit-ext/archive/refs/tags/v1.0.0.zip
-```
-
-**Benefits**: Quick for one-off testing or private extensions
-
-**Tradeoff**: Extensions installed this way won't appear in `specify extension search` for other team members unless you also add them to your `catalog.json`.
-
-## Available Community Extensions
-
-The following community-contributed extensions are available in [`catalog.community.json`](catalog.community.json):
-
-| Extension | Purpose | URL |
-|-----------|---------|-----|
-| Azure DevOps Integration | Sync user stories and tasks to Azure DevOps work items using OAuth authentication | [spec-kit-azure-devops](https://github.com/pragya247/spec-kit-azure-devops) |
-| 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 | [spec-kit-cleanup](https://github.com/dsrednicki/spec-kit-cleanup) |
-| Fleet Orchestrator | Orchestrate a full feature lifecycle with human-in-the-loop gates across all SpecKit phases | [spec-kit-fleet](https://github.com/sharathsatish/spec-kit-fleet) |
-| Jira Integration | Create Jira Epics, Stories, and Issues from spec-kit specifications and task breakdowns with configurable hierarchy and custom field support | [spec-kit-jira](https://github.com/mbachorik/spec-kit-jira) |
-| Ralph Loop | Autonomous implementation loop using AI agent CLI | [spec-kit-ralph](https://github.com/Rubiss/spec-kit-ralph) |
-| Retrospective Extension | Post-implementation retrospective with spec adherence scoring, drift analysis, and human-gated spec updates | [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 | [spec-kit-review](https://github.com/ismaelJimenez/spec-kit-review) |
-| Spec Sync | Detect and resolve drift between specs and implementation. AI-assisted resolution with human approval | [spec-kit-sync](https://github.com/bgervin/spec-kit-sync) |
-| Understanding | Automated requirements quality analysis — 31 deterministic metrics against IEEE/ISO standards with experimental energy-based ambiguity detection | [understanding](https://github.com/Testimonial/understanding) |
-| V-Model Extension Pack | Enforces V-Model paired generation of development specs and test specs with full traceability | [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 | [spec-kit-verify](https://github.com/ismaelJimenez/spec-kit-verify) |
-
-
-## Adding Your Extension
-
-### Submission Process
-
-To add your extension to the community catalog:
-
-1. **Prepare your extension** following the [Extension Development Guide](EXTENSION-DEVELOPMENT-GUIDE.md)
-2. **Create a GitHub release** for your extension
-3. **Submit a Pull Request** that:
-   - Adds your extension to `extensions/catalog.community.json`
-   - Updates this README with your extension in the Available Extensions table
-4. **Wait for review** - maintainers will review and merge if criteria are met
-
-See the [Extension Publishing Guide](EXTENSION-PUBLISHING-GUIDE.md) for detailed step-by-step instructions.
-
-### Submission Checklist
-
-Before submitting, ensure:
-
-- ✅ Valid `extension.yml` manifest
-- ✅ Complete README with installation and usage instructions
-- ✅ LICENSE file included
-- ✅ GitHub release created with semantic version (e.g., v1.0.0)
-- ✅ Extension tested on a real project
-- ✅ All commands working as documented
-
-## Installing Extensions
-Once extensions are available (either in your catalog or via direct URL), install them:
-
-```bash
-# From your curated catalog (by name)
-specify extension search                  # See what's in your catalog
-specify extension add <extension-name>    # Install by name
-
-# Direct from URL (bypasses catalog)
-specify extension add --from https://github.com/<org>/<repo>/archive/refs/tags/<version>.zip
-
-# List installed extensions
-specify extension list
-```
-
-For more information, see the [Extension User Guide](EXTENSION-USER-GUIDE.md).

extensions/catalog.community.json

@@ -1,366 +0,0 @@
-{
-  "schema_version": "1.0",
-  "updated_at": "2026-03-09T00:00:00Z",
-  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.community.json",
-  "extensions": {
-    "azure-devops": {
-      "name": "Azure DevOps Integration",
-      "id": "azure-devops",
-      "description": "Sync user stories and tasks to Azure DevOps work items using OAuth authentication.",
-      "author": "pragya247",
-      "version": "1.0.0",
-      "download_url": "https://github.com/pragya247/spec-kit-azure-devops/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/pragya247/spec-kit-azure-devops",
-      "homepage": "https://github.com/pragya247/spec-kit-azure-devops",
-      "documentation": "https://github.com/pragya247/spec-kit-azure-devops/blob/main/README.md",
-      "changelog": "https://github.com/pragya247/spec-kit-azure-devops/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          {
-            "name": "az",
-            "version": ">=2.0.0",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 1,
-        "hooks": 1
-      },
-      "tags": [
-        "azure",
-        "devops",
-        "project-management",
-        "work-items",
-        "issue-tracking"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-03-03T00:00:00Z",
-      "updated_at": "2026-03-03T00:00:00Z"
-    },
-    "cleanup": {
-      "name": "Cleanup Extension",
-      "id": "cleanup",
-      "description": "Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues.",
-      "author": "dsrednicki",
-      "version": "1.0.0",
-      "download_url": "https://github.com/dsrednicki/spec-kit-cleanup/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/dsrednicki/spec-kit-cleanup",
-      "homepage": "https://github.com/dsrednicki/spec-kit-cleanup",
-      "documentation": "https://github.com/dsrednicki/spec-kit-cleanup/blob/main/README.md",
-      "changelog": "https://github.com/dsrednicki/spec-kit-cleanup/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 1,
-        "hooks": 1
-      },
-      "tags": [
-        "quality",
-        "tech-debt",
-        "review",
-        "cleanup",
-        "scout-rule"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-02-22T00:00:00Z",
-      "updated_at": "2026-02-22T00:00:00Z"
-    },
-    "fleet": {
-      "name": "Fleet Orchestrator",
-      "id": "fleet",
-      "description": "Orchestrate a full feature lifecycle with human-in-the-loop gates across all SpecKit phases.",
-      "author": "sharathsatish",
-      "version": "1.0.0",
-      "download_url": "https://github.com/sharathsatish/spec-kit-fleet/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/sharathsatish/spec-kit-fleet",
-      "homepage": "https://github.com/sharathsatish/spec-kit-fleet",
-      "documentation": "https://github.com/sharathsatish/spec-kit-fleet/blob/main/README.md",
-      "changelog": "https://github.com/sharathsatish/spec-kit-fleet/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 2,
-        "hooks": 1
-      },
-      "tags": ["orchestration", "workflow", "human-in-the-loop", "parallel"],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-03-06T00:00:00Z",
-      "updated_at": "2026-03-06T00:00:00Z"
-    },
-    "jira": {
-      "name": "Jira Integration",
-      "id": "jira",
-      "description": "Create Jira Epics, Stories, and Issues from spec-kit specifications and task breakdowns with configurable hierarchy and custom field support.",
-      "author": "mbachorik",
-      "version": "2.1.0",
-      "download_url": "https://github.com/mbachorik/spec-kit-jira/archive/refs/tags/v2.1.0.zip",
-      "repository": "https://github.com/mbachorik/spec-kit-jira",
-      "homepage": "https://github.com/mbachorik/spec-kit-jira",
-      "documentation": "https://github.com/mbachorik/spec-kit-jira/blob/main/README.md",
-      "changelog": "https://github.com/mbachorik/spec-kit-jira/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 1
-      },
-      "tags": [
-        "issue-tracking",
-        "jira",
-        "atlassian",
-        "project-management"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-03-05T00:00:00Z",
-      "updated_at": "2026-03-05T00:00:00Z"
-    },
-    "ralph": {
-      "name": "Ralph Loop",
-      "id": "ralph",
-      "description": "Autonomous implementation loop using AI agent CLI.",
-      "author": "Rubiss",
-      "version": "1.0.0",
-      "download_url": "https://github.com/Rubiss/spec-kit-ralph/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/Rubiss/spec-kit-ralph",
-      "homepage": "https://github.com/Rubiss/spec-kit-ralph",
-      "documentation": "https://github.com/Rubiss/spec-kit-ralph/blob/main/README.md",
-      "changelog": "https://github.com/Rubiss/spec-kit-ralph/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          {
-            "name": "copilot",
-            "required": true
-          },
-          {
-            "name": "git",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 2,
-        "hooks": 1
-      },
-      "tags": ["implementation", "automation", "loop", "copilot"],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-03-09T00:00:00Z",
-      "updated_at": "2026-03-09T00:00:00Z"
-    },
-    "retrospective": {
-      "name": "Retrospective Extension",
-      "id": "retrospective",
-      "description": "Post-implementation retrospective with spec adherence scoring, drift analysis, and human-gated spec updates.",
-      "author": "emi-dm",
-      "version": "1.0.0",
-      "download_url": "https://github.com/emi-dm/spec-kit-retrospective/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/emi-dm/spec-kit-retrospective",
-      "homepage": "https://github.com/emi-dm/spec-kit-retrospective",
-      "documentation": "https://github.com/emi-dm/spec-kit-retrospective/blob/main/README.md",
-      "changelog": "https://github.com/emi-dm/spec-kit-retrospective/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 1,
-        "hooks": 1
-      },
-      "tags": [
-        "retrospective",
-        "spec-drift",
-        "quality",
-        "analysis",
-        "governance"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-02-24T00:00:00Z",
-      "updated_at": "2026-02-24T00:00:00Z"
-    },
-    "review": {
-      "name": "Review Extension",
-      "id": "review",
-      "description": "Post-implementation comprehensive code review with specialized agents for code quality, comments, tests, error handling, type design, and simplification.",
-      "author": "ismaelJimenez",
-      "version": "1.0.0",
-      "download_url": "https://github.com/ismaelJimenez/spec-kit-review/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/ismaelJimenez/spec-kit-review",
-      "homepage": "https://github.com/ismaelJimenez/spec-kit-review",
-      "documentation": "https://github.com/ismaelJimenez/spec-kit-review/blob/main/README.md",
-      "changelog": "https://github.com/ismaelJimenez/spec-kit-review/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 7,
-        "hooks": 1
-      },
-      "tags": ["code-review", "quality", "review", "testing", "error-handling", "type-design", "simplification"],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-03-06T00:00:00Z",
-      "updated_at": "2026-03-06T00:00:00Z"
-    },
-    "sync": {
-      "name": "Spec Sync",
-      "id": "sync",
-      "description": "Detect and resolve drift between specs and implementation. AI-assisted resolution with human approval.",
-      "author": "bgervin",
-      "version": "0.1.0",
-      "download_url": "https://github.com/bgervin/spec-kit-sync/archive/refs/tags/v0.1.0.zip",
-      "repository": "https://github.com/bgervin/spec-kit-sync",
-      "homepage": "https://github.com/bgervin/spec-kit-sync",
-      "documentation": "https://github.com/bgervin/spec-kit-sync/blob/main/README.md",
-      "changelog": "https://github.com/bgervin/spec-kit-sync/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 5,
-        "hooks": 1
-      },
-      "tags": [
-        "sync",
-        "drift",
-        "validation",
-        "bidirectional",
-        "backfill"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-03-02T00:00:00Z",
-      "updated_at": "2026-03-02T00:00:00Z"
-    },
-    "understanding": {
-      "name": "Understanding",
-      "id": "understanding",
-      "description": "Automated requirements quality analysis — validates specs against IEEE/ISO standards using 31 deterministic metrics. Catches ambiguity, missing testability, and structural issues before they reach implementation. Includes experimental energy-based ambiguity detection using local LM token perplexity.",
-      "author": "Ladislav Bihari",
-      "version": "3.4.0",
-      "download_url": "https://github.com/Testimonial/understanding/archive/refs/tags/v3.4.0.zip",
-      "repository": "https://github.com/Testimonial/understanding",
-      "homepage": "https://github.com/Testimonial/understanding",
-      "documentation": "https://github.com/Testimonial/understanding/blob/main/extension/README.md",
-      "changelog": "https://github.com/Testimonial/understanding/blob/main/extension/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0",
-        "tools": [
-          {
-            "name": "understanding",
-            "version": ">=3.4.0",
-            "required": true
-          }
-        ]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 1
-      },
-      "tags": [
-        "quality",
-        "metrics",
-        "requirements",
-        "validation",
-        "readability",
-        "IEEE-830",
-        "ISO-29148"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-03-07T00:00:00Z",
-      "updated_at": "2026-03-07T00:00:00Z"
-    },
-    "v-model": {
-      "name": "V-Model Extension Pack",
-      "id": "v-model",
-      "description": "Enforces V-Model paired generation of development specs and test specs with full traceability.",
-      "author": "leocamello",
-      "version": "0.4.0",
-      "download_url": "https://github.com/leocamello/spec-kit-v-model/archive/refs/tags/v0.4.0.zip",
-      "repository": "https://github.com/leocamello/spec-kit-v-model",
-      "homepage": "https://github.com/leocamello/spec-kit-v-model",
-      "documentation": "https://github.com/leocamello/spec-kit-v-model/blob/main/README.md",
-      "changelog": "https://github.com/leocamello/spec-kit-v-model/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 9,
-        "hooks": 1
-      },
-      "tags": [
-        "v-model",
-        "traceability",
-        "testing",
-        "compliance",
-        "safety-critical"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-02-20T00:00:00Z",
-      "updated_at": "2026-02-22T00:00:00Z"
-    },
-    "verify": {
-      "name": "Verify Extension",
-      "id": "verify",
-      "description": "Post-implementation quality gate that validates implemented code against specification artifacts.",
-      "author": "ismaelJimenez",
-      "version": "1.0.0",
-      "download_url": "https://github.com/ismaelJimenez/spec-kit-verify/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/ismaelJimenez/spec-kit-verify",
-      "homepage": "https://github.com/ismaelJimenez/spec-kit-verify",
-      "documentation": "https://github.com/ismaelJimenez/spec-kit-verify/blob/main/README.md",
-      "changelog": "https://github.com/ismaelJimenez/spec-kit-verify/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "commands": 1,
-        "hooks": 1
-      },
-      "tags": [
-        "verification",
-        "quality-gate",
-        "implementation",
-        "spec-adherence",
-        "compliance"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-03-03T00:00:00Z",
-      "updated_at": "2026-03-03T00:00:00Z"
-    }
-  }
-}

extensions/catalog.json

@@ -1,6 +0,0 @@
-{
-  "schema_version": "1.0",
-  "updated_at": "2026-02-03T00:00:00Z",
-  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.json",
-  "extensions": {}
-}

extensions/template/.gitignore

@@ -1,39 +0,0 @@
-# Local configuration overrides
-*-config.local.yml
-
-# Python
-__pycache__/
-*.py[cod]
-*$py.class
-*.so
-.Python
-env/
-venv/
-
-# Testing
-.pytest_cache/
-.coverage
-htmlcov/
-
-# IDEs
-.vscode/
-.idea/
-*.swp
-*.swo
-*~
-
-# OS
-.DS_Store
-Thumbs.db
-
-# Logs
-*.log
-
-# Build artifacts
-dist/
-build/
-*.egg-info/
-
-# Temporary files
-*.tmp
-.cache/

extensions/template/CHANGELOG.md

@@ -1,39 +0,0 @@
-# Changelog
-
-All notable changes to this extension will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to  [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [Unreleased]
-
-### Planned
-
-- Feature ideas for future versions
-- Enhancements
-- Bug fixes
-
-## [1.0.0] - YYYY-MM-DD
-
-### Added
-
-- Initial release of extension
-- Command: `/speckit.my-extension.example` - Example command functionality
-- Configuration system with template
-- Documentation and examples
-
-### Features
-
-- Feature 1 description
-- Feature 2 description
-- Feature 3 description
-
-### Requirements
-
-- Spec Kit: >=0.1.0
-- External dependencies (if any)
-
----
-
-[Unreleased]: https://github.com/your-org/spec-kit-my-extension/compare/v1.0.0...HEAD
-[1.0.0]: https://github.com/your-org/spec-kit-my-extension/releases/tag/v1.0.0

extensions/template/EXAMPLE-README.md

@@ -1,158 +0,0 @@
-# EXAMPLE: Extension README
-
-This is an example of what your extension README should look like after customization.
-**Delete this file and replace README.md with content similar to this.**
-
----
-
-# My Extension
-
-<!-- CUSTOMIZE: Replace with your extension description -->
-
-Brief description of what your extension does and why it's useful.
-
-## Features
-
-<!-- CUSTOMIZE: List key features -->
-
-- Feature 1: Description
-- Feature 2: Description
-- Feature 3: Description
-
-## Installation
-
-```bash
-# Install from catalog
-specify extension add my-extension
-
-# Or install from local development directory
-specify extension add --dev /path/to/my-extension
-```
-
-## Configuration
-
-1. Create configuration file:
-
-   ```bash
-   cp .specify/extensions/my-extension/config-template.yml \
-      .specify/extensions/my-extension/my-extension-config.yml
-   ```
-
-2. Edit configuration:
-
-   ```bash
-   vim .specify/extensions/my-extension/my-extension-config.yml
-   ```
-
-3. Set required values:
-   <!-- CUSTOMIZE: List required configuration -->
-   ```yaml
-   connection:
-     url: "https://api.example.com"
-     api_key: "your-api-key"
-
-   project:
-     id: "your-project-id"
-   ```
-
-## Usage
-
-<!-- CUSTOMIZE: Add usage examples -->
-
-### Command: example
-
-Description of what this command does.
-
-```bash
-# In Claude Code
-> /speckit.my-extension.example
-```
-
-**Prerequisites**:
-
-- Prerequisite 1
-- Prerequisite 2
-
-**Output**:
-
-- What this command produces
-- Where results are saved
-
-## Configuration Reference
-
-<!-- CUSTOMIZE: Document all configuration options -->
-
-### Connection Settings
-
-| Setting | Type | Required | Description |
-|---------|------|----------|-------------|
-| `connection.url` | string | Yes | API endpoint URL |
-| `connection.api_key` | string | Yes | API authentication key |
-
-### Project Settings
-
-| Setting | Type | Required | Description |
-|---------|------|----------|-------------|
-| `project.id` | string | Yes | Project identifier |
-| `project.workspace` | string | No | Workspace or organization |
-
-## Environment Variables
-
-Override configuration with environment variables:
-
-```bash
-# Override connection settings
-export SPECKIT_MY_EXTENSION_CONNECTION_URL="https://custom-api.com"
-export SPECKIT_MY_EXTENSION_CONNECTION_API_KEY="custom-key"
-```
-
-## Examples
-
-<!-- CUSTOMIZE: Add real-world examples -->
-
-### Example 1: Basic Workflow
-
-```bash
-# Step 1: Create specification
-> /speckit.spec
-
-# Step 2: Generate tasks
-> /speckit.tasks
-
-# Step 3: Use extension
-> /speckit.my-extension.example
-```
-
-## Troubleshooting
-
-<!-- CUSTOMIZE: Add common issues -->
-
-### Issue: Configuration not found
-
-**Solution**: Create config from template (see Configuration section)
-
-### Issue: Command not available
-
-**Solutions**:
-
-1. Check extension is installed: `specify extension list`
-2. Restart AI agent
-3. Reinstall extension
-
-## License
-
-MIT License - see LICENSE file
-
-## Support
-
-- **Issues**: <https://github.com/your-org/spec-kit-my-extension/issues>
-- **Spec Kit Docs**: <https://github.com/statsperform/spec-kit>
-
-## Changelog
-
-See [CHANGELOG.md](CHANGELOG.md) for version history.
-
----
-
-*Extension Version: 1.0.0*
-*Spec Kit: >=0.1.0*

extensions/template/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 [Your Name or Organization]
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

extensions/template/README.md

@@ -1,79 +0,0 @@
-# Extension Template
-
-Starter template for creating a Spec Kit extension.
-
-## Quick Start
-
-1. **Copy this template**:
-
-   ```bash
-   cp -r extensions/template my-extension
-   cd my-extension
-   ```
-
-2. **Customize `extension.yml`**:
-   - Change extension ID, name, description
-   - Update author and repository
-   - Define your commands
-
-3. **Create commands**:
-   - Add command files in `commands/` directory
-   - Use Markdown format with YAML frontmatter
-
-4. **Create config template**:
-   - Define configuration options
-   - Document all settings
-
-5. **Write documentation**:
-   - Update README.md with usage instructions
-   - Add examples
-
-6. **Test locally**:
-
-   ```bash
-   cd /path/to/spec-kit-project
-   specify extension add --dev /path/to/my-extension
-   ```
-
-7. **Publish** (optional):
-   - Create GitHub repository
-   - Create release
-   - Submit to catalog (see EXTENSION-PUBLISHING-GUIDE.md)
-
-## Files in This Template
-
-- `extension.yml` - Extension manifest (CUSTOMIZE THIS)
-- `config-template.yml` - Configuration template (CUSTOMIZE THIS)
-- `commands/example.md` - Example command (REPLACE THIS)
-- `README.md` - Extension documentation (REPLACE THIS)
-- `LICENSE` - MIT License (REVIEW THIS)
-- `CHANGELOG.md` - Version history (UPDATE THIS)
-- `.gitignore` - Git ignore rules
-
-## Customization Checklist
-
-- [ ] Update `extension.yml` with your extension details
-- [ ] Change extension ID to your extension name
-- [ ] Update author information
-- [ ] Define your commands
-- [ ] Create command files in `commands/`
-- [ ] Update config template
-- [ ] Write README with usage instructions
-- [ ] Add examples
-- [ ] Update LICENSE if needed
-- [ ] Test extension locally
-- [ ] Create git repository
-- [ ] Create first release
-
-## Need Help?
-
-- **Development Guide**: See EXTENSION-DEVELOPMENT-GUIDE.md
-- **API Reference**: See EXTENSION-API-REFERENCE.md
-- **Publishing Guide**: See EXTENSION-PUBLISHING-GUIDE.md
-- **User Guide**: See EXTENSION-USER-GUIDE.md
-
-## Template Version
-
-- Version: 1.0.0
-- Last Updated: 2026-01-28
-- Compatible with Spec Kit: >=0.1.0

extensions/template/commands/example.md

@@ -1,210 +0,0 @@
----
-description: "Example command that demonstrates extension functionality"
-# CUSTOMIZE: List MCP tools this command uses
-tools:
-  - 'example-mcp-server/example_tool'
----
-
-# Example Command
-
-<!-- CUSTOMIZE: Replace this entire file with your command documentation -->
-
-This is an example command that demonstrates how to create commands for Spec Kit extensions.
-
-## Purpose
-
-Describe what this command does and when to use it.
-
-## Prerequisites
-
-List requirements before using this command:
-
-1. Prerequisite 1 (e.g., "MCP server configured")
-2. Prerequisite 2 (e.g., "Configuration file exists")
-3. Prerequisite 3 (e.g., "Valid API credentials")
-
-## User Input
-
-$ARGUMENTS
-
-## Steps
-
-### Step 1: Load Configuration
-
-<!-- CUSTOMIZE: Replace with your actual steps -->
-
-Load extension configuration from the project:
-
-``bash
-config_file=".specify/extensions/my-extension/my-extension-config.yml"
-
-if [ ! -f "$config_file" ]; then
-  echo "❌ Error: Configuration not found at $config_file"
-  echo "Run 'specify extension add my-extension' to install and configure"
-  exit 1
-fi
-
-# Read configuration values
-
-setting_value=$(yq eval '.settings.key' "$config_file")
-
-# Apply environment variable overrides
-
-setting_value="${SPECKIT_MY_EXTENSION_KEY:-$setting_value}"
-
-# Validate configuration
-
-if [ -z "$setting_value" ]; then
-  echo "❌ Error: Configuration value not set"
-  echo "Edit $config_file and set 'settings.key'"
-  exit 1
-fi
-
-echo "📋 Configuration loaded: $setting_value"
-``
-
-### Step 2: Perform Main Action
-
-<!-- CUSTOMIZE: Replace with your command logic -->
-
-Describe what this step does:
-
-``markdown
-Use MCP tools to perform the main action:
-
-- Tool: example-mcp-server example_tool
-- Parameters: { "key": "$setting_value" }
-
-This calls the MCP server tool to execute the operation.
-``
-
-### Step 3: Process Results
-
-<!-- CUSTOMIZE: Add more steps as needed -->
-
-Process the results and provide output:
-
-`` bash
-echo ""
-echo "✅ Command completed successfully!"
-echo ""
-echo "Results:"
-echo "  • Item 1: Value"
-echo "  • Item 2: Value"
-echo ""
-``
-
-### Step 4: Save Output (Optional)
-
-Save results to a file if needed:
-
-``bash
-output_file=".specify/my-extension-output.json"
-
-cat > "$output_file" <<EOF
-{
-  "timestamp": "$(date -u +"%Y-%m-%dT%H:%M:%SZ")",
-  "setting": "$setting_value",
-  "results": []
-}
-EOF
-
-echo "💾 Output saved to $output_file"
-``
-
-## Configuration Reference
-
-<!-- CUSTOMIZE: Document configuration options -->
-
-This command uses the following configuration from `my-extension-config.yml`:
-
-- **settings.key**: Description of what this setting does
-  - Type: string
-  - Required: Yes
-  - Example: `"example-value"`
-
-- **settings.another_key**: Description of another setting
-  - Type: boolean
-  - Required: No
-  - Default: `false`
-  - Example: `true`
-
-## Environment Variables
-
-<!-- CUSTOMIZE: Document environment variable overrides -->
-
-Configuration can be overridden with environment variables:
-
-- `SPECKIT_MY_EXTENSION_KEY` - Overrides `settings.key`
-- `SPECKIT_MY_EXTENSION_ANOTHER_KEY` - Overrides `settings.another_key`
-
-Example:
-``bash
-export SPECKIT_MY_EXTENSION_KEY="override-value"
-``
-
-## Troubleshooting
-
-<!-- CUSTOMIZE: Add common issues and solutions -->
-
-### "Configuration not found"
-
-**Solution**: Install the extension and create configuration:
-``bash
-specify extension add my-extension
-cp .specify/extensions/my-extension/config-template.yml \
-   .specify/extensions/my-extension/my-extension-config.yml
-``
-
-### "MCP tool not available"
-
-**Solution**: Ensure MCP server is configured in your AI agent settings.
-
-### "Permission denied"
-
-**Solution**: Check credentials and permissions in the external service.
-
-## Notes
-
-<!-- CUSTOMIZE: Add helpful notes and tips -->
-
-- This command requires an active connection to the external service
-- Results are cached for performance
-- Re-run the command to refresh data
-
-## Examples
-
-<!-- CUSTOMIZE: Add usage examples -->
-
-### Example 1: Basic Usage
-
-``bash
-
-# Run with default configuration
->
-> /speckit.my-extension.example
-``
-
-### Example 2: With Environment Override
-
-``bash
-
-# Override configuration with environment variable
-
-export SPECKIT_MY_EXTENSION_KEY="custom-value"
-> /speckit.my-extension.example
-``
-
-### Example 3: After Core Command
-
-``bash
-
-# Use as part of a workflow
->
-> /speckit.tasks
-> /speckit.my-extension.example
-``
-
----
-
-*For more information, see the extension README or run `specify extension info my-extension`*

extensions/template/config-template.yml

@@ -1,75 +0,0 @@
-# Extension Configuration Template
-# Copy this to my-extension-config.yml and customize for your project
-
-# CUSTOMIZE: Add your configuration sections below
-
-# Example: Connection settings
-connection:
-  # URL to external service
-  url: ""  # REQUIRED: e.g., "https://api.example.com"
-
-  # API key or token
-  api_key: ""  # REQUIRED: Your API key
-
-# Example: Project settings
-project:
-  # Project identifier
-  id: ""  # REQUIRED: e.g., "my-project"
-
-  # Workspace or organization
-  workspace: ""  # OPTIONAL: e.g., "my-org"
-
-# Example: Feature flags
-features:
-  # Enable/disable main functionality
-  enabled: true
-
-  # Automatic synchronization
-  auto_sync: false
-
-  # Verbose logging
-  verbose: false
-
-# Example: Default values
-defaults:
-  # Labels to apply
-  labels: []  # e.g., ["automated", "spec-kit"]
-
-  # Priority level
-  priority: "medium"  # Options: "low", "medium", "high"
-
-  # Assignee
-  assignee: ""  # OPTIONAL: Default assignee
-
-# Example: Field mappings
-# Map internal names to external field IDs
-field_mappings:
-  # Example mappings
-  # internal_field: "external_field_id"
-  # status: "customfield_10001"
-
-# Example: Advanced settings
-advanced:
-  # Timeout in seconds
-  timeout: 30
-
-  # Retry attempts
-  retry_count: 3
-
-  # Cache duration in seconds
-  cache_duration: 3600
-
-# Environment Variable Overrides:
-# You can override any setting with environment variables  using this pattern:
-# SPECKIT_MY_EXTENSION_{SECTION}_{KEY}
-#
-# Examples:
-# - SPECKIT_MY_EXTENSION_CONNECTION_API_KEY: Override connection.api_key
-# - SPECKIT_MY_EXTENSION_PROJECT_ID: Override project.id
-# - SPECKIT_MY_EXTENSION_FEATURES_ENABLED: Override features.enabled
-#
-# Note: Use uppercase and replace dots with underscores
-
-# Local Overrides:
-# For local development, create my-extension-config.local.yml (gitignored)
-# to override settings without affecting the team configuration

extensions/template/extension.yml

@@ -1,97 +0,0 @@
-schema_version: "1.0"
-
-extension:
-  # CUSTOMIZE: Change 'my-extension' to your extension ID (lowercase, hyphen-separated)
-  id: "my-extension"
-
-  # CUSTOMIZE: Human-readable name for your extension
-  name: "My Extension"
-
-  # CUSTOMIZE: Update version when releasing (semantic versioning: X.Y.Z)
-  version: "1.0.0"
-
-  # CUSTOMIZE: Brief description (under 200 characters)
-  description: "Brief description of what your extension does"
-
-  # CUSTOMIZE: Your name or organization name
-  author: "Your Name"
-
-  # CUSTOMIZE: GitHub repository URL (create before publishing)
-  repository: "https://github.com/your-org/spec-kit-my-extension"
-
-  # REVIEW: License (MIT is recommended for open source)
-  license: "MIT"
-
-  # CUSTOMIZE: Extension homepage (can be same as repository)
-  homepage: "https://github.com/your-org/spec-kit-my-extension"
-
-# Requirements for this extension
-requires:
-  # CUSTOMIZE: Minimum spec-kit version required
-  # Use >=X.Y.Z for minimum version
-  # Use >=X.Y.Z,<Y.0.0 for version range
-  speckit_version: ">=0.1.0"
-
-  # CUSTOMIZE: Add MCP tools or other dependencies
-  # Remove if no external tools required
-  tools:
-    - name: "example-mcp-server"
-      version: ">=1.0.0"
-      required: true
-
-# Commands provided by this extension
-provides:
-  commands:
-    # CUSTOMIZE: Define your commands
-    # Pattern: speckit.{extension-id}.{command-name}
-    - name: "speckit.my-extension.example"
-      file: "commands/example.md"
-      description: "Example command that demonstrates functionality"
-      # Optional: Add aliases for shorter command names
-      aliases: ["speckit.example"]
-
-    # ADD MORE COMMANDS: Copy this block for each command
-    # - name: "speckit.my-extension.another-command"
-    #   file: "commands/another-command.md"
-    #   description: "Another command"
-
-  # CUSTOMIZE: Define configuration files
-  config:
-    - name: "my-extension-config.yml"
-      template: "config-template.yml"
-      description: "Extension configuration"
-      required: true # Set to false if config is optional
-
-# CUSTOMIZE: Define hooks (optional)
-# Remove if no hooks needed
-hooks:
-  # Hook that runs after /speckit.tasks
-  after_tasks:
-    command: "speckit.my-extension.example"
-    optional: true # User will be prompted
-    prompt: "Run example command?"
-    description: "Demonstrates hook functionality"
-    condition: null # Future: conditional execution
-
-  # ADD MORE HOOKS: Copy this block for other events
-  # after_implement:
-  #   command: "speckit.my-extension.another"
-  #   optional: false  # Auto-execute without prompting
-  #   description: "Runs automatically after implementation"
-
-# CUSTOMIZE: Add relevant tags (2-5 recommended)
-# Used for discovery in catalog
-tags:
-  - "example"
-  - "template"
-  # ADD MORE: "category", "tool-name", etc.
-
-# CUSTOMIZE: Default configuration values (optional)
-# These are merged with user config
-defaults:
-  # Example default values
-  feature:
-    enabled: true
-    auto_sync: false
-
-  # ADD MORE: Any default settings for your extension

memory/constitution.md

@@ -47,4 +47,4 @@
 <!-- Example: All PRs/reviews must verify compliance; Complexity must be justified; Use [GUIDANCE_FILE] for runtime development guidance -->
 
 **Version**: [CONSTITUTION_VERSION] | **Ratified**: [RATIFICATION_DATE] | **Last Amended**: [LAST_AMENDED_DATE]
-<!-- Example: Version: 2.1.1 | Ratified: 2025-06-13 | Last Amended: 2025-07-16 -->
+<!-- Example: Version: 2.1.1 | Ratified: 2025-06-13 | Last Amended: 2025-07-16 -->

memory/constitution_update_checklist.md

@@ -0,0 +1,85 @@
+# Constitution Update Checklist
+
+When amending the constitution (`/memory/constitution.md`), ensure all dependent documents are updated to maintain consistency.
+
+## Templates to Update
+
+### When adding/modifying ANY article:
+- [ ] `/templates/plan-template.md` - Update Constitution Check section
+- [ ] `/templates/spec-template.md` - Update if requirements/scope affected
+- [ ] `/templates/tasks-template.md` - Update if new task types needed
+- [ ] `/.claude/commands/plan.md` - Update if planning process changes
+- [ ] `/.claude/commands/tasks.md` - Update if task generation affected
+- [ ] `/CLAUDE.md` - Update runtime development guidelines
+
+### Article-specific updates:
+
+#### Article I (Library-First):
+- [ ] Ensure templates emphasize library creation
+- [ ] Update CLI command examples
+- [ ] Add llms.txt documentation requirements
+
+#### Article II (CLI Interface):
+- [ ] Update CLI flag requirements in templates
+- [ ] Add text I/O protocol reminders
+
+#### Article III (Test-First):
+- [ ] Update test order in all templates
+- [ ] Emphasize TDD requirements
+- [ ] Add test approval gates
+
+#### Article IV (Integration Testing):
+- [ ] List integration test triggers
+- [ ] Update test type priorities
+- [ ] Add real dependency requirements
+
+#### Article V (Observability):
+- [ ] Add logging requirements to templates
+- [ ] Include multi-tier log streaming
+- [ ] Update performance monitoring sections
+
+#### Article VI (Versioning):
+- [ ] Add version increment reminders
+- [ ] Include breaking change procedures
+- [ ] Update migration requirements
+
+#### Article VII (Simplicity):
+- [ ] Update project count limits
+- [ ] Add pattern prohibition examples
+- [ ] Include YAGNI reminders
+
+## Validation Steps
+
+1. **Before committing constitution changes:**
+   - [ ] All templates reference new requirements
+   - [ ] Examples updated to match new rules
+   - [ ] No contradictions between documents
+
+2. **After updating templates:**
+   - [ ] Run through a sample implementation plan
+   - [ ] Verify all constitution requirements addressed
+   - [ ] Check that templates are self-contained (readable without constitution)
+
+3. **Version tracking:**
+   - [ ] Update constitution version number
+   - [ ] Note version in template footers
+   - [ ] Add amendment to constitution history
+
+## Common Misses
+
+Watch for these often-forgotten updates:
+- Command documentation (`/commands/*.md`)
+- Checklist items in templates
+- Example code/commands
+- Domain-specific variations (web vs mobile vs CLI)
+- Cross-references between documents
+
+## Template Sync Status
+
+Last sync check: 2025-07-16
+- Constitution version: 2.1.1
+- Templates aligned: ❌ (missing versioning, observability details)
+
+---
+
+*This checklist ensures the constitution's principles are consistently applied across all project documentation.*

presets/ARCHITECTURE.md

@@ -1,157 +0,0 @@
-# Preset System Architecture
-
-This document describes the internal architecture of the preset system — how template resolution, command registration, and catalog management work under the hood.
-
-For usage instructions, see [README.md](README.md).
-
-## Template Resolution
-
-When Spec Kit needs a template (e.g. `spec-template`), the `PresetResolver` walks a priority stack and returns the first match:
-
-```mermaid
-flowchart TD
-    A["resolve_template('spec-template')"] --> B{Override exists?}
-    B -- Yes --> C[".specify/templates/overrides/spec-template.md"]
-    B -- No --> D{Preset provides it?}
-    D -- Yes --> E[".specify/presets/‹preset-id›/templates/spec-template.md"]
-    D -- No --> F{Extension provides it?}
-    F -- Yes --> G[".specify/extensions/‹ext-id›/templates/spec-template.md"]
-    F -- No --> H[".specify/templates/spec-template.md"]
-
-    E -- "multiple presets?" --> I["lowest priority number wins"]
-    I --> E
-
-    style C fill:#4caf50,color:#fff
-    style E fill:#2196f3,color:#fff
-    style G fill:#ff9800,color:#fff
-    style H fill:#9e9e9e,color:#fff
-```
-
-| Priority | Source | Path | Use case |
-|----------|--------|------|----------|
-| 1 (highest) | Override | `.specify/templates/overrides/` | One-off project-local tweaks |
-| 2 | Preset | `.specify/presets/<id>/templates/` | Shareable, stackable customizations |
-| 3 | Extension | `.specify/extensions/<id>/templates/` | Extension-provided templates |
-| 4 (lowest) | Core | `.specify/templates/` | Shipped defaults |
-
-When multiple presets are installed, they're sorted by their `priority` field (lower number = higher precedence). This is set via `--priority` on `specify preset add`.
-
-The resolution is implemented three times to ensure consistency:
-- **Python**: `PresetResolver` in `src/specify_cli/presets.py`
-- **Bash**: `resolve_template()` in `scripts/bash/common.sh`
-- **PowerShell**: `Resolve-Template` in `scripts/powershell/common.ps1`
-
-## Command Registration
-
-When a preset is installed with `type: "command"` entries, the `PresetManager` registers them into all detected agent directories using the shared `CommandRegistrar` from `src/specify_cli/agents.py`.
-
-```mermaid
-flowchart TD
-    A["specify preset add my-preset"] --> B{Preset has type: command?}
-    B -- No --> Z["done (templates only)"]
-    B -- Yes --> C{Extension command?}
-    C -- "speckit.myext.cmd\n(3+ dot segments)" --> D{Extension installed?}
-    D -- No --> E["skip (extension not active)"]
-    D -- Yes --> F["register command"]
-    C -- "speckit.specify\n(core command)" --> F
-    F --> G["detect agent directories"]
-    G --> H[".claude/commands/"]
-    G --> I[".gemini/commands/"]
-    G --> J[".github/agents/"]
-    G --> K["... (17+ agents)"]
-    H --> L["write .md (Markdown format)"]
-    I --> M["write .toml (TOML format)"]
-    J --> N["write .agent.md + .prompt.md"]
-
-    style E fill:#ff5722,color:#fff
-    style L fill:#4caf50,color:#fff
-    style M fill:#4caf50,color:#fff
-    style N fill:#4caf50,color:#fff
-```
-
-### Extension safety check
-
-Command names follow the pattern `speckit.<ext-id>.<cmd-name>`. When a command has 3+ dot segments, the system extracts the extension ID and checks if `.specify/extensions/<ext-id>/` exists. If the extension isn't installed, the command is skipped — preventing orphan files referencing non-existent extensions.
-
-Core commands (e.g. `speckit.specify`, with only 2 segments) are always registered.
-
-### Agent format rendering
-
-The `CommandRegistrar` renders commands differently per agent:
-
-| Agent | Format | Extension | Arg placeholder |
-|-------|--------|-----------|-----------------|
-| Claude, Cursor, opencode, Windsurf, etc. | Markdown | `.md` | `$ARGUMENTS` |
-| Copilot | Markdown | `.agent.md` + `.prompt.md` | `$ARGUMENTS` |
-| Gemini, Qwen, Tabnine | TOML | `.toml` | `{{args}}` |
-
-### Cleanup on removal
-
-When `specify preset remove` is called, the registered commands are read from the registry metadata and the corresponding files are deleted from each agent directory, including Copilot companion `.prompt.md` files.
-
-## Catalog System
-
-```mermaid
-flowchart TD
-    A["specify preset search"] --> B["PresetCatalog.get_active_catalogs()"]
-    B --> C{SPECKIT_PRESET_CATALOG_URL set?}
-    C -- Yes --> D["single custom catalog"]
-    C -- No --> E{.specify/preset-catalogs.yml exists?}
-    E -- Yes --> F["project-level catalog stack"]
-    E -- No --> G{"~/.specify/preset-catalogs.yml exists?"}
-    G -- Yes --> H["user-level catalog stack"]
-    G -- No --> I["built-in defaults"]
-    I --> J["default (install allowed)"]
-    I --> K["community (discovery only)"]
-
-    style D fill:#ff9800,color:#fff
-    style F fill:#2196f3,color:#fff
-    style H fill:#2196f3,color:#fff
-    style J fill:#4caf50,color:#fff
-    style K fill:#9e9e9e,color:#fff
-```
-
-Catalogs are fetched with a 1-hour cache (per-URL, SHA256-hashed cache files). Each catalog entry has a `priority` (for merge ordering) and `install_allowed` flag.
-
-## Repository Layout
-
-```
-presets/
-├── ARCHITECTURE.md                         # This file
-├── PUBLISHING.md                           # Guide for submitting presets to the catalog
-├── README.md                               # User guide
-├── catalog.json                            # Official preset catalog
-├── catalog.community.json                  # Community preset catalog
-├── scaffold/                               # Scaffold for creating new presets
-│   ├── preset.yml                          # Example manifest
-│   ├── README.md                           # Guide for customizing the scaffold
-│   ├── commands/
-│   │   ├── speckit.specify.md              # Core command override example
-│   │   └── speckit.myext.myextcmd.md       # Extension command override example
-│   └── templates/
-│       ├── spec-template.md                # Core template override example
-│       └── myext-template.md               # Extension template override example
-└── self-test/                              # Self-test preset (overrides all core templates)
-    ├── preset.yml
-    ├── commands/
-    │   └── speckit.specify.md
-    └── templates/
-        ├── spec-template.md
-        ├── plan-template.md
-        ├── tasks-template.md
-        ├── checklist-template.md
-        ├── constitution-template.md
-        └── agent-file-template.md
-```
-
-## Module Structure
-
-```
-src/specify_cli/
-├── agents.py       # CommandRegistrar — shared infrastructure for writing
-│                    #   command files to agent directories
-├── presets.py       # PresetManifest, PresetRegistry, PresetManager,
-│                    #   PresetCatalog, PresetCatalogEntry, PresetResolver
-└── __init__.py      # CLI commands: specify preset list/add/remove/search/
-                     #   resolve/info, specify preset catalog list/add/remove
-```

presets/PUBLISHING.md

@@ -1,295 +0,0 @@
-# Preset Publishing Guide
-
-This guide explains how to publish your preset to the Spec Kit preset catalog, making it discoverable by `specify preset search`.
-
-## Table of Contents
-
-1. [Prerequisites](#prerequisites)
-2. [Prepare Your Preset](#prepare-your-preset)
-3. [Submit to Catalog](#submit-to-catalog)
-4. [Verification Process](#verification-process)
-5. [Release Workflow](#release-workflow)
-6. [Best Practices](#best-practices)
-
----
-
-## Prerequisites
-
-Before publishing a preset, ensure you have:
-
-1. **Valid Preset**: A working preset with a valid `preset.yml` manifest
-2. **Git Repository**: Preset hosted on GitHub (or other public git hosting)
-3. **Documentation**: README.md with description and usage instructions
-4. **License**: Open source license file (MIT, Apache 2.0, etc.)
-5. **Versioning**: Semantic versioning (e.g., 1.0.0)
-6. **Testing**: Preset tested on real projects with `specify preset add --dev`
-
----
-
-## Prepare Your Preset
-
-### 1. Preset Structure
-
-Ensure your preset follows the standard structure:
-
-```text
-your-preset/
-├── preset.yml                 # Required: Preset manifest
-├── README.md                  # Required: Documentation
-├── LICENSE                    # Required: License file
-├── CHANGELOG.md               # Recommended: Version history
-│
-├── templates/                 # Template overrides
-│   ├── spec-template.md
-│   ├── plan-template.md
-│   └── ...
-│
-└── commands/                  # Command overrides (optional)
-    └── speckit.specify.md
-```
-
-Start from the [scaffold](scaffold/) if you're creating a new preset.
-
-### 2. preset.yml Validation
-
-Verify your manifest is valid:
-
-```yaml
-schema_version: "1.0"
-
-preset:
-  id: "your-preset"               # Unique lowercase-hyphenated ID
-  name: "Your Preset Name"        # Human-readable name
-  version: "1.0.0"                # Semantic version
-  description: "Brief description (one sentence)"
-  author: "Your Name or Organization"
-  repository: "https://github.com/your-org/spec-kit-preset-your-preset"
-  license: "MIT"
-
-requires:
-  speckit_version: ">=0.1.0"      # Required spec-kit version
-
-provides:
-  templates:
-    - type: "template"
-      name: "spec-template"
-      file: "templates/spec-template.md"
-      description: "Custom spec template"
-      replaces: "spec-template"
-
-tags:                              # 2-5 relevant tags
-  - "category"
-  - "workflow"
-```
-
-**Validation Checklist**:
-
-- ✅ `id` is lowercase with hyphens only (no underscores, spaces, or special characters)
-- ✅ `version` follows semantic versioning (X.Y.Z)
-- ✅ `description` is concise (under 200 characters)
-- ✅ `repository` URL is valid and public
-- ✅ All template and command files exist in the preset directory
-- ✅ Template names are lowercase with hyphens only
-- ✅ Command names use dot notation (e.g. `speckit.specify`)
-- ✅ Tags are lowercase and descriptive
-
-### 3. Test Locally
-
-```bash
-# Install from local directory
-specify preset add --dev /path/to/your-preset
-
-# Verify templates resolve from your preset
-specify preset resolve spec-template
-
-# Verify preset info
-specify preset info your-preset
-
-# List installed presets
-specify preset list
-
-# Remove when done testing
-specify preset remove your-preset
-```
-
-If your preset includes command overrides, verify they appear in the agent directories:
-
-```bash
-# Check Claude commands (if using Claude)
-ls .claude/commands/speckit.*.md
-
-# Check Copilot commands (if using Copilot)
-ls .github/agents/speckit.*.agent.md
-
-# Check Gemini commands (if using Gemini)
-ls .gemini/commands/speckit.*.toml
-```
-
-### 4. Create GitHub Release
-
-Create a GitHub release for your preset version:
-
-```bash
-# Tag the release
-git tag v1.0.0
-git push origin v1.0.0
-```
-
-The release archive URL will be:
-
-```text
-https://github.com/your-org/spec-kit-preset-your-preset/archive/refs/tags/v1.0.0.zip
-```
-
-### 5. Test Installation from Archive
-
-```bash
-specify preset add --from https://github.com/your-org/spec-kit-preset-your-preset/archive/refs/tags/v1.0.0.zip
-```
-
----
-
-## Submit to Catalog
-
-### Understanding the Catalogs
-
-Spec Kit uses a dual-catalog system:
-
-- **`catalog.json`** — Official, verified presets (install allowed by default)
-- **`catalog.community.json`** — Community-contributed presets (discovery only by default)
-
-All community presets should be submitted to `catalog.community.json`.
-
-### 1. Fork the spec-kit Repository
-
-```bash
-git clone https://github.com/YOUR-USERNAME/spec-kit.git
-cd spec-kit
-```
-
-### 2. Add Preset to Community Catalog
-
-Edit `presets/catalog.community.json` and add your preset.
-
-> **⚠️ Entries must be sorted alphabetically by preset ID.** Insert your preset in the correct position within the `"presets"` object.
-
-```json
-{
-  "schema_version": "1.0",
-  "updated_at": "2026-03-10T00:00:00Z",
-  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/presets/catalog.community.json",
-  "presets": {
-    "your-preset": {
-      "name": "Your Preset Name",
-      "description": "Brief description of what your preset provides",
-      "author": "Your Name",
-      "version": "1.0.0",
-      "download_url": "https://github.com/your-org/spec-kit-preset-your-preset/archive/refs/tags/v1.0.0.zip",
-      "repository": "https://github.com/your-org/spec-kit-preset-your-preset",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.1.0"
-      },
-      "provides": {
-        "templates": 3,
-        "commands": 1
-      },
-      "tags": [
-        "category",
-        "workflow"
-      ],
-      "created_at": "2026-03-10T00:00:00Z",
-      "updated_at": "2026-03-10T00:00:00Z"
-    }
-  }
-}
-```
-
-### 3. Submit Pull Request
-
-```bash
-git checkout -b add-your-preset
-git add presets/catalog.community.json
-git commit -m "Add your-preset to community catalog
-
-- Preset ID: your-preset
-- Version: 1.0.0
-- Author: Your Name
-- Description: Brief description
-"
-git push origin add-your-preset
-```
-
-**Pull Request Checklist**:
-
-```markdown
-## Preset Submission
-
-**Preset Name**: Your Preset Name
-**Preset ID**: your-preset
-**Version**: 1.0.0
-**Repository**: https://github.com/your-org/spec-kit-preset-your-preset
-
-### Checklist
-- [ ] Valid preset.yml manifest
-- [ ] README.md with description and usage
-- [ ] LICENSE file included
-- [ ] GitHub release created
-- [ ] Preset tested with `specify preset add --dev`
-- [ ] Templates resolve correctly (`specify preset resolve`)
-- [ ] Commands register to agent directories (if applicable)
-- [ ] Commands match template sections (command + template are coherent)
-- [ ] Added to presets/catalog.community.json
-```
-
----
-
-## Verification Process
-
-After submission, maintainers will review:
-
-1. **Manifest validation** — valid `preset.yml`, all files exist
-2. **Template quality** — templates are useful and well-structured
-3. **Command coherence** — commands reference sections that exist in templates
-4. **Security** — no malicious content, safe file operations
-5. **Documentation** — clear README explaining what the preset does
-
-Once verified, `verified: true` is set and the preset appears in `specify preset search`.
-
----
-
-## Release Workflow
-
-When releasing a new version:
-
-1. Update `version` in `preset.yml`
-2. Update CHANGELOG.md
-3. Tag and push: `git tag v1.1.0 && git push origin v1.1.0`
-4. Submit PR to update `version` and `download_url` in `presets/catalog.community.json`
-
----
-
-## Best Practices
-
-### Template Design
-
-- **Keep sections clear** — use headings and placeholder text the LLM can replace
-- **Match commands to templates** — if your preset overrides a command, make sure it references the sections in your template
-- **Document customization points** — use HTML comments to guide users on what to change
-
-### Naming
-
-- Preset IDs should be descriptive: `healthcare-compliance`, `enterprise-safe`, `startup-lean`
-- Avoid generic names: `my-preset`, `custom`, `test`
-
-### Stacking
-
-- Design presets to work well when stacked with others
-- Only override templates you need to change
-- Document which templates and commands your preset modifies
-
-### Command Overrides
-
-- Only override commands when the workflow needs to change, not just the output format
-- If you only need different template sections, a template override is sufficient
-- Test command overrides with multiple agents (Claude, Gemini, Copilot)

presets/README.md

@@ -1,115 +0,0 @@
-# Presets
-
-Presets are stackable, priority-ordered collections of template and command overrides for Spec Kit. They let you customize both the artifacts produced by the Spec-Driven Development workflow (specs, plans, tasks, checklists, constitutions) and the commands that guide the LLM in creating them — without forking or modifying core files.
-
-## How It Works
-
-When Spec Kit needs a template (e.g. `spec-template`), it walks a resolution stack:
-
-1. `.specify/templates/overrides/` — project-local one-off overrides
-2. `.specify/presets/<preset-id>/templates/` — installed presets (sorted by priority)
-3. `.specify/extensions/<ext-id>/templates/` — extension-provided templates
-4. `.specify/templates/` — core templates shipped with Spec Kit
-
-If no preset is installed, core templates are used — exactly the same behavior as before presets existed.
-
-For detailed resolution and command registration flows, see [ARCHITECTURE.md](ARCHITECTURE.md).
-
-## Command Overrides
-
-Presets can also override the commands that guide the SDD workflow. Templates define *what* gets produced (specs, plans, constitutions); commands define *how* the LLM produces them (the step-by-step instructions).
-
-When a preset includes `type: "command"` entries, the commands are automatically registered into all detected agent directories (`.claude/commands/`, `.gemini/commands/`, etc.) in the correct format (Markdown or TOML with appropriate argument placeholders). When the preset is removed, the registered commands are cleaned up.
-
-## Quick Start
-
-```bash
-# Search available presets
-specify preset search
-
-# Install a preset from the catalog
-specify preset add healthcare-compliance
-
-# Install from a local directory (for development)
-specify preset add --dev ./my-preset
-
-# Install with a specific priority (lower = higher precedence)
-specify preset add healthcare-compliance --priority 5
-
-# List installed presets
-specify preset list
-
-# See which template a name resolves to
-specify preset resolve spec-template
-
-# Get detailed info about a preset
-specify preset info healthcare-compliance
-
-# Remove a preset
-specify preset remove healthcare-compliance
-```
-
-## Stacking Presets
-
-Multiple presets can be installed simultaneously. The `--priority` flag controls which one wins when two presets provide the same template (lower number = higher precedence):
-
-```bash
-specify preset add enterprise-safe --priority 10      # base layer
-specify preset add healthcare-compliance --priority 5  # overrides enterprise-safe
-specify preset add pm-workflow --priority 1            # overrides everything
-```
-
-Presets **override**, they don't merge. If two presets both provide `spec-template`, the one with the lowest priority number wins entirely.
-
-## Catalog Management
-
-Presets are discovered through catalogs. By default, Spec Kit uses the official and community catalogs:
-
-```bash
-# List active catalogs
-specify preset catalog list
-
-# Add a custom catalog
-specify preset catalog add https://example.com/catalog.json --name my-org --install-allowed
-
-# Remove a catalog
-specify preset catalog remove my-org
-```
-
-## Creating a Preset
-
-See [scaffold/](scaffold/) for a scaffold you can copy to create your own preset.
-
-1. Copy `scaffold/` to a new directory
-2. Edit `preset.yml` with your preset's metadata
-3. Add or replace templates in `templates/`
-4. Test locally with `specify preset add --dev .`
-5. Verify with `specify preset resolve spec-template`
-
-## Environment Variables
-
-| Variable | Description |
-|----------|-------------|
-| `SPECKIT_PRESET_CATALOG_URL` | Override the catalog URL (replaces all defaults) |
-
-## Configuration Files
-
-| File | Scope | Description |
-|------|-------|-------------|
-| `.specify/preset-catalogs.yml` | Project | Custom catalog stack for this project |
-| `~/.specify/preset-catalogs.yml` | User | Custom catalog stack for all projects |
-
-## Future Considerations
-
-The following enhancements are under consideration for future releases:
-
-- **Composition strategies** — Allow presets to declare a `strategy` per template instead of the default `replace`:
-
-  | Type | `replace` | `prepend` | `append` | `wrap` |
-  |------|-----------|-----------|----------|--------|
-  | **template** | ✓ (default) | ✓ | ✓ | ✓ |
-  | **command** | ✓ (default) | ✓ | ✓ | ✓ |
-  | **script** | ✓ (default) | — | — | ✓ |
-
-  For artifacts and commands (which are LLM directives), `wrap` would inject preset content before and after the core template using a `{CORE_TEMPLATE}` placeholder. For scripts, `wrap` would run custom logic before/after the core script via a `$CORE_SCRIPT` variable.
-- **Script overrides** — Enable presets to provide alternative versions of core scripts (e.g. `create-new-feature.sh`) for workflow customization. A `strategy: "wrap"` option could allow presets to run custom logic before/after the core script without fully replacing it.

presets/catalog.community.json

@@ -1,6 +0,0 @@
-{
-  "schema_version": "1.0",
-  "updated_at": "2026-03-09T00:00:00Z",
-  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/presets/catalog.community.json",
-  "presets": {}
-}

presets/catalog.json

@@ -1,6 +0,0 @@
-{
-  "schema_version": "1.0",
-  "updated_at": "2026-03-10T00:00:00Z",
-  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/presets/catalog.json",
-  "presets": {}
-}

presets/scaffold/README.md

@@ -1,46 +0,0 @@
-# My Preset
-
-A custom preset for Spec Kit. Copy this directory and customize it to create your own.
-
-## Templates Included
-
-| Template | Type | Description |
-|----------|------|-------------|
-| `spec-template` | template | Custom feature specification template (overrides core and extensions) |
-| `myext-template` | template | Override of the myext extension's report template |
-| `speckit.specify` | command | Custom specification command (overrides core) |
-| `speckit.myext.myextcmd` | command | Override of the myext extension's myextcmd command |
-
-## Development
-
-1. Copy this directory: `cp -r presets/scaffold my-preset`
-2. Edit `preset.yml` — set your preset's ID, name, description, and templates
-3. Add or modify templates in `templates/`
-4. Test locally: `specify preset add --dev ./my-preset`
-5. Verify resolution: `specify preset resolve spec-template`
-6. Remove when done testing: `specify preset remove my-preset`
-
-## Manifest Reference (`preset.yml`)
-
-Required fields:
-- `schema_version` — always `"1.0"`
-- `preset.id` — lowercase alphanumeric with hyphens
-- `preset.name` — human-readable name
-- `preset.version` — semantic version (e.g. `1.0.0`)
-- `preset.description` — brief description
-- `requires.speckit_version` — version constraint (e.g. `>=0.1.0`)
-- `provides.templates` — list of templates with `type`, `name`, and `file`
-
-## Template Types
-
-- **template** — Document scaffolds (spec-template.md, plan-template.md, tasks-template.md, etc.)
-- **command** — AI agent workflow prompts (e.g. speckit.specify, speckit.plan)
-- **script** — Custom scripts (reserved for future use)
-
-## Publishing
-
-See the [Preset Publishing Guide](../PUBLISHING.md) for details on submitting to the catalog.
-
-## License
-
-MIT

presets/scaffold/commands/speckit.myext.myextcmd.md

@@ -1,20 +0,0 @@
----
-description: "Override of the myext extension's myextcmd command"
----
-
-<!-- Preset override for speckit.myext.myextcmd -->
-
-You are following a customized version of the myext extension's myextcmd command.
-
-When executing this command:
-
-1. Read the user's input from $ARGUMENTS
-2. Follow the standard myextcmd workflow
-3. Additionally, apply the following customizations from this preset:
-   - Add compliance checks before proceeding
-   - Include audit trail entries in the output
-
-> CUSTOMIZE: Replace the instructions above with your own.
-> This file overrides the command that the "myext" extension provides.
-> When this preset is installed, all agents (Claude, Gemini, Copilot, etc.)
-> will use this version instead of the extension's original.

presets/scaffold/commands/speckit.specify.md

@@ -1,23 +0,0 @@
----
-description: "Create a feature specification (preset override)"
-scripts:
-  sh: scripts/bash/create-new-feature.sh "{ARGS}"
-  ps: scripts/powershell/create-new-feature.ps1 "{ARGS}"
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-Given the feature description above:
-
-1. **Create the feature branch** by running the script:
-   - Bash: `{SCRIPT} --json --short-name "<short-name>" "<description>"`
-   - The JSON output contains BRANCH_NAME and SPEC_FILE paths.
-
-2. **Read the spec-template** to see the sections you need to fill.
-
-3. **Write the specification** to SPEC_FILE, replacing the placeholders in each section
-   (Overview, Requirements, Acceptance Criteria) with details from the user's description.

presets/scaffold/preset.yml

@@ -1,91 +0,0 @@
-schema_version: "1.0"
-
-preset:
-  # CUSTOMIZE: Change 'my-preset' to your preset ID (lowercase, hyphen-separated)
-  id: "my-preset"
-
-  # CUSTOMIZE: Human-readable name for your preset
-  name: "My Preset"
-
-  # CUSTOMIZE: Update version when releasing (semantic versioning: X.Y.Z)
-  version: "1.0.0"
-
-  # CUSTOMIZE: Brief description (under 200 characters)
-  description: "Brief description of what your preset provides"
-
-  # CUSTOMIZE: Your name or organization name
-  author: "Your Name"
-
-  # CUSTOMIZE: GitHub repository URL (create before publishing)
-  repository: "https://github.com/your-org/spec-kit-preset-my-preset"
-
-  # REVIEW: License (MIT is recommended for open source)
-  license: "MIT"
-
-# Requirements for this preset
-requires:
-  # CUSTOMIZE: Minimum spec-kit version required
-  speckit_version: ">=0.1.0"
-
-# Templates provided by this preset
-provides:
-  templates:
-    # CUSTOMIZE: Define your template overrides
-    # Templates are document scaffolds (spec-template.md, plan-template.md, etc.)
-    - type: "template"
-      name: "spec-template"
-      file: "templates/spec-template.md"
-      description: "Custom feature specification template"
-      replaces: "spec-template"  # Which core template this overrides (optional)
-
-    # ADD MORE TEMPLATES: Copy this block for each template
-    # - type: "template"
-    #   name: "plan-template"
-    #   file: "templates/plan-template.md"
-    #   description: "Custom plan template"
-    #   replaces: "plan-template"
-
-    # OVERRIDE EXTENSION TEMPLATES:
-    # Presets sit above extensions in the resolution stack, so you can
-    # override templates provided by any installed extension.
-    # For example, if the "myext" extension provides a spec-template,
-    # the preset's version above will take priority automatically.
-
-    # Override a template provided by the "myext" extension:
-    - type: "template"
-      name: "myext-template"
-      file: "templates/myext-template.md"
-      description: "Override myext's report template"
-      replaces: "myext-template"
-
-    # Command overrides (AI agent workflow prompts)
-    # Presets can override both core and extension commands.
-    # Commands are automatically registered into all detected agent
-    # directories (.claude/commands/, .gemini/commands/, etc.)
-
-    # Override a core command:
-    - type: "command"
-      name: "speckit.specify"
-      file: "commands/speckit.specify.md"
-      description: "Custom specification command"
-      replaces: "speckit.specify"
-
-    # Override an extension command (e.g. from the "myext" extension):
-    - type: "command"
-      name: "speckit.myext.myextcmd"
-      file: "commands/speckit.myext.myextcmd.md"
-      description: "Override myext's myextcmd command with custom workflow"
-      replaces: "speckit.myext.myextcmd"
-
-    # Script templates (reserved for future use)
-    # - type: "script"
-    #   name: "create-new-feature"
-    #   file: "scripts/bash/create-new-feature.sh"
-    #   description: "Custom feature creation script"
-    #   replaces: "create-new-feature"
-
-# CUSTOMIZE: Add relevant tags (2-5 recommended)
-# Used for discovery in catalog
-tags:
-  - "example"
-  - "preset"

presets/scaffold/templates/myext-template.md

@@ -1,24 +0,0 @@
-# MyExt Report
-
-> This template overrides the one provided by the "myext" extension.
-> Customize it to match your needs.
-
-## Summary
-
-Brief summary of the report.
-
-## Details
-
-- Detail 1
-- Detail 2
-
-## Actions
-
-- [ ] Action 1
-- [ ] Action 2
-
-<!--
-  CUSTOMIZE: This template takes priority over the myext extension's
-  version of myext-template. The extension's original is still available
-  if you remove this preset.
--->

presets/scaffold/templates/spec-template.md

@@ -1,18 +0,0 @@
-# Feature Specification: [FEATURE NAME]
-
-**Created**: [DATE]
-**Status**: Draft
-
-## Overview
-
-[Brief description of the feature]
-
-## Requirements
-
-- [ ] Requirement 1
-- [ ] Requirement 2
-
-## Acceptance Criteria
-
-- [ ] Criterion 1
-- [ ] Criterion 2

presets/self-test/commands/speckit.specify.md

@@ -1,15 +0,0 @@
----
-description: "Self-test override of the specify command"
----
-
-<!-- preset:self-test -->
-
-You are following the self-test preset's version of the specify command.
-
-When creating a specification, follow this process:
-
-1. Read the user's requirements from $ARGUMENTS
-2. Create a specification document using the spec-template
-3. Include all standard sections plus the self-test marker
-
-> This command is provided by the self-test preset.

presets/self-test/preset.yml

@@ -1,61 +0,0 @@
-schema_version: "1.0"
-
-preset:
-  id: "self-test"
-  name: "Self-Test Preset"
-  version: "1.0.0"
-  description: "A preset that overrides all core templates for testing purposes"
-  author: "github"
-  repository: "https://github.com/github/spec-kit"
-  license: "MIT"
-
-requires:
-  speckit_version: ">=0.1.0"
-
-provides:
-  templates:
-    - type: "template"
-      name: "spec-template"
-      file: "templates/spec-template.md"
-      description: "Self-test spec template"
-      replaces: "spec-template"
-
-    - type: "template"
-      name: "plan-template"
-      file: "templates/plan-template.md"
-      description: "Self-test plan template"
-      replaces: "plan-template"
-
-    - type: "template"
-      name: "tasks-template"
-      file: "templates/tasks-template.md"
-      description: "Self-test tasks template"
-      replaces: "tasks-template"
-
-    - type: "template"
-      name: "checklist-template"
-      file: "templates/checklist-template.md"
-      description: "Self-test checklist template"
-      replaces: "checklist-template"
-
-    - type: "template"
-      name: "constitution-template"
-      file: "templates/constitution-template.md"
-      description: "Self-test constitution template"
-      replaces: "constitution-template"
-
-    - type: "template"
-      name: "agent-file-template"
-      file: "templates/agent-file-template.md"
-      description: "Self-test agent file template"
-      replaces: "agent-file-template"
-
-    - type: "command"
-      name: "speckit.specify"
-      file: "commands/speckit.specify.md"
-      description: "Self-test override of the specify command"
-      replaces: "speckit.specify"
-
-tags:
-  - "testing"
-  - "self-test"

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

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

presets/self-test/templates/checklist-template.md

@@ -1,15 +0,0 @@
-# Checklist (Self-Test Preset)
-
-<!-- preset:self-test -->
-
-> This template is provided by the self-test preset.
-
-## Pre-Implementation
-
-- [ ] Spec reviewed
-- [ ] Plan approved
-
-## Post-Implementation
-
-- [ ] Tests passing
-- [ ] Documentation updated

presets/self-test/templates/constitution-template.md

@@ -1,15 +0,0 @@
-# Constitution (Self-Test Preset)
-
-<!-- preset:self-test -->
-
-> This template is provided by the self-test preset.
-
-## Principles
-
-1. Principle 1
-2. Principle 2
-
-## Guidelines
-
-- Guideline 1
-- Guideline 2

presets/self-test/templates/plan-template.md

@@ -1,22 +0,0 @@
-# Implementation Plan (Self-Test Preset)
-
-<!-- preset:self-test -->
-
-> This template is provided by the self-test preset.
-
-## Approach
-
-Describe the implementation approach.
-
-## Steps
-
-1. Step 1
-2. Step 2
-
-## Dependencies
-
-- Dependency 1
-
-## Risks
-
-- Risk 1

presets/self-test/templates/spec-template.md

@@ -1,23 +0,0 @@
-# Feature Specification (Self-Test Preset)
-
-<!-- preset:self-test -->
-
-> This template is provided by the self-test preset.
-
-## Overview
-
-Brief description of the feature.
-
-## Requirements
-
-- Requirement 1
-- Requirement 2
-
-## Design
-
-Describe the design approach.
-
-## Acceptance Criteria
-
-- [ ] Criterion 1
-- [ ] Criterion 2

presets/self-test/templates/tasks-template.md

@@ -1,17 +0,0 @@
-# Tasks (Self-Test Preset)
-
-<!-- preset:self-test -->
-
-> This template is provided by the self-test preset.
-
-## Task List
-
-- [ ] Task 1
-- [ ] Task 2
-
-## Estimation
-
-| Task | Estimate |
-|------|----------|
-| Task 1 | TBD |
-| Task 2 | TBD |

pyproject.toml

@@ -1,54 +1,44 @@
 [project]
 name = "specify-cli"
-version = "0.2.1"
-description = "Specify CLI, part of GitHub Spec Kit. A tool to bootstrap your projects for Spec-Driven Development (SDD)."
+version = "0.0.4"
+description = "Setup tool for Specify spec-driven development projects"
 requires-python = ">=3.11"
 dependencies = [
+    # Existing spec-kit dependencies
     "typer",
-    "click>=8.1",
-    "rich",
+    "rich>=13.0.0",
     "httpx[socks]",
     "platformdirs",
     "readchar",
     "truststore>=0.10.4",
-    "pyyaml>=6.0",
-    "packaging>=23.0",
-    "pathspec>=0.12.0",
+    # APM dependencies (from awd-cli, excluding runtime/embargo items)
+    "click>=8.0.0",
+    "colorama>=0.4.6",
+    "pyyaml>=6.0.0",
+    "requests>=2.28.0",
+    "python-frontmatter>=1.0.0",
+    "tomli>=1.2.0; python_version<'3.11'",
+    "toml>=0.10.2",
+    "rich-click>=1.7.0",
+    "watchdog>=3.0.0",
+    "GitPython>=3.1.0",
 ]
 
 [project.scripts]
 specify = "specify_cli:main"
 
+[project.optional-dependencies]
+dev = [
+    "pytest>=7.0.0",
+    "pytest-cov>=4.0.0",
+    "black>=23.0.0",
+    "isort>=5.0.0",
+    "mypy>=1.0.0",
+]
+
 [build-system]
 requires = ["hatchling"]
 build-backend = "hatchling.build"
 
 [tool.hatch.build.targets.wheel]
-packages = ["src/specify_cli"]
-
-[project.optional-dependencies]
-test = [
-    "pytest>=7.0",
-    "pytest-cov>=4.0",
-]
-
-[tool.pytest.ini_options]
-testpaths = ["tests"]
-python_files = ["test_*.py"]
-python_classes = ["Test*"]
-python_functions = ["test_*"]
-addopts = [
-    "-v",
-    "--strict-markers",
-    "--tb=short",
-]
-
-[tool.coverage.run]
-source = ["src"]
-omit = ["*/tests/*", "*/__pycache__/*"]
-
-[tool.coverage.report]
-precision = 2
-show_missing = true
-skip_covered = false
-
+packages = ["src/specify_cli", "src/apm_cli"]

scripts/bash/check-prerequisites.sh

@@ -1,166 +0,0 @@
-#!/usr/bin/env bash
-
-# Consolidated prerequisite checking script
-#
-# This script provides unified prerequisite checking for Spec-Driven Development workflow.
-# It replaces the functionality previously spread across multiple scripts.
-#
-# Usage: ./check-prerequisites.sh [OPTIONS]
-#
-# OPTIONS:
-#   --json              Output in JSON format
-#   --require-tasks     Require tasks.md to exist (for implementation phase)
-#   --include-tasks     Include tasks.md in AVAILABLE_DOCS list
-#   --paths-only        Only output path variables (no validation)
-#   --help, -h          Show help message
-#
-# OUTPUTS:
-#   JSON mode: {"FEATURE_DIR":"...", "AVAILABLE_DOCS":["..."]}
-#   Text mode: FEATURE_DIR:... \n AVAILABLE_DOCS: \n ✓/✗ file.md
-#   Paths only: REPO_ROOT: ... \n BRANCH: ... \n FEATURE_DIR: ... etc.
-
-set -e
-
-# Parse command line arguments
-JSON_MODE=false
-REQUIRE_TASKS=false
-INCLUDE_TASKS=false
-PATHS_ONLY=false
-
-for arg in "$@"; do
-    case "$arg" in
-        --json)
-            JSON_MODE=true
-            ;;
-        --require-tasks)
-            REQUIRE_TASKS=true
-            ;;
-        --include-tasks)
-            INCLUDE_TASKS=true
-            ;;
-        --paths-only)
-            PATHS_ONLY=true
-            ;;
-        --help|-h)
-            cat << 'EOF'
-Usage: check-prerequisites.sh [OPTIONS]
-
-Consolidated prerequisite checking for Spec-Driven Development workflow.
-
-OPTIONS:
-  --json              Output in JSON format
-  --require-tasks     Require tasks.md to exist (for implementation phase)
-  --include-tasks     Include tasks.md in AVAILABLE_DOCS list
-  --paths-only        Only output path variables (no prerequisite validation)
-  --help, -h          Show this help message
-
-EXAMPLES:
-  # Check task prerequisites (plan.md required)
-  ./check-prerequisites.sh --json
-  
-  # Check implementation prerequisites (plan.md + tasks.md required)
-  ./check-prerequisites.sh --json --require-tasks --include-tasks
-  
-  # Get feature paths only (no validation)
-  ./check-prerequisites.sh --paths-only
-  
-EOF
-            exit 0
-            ;;
-        *)
-            echo "ERROR: Unknown option '$arg'. Use --help for usage information." >&2
-            exit 1
-            ;;
-    esac
-done
-
-# Source common functions
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/common.sh"
-
-# Get feature paths and validate branch
-eval $(get_feature_paths)
-check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
-
-# 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)
-        printf '{"REPO_ROOT":"%s","BRANCH":"%s","FEATURE_DIR":"%s","FEATURE_SPEC":"%s","IMPL_PLAN":"%s","TASKS":"%s"}\n' \
-            "$REPO_ROOT" "$CURRENT_BRANCH" "$FEATURE_DIR" "$FEATURE_SPEC" "$IMPL_PLAN" "$TASKS"
-    else
-        echo "REPO_ROOT: $REPO_ROOT"
-        echo "BRANCH: $CURRENT_BRANCH"
-        echo "FEATURE_DIR: $FEATURE_DIR"
-        echo "FEATURE_SPEC: $FEATURE_SPEC"
-        echo "IMPL_PLAN: $IMPL_PLAN"
-        echo "TASKS: $TASKS"
-    fi
-    exit 0
-fi
-
-# Validate required directories and files
-if [[ ! -d "$FEATURE_DIR" ]]; then
-    echo "ERROR: Feature directory not found: $FEATURE_DIR" >&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.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.tasks first to create the task list." >&2
-    exit 1
-fi
-
-# Build list of available documents
-docs=()
-
-# Always check these optional docs
-[[ -f "$RESEARCH" ]] && docs+=("research.md")
-[[ -f "$DATA_MODEL" ]] && docs+=("data-model.md")
-
-# Check contracts directory (only if it exists and has files)
-if [[ -d "$CONTRACTS_DIR" ]] && [[ -n "$(ls -A "$CONTRACTS_DIR" 2>/dev/null)" ]]; then
-    docs+=("contracts/")
-fi
-
-[[ -f "$QUICKSTART" ]] && docs+=("quickstart.md")
-
-# Include tasks.md if requested and it exists
-if $INCLUDE_TASKS && [[ -f "$TASKS" ]]; then
-    docs+=("tasks.md")
-fi
-
-# Output results
-if $JSON_MODE; then
-    # Build JSON array of documents
-    if [[ ${#docs[@]} -eq 0 ]]; then
-        json_docs="[]"
-    else
-        json_docs=$(printf '"%s",' "${docs[@]}")
-        json_docs="[${json_docs%,}]"
-    fi
-    
-    printf '{"FEATURE_DIR":"%s","AVAILABLE_DOCS":%s}\n' "$FEATURE_DIR" "$json_docs"
-else
-    # Text output
-    echo "FEATURE_DIR:$FEATURE_DIR"
-    echo "AVAILABLE_DOCS:"
-    
-    # Show status of each potential document
-    check_file "$RESEARCH" "research.md"
-    check_file "$DATA_MODEL" "data-model.md"
-    check_dir "$CONTRACTS_DIR" "contracts/"
-    check_file "$QUICKSTART" "quickstart.md"
-    
-    if $INCLUDE_TASKS; then
-        check_file "$TASKS" "tasks.md"
-    fi
-fi

scripts/bash/check-task-prerequisites.sh

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+set -e
+JSON_MODE=false
+for arg in "$@"; do case "$arg" in --json) JSON_MODE=true ;; --help|-h) echo "Usage: $0 [--json]"; exit 0 ;; esac; done
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "$SCRIPT_DIR/common.sh"
+eval $(get_feature_paths)
+check_feature_branch "$CURRENT_BRANCH" || exit 1
+if [[ ! -d "$FEATURE_DIR" ]]; then echo "ERROR: Feature directory not found: $FEATURE_DIR"; echo "Run /specify first."; exit 1; fi
+if [[ ! -f "$IMPL_PLAN" ]]; then echo "ERROR: plan.md not found in $FEATURE_DIR"; echo "Run /plan first."; exit 1; fi
+if $JSON_MODE; then
+  docs=(); [[ -f "$RESEARCH" ]] && docs+=("research.md"); [[ -f "$DATA_MODEL" ]] && docs+=("data-model.md"); ([[ -d "$CONTRACTS_DIR" ]] && [[ -n "$(ls -A "$CONTRACTS_DIR" 2>/dev/null)" ]]) && docs+=("contracts/"); [[ -f "$QUICKSTART" ]] && docs+=("quickstart.md");
+  json_docs=$(printf '"%s",' "${docs[@]}"); json_docs="[${json_docs%,}]"; printf '{"FEATURE_DIR":"%s","AVAILABLE_DOCS":%s}\n' "$FEATURE_DIR" "$json_docs"
+else
+  echo "FEATURE_DIR:$FEATURE_DIR"; echo "AVAILABLE_DOCS:"; check_file "$RESEARCH" "research.md"; check_file "$DATA_MODEL" "data-model.md"; check_dir "$CONTRACTS_DIR" "contracts/"; check_file "$QUICKSTART" "quickstart.md"; fi

scripts/bash/common.sh

@@ -1,145 +1,27 @@
 #!/usr/bin/env bash
-# Common functions and variables for all scripts
+# (Moved to scripts/bash/) Common functions and variables for all scripts
 
-# Get repository root, with fallback for non-git repositories
-get_repo_root() {
-    if git rev-parse --show-toplevel >/dev/null 2>&1; then
-        git rev-parse --show-toplevel
-    else
-        # Fall back to script location for non-git repos
-        local script_dir="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-        (cd "$script_dir/../../.." && pwd)
-    fi
-}
-
-# Get current branch, with fallback for non-git repositories
-get_current_branch() {
-    # First check if SPECIFY_FEATURE environment variable is set
-    if [[ -n "${SPECIFY_FEATURE:-}" ]]; then
-        echo "$SPECIFY_FEATURE"
-        return
-    fi
-
-    # Then check git if available
-    if git rev-parse --abbrev-ref HEAD >/dev/null 2>&1; then
-        git rev-parse --abbrev-ref HEAD
-        return
-    fi
-
-    # For non-git repos, try to find the latest feature directory
-    local repo_root=$(get_repo_root)
-    local specs_dir="$repo_root/specs"
-
-    if [[ -d "$specs_dir" ]]; then
-        local latest_feature=""
-        local highest=0
-
-        for dir in "$specs_dir"/*; do
-            if [[ -d "$dir" ]]; then
-                local dirname=$(basename "$dir")
-                if [[ "$dirname" =~ ^([0-9]{3})- ]]; then
-                    local number=${BASH_REMATCH[1]}
-                    number=$((10#$number))
-                    if [[ "$number" -gt "$highest" ]]; then
-                        highest=$number
-                        latest_feature=$dirname
-                    fi
-                fi
-            fi
-        done
-
-        if [[ -n "$latest_feature" ]]; then
-            echo "$latest_feature"
-            return
-        fi
-    fi
-
-    echo "main"  # Final fallback
-}
-
-# Check if we have git available
-has_git() {
-    git rev-parse --show-toplevel >/dev/null 2>&1
-}
+get_repo_root() { git rev-parse --show-toplevel; }
+get_current_branch() { git rev-parse --abbrev-ref HEAD; }
 
 check_feature_branch() {
     local branch="$1"
-    local has_git_repo="$2"
-
-    # For non-git repos, we can't enforce branch naming but still provide output
-    if [[ "$has_git_repo" != "true" ]]; then
-        echo "[specify] Warning: Git repository not detected; skipped branch validation" >&2
-        return 0
-    fi
-
     if [[ ! "$branch" =~ ^[0-9]{3}- ]]; then
         echo "ERROR: Not on a feature branch. Current branch: $branch" >&2
         echo "Feature branches should be named like: 001-feature-name" >&2
         return 1
-    fi
-
-    return 0
+    fi; return 0
 }
 
 get_feature_dir() { echo "$1/specs/$2"; }
 
-# Find feature directory by numeric prefix instead of exact branch match
-# This allows multiple branches to work on the same spec (e.g., 004-fix-bug, 004-add-feature)
-find_feature_dir_by_prefix() {
-    local repo_root="$1"
-    local branch_name="$2"
-    local specs_dir="$repo_root/specs"
-
-    # Extract numeric prefix from branch (e.g., "004" from "004-whatever")
-    if [[ ! "$branch_name" =~ ^([0-9]{3})- ]]; then
-        # If branch doesn't have numeric prefix, fall back to exact match
-        echo "$specs_dir/$branch_name"
-        return
-    fi
-
-    local prefix="${BASH_REMATCH[1]}"
-
-    # Search for directories in specs/ that start with this prefix
-    local matches=()
-    if [[ -d "$specs_dir" ]]; then
-        for dir in "$specs_dir"/"$prefix"-*; do
-            if [[ -d "$dir" ]]; then
-                matches+=("$(basename "$dir")")
-            fi
-        done
-    fi
-
-    # Handle results
-    if [[ ${#matches[@]} -eq 0 ]]; then
-        # No match found - return the branch name path (will fail later with clear error)
-        echo "$specs_dir/$branch_name"
-    elif [[ ${#matches[@]} -eq 1 ]]; then
-        # Exactly one match - perfect!
-        echo "$specs_dir/${matches[0]}"
-    else
-        # Multiple matches - this shouldn't happen with proper naming convention
-        echo "ERROR: Multiple spec directories found with prefix '$prefix': ${matches[*]}" >&2
-        echo "Please ensure only one spec directory exists per numeric prefix." >&2
-        echo "$specs_dir/$branch_name"  # Return something to avoid breaking the script
-    fi
-}
-
 get_feature_paths() {
     local repo_root=$(get_repo_root)
     local current_branch=$(get_current_branch)
-    local has_git_repo="false"
-
-    if has_git; then
-        has_git_repo="true"
-    fi
-
-    # Use prefix-based lookup to support multiple branches per spec
-    local feature_dir=$(find_feature_dir_by_prefix "$repo_root" "$current_branch")
-
+    local feature_dir=$(get_feature_dir "$repo_root" "$current_branch")
     cat <<EOF
 REPO_ROOT='$repo_root'
 CURRENT_BRANCH='$current_branch'
-HAS_GIT='$has_git_repo'
 FEATURE_DIR='$feature_dir'
 FEATURE_SPEC='$feature_dir/spec.md'
 IMPL_PLAN='$feature_dir/plan.md'
@@ -153,78 +35,3 @@ EOF
 
 check_file() { [[ -f "$1" ]] && echo "  ✓ $2" || echo "  ✗ $2"; }
 check_dir() { [[ -d "$1" && -n $(ls -A "$1" 2>/dev/null) ]] && echo "  ✓ $2" || echo "  ✗ $2"; }
-
-# Resolve a template name to a file path using the priority stack:
-#   1. .specify/templates/overrides/
-#   2. .specify/presets/<preset-id>/templates/ (sorted by priority from .registry)
-#   3. .specify/extensions/<ext-id>/templates/
-#   4. .specify/templates/ (core)
-resolve_template() {
-    local template_name="$1"
-    local repo_root="$2"
-    local base="$repo_root/.specify/templates"
-
-    # Priority 1: Project overrides
-    local override="$base/overrides/${template_name}.md"
-    [ -f "$override" ] && echo "$override" && return 0
-
-    # Priority 2: Installed presets (sorted by priority from .registry)
-    local presets_dir="$repo_root/.specify/presets"
-    if [ -d "$presets_dir" ]; then
-        local registry_file="$presets_dir/.registry"
-        if [ -f "$registry_file" ] && command -v python3 >/dev/null 2>&1; then
-            # Read preset IDs sorted by priority (lower number = higher precedence)
-            local sorted_presets
-            sorted_presets=$(SPECKIT_REGISTRY="$registry_file" python3 -c "
-import json, sys, os
-try:
-    with open(os.environ['SPECKIT_REGISTRY']) as f:
-        data = json.load(f)
-    presets = data.get('presets', {})
-    for pid, meta in sorted(presets.items(), key=lambda x: x[1].get('priority', 10)):
-        print(pid)
-except Exception:
-    sys.exit(1)
-" 2>/dev/null)
-            if [ $? -eq 0 ] && [ -n "$sorted_presets" ]; then
-                while IFS= read -r preset_id; do
-                    local candidate="$presets_dir/$preset_id/templates/${template_name}.md"
-                    [ -f "$candidate" ] && echo "$candidate" && return 0
-                done <<< "$sorted_presets"
-            else
-                # python3 returned empty list — fall through to directory scan
-                for preset in "$presets_dir"/*/; do
-                    [ -d "$preset" ] || continue
-                    local candidate="$preset/templates/${template_name}.md"
-                    [ -f "$candidate" ] && echo "$candidate" && return 0
-                done
-            fi
-        else
-            # Fallback: alphabetical directory order (no python3 available)
-            for preset in "$presets_dir"/*/; do
-                [ -d "$preset" ] || continue
-                local candidate="$preset/templates/${template_name}.md"
-                [ -f "$candidate" ] && echo "$candidate" && return 0
-            done
-        fi
-    fi
-
-    # Priority 3: Extension-provided templates
-    local ext_dir="$repo_root/.specify/extensions"
-    if [ -d "$ext_dir" ]; then
-        for ext in "$ext_dir"/*/; do
-            [ -d "$ext" ] || continue
-            # Skip hidden directories (e.g. .backup, .cache)
-            case "$(basename "$ext")" in .*) continue;; esac
-            local candidate="$ext/templates/${template_name}.md"
-            [ -f "$candidate" ] && echo "$candidate" && return 0
-        done
-    fi
-
-    # Priority 4: Core templates
-    local core="$base/${template_name}.md"
-    [ -f "$core" ] && echo "$core" && return 0
-
-    return 1
-}
-

scripts/bash/create-new-feature.sh

@@ -1,308 +1,53 @@
 #!/usr/bin/env bash
-
+# (Moved to scripts/bash/) Create a new feature with branch, directory structure, and template
 set -e
 
 JSON_MODE=false
-SHORT_NAME=""
-BRANCH_NUMBER=""
 ARGS=()
-i=1
-while [ $i -le $# ]; do
-    arg="${!i}"
+for arg in "$@"; do
     case "$arg" in
-        --json) 
-            JSON_MODE=true 
-            ;;
-        --short-name)
-            if [ $((i + 1)) -gt $# ]; then
-                echo 'Error: --short-name requires a value' >&2
-                exit 1
-            fi
-            i=$((i + 1))
-            next_arg="${!i}"
-            # Check if the next argument is another option (starts with --)
-            if [[ "$next_arg" == --* ]]; then
-                echo 'Error: --short-name requires a value' >&2
-                exit 1
-            fi
-            SHORT_NAME="$next_arg"
-            ;;
-        --number)
-            if [ $((i + 1)) -gt $# ]; then
-                echo 'Error: --number requires a value' >&2
-                exit 1
-            fi
-            i=$((i + 1))
-            next_arg="${!i}"
-            if [[ "$next_arg" == --* ]]; then
-                echo 'Error: --number requires a value' >&2
-                exit 1
-            fi
-            BRANCH_NUMBER="$next_arg"
-            ;;
-        --help|-h) 
-            echo "Usage: $0 [--json] [--short-name <name>] [--number N] <feature_description>"
-            echo ""
-            echo "Options:"
-            echo "  --json              Output in JSON format"
-            echo "  --short-name <name> Provide a custom short name (2-4 words) for the branch"
-            echo "  --number N          Specify branch number manually (overrides auto-detection)"
-            echo "  --help, -h          Show this help message"
-            echo ""
-            echo "Examples:"
-            echo "  $0 'Add user authentication system' --short-name 'user-auth'"
-            echo "  $0 'Implement OAuth2 integration for API' --number 5"
-            exit 0
-            ;;
-        *) 
-            ARGS+=("$arg") 
-            ;;
+        --json) JSON_MODE=true ;;
+        --help|-h) echo "Usage: $0 [--json] <feature_description>"; exit 0 ;;
+        *) ARGS+=("$arg") ;;
     esac
-    i=$((i + 1))
 done
 
 FEATURE_DESCRIPTION="${ARGS[*]}"
 if [ -z "$FEATURE_DESCRIPTION" ]; then
-    echo "Usage: $0 [--json] [--short-name <name>] [--number N] <feature_description>" >&2
+    echo "Usage: $0 [--json] <feature_description>" >&2
     exit 1
 fi
 
-# Trim whitespace and validate description is not empty (e.g., user passed only whitespace)
-FEATURE_DESCRIPTION=$(echo "$FEATURE_DESCRIPTION" | xargs)
-if [ -z "$FEATURE_DESCRIPTION" ]; then
-    echo "Error: Feature description cannot be empty or contain only whitespace" >&2
-    exit 1
-fi
-
-# Function to find the repository root by searching for existing project markers
-find_repo_root() {
-    local dir="$1"
-    while [ "$dir" != "/" ]; do
-        if [ -d "$dir/.git" ] || [ -d "$dir/.specify" ]; then
-            echo "$dir"
-            return 0
-        fi
-        dir="$(dirname "$dir")"
-    done
-    return 1
-}
-
-# Function to get highest number from specs directory
-get_highest_from_specs() {
-    local specs_dir="$1"
-    local highest=0
-    
-    if [ -d "$specs_dir" ]; then
-        for dir in "$specs_dir"/*; do
-            [ -d "$dir" ] || continue
-            dirname=$(basename "$dir")
-            number=$(echo "$dirname" | grep -o '^[0-9]\+' || echo "0")
-            number=$((10#$number))
-            if [ "$number" -gt "$highest" ]; then
-                highest=$number
-            fi
-        done
-    fi
-    
-    echo "$highest"
-}
-
-# Function to get highest number from git branches
-get_highest_from_branches() {
-    local highest=0
-    
-    # Get all branches (local and remote)
-    branches=$(git branch -a 2>/dev/null || echo "")
-    
-    if [ -n "$branches" ]; then
-        while IFS= read -r branch; do
-            # Clean branch name: remove leading markers and remote prefixes
-            clean_branch=$(echo "$branch" | sed 's/^[* ]*//; s|^remotes/[^/]*/||')
-            
-            # Extract feature number if branch matches pattern ###-*
-            if echo "$clean_branch" | grep -q '^[0-9]\{3\}-'; then
-                number=$(echo "$clean_branch" | grep -o '^[0-9]\{3\}' || echo "0")
-                number=$((10#$number))
-                if [ "$number" -gt "$highest" ]; then
-                    highest=$number
-                fi
-            fi
-        done <<< "$branches"
-    fi
-    
-    echo "$highest"
-}
-
-# Function to check existing branches (local and remote) and return next available number
-check_existing_branches() {
-    local specs_dir="$1"
-
-    # Fetch all remotes to get latest branch info (suppress errors if no remotes)
-    git fetch --all --prune 2>/dev/null || true
-
-    # Get highest number from ALL branches (not just matching short name)
-    local highest_branch=$(get_highest_from_branches)
-
-    # Get highest number from ALL specs (not just matching short name)
-    local highest_spec=$(get_highest_from_specs "$specs_dir")
-
-    # Take the maximum of both
-    local max_num=$highest_branch
-    if [ "$highest_spec" -gt "$max_num" ]; then
-        max_num=$highest_spec
-    fi
-
-    # Return next number
-    echo $((max_num + 1))
-}
-
-# Function to clean and format a branch name
-clean_branch_name() {
-    local name="$1"
-    echo "$name" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/-\+/-/g' | sed 's/^-//' | sed 's/-$//'
-}
-
-# Resolve repository root. Prefer git information when available, but fall back
-# to searching for repository markers so the workflow still functions in repositories that
-# were initialised with --no-git.
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/common.sh"
-
-if git rev-parse --show-toplevel >/dev/null 2>&1; then
-    REPO_ROOT=$(git rev-parse --show-toplevel)
-    HAS_GIT=true
-else
-    REPO_ROOT="$(find_repo_root "$SCRIPT_DIR")"
-    if [ -z "$REPO_ROOT" ]; then
-        echo "Error: Could not determine repository root. Please run this script from within the repository." >&2
-        exit 1
-    fi
-    HAS_GIT=false
-fi
-
-cd "$REPO_ROOT"
-
+REPO_ROOT=$(git rev-parse --show-toplevel)
 SPECS_DIR="$REPO_ROOT/specs"
 mkdir -p "$SPECS_DIR"
 
-# Function to generate branch name with stop word filtering and length filtering
-generate_branch_name() {
-    local description="$1"
-    
-    # Common stop words to filter out
-    local stop_words="^(i|a|an|the|to|for|of|in|on|at|by|with|from|is|are|was|were|be|been|being|have|has|had|do|does|did|will|would|should|could|can|may|might|must|shall|this|that|these|those|my|your|our|their|want|need|add|get|set)$"
-    
-    # Convert to lowercase and split into words
-    local clean_name=$(echo "$description" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/ /g')
-    
-    # Filter words: remove stop words and words shorter than 3 chars (unless they're uppercase acronyms in original)
-    local meaningful_words=()
-    for word in $clean_name; do
-        # Skip empty words
-        [ -z "$word" ] && continue
-        
-        # Keep words that are NOT stop words AND (length >= 3 OR are potential acronyms)
-        if ! echo "$word" | grep -qiE "$stop_words"; then
-            if [ ${#word} -ge 3 ]; then
-                meaningful_words+=("$word")
-            elif echo "$description" | grep -q "\b${word^^}\b"; then
-                # Keep short words if they appear as uppercase in original (likely acronyms)
-                meaningful_words+=("$word")
-            fi
-        fi
+HIGHEST=0
+if [ -d "$SPECS_DIR" ]; then
+    for dir in "$SPECS_DIR"/*; do
+        [ -d "$dir" ] || continue
+        dirname=$(basename "$dir")
+        number=$(echo "$dirname" | grep -o '^[0-9]\+' || echo "0")
+        number=$((10#$number))
+        if [ "$number" -gt "$HIGHEST" ]; then HIGHEST=$number; fi
     done
-    
-    # If we have meaningful words, use first 3-4 of them
-    if [ ${#meaningful_words[@]} -gt 0 ]; then
-        local max_words=3
-        if [ ${#meaningful_words[@]} -eq 4 ]; then max_words=4; fi
-        
-        local result=""
-        local count=0
-        for word in "${meaningful_words[@]}"; do
-            if [ $count -ge $max_words ]; then break; fi
-            if [ -n "$result" ]; then result="$result-"; fi
-            result="$result$word"
-            count=$((count + 1))
-        done
-        echo "$result"
-    else
-        # Fallback to original logic if no meaningful words found
-        local cleaned=$(clean_branch_name "$description")
-        echo "$cleaned" | tr '-' '\n' | grep -v '^$' | head -3 | tr '\n' '-' | sed 's/-$//'
-    fi
-}
-
-# Generate branch name
-if [ -n "$SHORT_NAME" ]; then
-    # Use provided short name, just clean it up
-    BRANCH_SUFFIX=$(clean_branch_name "$SHORT_NAME")
-else
-    # Generate from description with smart filtering
-    BRANCH_SUFFIX=$(generate_branch_name "$FEATURE_DESCRIPTION")
 fi
 
-# Determine branch number
-if [ -z "$BRANCH_NUMBER" ]; then
-    if [ "$HAS_GIT" = true ]; then
-        # Check existing branches on remotes
-        BRANCH_NUMBER=$(check_existing_branches "$SPECS_DIR")
-    else
-        # Fall back to local directory check
-        HIGHEST=$(get_highest_from_specs "$SPECS_DIR")
-        BRANCH_NUMBER=$((HIGHEST + 1))
-    fi
-fi
+NEXT=$((HIGHEST + 1))
+FEATURE_NUM=$(printf "%03d" "$NEXT")
 
-# Force base-10 interpretation to prevent octal conversion (e.g., 010 → 8 in octal, but should be 10 in decimal)
-FEATURE_NUM=$(printf "%03d" "$((10#$BRANCH_NUMBER))")
-BRANCH_NAME="${FEATURE_NUM}-${BRANCH_SUFFIX}"
+BRANCH_NAME=$(echo "$FEATURE_DESCRIPTION" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/-\+/-/g' | sed 's/^-//' | sed 's/-$//')
+WORDS=$(echo "$BRANCH_NAME" | tr '-' '\n' | grep -v '^$' | head -3 | tr '\n' '-' | sed 's/-$//')
+BRANCH_NAME="${FEATURE_NUM}-${WORDS}"
 
-# GitHub enforces a 244-byte limit on branch names
-# Validate and truncate if necessary
-MAX_BRANCH_LENGTH=244
-if [ ${#BRANCH_NAME} -gt $MAX_BRANCH_LENGTH ]; then
-    # Calculate how much we need to trim from suffix
-    # Account for: feature number (3) + hyphen (1) = 4 chars
-    MAX_SUFFIX_LENGTH=$((MAX_BRANCH_LENGTH - 4))
-    
-    # Truncate suffix at word boundary if possible
-    TRUNCATED_SUFFIX=$(echo "$BRANCH_SUFFIX" | cut -c1-$MAX_SUFFIX_LENGTH)
-    # Remove trailing hyphen if truncation created one
-    TRUNCATED_SUFFIX=$(echo "$TRUNCATED_SUFFIX" | sed 's/-$//')
-    
-    ORIGINAL_BRANCH_NAME="$BRANCH_NAME"
-    BRANCH_NAME="${FEATURE_NUM}-${TRUNCATED_SUFFIX}"
-    
-    >&2 echo "[specify] Warning: Branch name exceeded GitHub's 244-byte limit"
-    >&2 echo "[specify] Original: $ORIGINAL_BRANCH_NAME (${#ORIGINAL_BRANCH_NAME} bytes)"
-    >&2 echo "[specify] Truncated to: $BRANCH_NAME (${#BRANCH_NAME} bytes)"
-fi
-
-if [ "$HAS_GIT" = true ]; then
-    if ! git checkout -b "$BRANCH_NAME" 2>/dev/null; then
-        # Check if branch already exists
-        if git branch --list "$BRANCH_NAME" | grep -q .; then
-            >&2 echo "Error: Branch '$BRANCH_NAME' already exists. Please use a different feature name or specify a different number with --number."
-            exit 1
-        else
-            >&2 echo "Error: Failed to create git branch '$BRANCH_NAME'. Please check your git configuration and try again."
-            exit 1
-        fi
-    fi
-else
-    >&2 echo "[specify] Warning: Git repository not detected; skipped branch creation for $BRANCH_NAME"
-fi
+git checkout -b "$BRANCH_NAME"
 
 FEATURE_DIR="$SPECS_DIR/$BRANCH_NAME"
 mkdir -p "$FEATURE_DIR"
 
-TEMPLATE=$(resolve_template "spec-template" "$REPO_ROOT")
+TEMPLATE="$REPO_ROOT/templates/spec-template.md"
 SPEC_FILE="$FEATURE_DIR/spec.md"
-if [ -n "$TEMPLATE" ] && [ -f "$TEMPLATE" ]; then cp "$TEMPLATE" "$SPEC_FILE"; else touch "$SPEC_FILE"; fi
-
-# Set the SPECIFY_FEATURE environment variable for the current session
-export SPECIFY_FEATURE="$BRANCH_NAME"
+if [ -f "$TEMPLATE" ]; then cp "$TEMPLATE" "$SPEC_FILE"; else touch "$SPEC_FILE"; fi
 
 if $JSON_MODE; then
     printf '{"BRANCH_NAME":"%s","SPEC_FILE":"%s","FEATURE_NUM":"%s"}\n' "$BRANCH_NAME" "$SPEC_FILE" "$FEATURE_NUM"
@@ -310,5 +55,4 @@ else
     echo "BRANCH_NAME: $BRANCH_NAME"
     echo "SPEC_FILE: $SPEC_FILE"
     echo "FEATURE_NUM: $FEATURE_NUM"
-    echo "SPECIFY_FEATURE environment variable set to: $BRANCH_NAME"
 fi

scripts/bash/get-feature-paths.sh

@@ -0,0 +1,7 @@
+#!/usr/bin/env bash
+set -e
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "$SCRIPT_DIR/common.sh"
+eval $(get_feature_paths)
+check_feature_branch "$CURRENT_BRANCH" || exit 1
+echo "REPO_ROOT: $REPO_ROOT"; echo "BRANCH: $CURRENT_BRANCH"; echo "FEATURE_DIR: $FEATURE_DIR"; echo "FEATURE_SPEC: $FEATURE_SPEC"; echo "IMPL_PLAN: $IMPL_PLAN"; echo "TASKS: $TASKS"

scripts/bash/setup-plan.sh

@@ -1,61 +1,17 @@
 #!/usr/bin/env bash
-
 set -e
-
-# Parse command line arguments
 JSON_MODE=false
-ARGS=()
-
-for arg in "$@"; do
-    case "$arg" in
-        --json) 
-            JSON_MODE=true 
-            ;;
-        --help|-h) 
-            echo "Usage: $0 [--json]"
-            echo "  --json    Output results in JSON format"
-            echo "  --help    Show this help message"
-            exit 0 
-            ;;
-        *) 
-            ARGS+=("$arg") 
-            ;;
-    esac
-done
-
-# Get script directory and load common functions
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+for arg in "$@"; do case "$arg" in --json) JSON_MODE=true ;; --help|-h) echo "Usage: $0 [--json]"; exit 0 ;; esac; done
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 source "$SCRIPT_DIR/common.sh"
-
-# Get all paths and variables from common functions
 eval $(get_feature_paths)
-
-# Check if we're on a proper feature branch (only for git repos)
-check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
-
-# Ensure the feature directory exists
+check_feature_branch "$CURRENT_BRANCH" || exit 1
 mkdir -p "$FEATURE_DIR"
-
-# Copy plan template if it exists
-TEMPLATE=$(resolve_template "plan-template" "$REPO_ROOT")
-if [[ -n "$TEMPLATE" ]] && [[ -f "$TEMPLATE" ]]; then
-    cp "$TEMPLATE" "$IMPL_PLAN"
-    echo "Copied plan template to $IMPL_PLAN"
-else
-    echo "Warning: Plan template not found"
-    # Create a basic plan file if template doesn't exist
-    touch "$IMPL_PLAN"
-fi
-
-# Output results
+TEMPLATE="$REPO_ROOT/.specify/templates/plan-template.md"
+[[ -f "$TEMPLATE" ]] && cp "$TEMPLATE" "$IMPL_PLAN"
 if $JSON_MODE; then
-    printf '{"FEATURE_SPEC":"%s","IMPL_PLAN":"%s","SPECS_DIR":"%s","BRANCH":"%s","HAS_GIT":"%s"}\n' \
-        "$FEATURE_SPEC" "$IMPL_PLAN" "$FEATURE_DIR" "$CURRENT_BRANCH" "$HAS_GIT"
+  printf '{"FEATURE_SPEC":"%s","IMPL_PLAN":"%s","SPECS_DIR":"%s","BRANCH":"%s"}\n' \
+    "$FEATURE_SPEC" "$IMPL_PLAN" "$FEATURE_DIR" "$CURRENT_BRANCH"
 else
-    echo "FEATURE_SPEC: $FEATURE_SPEC"
-    echo "IMPL_PLAN: $IMPL_PLAN" 
-    echo "SPECS_DIR: $FEATURE_DIR"
-    echo "BRANCH: $CURRENT_BRANCH"
-    echo "HAS_GIT: $HAS_GIT"
+  echo "FEATURE_SPEC: $FEATURE_SPEC"; echo "IMPL_PLAN: $IMPL_PLAN"; echo "SPECS_DIR: $FEATURE_DIR"; echo "BRANCH: $CURRENT_BRANCH"
 fi
-

scripts/bash/update-agent-context.sh

@@ -1,846 +1,57 @@
 #!/usr/bin/env bash
-
-# Update agent context files with information from plan.md
-#
-# This script maintains AI agent context files by parsing feature specifications 
-# and updating agent-specific configuration files with project information.
-#
-# MAIN FUNCTIONS:
-# 1. Environment Validation
-#    - Verifies git repository structure and branch information
-#    - Checks for required plan.md files and templates
-#    - Validates file permissions and accessibility
-#
-# 2. Plan Data Extraction
-#    - Parses plan.md files to extract project metadata
-#    - Identifies language/version, frameworks, databases, and project types
-#    - Handles missing or incomplete specification data gracefully
-#
-# 3. Agent File Management
-#    - Creates new agent context files from templates when needed
-#    - Updates existing agent files with new project information
-#    - Preserves manual additions and custom configurations
-#    - Supports multiple AI agent formats and directory structures
-#
-# 4. Content Generation
-#    - Generates language-specific build/test commands
-#    - Creates appropriate project directory structures
-#    - Updates technology stacks and recent changes sections
-#    - Maintains consistent formatting and timestamps
-#
-# 5. Multi-Agent Support
-#    - Handles agent-specific file paths and naming conventions
-#    - Supports: Claude, Gemini, Copilot, Cursor, Qwen, opencode, Codex, Windsurf, Kilo Code, Auggie CLI, Roo Code, CodeBuddy CLI, Qoder CLI, Amp, SHAI, Tabnine CLI, Kiro CLI, Mistral Vibe, Antigravity or Generic
-#    - Can update single agents or all existing agent files
-#    - Creates default Claude file if no agent files exist
-#
-# Usage: ./update-agent-context.sh [agent_type]
-# Agent types: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|codebuddy|amp|shai|tabnine|kiro-cli|agy|bob|vibe|qodercli|generic
-# Leave empty to update all existing agent files
-
 set -e
-
-# Enable strict error handling
-set -u
-set -o pipefail
-
-#==============================================================================
-# Configuration and Global Variables
-#==============================================================================
-
-# Get script directory and load common functions
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/common.sh"
-
-# Get all paths and variables from common functions
-eval $(get_feature_paths)
-
-NEW_PLAN="$IMPL_PLAN"  # Alias for compatibility with existing code
-AGENT_TYPE="${1:-}"
-
-# Agent-specific file paths  
-CLAUDE_FILE="$REPO_ROOT/CLAUDE.md"
-GEMINI_FILE="$REPO_ROOT/GEMINI.md"
-COPILOT_FILE="$REPO_ROOT/.github/agents/copilot-instructions.md"
-CURSOR_FILE="$REPO_ROOT/.cursor/rules/specify-rules.mdc"
-QWEN_FILE="$REPO_ROOT/QWEN.md"
-AGENTS_FILE="$REPO_ROOT/AGENTS.md"
-WINDSURF_FILE="$REPO_ROOT/.windsurf/rules/specify-rules.md"
-KILOCODE_FILE="$REPO_ROOT/.kilocode/rules/specify-rules.md"
-AUGGIE_FILE="$REPO_ROOT/.augment/rules/specify-rules.md"
-ROO_FILE="$REPO_ROOT/.roo/rules/specify-rules.md"
-CODEBUDDY_FILE="$REPO_ROOT/CODEBUDDY.md"
-QODER_FILE="$REPO_ROOT/QODER.md"
-AMP_FILE="$REPO_ROOT/AGENTS.md"
-SHAI_FILE="$REPO_ROOT/SHAI.md"
-TABNINE_FILE="$REPO_ROOT/TABNINE.md"
-KIRO_FILE="$REPO_ROOT/AGENTS.md"
-AGY_FILE="$REPO_ROOT/.agent/rules/specify-rules.md"
-BOB_FILE="$REPO_ROOT/AGENTS.md"
-VIBE_FILE="$REPO_ROOT/.vibe/agents/specify-agents.md"
-
-# Template file
-TEMPLATE_FILE="$REPO_ROOT/.specify/templates/agent-file-template.md"
-
-# Global variables for parsed plan data
-NEW_LANG=""
-NEW_FRAMEWORK=""
-NEW_DB=""
-NEW_PROJECT_TYPE=""
-
-#==============================================================================
-# Utility Functions
-#==============================================================================
-
-log_info() {
-    echo "INFO: $1"
-}
-
-log_success() {
-    echo "✓ $1"
-}
-
-log_error() {
-    echo "ERROR: $1" >&2
-}
-
-log_warning() {
-    echo "WARNING: $1" >&2
-}
-
-# Cleanup function for temporary files
-cleanup() {
-    local exit_code=$?
-    rm -f /tmp/agent_update_*_$$
-    rm -f /tmp/manual_additions_$$
-    exit $exit_code
-}
-
-# Set up cleanup trap
-trap cleanup EXIT INT TERM
-
-#==============================================================================
-# Validation Functions
-#==============================================================================
-
-validate_environment() {
-    # Check if we have a current branch/feature (git or non-git)
-    if [[ -z "$CURRENT_BRANCH" ]]; then
-        log_error "Unable to determine current feature"
-        if [[ "$HAS_GIT" == "true" ]]; then
-            log_info "Make sure you're on a feature branch"
-        else
-            log_info "Set SPECIFY_FEATURE environment variable or create a feature first"
-        fi
-        exit 1
-    fi
-    
-    # Check if plan.md exists
-    if [[ ! -f "$NEW_PLAN" ]]; then
-        log_error "No plan.md found at $NEW_PLAN"
-        log_info "Make sure you're working on a feature with a corresponding spec directory"
-        if [[ "$HAS_GIT" != "true" ]]; then
-            log_info "Use: export SPECIFY_FEATURE=your-feature-name or create a new feature first"
-        fi
-        exit 1
-    fi
-    
-    # Check if template exists (needed for new files)
-    if [[ ! -f "$TEMPLATE_FILE" ]]; then
-        log_warning "Template file not found at $TEMPLATE_FILE"
-        log_warning "Creating new agent files will fail"
-    fi
-}
-
-#==============================================================================
-# Plan Parsing Functions
-#==============================================================================
-
-extract_plan_field() {
-    local field_pattern="$1"
-    local plan_file="$2"
-    
-    grep "^\*\*${field_pattern}\*\*: " "$plan_file" 2>/dev/null | \
-        head -1 | \
-        sed "s|^\*\*${field_pattern}\*\*: ||" | \
-        sed 's/^[ \t]*//;s/[ \t]*$//' | \
-        grep -v "NEEDS CLARIFICATION" | \
-        grep -v "^N/A$" || echo ""
-}
-
-parse_plan_data() {
-    local plan_file="$1"
-    
-    if [[ ! -f "$plan_file" ]]; then
-        log_error "Plan file not found: $plan_file"
-        return 1
-    fi
-    
-    if [[ ! -r "$plan_file" ]]; then
-        log_error "Plan file is not readable: $plan_file"
-        return 1
-    fi
-    
-    log_info "Parsing plan data from $plan_file"
-    
-    NEW_LANG=$(extract_plan_field "Language/Version" "$plan_file")
-    NEW_FRAMEWORK=$(extract_plan_field "Primary Dependencies" "$plan_file")
-    NEW_DB=$(extract_plan_field "Storage" "$plan_file")
-    NEW_PROJECT_TYPE=$(extract_plan_field "Project Type" "$plan_file")
-    
-    # Log what we found
-    if [[ -n "$NEW_LANG" ]]; then
-        log_info "Found language: $NEW_LANG"
-    else
-        log_warning "No language information found in plan"
-    fi
-    
-    if [[ -n "$NEW_FRAMEWORK" ]]; then
-        log_info "Found framework: $NEW_FRAMEWORK"
-    fi
-    
-    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]]; then
-        log_info "Found database: $NEW_DB"
-    fi
-    
-    if [[ -n "$NEW_PROJECT_TYPE" ]]; then
-        log_info "Found project type: $NEW_PROJECT_TYPE"
-    fi
-}
-
-format_technology_stack() {
-    local lang="$1"
-    local framework="$2"
-    local parts=()
-    
-    # Add non-empty parts
-    [[ -n "$lang" && "$lang" != "NEEDS CLARIFICATION" ]] && parts+=("$lang")
-    [[ -n "$framework" && "$framework" != "NEEDS CLARIFICATION" && "$framework" != "N/A" ]] && parts+=("$framework")
-    
-    # Join with proper formatting
-    if [[ ${#parts[@]} -eq 0 ]]; then
-        echo ""
-    elif [[ ${#parts[@]} -eq 1 ]]; then
-        echo "${parts[0]}"
-    else
-        # Join multiple parts with " + "
-        local result="${parts[0]}"
-        for ((i=1; i<${#parts[@]}; i++)); do
-            result="$result + ${parts[i]}"
-        done
-        echo "$result"
-    fi
-}
-
-#==============================================================================
-# Template and Content Generation Functions
-#==============================================================================
-
-get_project_structure() {
-    local project_type="$1"
-    
-    if [[ "$project_type" == *"web"* ]]; then
-        echo "backend/\\nfrontend/\\ntests/"
-    else
-        echo "src/\\ntests/"
-    fi
-}
-
-get_commands_for_language() {
-    local lang="$1"
-    
-    case "$lang" in
-        *"Python"*)
-            echo "cd src && pytest && ruff check ."
-            ;;
-        *"Rust"*)
-            echo "cargo test && cargo clippy"
-            ;;
-        *"JavaScript"*|*"TypeScript"*)
-            echo "npm test \\&\\& npm run lint"
-            ;;
-        *)
-            echo "# Add commands for $lang"
-            ;;
-    esac
-}
-
-get_language_conventions() {
-    local lang="$1"
-    echo "$lang: Follow standard conventions"
-}
-
-create_new_agent_file() {
-    local target_file="$1"
-    local temp_file="$2"
-    local project_name="$3"
-    local current_date="$4"
-    
-    if [[ ! -f "$TEMPLATE_FILE" ]]; then
-        log_error "Template not found at $TEMPLATE_FILE"
-        return 1
-    fi
-    
-    if [[ ! -r "$TEMPLATE_FILE" ]]; then
-        log_error "Template file is not readable: $TEMPLATE_FILE"
-        return 1
-    fi
-    
-    log_info "Creating new agent context file from template..."
-    
-    if ! cp "$TEMPLATE_FILE" "$temp_file"; then
-        log_error "Failed to copy template file"
-        return 1
-    fi
-    
-    # Replace template placeholders
-    local project_structure
-    project_structure=$(get_project_structure "$NEW_PROJECT_TYPE")
-    
-    local commands
-    commands=$(get_commands_for_language "$NEW_LANG")
-    
-    local language_conventions
-    language_conventions=$(get_language_conventions "$NEW_LANG")
-    
-    # Perform substitutions with error checking using safer approach
-    # Escape special characters for sed by using a different delimiter or escaping
-    local escaped_lang=$(printf '%s\n' "$NEW_LANG" | sed 's/[\[\.*^$()+{}|]/\\&/g')
-    local escaped_framework=$(printf '%s\n' "$NEW_FRAMEWORK" | sed 's/[\[\.*^$()+{}|]/\\&/g')
-    local escaped_branch=$(printf '%s\n' "$CURRENT_BRANCH" | sed 's/[\[\.*^$()+{}|]/\\&/g')
-    
-    # Build technology stack and recent change strings conditionally
-    local tech_stack
-    if [[ -n "$escaped_lang" && -n "$escaped_framework" ]]; then
-        tech_stack="- $escaped_lang + $escaped_framework ($escaped_branch)"
-    elif [[ -n "$escaped_lang" ]]; then
-        tech_stack="- $escaped_lang ($escaped_branch)"
-    elif [[ -n "$escaped_framework" ]]; then
-        tech_stack="- $escaped_framework ($escaped_branch)"
-    else
-        tech_stack="- ($escaped_branch)"
-    fi
-
-    local recent_change
-    if [[ -n "$escaped_lang" && -n "$escaped_framework" ]]; then
-        recent_change="- $escaped_branch: Added $escaped_lang + $escaped_framework"
-    elif [[ -n "$escaped_lang" ]]; then
-        recent_change="- $escaped_branch: Added $escaped_lang"
-    elif [[ -n "$escaped_framework" ]]; then
-        recent_change="- $escaped_branch: Added $escaped_framework"
-    else
-        recent_change="- $escaped_branch: Added"
-    fi
-
-    local substitutions=(
-        "s|\[PROJECT NAME\]|$project_name|"
-        "s|\[DATE\]|$current_date|"
-        "s|\[EXTRACTED FROM ALL PLAN.MD FILES\]|$tech_stack|"
-        "s|\[ACTUAL STRUCTURE FROM PLANS\]|$project_structure|g"
-        "s|\[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES\]|$commands|"
-        "s|\[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE\]|$language_conventions|"
-        "s|\[LAST 3 FEATURES AND WHAT THEY ADDED\]|$recent_change|"
-    )
-    
-    for substitution in "${substitutions[@]}"; do
-        if ! sed -i.bak -e "$substitution" "$temp_file"; then
-            log_error "Failed to perform substitution: $substitution"
-            rm -f "$temp_file" "$temp_file.bak"
-            return 1
-        fi
-    done
-    
-    # Convert \n sequences to actual newlines
-    newline=$(printf '\n')
-    sed -i.bak2 "s/\\\\n/${newline}/g" "$temp_file"
-
-    # Clean up backup files
-    rm -f "$temp_file.bak" "$temp_file.bak2"
-
-    # Prepend Cursor frontmatter for .mdc files so rules are auto-included
-    if [[ "$target_file" == *.mdc ]]; then
-        local frontmatter_file
-        frontmatter_file=$(mktemp) || return 1
-        printf '%s\n' "---" "description: Project Development Guidelines" "globs: [\"**/*\"]" "alwaysApply: true" "---" "" > "$frontmatter_file"
-        cat "$temp_file" >> "$frontmatter_file"
-        mv "$frontmatter_file" "$temp_file"
-    fi
-
-    return 0
-}
-
-
-
-
-update_existing_agent_file() {
-    local target_file="$1"
-    local current_date="$2"
-    
-    log_info "Updating existing agent context file..."
-    
-    # Use a single temporary file for atomic update
-    local temp_file
-    temp_file=$(mktemp) || {
-        log_error "Failed to create temporary file"
-        return 1
-    }
-    
-    # Process the file in one pass
-    local tech_stack=$(format_technology_stack "$NEW_LANG" "$NEW_FRAMEWORK")
-    local new_tech_entries=()
-    local new_change_entry=""
-    
-    # Prepare new technology entries
-    if [[ -n "$tech_stack" ]] && ! grep -q "$tech_stack" "$target_file"; then
-        new_tech_entries+=("- $tech_stack ($CURRENT_BRANCH)")
-    fi
-    
-    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]] && [[ "$NEW_DB" != "NEEDS CLARIFICATION" ]] && ! grep -q "$NEW_DB" "$target_file"; then
-        new_tech_entries+=("- $NEW_DB ($CURRENT_BRANCH)")
-    fi
-    
-    # Prepare new change entry
-    if [[ -n "$tech_stack" ]]; then
-        new_change_entry="- $CURRENT_BRANCH: Added $tech_stack"
-    elif [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]] && [[ "$NEW_DB" != "NEEDS CLARIFICATION" ]]; then
-        new_change_entry="- $CURRENT_BRANCH: Added $NEW_DB"
-    fi
-    
-    # Check if sections exist in the file
-    local has_active_technologies=0
-    local has_recent_changes=0
-    
-    if grep -q "^## Active Technologies" "$target_file" 2>/dev/null; then
-        has_active_technologies=1
-    fi
-    
-    if grep -q "^## Recent Changes" "$target_file" 2>/dev/null; then
-        has_recent_changes=1
-    fi
-    
-    # Process file line by line
-    local in_tech_section=false
-    local in_changes_section=false
-    local tech_entries_added=false
-    local changes_entries_added=false
-    local existing_changes_count=0
-    local file_ended=false
-    
-    while IFS= read -r line || [[ -n "$line" ]]; do
-        # Handle Active Technologies section
-        if [[ "$line" == "## Active Technologies" ]]; then
-            echo "$line" >> "$temp_file"
-            in_tech_section=true
-            continue
-        elif [[ $in_tech_section == true ]] && [[ "$line" =~ ^##[[:space:]] ]]; then
-            # Add new tech entries before closing the section
-            if [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
-                printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
-                tech_entries_added=true
-            fi
-            echo "$line" >> "$temp_file"
-            in_tech_section=false
-            continue
-        elif [[ $in_tech_section == true ]] && [[ -z "$line" ]]; then
-            # Add new tech entries before empty line in tech section
-            if [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
-                printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
-                tech_entries_added=true
-            fi
-            echo "$line" >> "$temp_file"
-            continue
-        fi
-        
-        # Handle Recent Changes section
-        if [[ "$line" == "## Recent Changes" ]]; then
-            echo "$line" >> "$temp_file"
-            # Add new change entry right after the heading
-            if [[ -n "$new_change_entry" ]]; then
-                echo "$new_change_entry" >> "$temp_file"
-            fi
-            in_changes_section=true
-            changes_entries_added=true
-            continue
-        elif [[ $in_changes_section == true ]] && [[ "$line" =~ ^##[[:space:]] ]]; then
-            echo "$line" >> "$temp_file"
-            in_changes_section=false
-            continue
-        elif [[ $in_changes_section == true ]] && [[ "$line" == "- "* ]]; then
-            # Keep only first 2 existing changes
-            if [[ $existing_changes_count -lt 2 ]]; then
-                echo "$line" >> "$temp_file"
-                ((existing_changes_count++))
-            fi
-            continue
-        fi
-        
-        # Update timestamp
-        if [[ "$line" =~ \*\*Last\ updated\*\*:.*[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9] ]]; then
-            echo "$line" | sed "s/[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]/$current_date/" >> "$temp_file"
-        else
-            echo "$line" >> "$temp_file"
-        fi
-    done < "$target_file"
-    
-    # Post-loop check: if we're still in the Active Technologies section and haven't added new entries
-    if [[ $in_tech_section == true ]] && [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
-        printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
-        tech_entries_added=true
-    fi
-    
-    # If sections don't exist, add them at the end of the file
-    if [[ $has_active_technologies -eq 0 ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
-        echo "" >> "$temp_file"
-        echo "## Active Technologies" >> "$temp_file"
-        printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
-        tech_entries_added=true
-    fi
-    
-    if [[ $has_recent_changes -eq 0 ]] && [[ -n "$new_change_entry" ]]; then
-        echo "" >> "$temp_file"
-        echo "## Recent Changes" >> "$temp_file"
-        echo "$new_change_entry" >> "$temp_file"
-        changes_entries_added=true
-    fi
-    
-    # Ensure Cursor .mdc files have YAML frontmatter for auto-inclusion
-    if [[ "$target_file" == *.mdc ]]; then
-        if ! head -1 "$temp_file" | grep -q '^---'; then
-            local frontmatter_file
-            frontmatter_file=$(mktemp) || { rm -f "$temp_file"; return 1; }
-            printf '%s\n' "---" "description: Project Development Guidelines" "globs: [\"**/*\"]" "alwaysApply: true" "---" "" > "$frontmatter_file"
-            cat "$temp_file" >> "$frontmatter_file"
-            mv "$frontmatter_file" "$temp_file"
-        fi
-    fi
-
-    # Move temp file to target atomically
-    if ! mv "$temp_file" "$target_file"; then
-        log_error "Failed to update target file"
-        rm -f "$temp_file"
-        return 1
-    fi
-
-    return 0
-}
-#==============================================================================
-# Main Agent File Update Function
-#==============================================================================
-
-update_agent_file() {
-    local target_file="$1"
-    local agent_name="$2"
-    
-    if [[ -z "$target_file" ]] || [[ -z "$agent_name" ]]; then
-        log_error "update_agent_file requires target_file and agent_name parameters"
-        return 1
-    fi
-    
-    log_info "Updating $agent_name context file: $target_file"
-    
-    local project_name
-    project_name=$(basename "$REPO_ROOT")
-    local current_date
-    current_date=$(date +%Y-%m-%d)
-    
-    # Create directory if it doesn't exist
-    local target_dir
-    target_dir=$(dirname "$target_file")
-    if [[ ! -d "$target_dir" ]]; then
-        if ! mkdir -p "$target_dir"; then
-            log_error "Failed to create directory: $target_dir"
-            return 1
-        fi
-    fi
-    
-    if [[ ! -f "$target_file" ]]; then
-        # Create new file from template
-        local temp_file
-        temp_file=$(mktemp) || {
-            log_error "Failed to create temporary file"
-            return 1
-        }
-        
-        if create_new_agent_file "$target_file" "$temp_file" "$project_name" "$current_date"; then
-            if mv "$temp_file" "$target_file"; then
-                log_success "Created new $agent_name context file"
-            else
-                log_error "Failed to move temporary file to $target_file"
-                rm -f "$temp_file"
-                return 1
-            fi
-        else
-            log_error "Failed to create new agent file"
-            rm -f "$temp_file"
-            return 1
-        fi
-    else
-        # Update existing file
-        if [[ ! -r "$target_file" ]]; then
-            log_error "Cannot read existing file: $target_file"
-            return 1
-        fi
-        
-        if [[ ! -w "$target_file" ]]; then
-            log_error "Cannot write to existing file: $target_file"
-            return 1
-        fi
-        
-        if update_existing_agent_file "$target_file" "$current_date"; then
-            log_success "Updated existing $agent_name context file"
-        else
-            log_error "Failed to update existing agent file"
-            return 1
-        fi
-    fi
-    
-    return 0
-}
-
-#==============================================================================
-# Agent Selection and Processing
-#==============================================================================
-
-update_specific_agent() {
-    local agent_type="$1"
-    
-    case "$agent_type" in
-        claude)
-            update_agent_file "$CLAUDE_FILE" "Claude Code"
-            ;;
-        gemini)
-            update_agent_file "$GEMINI_FILE" "Gemini CLI"
-            ;;
-        copilot)
-            update_agent_file "$COPILOT_FILE" "GitHub Copilot"
-            ;;
-        cursor-agent)
-            update_agent_file "$CURSOR_FILE" "Cursor IDE"
-            ;;
-        qwen)
-            update_agent_file "$QWEN_FILE" "Qwen Code"
-            ;;
-        opencode)
-            update_agent_file "$AGENTS_FILE" "opencode"
-            ;;
-        codex)
-            update_agent_file "$AGENTS_FILE" "Codex CLI"
-            ;;
-        windsurf)
-            update_agent_file "$WINDSURF_FILE" "Windsurf"
-            ;;
-        kilocode)
-            update_agent_file "$KILOCODE_FILE" "Kilo Code"
-            ;;
-        auggie)
-            update_agent_file "$AUGGIE_FILE" "Auggie CLI"
-            ;;
-        roo)
-            update_agent_file "$ROO_FILE" "Roo Code"
-            ;;
-        codebuddy)
-            update_agent_file "$CODEBUDDY_FILE" "CodeBuddy CLI"
-            ;;
-        qodercli)
-            update_agent_file "$QODER_FILE" "Qoder CLI"
-            ;;
-        amp)
-            update_agent_file "$AMP_FILE" "Amp"
-            ;;
-        shai)
-            update_agent_file "$SHAI_FILE" "SHAI"
-            ;;
-        tabnine)
-            update_agent_file "$TABNINE_FILE" "Tabnine CLI"
-            ;;
-        kiro-cli)
-            update_agent_file "$KIRO_FILE" "Kiro CLI"
-            ;;
-        agy)
-            update_agent_file "$AGY_FILE" "Antigravity"
-            ;;
-        bob)
-            update_agent_file "$BOB_FILE" "IBM Bob"
-            ;;
-        vibe)
-            update_agent_file "$VIBE_FILE" "Mistral Vibe"
-            ;;
-        generic)
-            log_info "Generic agent: no predefined context file. Use the agent-specific update script for your agent."
-            ;;
-        *)
-            log_error "Unknown agent type '$agent_type'"
-            log_error "Expected: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|codebuddy|amp|shai|tabnine|kiro-cli|agy|bob|vibe|qodercli|generic"
-            exit 1
-            ;;
-    esac
-}
-
-update_all_existing_agents() {
-    local found_agent=false
-    
-    # Check each possible agent file and update if it exists
-    if [[ -f "$CLAUDE_FILE" ]]; then
-        update_agent_file "$CLAUDE_FILE" "Claude Code"
-        found_agent=true
-    fi
-    
-    if [[ -f "$GEMINI_FILE" ]]; then
-        update_agent_file "$GEMINI_FILE" "Gemini CLI"
-        found_agent=true
-    fi
-    
-    if [[ -f "$COPILOT_FILE" ]]; then
-        update_agent_file "$COPILOT_FILE" "GitHub Copilot"
-        found_agent=true
-    fi
-    
-    if [[ -f "$CURSOR_FILE" ]]; then
-        update_agent_file "$CURSOR_FILE" "Cursor IDE"
-        found_agent=true
-    fi
-    
-    if [[ -f "$QWEN_FILE" ]]; then
-        update_agent_file "$QWEN_FILE" "Qwen Code"
-        found_agent=true
-    fi
-    
-    if [[ -f "$AGENTS_FILE" ]]; then
-        update_agent_file "$AGENTS_FILE" "Codex/opencode"
-        found_agent=true
-    fi
-    
-    if [[ -f "$WINDSURF_FILE" ]]; then
-        update_agent_file "$WINDSURF_FILE" "Windsurf"
-        found_agent=true
-    fi
-    
-    if [[ -f "$KILOCODE_FILE" ]]; then
-        update_agent_file "$KILOCODE_FILE" "Kilo Code"
-        found_agent=true
-    fi
-
-    if [[ -f "$AUGGIE_FILE" ]]; then
-        update_agent_file "$AUGGIE_FILE" "Auggie CLI"
-        found_agent=true
-    fi
-    
-    if [[ -f "$ROO_FILE" ]]; then
-        update_agent_file "$ROO_FILE" "Roo Code"
-        found_agent=true
-    fi
-
-    if [[ -f "$CODEBUDDY_FILE" ]]; then
-        update_agent_file "$CODEBUDDY_FILE" "CodeBuddy CLI"
-        found_agent=true
-    fi
-
-    if [[ -f "$SHAI_FILE" ]]; then
-        update_agent_file "$SHAI_FILE" "SHAI"
-        found_agent=true
-    fi
-
-    if [[ -f "$TABNINE_FILE" ]]; then
-        update_agent_file "$TABNINE_FILE" "Tabnine CLI"
-        found_agent=true
-    fi
-
-    if [[ -f "$QODER_FILE" ]]; then
-        update_agent_file "$QODER_FILE" "Qoder CLI"
-        found_agent=true
-    fi
-
-    if [[ -f "$KIRO_FILE" ]]; then
-        update_agent_file "$KIRO_FILE" "Kiro CLI"
-        found_agent=true
-    fi
-
-    if [[ -f "$AGY_FILE" ]]; then
-        update_agent_file "$AGY_FILE" "Antigravity"
-        found_agent=true
-    fi
-    if [[ -f "$BOB_FILE" ]]; then
-        update_agent_file "$BOB_FILE" "IBM Bob"
-        found_agent=true
-    fi
-
-    if [[ -f "$VIBE_FILE" ]]; then
-        update_agent_file "$VIBE_FILE" "Mistral Vibe"
-        found_agent=true
-    fi
-    
-    # If no agent files exist, create a default Claude file
-    if [[ "$found_agent" == false ]]; then
-        log_info "No existing agent files found, creating default Claude file..."
-        update_agent_file "$CLAUDE_FILE" "Claude Code"
-    fi
-}
-print_summary() {
-    echo
-    log_info "Summary of changes:"
-    
-    if [[ -n "$NEW_LANG" ]]; then
-        echo "  - Added language: $NEW_LANG"
-    fi
-    
-    if [[ -n "$NEW_FRAMEWORK" ]]; then
-        echo "  - Added framework: $NEW_FRAMEWORK"
-    fi
-    
-    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]]; then
-        echo "  - Added database: $NEW_DB"
-    fi
-    
-    echo
-    log_info "Usage: $0 [claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|codebuddy|amp|shai|tabnine|kiro-cli|agy|bob|vibe|qodercli|generic]"
-}
-
-#==============================================================================
-# Main Execution
-#==============================================================================
-
-main() {
-    # Validate environment before proceeding
-    validate_environment
-    
-    log_info "=== Updating agent context files for feature $CURRENT_BRANCH ==="
-    
-    # Parse the plan file to extract project information
-    if ! parse_plan_data "$NEW_PLAN"; then
-        log_error "Failed to parse plan data"
-        exit 1
-    fi
-    
-    # Process based on agent type argument
-    local success=true
-    
-    if [[ -z "$AGENT_TYPE" ]]; then
-        # No specific agent provided - update all existing agent files
-        log_info "No agent specified, updating all existing agent files..."
-        if ! update_all_existing_agents; then
-            success=false
-        fi
-    else
-        # Specific agent provided - update only that agent
-        log_info "Updating specific agent: $AGENT_TYPE"
-        if ! update_specific_agent "$AGENT_TYPE"; then
-            success=false
-        fi
-    fi
-    
-    # Print summary
-    print_summary
-    
-    if [[ "$success" == true ]]; then
-        log_success "Agent context update completed successfully"
-        exit 0
-    else
-        log_error "Agent context update completed with errors"
-        exit 1
-    fi
-}
-
-# Execute main function if script is run directly
-if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
-    main "$@"
-fi
+REPO_ROOT=$(git rev-parse --show-toplevel)
+CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
+FEATURE_DIR="$REPO_ROOT/specs/$CURRENT_BRANCH"
+NEW_PLAN="$FEATURE_DIR/plan.md"
+CLAUDE_FILE="$REPO_ROOT/CLAUDE.md"; GEMINI_FILE="$REPO_ROOT/GEMINI.md"; COPILOT_FILE="$REPO_ROOT/.github/copilot-instructions.md"
+AGENT_TYPE="$1"
+[ -f "$NEW_PLAN" ] || { echo "ERROR: No plan.md found at $NEW_PLAN"; exit 1; }
+echo "=== Updating agent context files for feature $CURRENT_BRANCH ==="
+NEW_LANG=$(grep "^**Language/Version**: " "$NEW_PLAN" 2>/dev/null | head -1 | sed 's/^**Language\/Version**: //' | grep -v "NEEDS CLARIFICATION" || echo "")
+NEW_FRAMEWORK=$(grep "^**Primary Dependencies**: " "$NEW_PLAN" 2>/dev/null | head -1 | sed 's/^**Primary Dependencies**: //' | grep -v "NEEDS CLARIFICATION" || echo "")
+NEW_DB=$(grep "^**Storage**: " "$NEW_PLAN" 2>/dev/null | head -1 | sed 's/^**Storage**: //' | grep -v "N/A" | grep -v "NEEDS CLARIFICATION" || echo "")
+NEW_PROJECT_TYPE=$(grep "^**Project Type**: " "$NEW_PLAN" 2>/dev/null | head -1 | sed 's/^**Project Type**: //' || echo "")
+update_agent_file() { local target_file="$1" agent_name="$2"; echo "Updating $agent_name context file: $target_file"; local temp_file=$(mktemp); if [ ! -f "$target_file" ]; then
+  echo "Creating new $agent_name context file..."; if [ -f "$REPO_ROOT/templates/agent-file-template.md" ]; then cp "$REPO_ROOT/templates/agent-file-template.md" "$temp_file"; else echo "ERROR: Template not found"; return 1; fi;
+  sed -i.bak "s/\[PROJECT NAME\]/$(basename $REPO_ROOT)/" "$temp_file"; sed -i.bak "s/\[DATE\]/$(date +%Y-%m-%d)/" "$temp_file"; sed -i.bak "s/\[EXTRACTED FROM ALL PLAN.MD FILES\]/- $NEW_LANG + $NEW_FRAMEWORK ($CURRENT_BRANCH)/" "$temp_file";
+  if [[ "$NEW_PROJECT_TYPE" == *"web"* ]]; then sed -i.bak "s|\[ACTUAL STRUCTURE FROM PLANS\]|backend/\nfrontend/\ntests/|" "$temp_file"; else sed -i.bak "s|\[ACTUAL STRUCTURE FROM PLANS\]|src/\ntests/|" "$temp_file"; fi;
+  if [[ "$NEW_LANG" == *"Python"* ]]; then COMMANDS="cd src && pytest && ruff check ."; elif [[ "$NEW_LANG" == *"Rust"* ]]; then COMMANDS="cargo test && cargo clippy"; elif [[ "$NEW_LANG" == *"JavaScript"* ]] || [[ "$NEW_LANG" == *"TypeScript"* ]]; then COMMANDS="npm test && npm run lint"; else COMMANDS="# Add commands for $NEW_LANG"; fi; sed -i.bak "s|\[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES\]|$COMMANDS|" "$temp_file";
+  sed -i.bak "s|\[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE\]|$NEW_LANG: Follow standard conventions|" "$temp_file"; sed -i.bak "s|\[LAST 3 FEATURES AND WHAT THEY ADDED\]|- $CURRENT_BRANCH: Added $NEW_LANG + $NEW_FRAMEWORK|" "$temp_file"; rm "$temp_file.bak";
+else
+  echo "Updating existing $agent_name context file..."; manual_start=$(grep -n "<!-- MANUAL ADDITIONS START -->" "$target_file" | cut -d: -f1); manual_end=$(grep -n "<!-- MANUAL ADDITIONS END -->" "$target_file" | cut -d: -f1); if [ -n "$manual_start" ] && [ -n "$manual_end" ]; then sed -n "${manual_start},${manual_end}p" "$target_file" > /tmp/manual_additions.txt; fi;
+  python3 - "$target_file" <<'EOF'
+import re,sys,datetime
+target=sys.argv[1]
+with open(target) as f: content=f.read()
+NEW_LANG="'$NEW_LANG'";NEW_FRAMEWORK="'$NEW_FRAMEWORK'";CURRENT_BRANCH="'$CURRENT_BRANCH'";NEW_DB="'$NEW_DB'";NEW_PROJECT_TYPE="'$NEW_PROJECT_TYPE'"
+# Tech section
+m=re.search(r'## Active Technologies\n(.*?)\n\n',content, re.DOTALL)
+if m:
+  existing=m.group(1)
+  additions=[]
+  if '$NEW_LANG' and '$NEW_LANG' not in existing: additions.append(f"- $NEW_LANG + $NEW_FRAMEWORK ($CURRENT_BRANCH)")
+  if '$NEW_DB' and '$NEW_DB' not in existing and '$NEW_DB'!='N/A': additions.append(f"- $NEW_DB ($CURRENT_BRANCH)")
+  if additions:
+    new_block=existing+"\n"+"\n".join(additions)
+    content=content.replace(m.group(0),f"## Active Technologies\n{new_block}\n\n")
+# Recent changes
+m2=re.search(r'## Recent Changes\n(.*?)(\n\n|$)',content, re.DOTALL)
+if m2:
+  lines=[l for l in m2.group(1).strip().split('\n') if l]
+  lines.insert(0,f"- $CURRENT_BRANCH: Added $NEW_LANG + $NEW_FRAMEWORK")
+  lines=lines[:3]
+  content=re.sub(r'## Recent Changes\n.*?(\n\n|$)', '## Recent Changes\n'+"\n".join(lines)+'\n\n', content, flags=re.DOTALL)
+content=re.sub(r'Last updated: \d{4}-\d{2}-\d{2}', 'Last updated: '+datetime.datetime.now().strftime('%Y-%m-%d'), content)
+open(target+'.tmp','w').write(content)
+EOF
+  mv "$target_file.tmp" "$target_file"; if [ -f /tmp/manual_additions.txt ]; then sed -i.bak '/<!-- MANUAL ADDITIONS START -->/,/<!-- MANUAL ADDITIONS END -->/d' "$target_file"; cat /tmp/manual_additions.txt >> "$target_file"; rm /tmp/manual_additions.txt "$target_file.bak"; fi;
+fi; mv "$temp_file" "$target_file" 2>/dev/null || true; echo "✅ $agent_name context file updated successfully"; }
+case "$AGENT_TYPE" in
+  claude) update_agent_file "$CLAUDE_FILE" "Claude Code" ;;
+  gemini) update_agent_file "$GEMINI_FILE" "Gemini CLI" ;;
+  copilot) update_agent_file "$COPILOT_FILE" "GitHub Copilot" ;;
+  "") [ -f "$CLAUDE_FILE" ] && update_agent_file "$CLAUDE_FILE" "Claude Code"; [ -f "$GEMINI_FILE" ] && update_agent_file "$GEMINI_FILE" "Gemini CLI"; [ -f "$COPILOT_FILE" ] && update_agent_file "$COPILOT_FILE" "GitHub Copilot"; if [ ! -f "$CLAUDE_FILE" ] && [ ! -f "$GEMINI_FILE" ] && [ ! -f "$COPILOT_FILE" ]; then update_agent_file "$CLAUDE_FILE" "Claude Code"; fi ;;
+  *) echo "ERROR: Unknown agent type '$AGENT_TYPE'"; exit 1 ;;
+esac
+echo; echo "Summary of changes:"; [ -n "$NEW_LANG" ] && echo "- Added language: $NEW_LANG"; [ -n "$NEW_FRAMEWORK" ] && echo "- Added framework: $NEW_FRAMEWORK"; [ -n "$NEW_DB" ] && [ "$NEW_DB" != "N/A" ] && echo "- Added database: $NEW_DB"; echo; echo "Usage: $0 [claude|gemini|copilot]"

scripts/powershell/check-prerequisites.ps1

@@ -1,148 +0,0 @@
-#!/usr/bin/env pwsh
-
-# Consolidated prerequisite checking script (PowerShell)
-#
-# This script provides unified prerequisite checking for Spec-Driven Development workflow.
-# It replaces the functionality previously spread across multiple scripts.
-#
-# Usage: ./check-prerequisites.ps1 [OPTIONS]
-#
-# OPTIONS:
-#   -Json               Output in JSON format
-#   -RequireTasks       Require tasks.md to exist (for implementation phase)
-#   -IncludeTasks       Include tasks.md in AVAILABLE_DOCS list
-#   -PathsOnly          Only output path variables (no validation)
-#   -Help, -h           Show help message
-
-[CmdletBinding()]
-param(
-    [switch]$Json,
-    [switch]$RequireTasks,
-    [switch]$IncludeTasks,
-    [switch]$PathsOnly,
-    [switch]$Help
-)
-
-$ErrorActionPreference = 'Stop'
-
-# Show help if requested
-if ($Help) {
-    Write-Output @"
-Usage: check-prerequisites.ps1 [OPTIONS]
-
-Consolidated prerequisite checking for Spec-Driven Development workflow.
-
-OPTIONS:
-  -Json               Output in JSON format
-  -RequireTasks       Require tasks.md to exist (for implementation phase)
-  -IncludeTasks       Include tasks.md in AVAILABLE_DOCS list
-  -PathsOnly          Only output path variables (no prerequisite validation)
-  -Help, -h           Show this help message
-
-EXAMPLES:
-  # Check task prerequisites (plan.md required)
-  .\check-prerequisites.ps1 -Json
-  
-  # Check implementation prerequisites (plan.md + tasks.md required)
-  .\check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
-  
-  # Get feature paths only (no validation)
-  .\check-prerequisites.ps1 -PathsOnly
-
-"@
-    exit 0
-}
-
-# Source common functions
-. "$PSScriptRoot/common.ps1"
-
-# Get feature paths and validate branch
-$paths = Get-FeaturePathsEnv
-
-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]@{
-            REPO_ROOT    = $paths.REPO_ROOT
-            BRANCH       = $paths.CURRENT_BRANCH
-            FEATURE_DIR  = $paths.FEATURE_DIR
-            FEATURE_SPEC = $paths.FEATURE_SPEC
-            IMPL_PLAN    = $paths.IMPL_PLAN
-            TASKS        = $paths.TASKS
-        } | ConvertTo-Json -Compress
-    } else {
-        Write-Output "REPO_ROOT: $($paths.REPO_ROOT)"
-        Write-Output "BRANCH: $($paths.CURRENT_BRANCH)"
-        Write-Output "FEATURE_DIR: $($paths.FEATURE_DIR)"
-        Write-Output "FEATURE_SPEC: $($paths.FEATURE_SPEC)"
-        Write-Output "IMPL_PLAN: $($paths.IMPL_PLAN)"
-        Write-Output "TASKS: $($paths.TASKS)"
-    }
-    exit 0
-}
-
-# 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.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.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.tasks first to create the task list."
-    exit 1
-}
-
-# Build list of available documents
-$docs = @()
-
-# Always check these optional docs
-if (Test-Path $paths.RESEARCH) { $docs += 'research.md' }
-if (Test-Path $paths.DATA_MODEL) { $docs += 'data-model.md' }
-
-# Check contracts directory (only if it exists and has files)
-if ((Test-Path $paths.CONTRACTS_DIR) -and (Get-ChildItem -Path $paths.CONTRACTS_DIR -ErrorAction SilentlyContinue | Select-Object -First 1)) { 
-    $docs += 'contracts/' 
-}
-
-if (Test-Path $paths.QUICKSTART) { $docs += 'quickstart.md' }
-
-# Include tasks.md if requested and it exists
-if ($IncludeTasks -and (Test-Path $paths.TASKS)) { 
-    $docs += 'tasks.md' 
-}
-
-# Output results
-if ($Json) {
-    # JSON output
-    [PSCustomObject]@{ 
-        FEATURE_DIR = $paths.FEATURE_DIR
-        AVAILABLE_DOCS = $docs 
-    } | ConvertTo-Json -Compress
-} else {
-    # Text output
-    Write-Output "FEATURE_DIR:$($paths.FEATURE_DIR)"
-    Write-Output "AVAILABLE_DOCS:"
-    
-    # Show status of each potential document
-    Test-FileExists -Path $paths.RESEARCH -Description 'research.md' | Out-Null
-    Test-FileExists -Path $paths.DATA_MODEL -Description 'data-model.md' | Out-Null
-    Test-DirHasFiles -Path $paths.CONTRACTS_DIR -Description 'contracts/' | Out-Null
-    Test-FileExists -Path $paths.QUICKSTART -Description 'quickstart.md' | Out-Null
-    
-    if ($IncludeTasks) {
-        Test-FileExists -Path $paths.TASKS -Description 'tasks.md' | Out-Null
-    }
-}

scripts/powershell/check-task-prerequisites.ps1

@@ -0,0 +1,35 @@
+#!/usr/bin/env pwsh
+[CmdletBinding()]
+param([switch]$Json)
+$ErrorActionPreference = 'Stop'
+. "$PSScriptRoot/common.ps1"
+
+$paths = Get-FeaturePathsEnv
+if (-not (Test-FeatureBranch -Branch $paths.CURRENT_BRANCH)) { exit 1 }
+
+if (-not (Test-Path $paths.FEATURE_DIR -PathType Container)) {
+    Write-Output "ERROR: Feature directory not found: $($paths.FEATURE_DIR)"
+    Write-Output "Run /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 /plan first to create the plan."
+    exit 1
+}
+
+if ($Json) {
+    $docs = @()
+    if (Test-Path $paths.RESEARCH) { $docs += 'research.md' }
+    if (Test-Path $paths.DATA_MODEL) { $docs += 'data-model.md' }
+    if ((Test-Path $paths.CONTRACTS_DIR) -and (Get-ChildItem -Path $paths.CONTRACTS_DIR -ErrorAction SilentlyContinue | Select-Object -First 1)) { $docs += 'contracts/' }
+    if (Test-Path $paths.QUICKSTART) { $docs += 'quickstart.md' }
+    [PSCustomObject]@{ FEATURE_DIR=$paths.FEATURE_DIR; AVAILABLE_DOCS=$docs } | ConvertTo-Json -Compress
+} else {
+    Write-Output "FEATURE_DIR:$($paths.FEATURE_DIR)"
+    Write-Output "AVAILABLE_DOCS:"
+    Test-FileExists -Path $paths.RESEARCH -Description 'research.md' | Out-Null
+    Test-FileExists -Path $paths.DATA_MODEL -Description 'data-model.md' | Out-Null
+    Test-DirHasFiles -Path $paths.CONTRACTS_DIR -Description 'contracts/' | Out-Null
+    Test-FileExists -Path $paths.QUICKSTART -Description 'quickstart.md' | Out-Null
+}

scripts/powershell/common.ps1

@@ -1,84 +1,16 @@
 #!/usr/bin/env pwsh
-# Common PowerShell functions analogous to common.sh
+# Common PowerShell functions analogous to common.sh (moved to powershell/)
 
 function Get-RepoRoot {
-    try {
-        $result = git rev-parse --show-toplevel 2>$null
-        if ($LASTEXITCODE -eq 0) {
-            return $result
-        }
-    } catch {
-        # Git command failed
-    }
-    
-    # Fall back to script location for non-git repos
-    return (Resolve-Path (Join-Path $PSScriptRoot "../../..")).Path
+    git rev-parse --show-toplevel
 }
 
 function Get-CurrentBranch {
-    # First check if SPECIFY_FEATURE environment variable is set
-    if ($env:SPECIFY_FEATURE) {
-        return $env:SPECIFY_FEATURE
-    }
-    
-    # Then check git if available
-    try {
-        $result = git rev-parse --abbrev-ref HEAD 2>$null
-        if ($LASTEXITCODE -eq 0) {
-            return $result
-        }
-    } catch {
-        # Git command failed
-    }
-    
-    # For non-git repos, try to find the latest feature directory
-    $repoRoot = Get-RepoRoot
-    $specsDir = Join-Path $repoRoot "specs"
-    
-    if (Test-Path $specsDir) {
-        $latestFeature = ""
-        $highest = 0
-        
-        Get-ChildItem -Path $specsDir -Directory | ForEach-Object {
-            if ($_.Name -match '^(\d{3})-') {
-                $num = [int]$matches[1]
-                if ($num -gt $highest) {
-                    $highest = $num
-                    $latestFeature = $_.Name
-                }
-            }
-        }
-        
-        if ($latestFeature) {
-            return $latestFeature
-        }
-    }
-    
-    # Final fallback
-    return "main"
-}
-
-function Test-HasGit {
-    try {
-        git rev-parse --show-toplevel 2>$null | Out-Null
-        return ($LASTEXITCODE -eq 0)
-    } catch {
-        return $false
-    }
+    git rev-parse --abbrev-ref HEAD
 }
 
 function Test-FeatureBranch {
-    param(
-        [string]$Branch,
-        [bool]$HasGit = $true
-    )
-    
-    # For non-git repos, we can't enforce branch naming but still provide output
-    if (-not $HasGit) {
-        Write-Warning "[specify] Warning: Git repository not detected; skipped branch validation"
-        return $true
-    }
-    
+    param([string]$Branch)
     if ($Branch -notmatch '^[0-9]{3}-') {
         Write-Output "ERROR: Not on a feature branch. Current branch: $Branch"
         Write-Output "Feature branches should be named like: 001-feature-name"
@@ -95,20 +27,17 @@ function Get-FeatureDir {
 function Get-FeaturePathsEnv {
     $repoRoot = Get-RepoRoot
     $currentBranch = Get-CurrentBranch
-    $hasGit = Test-HasGit
     $featureDir = Get-FeatureDir -RepoRoot $repoRoot -Branch $currentBranch
-    
     [PSCustomObject]@{
-        REPO_ROOT     = $repoRoot
+        REPO_ROOT    = $repoRoot
         CURRENT_BRANCH = $currentBranch
-        HAS_GIT       = $hasGit
-        FEATURE_DIR   = $featureDir
-        FEATURE_SPEC  = Join-Path $featureDir 'spec.md'
-        IMPL_PLAN     = Join-Path $featureDir 'plan.md'
-        TASKS         = Join-Path $featureDir 'tasks.md'
-        RESEARCH      = Join-Path $featureDir 'research.md'
-        DATA_MODEL    = Join-Path $featureDir 'data-model.md'
-        QUICKSTART    = Join-Path $featureDir 'quickstart.md'
+        FEATURE_DIR  = $featureDir
+        FEATURE_SPEC = Join-Path $featureDir 'spec.md'
+        IMPL_PLAN    = Join-Path $featureDir 'plan.md'
+        TASKS        = Join-Path $featureDir 'tasks.md'
+        RESEARCH     = Join-Path $featureDir 'research.md'
+        DATA_MODEL   = Join-Path $featureDir 'data-model.md'
+        QUICKSTART   = Join-Path $featureDir 'quickstart.md'
         CONTRACTS_DIR = Join-Path $featureDir 'contracts'
     }
 }
@@ -134,71 +63,3 @@ function Test-DirHasFiles {
         return $false
     }
 }
-
-# Resolve a template name to a file path using the priority stack:
-#   1. .specify/templates/overrides/
-#   2. .specify/presets/<preset-id>/templates/ (sorted by priority from .registry)
-#   3. .specify/extensions/<ext-id>/templates/
-#   4. .specify/templates/ (core)
-function Resolve-Template {
-    param(
-        [Parameter(Mandatory=$true)][string]$TemplateName,
-        [Parameter(Mandatory=$true)][string]$RepoRoot
-    )
-
-    $base = Join-Path $RepoRoot '.specify/templates'
-
-    # Priority 1: Project overrides
-    $override = Join-Path $base "overrides/$TemplateName.md"
-    if (Test-Path $override) { return $override }
-
-    # Priority 2: Installed presets (sorted by priority from .registry)
-    $presetsDir = Join-Path $RepoRoot '.specify/presets'
-    if (Test-Path $presetsDir) {
-        $registryFile = Join-Path $presetsDir '.registry'
-        $sortedPresets = @()
-        if (Test-Path $registryFile) {
-            try {
-                $registryData = Get-Content $registryFile -Raw | ConvertFrom-Json
-                $presets = $registryData.presets
-                if ($presets) {
-                    $sortedPresets = $presets.PSObject.Properties |
-                        Sort-Object { if ($_.Value.priority) { $_.Value.priority } else { 10 } } |
-                        ForEach-Object { $_.Name }
-                }
-            } catch {
-                # Fallback: alphabetical directory order
-                $sortedPresets = @()
-            }
-        }
-
-        if ($sortedPresets.Count -gt 0) {
-            foreach ($presetId in $sortedPresets) {
-                $candidate = Join-Path $presetsDir "$presetId/templates/$TemplateName.md"
-                if (Test-Path $candidate) { return $candidate }
-            }
-        } else {
-            # Fallback: alphabetical directory order
-            foreach ($preset in Get-ChildItem -Path $presetsDir -Directory -ErrorAction SilentlyContinue | Where-Object { $_.Name -notlike '.*' }) {
-                $candidate = Join-Path $preset.FullName "templates/$TemplateName.md"
-                if (Test-Path $candidate) { return $candidate }
-            }
-        }
-    }
-
-    # Priority 3: Extension-provided templates
-    $extDir = Join-Path $RepoRoot '.specify/extensions'
-    if (Test-Path $extDir) {
-        foreach ($ext in Get-ChildItem -Path $extDir -Directory -ErrorAction SilentlyContinue | Where-Object { $_.Name -notlike '.*' } | Sort-Object Name) {
-            $candidate = Join-Path $ext.FullName "templates/$TemplateName.md"
-            if (Test-Path $candidate) { return $candidate }
-        }
-    }
-
-    # Priority 4: Core templates
-    $core = Join-Path $base "$TemplateName.md"
-    if (Test-Path $core) { return $core }
-
-    return $null
-}
-

scripts/powershell/create-new-feature.ps1

@@ -1,308 +1,52 @@
 #!/usr/bin/env pwsh
-# Create a new feature
+# Create a new feature (moved to powershell/)
 [CmdletBinding()]
 param(
     [switch]$Json,
-    [string]$ShortName,
-    [int]$Number = 0,
-    [switch]$Help,
     [Parameter(ValueFromRemainingArguments = $true)]
     [string[]]$FeatureDescription
 )
 $ErrorActionPreference = 'Stop'
 
-# Show help if requested
-if ($Help) {
-    Write-Host "Usage: ./create-new-feature.ps1 [-Json] [-ShortName <name>] [-Number N] <feature description>"
-    Write-Host ""
-    Write-Host "Options:"
-    Write-Host "  -Json               Output in JSON format"
-    Write-Host "  -ShortName <name>   Provide a custom short name (2-4 words) for the branch"
-    Write-Host "  -Number N           Specify branch number manually (overrides auto-detection)"
-    Write-Host "  -Help               Show this help message"
-    Write-Host ""
-    Write-Host "Examples:"
-    Write-Host "  ./create-new-feature.ps1 'Add user authentication system' -ShortName 'user-auth'"
-    Write-Host "  ./create-new-feature.ps1 'Implement OAuth2 integration for API'"
-    exit 0
-}
-
-# Check if feature description provided
 if (-not $FeatureDescription -or $FeatureDescription.Count -eq 0) {
-    Write-Error "Usage: ./create-new-feature.ps1 [-Json] [-ShortName <name>] <feature description>"
-    exit 1
+    Write-Error "Usage: ./create-new-feature.ps1 [-Json] <feature description>"; exit 1
 }
-
 $featureDesc = ($FeatureDescription -join ' ').Trim()
 
-# Validate description is not empty after trimming (e.g., user passed only whitespace)
-if ([string]::IsNullOrWhiteSpace($featureDesc)) {
-    Write-Error "Error: Feature description cannot be empty or contain only whitespace"
-    exit 1
-}
-
-# Resolve repository root. Prefer git information when available, but fall back
-# to searching for repository markers so the workflow still functions in repositories that
-# were initialized with --no-git.
-function Find-RepositoryRoot {
-    param(
-        [string]$StartDir,
-        [string[]]$Markers = @('.git', '.specify')
-    )
-    $current = Resolve-Path $StartDir
-    while ($true) {
-        foreach ($marker in $Markers) {
-            if (Test-Path (Join-Path $current $marker)) {
-                return $current
-            }
-        }
-        $parent = Split-Path $current -Parent
-        if ($parent -eq $current) {
-            # Reached filesystem root without finding markers
-            return $null
-        }
-        $current = $parent
-    }
-}
-
-function Get-HighestNumberFromSpecs {
-    param([string]$SpecsDir)
-    
-    $highest = 0
-    if (Test-Path $SpecsDir) {
-        Get-ChildItem -Path $SpecsDir -Directory | ForEach-Object {
-            if ($_.Name -match '^(\d+)') {
-                $num = [int]$matches[1]
-                if ($num -gt $highest) { $highest = $num }
-            }
-        }
-    }
-    return $highest
-}
-
-function Get-HighestNumberFromBranches {
-    param()
-    
-    $highest = 0
-    try {
-        $branches = git branch -a 2>$null
-        if ($LASTEXITCODE -eq 0) {
-            foreach ($branch in $branches) {
-                # Clean branch name: remove leading markers and remote prefixes
-                $cleanBranch = $branch.Trim() -replace '^\*?\s+', '' -replace '^remotes/[^/]+/', ''
-                
-                # Extract feature number if branch matches pattern ###-*
-                if ($cleanBranch -match '^(\d+)-') {
-                    $num = [int]$matches[1]
-                    if ($num -gt $highest) { $highest = $num }
-                }
-            }
-        }
-    } catch {
-        # If git command fails, return 0
-        Write-Verbose "Could not check Git branches: $_"
-    }
-    return $highest
-}
-
-function Get-NextBranchNumber {
-    param(
-        [string]$SpecsDir
-    )
-
-    # Fetch all remotes to get latest branch info (suppress errors if no remotes)
-    try {
-        git fetch --all --prune 2>$null | Out-Null
-    } catch {
-        # Ignore fetch errors
-    }
-
-    # Get highest number from ALL branches (not just matching short name)
-    $highestBranch = Get-HighestNumberFromBranches
-
-    # Get highest number from ALL specs (not just matching short name)
-    $highestSpec = Get-HighestNumberFromSpecs -SpecsDir $SpecsDir
-
-    # Take the maximum of both
-    $maxNum = [Math]::Max($highestBranch, $highestSpec)
-
-    # Return next number
-    return $maxNum + 1
-}
-
-function ConvertTo-CleanBranchName {
-    param([string]$Name)
-    
-    return $Name.ToLower() -replace '[^a-z0-9]', '-' -replace '-{2,}', '-' -replace '^-', '' -replace '-$', ''
-}
-$fallbackRoot = (Find-RepositoryRoot -StartDir $PSScriptRoot)
-if (-not $fallbackRoot) {
-    Write-Error "Error: Could not determine repository root. Please run this script from within the repository."
-    exit 1
-}
-
-# Load common functions (includes Resolve-Template)
-. "$PSScriptRoot/common.ps1"
-
-try {
-    $repoRoot = git rev-parse --show-toplevel 2>$null
-    if ($LASTEXITCODE -eq 0) {
-        $hasGit = $true
-    } else {
-        throw "Git not available"
-    }
-} catch {
-    $repoRoot = $fallbackRoot
-    $hasGit = $false
-}
-
-Set-Location $repoRoot
-
+$repoRoot = git rev-parse --show-toplevel
 $specsDir = Join-Path $repoRoot 'specs'
 New-Item -ItemType Directory -Path $specsDir -Force | Out-Null
 
-# Function to generate branch name with stop word filtering and length filtering
-function Get-BranchName {
-    param([string]$Description)
-    
-    # Common stop words to filter out
-    $stopWords = @(
-        'i', 'a', 'an', 'the', 'to', 'for', 'of', 'in', 'on', 'at', 'by', 'with', 'from',
-        'is', 'are', 'was', 'were', 'be', 'been', 'being', 'have', 'has', 'had',
-        'do', 'does', 'did', 'will', 'would', 'should', 'could', 'can', 'may', 'might', 'must', 'shall',
-        'this', 'that', 'these', 'those', 'my', 'your', 'our', 'their',
-        'want', 'need', 'add', 'get', 'set'
-    )
-    
-    # Convert to lowercase and extract words (alphanumeric only)
-    $cleanName = $Description.ToLower() -replace '[^a-z0-9\s]', ' '
-    $words = $cleanName -split '\s+' | Where-Object { $_ }
-    
-    # Filter words: remove stop words and words shorter than 3 chars (unless they're uppercase acronyms in original)
-    $meaningfulWords = @()
-    foreach ($word in $words) {
-        # Skip stop words
-        if ($stopWords -contains $word) { continue }
-        
-        # Keep words that are length >= 3 OR appear as uppercase in original (likely acronyms)
-        if ($word.Length -ge 3) {
-            $meaningfulWords += $word
-        } elseif ($Description -match "\b$($word.ToUpper())\b") {
-            # Keep short words if they appear as uppercase in original (likely acronyms)
-            $meaningfulWords += $word
+$highest = 0
+if (Test-Path $specsDir) {
+    Get-ChildItem -Path $specsDir -Directory | ForEach-Object {
+        if ($_.Name -match '^(\d{3})') {
+            $num = [int]$matches[1]
+            if ($num -gt $highest) { $highest = $num }
         }
     }
-    
-    # If we have meaningful words, use first 3-4 of them
-    if ($meaningfulWords.Count -gt 0) {
-        $maxWords = if ($meaningfulWords.Count -eq 4) { 4 } else { 3 }
-        $result = ($meaningfulWords | Select-Object -First $maxWords) -join '-'
-        return $result
-    } else {
-        # Fallback to original logic if no meaningful words found
-        $result = ConvertTo-CleanBranchName -Name $Description
-        $fallbackWords = ($result -split '-') | Where-Object { $_ } | Select-Object -First 3
-        return [string]::Join('-', $fallbackWords)
-    }
 }
+$next = $highest + 1
+$featureNum = ('{0:000}' -f $next)
 
-# Generate branch name
-if ($ShortName) {
-    # Use provided short name, just clean it up
-    $branchSuffix = ConvertTo-CleanBranchName -Name $ShortName
-} else {
-    # Generate from description with smart filtering
-    $branchSuffix = Get-BranchName -Description $featureDesc
-}
+$branchName = $featureDesc.ToLower() -replace '[^a-z0-9]', '-' -replace '-{2,}', '-' -replace '^-', '' -replace '-$', ''
+$words = ($branchName -split '-') | Where-Object { $_ } | Select-Object -First 3
+$branchName = "$featureNum-$([string]::Join('-', $words))"
 
-# Determine branch number
-if ($Number -eq 0) {
-    if ($hasGit) {
-        # Check existing branches on remotes
-        $Number = Get-NextBranchNumber -SpecsDir $specsDir
-    } else {
-        # Fall back to local directory check
-        $Number = (Get-HighestNumberFromSpecs -SpecsDir $specsDir) + 1
-    }
-}
-
-$featureNum = ('{0:000}' -f $Number)
-$branchName = "$featureNum-$branchSuffix"
-
-# GitHub enforces a 244-byte limit on branch names
-# Validate and truncate if necessary
-$maxBranchLength = 244
-if ($branchName.Length -gt $maxBranchLength) {
-    # Calculate how much we need to trim from suffix
-    # Account for: feature number (3) + hyphen (1) = 4 chars
-    $maxSuffixLength = $maxBranchLength - 4
-    
-    # Truncate suffix
-    $truncatedSuffix = $branchSuffix.Substring(0, [Math]::Min($branchSuffix.Length, $maxSuffixLength))
-    # Remove trailing hyphen if truncation created one
-    $truncatedSuffix = $truncatedSuffix -replace '-$', ''
-    
-    $originalBranchName = $branchName
-    $branchName = "$featureNum-$truncatedSuffix"
-    
-    Write-Warning "[specify] Branch name exceeded GitHub's 244-byte limit"
-    Write-Warning "[specify] Original: $originalBranchName ($($originalBranchName.Length) bytes)"
-    Write-Warning "[specify] Truncated to: $branchName ($($branchName.Length) bytes)"
-}
-
-if ($hasGit) {
-    $branchCreated = $false
-    try {
-        git checkout -b $branchName 2>$null | Out-Null
-        if ($LASTEXITCODE -eq 0) {
-            $branchCreated = $true
-        }
-    } catch {
-        # Exception during git command
-    }
-
-    if (-not $branchCreated) {
-        # Check if branch already exists
-        $existingBranch = git branch --list $branchName 2>$null
-        if ($existingBranch) {
-            Write-Error "Error: Branch '$branchName' already exists. Please use a different feature name or specify a different number with -Number."
-            exit 1
-        } else {
-            Write-Error "Error: Failed to create git branch '$branchName'. Please check your git configuration and try again."
-            exit 1
-        }
-    }
-} else {
-    Write-Warning "[specify] Warning: Git repository not detected; skipped branch creation for $branchName"
-}
+git checkout -b $branchName | Out-Null
 
 $featureDir = Join-Path $specsDir $branchName
 New-Item -ItemType Directory -Path $featureDir -Force | Out-Null
 
-$template = Resolve-Template -TemplateName 'spec-template' -RepoRoot $repoRoot
+$template = Join-Path $repoRoot 'templates/spec-template.md'
 $specFile = Join-Path $featureDir 'spec.md'
-if ($template -and (Test-Path $template)) { 
-    Copy-Item $template $specFile -Force 
-} else { 
-    New-Item -ItemType File -Path $specFile | Out-Null 
-}
-
-# Set the SPECIFY_FEATURE environment variable for the current session
-$env:SPECIFY_FEATURE = $branchName
+if (Test-Path $template) { Copy-Item $template $specFile -Force } else { New-Item -ItemType File -Path $specFile | Out-Null }
 
 if ($Json) {
-    $obj = [PSCustomObject]@{ 
-        BRANCH_NAME = $branchName
-        SPEC_FILE = $specFile
-        FEATURE_NUM = $featureNum
-        HAS_GIT = $hasGit
-    }
+    $obj = [PSCustomObject]@{ BRANCH_NAME = $branchName; SPEC_FILE = $specFile; FEATURE_NUM = $featureNum }
     $obj | ConvertTo-Json -Compress
 } else {
     Write-Output "BRANCH_NAME: $branchName"
     Write-Output "SPEC_FILE: $specFile"
     Write-Output "FEATURE_NUM: $featureNum"
-    Write-Output "HAS_GIT: $hasGit"
-    Write-Output "SPECIFY_FEATURE environment variable set to: $branchName"
 }
-

scripts/powershell/get-feature-paths.ps1

@@ -0,0 +1,15 @@
+#!/usr/bin/env pwsh
+param()
+$ErrorActionPreference = 'Stop'
+
+. "$PSScriptRoot/common.ps1"
+
+$paths = Get-FeaturePathsEnv
+if (-not (Test-FeatureBranch -Branch $paths.CURRENT_BRANCH)) { exit 1 }
+
+Write-Output "REPO_ROOT: $($paths.REPO_ROOT)"
+Write-Output "BRANCH: $($paths.CURRENT_BRANCH)"
+Write-Output "FEATURE_DIR: $($paths.FEATURE_DIR)"
+Write-Output "FEATURE_SPEC: $($paths.FEATURE_SPEC)"
+Write-Output "IMPL_PLAN: $($paths.IMPL_PLAN)"
+Write-Output "TASKS: $($paths.TASKS)"

scripts/powershell/setup-plan.ps1

@@ -1,61 +1,21 @@
 #!/usr/bin/env pwsh
-# Setup implementation plan for a feature
-
 [CmdletBinding()]
-param(
-    [switch]$Json,
-    [switch]$Help
-)
-
+param([switch]$Json)
 $ErrorActionPreference = 'Stop'
-
-# Show help if requested
-if ($Help) {
-    Write-Output "Usage: ./setup-plan.ps1 [-Json] [-Help]"
-    Write-Output "  -Json     Output results in JSON format"
-    Write-Output "  -Help     Show this help message"
-    exit 0
-}
-
-# Load common functions
 . "$PSScriptRoot/common.ps1"
 
-# Get all paths and variables from common functions
 $paths = Get-FeaturePathsEnv
+if (-not (Test-FeatureBranch -Branch $paths.CURRENT_BRANCH)) { exit 1 }
 
-# Check if we're on a proper feature branch (only for git repos)
-if (-not (Test-FeatureBranch -Branch $paths.CURRENT_BRANCH -HasGit $paths.HAS_GIT)) { 
-    exit 1 
-}
-
-# Ensure the feature directory exists
 New-Item -ItemType Directory -Path $paths.FEATURE_DIR -Force | Out-Null
+$template = Join-Path $paths.REPO_ROOT 'templates/plan-template.md'
+if (Test-Path $template) { Copy-Item $template $paths.IMPL_PLAN -Force }
 
-# 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 {
-    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
 if ($Json) {
-    $result = [PSCustomObject]@{ 
-        FEATURE_SPEC = $paths.FEATURE_SPEC
-        IMPL_PLAN = $paths.IMPL_PLAN
-        SPECS_DIR = $paths.FEATURE_DIR
-        BRANCH = $paths.CURRENT_BRANCH
-        HAS_GIT = $paths.HAS_GIT
-    }
-    $result | ConvertTo-Json -Compress
+    [PSCustomObject]@{ FEATURE_SPEC=$paths.FEATURE_SPEC; IMPL_PLAN=$paths.IMPL_PLAN; SPECS_DIR=$paths.FEATURE_DIR; BRANCH=$paths.CURRENT_BRANCH } | ConvertTo-Json -Compress
 } else {
     Write-Output "FEATURE_SPEC: $($paths.FEATURE_SPEC)"
     Write-Output "IMPL_PLAN: $($paths.IMPL_PLAN)"
     Write-Output "SPECS_DIR: $($paths.FEATURE_DIR)"
     Write-Output "BRANCH: $($paths.CURRENT_BRANCH)"
-    Write-Output "HAS_GIT: $($paths.HAS_GIT)"
 }

scripts/powershell/update-agent-context.ps1

@@ -1,469 +1,91 @@
 #!/usr/bin/env pwsh
-<#!
-.SYNOPSIS
-Update agent context files with information from plan.md (PowerShell version)
-
-.DESCRIPTION
-Mirrors the behavior of scripts/bash/update-agent-context.sh:
- 1. Environment Validation
- 2. Plan Data Extraction
- 3. Agent File Management (create from template or update existing)
- 4. Content Generation (technology stack, recent changes, timestamp)
- 5. Multi-Agent Support (claude, gemini, copilot, cursor-agent, qwen, opencode, codex, windsurf, kilocode, auggie, roo, codebuddy, amp, shai, tabnine, kiro-cli, agy, bob, vibe, qodercli, generic)
-
-.PARAMETER AgentType
-Optional agent key to update a single agent. If omitted, updates all existing agent files (creating a default Claude file if none exist).
-
-.EXAMPLE
-./update-agent-context.ps1 -AgentType claude
-
-.EXAMPLE
-./update-agent-context.ps1   # Updates all existing agent files
-
-.NOTES
-Relies on common helper functions in common.ps1
-#>
-param(
-    [Parameter(Position=0)]
-    [ValidateSet('claude','gemini','copilot','cursor-agent','qwen','opencode','codex','windsurf','kilocode','auggie','roo','codebuddy','amp','shai','tabnine','kiro-cli','agy','bob','qodercli','vibe','generic')]
-    [string]$AgentType
-)
-
+[CmdletBinding()]
+param([string]$AgentType)
 $ErrorActionPreference = 'Stop'
 
-# Import common helpers
-$ScriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
-. (Join-Path $ScriptDir 'common.ps1')
+$repoRoot = git rev-parse --show-toplevel
+$currentBranch = git rev-parse --abbrev-ref HEAD
+$featureDir = Join-Path $repoRoot "specs/$currentBranch"
+$newPlan = Join-Path $featureDir 'plan.md'
+if (-not (Test-Path $newPlan)) { Write-Error "ERROR: No plan.md found at $newPlan"; exit 1 }
 
-# Acquire environment paths
-$envData = Get-FeaturePathsEnv
-$REPO_ROOT     = $envData.REPO_ROOT
-$CURRENT_BRANCH = $envData.CURRENT_BRANCH
-$HAS_GIT       = $envData.HAS_GIT
-$IMPL_PLAN     = $envData.IMPL_PLAN
-$NEW_PLAN = $IMPL_PLAN
+$claudeFile = Join-Path $repoRoot 'CLAUDE.md'
+$geminiFile = Join-Path $repoRoot 'GEMINI.md'
+$copilotFile = Join-Path $repoRoot '.github/copilot-instructions.md'
 
-# Agent file paths
-$CLAUDE_FILE   = Join-Path $REPO_ROOT 'CLAUDE.md'
-$GEMINI_FILE   = Join-Path $REPO_ROOT 'GEMINI.md'
-$COPILOT_FILE  = Join-Path $REPO_ROOT '.github/agents/copilot-instructions.md'
-$CURSOR_FILE   = Join-Path $REPO_ROOT '.cursor/rules/specify-rules.mdc'
-$QWEN_FILE     = Join-Path $REPO_ROOT 'QWEN.md'
-$AGENTS_FILE   = Join-Path $REPO_ROOT 'AGENTS.md'
-$WINDSURF_FILE = Join-Path $REPO_ROOT '.windsurf/rules/specify-rules.md'
-$KILOCODE_FILE = Join-Path $REPO_ROOT '.kilocode/rules/specify-rules.md'
-$AUGGIE_FILE   = Join-Path $REPO_ROOT '.augment/rules/specify-rules.md'
-$ROO_FILE      = Join-Path $REPO_ROOT '.roo/rules/specify-rules.md'
-$CODEBUDDY_FILE = Join-Path $REPO_ROOT 'CODEBUDDY.md'
-$QODER_FILE    = Join-Path $REPO_ROOT 'QODER.md'
-$AMP_FILE      = Join-Path $REPO_ROOT 'AGENTS.md'
-$SHAI_FILE     = Join-Path $REPO_ROOT 'SHAI.md'
-$TABNINE_FILE  = Join-Path $REPO_ROOT 'TABNINE.md'
-$KIRO_FILE     = Join-Path $REPO_ROOT 'AGENTS.md'
-$AGY_FILE      = Join-Path $REPO_ROOT '.agent/rules/specify-rules.md'
-$BOB_FILE      = Join-Path $REPO_ROOT 'AGENTS.md'
-$VIBE_FILE     = Join-Path $REPO_ROOT '.vibe/agents/specify-agents.md'
+Write-Output "=== Updating agent context files for feature $currentBranch ==="
 
-$TEMPLATE_FILE = Join-Path $REPO_ROOT '.specify/templates/agent-file-template.md'
-
-# Parsed plan data placeholders
-$script:NEW_LANG = ''
-$script:NEW_FRAMEWORK = ''
-$script:NEW_DB = ''
-$script:NEW_PROJECT_TYPE = ''
-
-function Write-Info { 
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$Message
-    )
-    Write-Host "INFO: $Message" 
+function Get-PlanValue($pattern) {
+    if (-not (Test-Path $newPlan)) { return '' }
+    $line = Select-String -Path $newPlan -Pattern $pattern | Select-Object -First 1
+    if ($line) { return ($line.Line -replace "^\*\*$pattern\*\*: ", '') }
+    return ''
 }
 
-function Write-Success { 
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$Message
-    )
-    Write-Host "$([char]0x2713) $Message" 
+$newLang = Get-PlanValue 'Language/Version'
+$newFramework = Get-PlanValue 'Primary Dependencies'
+$newTesting = Get-PlanValue 'Testing'
+$newDb = Get-PlanValue 'Storage'
+$newProjectType = Get-PlanValue 'Project Type'
+
+function Initialize-AgentFile($targetFile, $agentName) {
+    if (Test-Path $targetFile) { return }
+    $template = Join-Path $repoRoot 'templates/agent-file-template.md'
+    if (-not (Test-Path $template)) { Write-Error "Template not found: $template"; return }
+    $content = Get-Content $template -Raw
+    $content = $content.Replace('[PROJECT NAME]', (Split-Path $repoRoot -Leaf))
+    $content = $content.Replace('[DATE]', (Get-Date -Format 'yyyy-MM-dd'))
+    $content = $content.Replace('[EXTRACTED FROM ALL PLAN.MD FILES]', "- $newLang + $newFramework ($currentBranch)")
+    if ($newProjectType -match 'web') { $structure = "backend/`nfrontend/`ntests/" } else { $structure = "src/`ntests/" }
+    $content = $content.Replace('[ACTUAL STRUCTURE FROM PLANS]', $structure)
+    if ($newLang -match 'Python') { $commands = 'cd src && pytest && ruff check .' }
+    elseif ($newLang -match 'Rust') { $commands = 'cargo test && cargo clippy' }
+    elseif ($newLang -match 'JavaScript|TypeScript') { $commands = 'npm test && npm run lint' }
+    else { $commands = "# Add commands for $newLang" }
+    $content = $content.Replace('[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES]', $commands)
+    $content = $content.Replace('[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE]', "${newLang}: Follow standard conventions")
+    $content = $content.Replace('[LAST 3 FEATURES AND WHAT THEY ADDED]', "- ${currentBranch}: Added ${newLang} + ${newFramework}")
+    $content | Set-Content $targetFile -Encoding UTF8
 }
 
-function Write-WarningMsg { 
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$Message
-    )
-    Write-Warning $Message 
-}
-
-function Write-Err { 
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$Message
-    )
-    Write-Host "ERROR: $Message" -ForegroundColor Red 
-}
-
-function Validate-Environment {
-    if (-not $CURRENT_BRANCH) {
-        Write-Err 'Unable to determine current feature'
-        if ($HAS_GIT) { Write-Info "Make sure you're on a feature branch" } else { Write-Info 'Set SPECIFY_FEATURE environment variable or create a feature first' }
-        exit 1
-    }
-    if (-not (Test-Path $NEW_PLAN)) {
-        Write-Err "No plan.md found at $NEW_PLAN"
-        Write-Info 'Ensure you are working on a feature with a corresponding spec directory'
-        if (-not $HAS_GIT) { Write-Info 'Use: $env:SPECIFY_FEATURE=your-feature-name or create a new feature first' }
-        exit 1
-    }
-    if (-not (Test-Path $TEMPLATE_FILE)) {
-        Write-Err "Template file not found at $TEMPLATE_FILE"
-        Write-Info 'Run specify init to scaffold .specify/templates, or add agent-file-template.md there.'
-        exit 1
+function Update-AgentFile($targetFile, $agentName) {
+    if (-not (Test-Path $targetFile)) { Initialize-AgentFile $targetFile $agentName; return }
+    $content = Get-Content $targetFile -Raw
+    if ($newLang -and ($content -notmatch [regex]::Escape($newLang))) { $content = $content -replace '(## Active Technologies\n)', "`$1- $newLang + $newFramework ($currentBranch)`n" }
+    if ($newDb -and $newDb -ne 'N/A' -and ($content -notmatch [regex]::Escape($newDb))) { $content = $content -replace '(## Active Technologies\n)', "`$1- $newDb ($currentBranch)`n" }
+    if ($content -match '## Recent Changes\n([\s\S]*?)(\n\n|$)') {
+        $changesBlock = $matches[1].Trim().Split("`n")
+        $changesBlock = ,"- $currentBranch: Added $newLang + $newFramework" + $changesBlock
+        $changesBlock = $changesBlock | Where-Object { $_ } | Select-Object -First 3
+        $joined = ($changesBlock -join "`n")
+        $content = [regex]::Replace($content, '## Recent Changes\n([\s\S]*?)(\n\n|$)', "## Recent Changes`n$joined`n`n")
     }
+    $content = [regex]::Replace($content, 'Last updated: \d{4}-\d{2}-\d{2}', "Last updated: $(Get-Date -Format 'yyyy-MM-dd')")
+    $content | Set-Content $targetFile -Encoding UTF8
+    Write-Output "✅ $agentName context file updated successfully"
 }
 
-function Extract-PlanField {
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$FieldPattern,
-        [Parameter(Mandatory=$true)]
-        [string]$PlanFile
-    )
-    if (-not (Test-Path $PlanFile)) { return '' }
-    # Lines like **Language/Version**: Python 3.12
-    $regex = "^\*\*$([Regex]::Escape($FieldPattern))\*\*: (.+)$"
-    Get-Content -LiteralPath $PlanFile -Encoding utf8 | ForEach-Object {
-        if ($_ -match $regex) { 
-            $val = $Matches[1].Trim()
-            if ($val -notin @('NEEDS CLARIFICATION','N/A')) { return $val }
+switch ($AgentType) {
+    'claude' { Update-AgentFile $claudeFile 'Claude Code' }
+    'gemini' { Update-AgentFile $geminiFile 'Gemini CLI' }
+    'copilot' { Update-AgentFile $copilotFile 'GitHub Copilot' }
+    '' {
+        foreach ($pair in @(@{file=$claudeFile; name='Claude Code'}, @{file=$geminiFile; name='Gemini CLI'}, @{file=$copilotFile; name='GitHub Copilot'})) {
+            if (Test-Path $pair.file) { Update-AgentFile $pair.file $pair.name }
         }
-    } | Select-Object -First 1
-}
-
-function Parse-PlanData {
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$PlanFile
-    )
-    if (-not (Test-Path $PlanFile)) { Write-Err "Plan file not found: $PlanFile"; return $false }
-    Write-Info "Parsing plan data from $PlanFile"
-    $script:NEW_LANG        = Extract-PlanField -FieldPattern 'Language/Version' -PlanFile $PlanFile
-    $script:NEW_FRAMEWORK   = Extract-PlanField -FieldPattern 'Primary Dependencies' -PlanFile $PlanFile
-    $script:NEW_DB          = Extract-PlanField -FieldPattern 'Storage' -PlanFile $PlanFile
-    $script:NEW_PROJECT_TYPE = Extract-PlanField -FieldPattern 'Project Type' -PlanFile $PlanFile
-
-    if ($NEW_LANG) { Write-Info "Found language: $NEW_LANG" } else { Write-WarningMsg 'No language information found in plan' }
-    if ($NEW_FRAMEWORK) { Write-Info "Found framework: $NEW_FRAMEWORK" }
-    if ($NEW_DB -and $NEW_DB -ne 'N/A') { Write-Info "Found database: $NEW_DB" }
-    if ($NEW_PROJECT_TYPE) { Write-Info "Found project type: $NEW_PROJECT_TYPE" }
-    return $true
-}
-
-function Format-TechnologyStack {
-    param(
-        [Parameter(Mandatory=$false)]
-        [string]$Lang,
-        [Parameter(Mandatory=$false)]
-        [string]$Framework
-    )
-    $parts = @()
-    if ($Lang -and $Lang -ne 'NEEDS CLARIFICATION') { $parts += $Lang }
-    if ($Framework -and $Framework -notin @('NEEDS CLARIFICATION','N/A')) { $parts += $Framework }
-    if (-not $parts) { return '' }
-    return ($parts -join ' + ')
-}
-
-function Get-ProjectStructure { 
-    param(
-        [Parameter(Mandatory=$false)]
-        [string]$ProjectType
-    )
-    if ($ProjectType -match 'web') { return "backend/`nfrontend/`ntests/" } else { return "src/`ntests/" } 
-}
-
-function Get-CommandsForLanguage { 
-    param(
-        [Parameter(Mandatory=$false)]
-        [string]$Lang
-    )
-    switch -Regex ($Lang) {
-        'Python' { return "cd src; pytest; ruff check ." }
-        'Rust' { return "cargo test; cargo clippy" }
-        'JavaScript|TypeScript' { return "npm test; npm run lint" }
-        default { return "# Add commands for $Lang" }
-    }
-}
-
-function Get-LanguageConventions { 
-    param(
-        [Parameter(Mandatory=$false)]
-        [string]$Lang
-    )
-    if ($Lang) { "${Lang}: Follow standard conventions" } else { 'General: Follow standard conventions' } 
-}
-
-function New-AgentFile {
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$TargetFile,
-        [Parameter(Mandatory=$true)]
-        [string]$ProjectName,
-        [Parameter(Mandatory=$true)]
-        [datetime]$Date
-    )
-    if (-not (Test-Path $TEMPLATE_FILE)) { Write-Err "Template not found at $TEMPLATE_FILE"; return $false }
-    $temp = New-TemporaryFile
-    Copy-Item -LiteralPath $TEMPLATE_FILE -Destination $temp -Force
-
-    $projectStructure = Get-ProjectStructure -ProjectType $NEW_PROJECT_TYPE
-    $commands = Get-CommandsForLanguage -Lang $NEW_LANG
-    $languageConventions = Get-LanguageConventions -Lang $NEW_LANG
-
-    $escaped_lang = $NEW_LANG
-    $escaped_framework = $NEW_FRAMEWORK
-    $escaped_branch = $CURRENT_BRANCH
-
-    $content = Get-Content -LiteralPath $temp -Raw -Encoding utf8
-    $content = $content -replace '\[PROJECT NAME\]',$ProjectName
-    $content = $content -replace '\[DATE\]',$Date.ToString('yyyy-MM-dd')
-    
-    # Build the technology stack string safely
-    $techStackForTemplate = ""
-    if ($escaped_lang -and $escaped_framework) {
-        $techStackForTemplate = "- $escaped_lang + $escaped_framework ($escaped_branch)"
-    } elseif ($escaped_lang) {
-        $techStackForTemplate = "- $escaped_lang ($escaped_branch)"
-    } elseif ($escaped_framework) {
-        $techStackForTemplate = "- $escaped_framework ($escaped_branch)"
-    }
-    
-    $content = $content -replace '\[EXTRACTED FROM ALL PLAN.MD FILES\]',$techStackForTemplate
-    # For project structure we manually embed (keep newlines)
-    $escapedStructure = [Regex]::Escape($projectStructure)
-    $content = $content -replace '\[ACTUAL STRUCTURE FROM PLANS\]',$escapedStructure
-    # Replace escaped newlines placeholder after all replacements
-    $content = $content -replace '\[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES\]',$commands
-    $content = $content -replace '\[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE\]',$languageConventions
-    
-    # Build the recent changes string safely
-    $recentChangesForTemplate = ""
-    if ($escaped_lang -and $escaped_framework) {
-        $recentChangesForTemplate = "- ${escaped_branch}: Added ${escaped_lang} + ${escaped_framework}"
-    } elseif ($escaped_lang) {
-        $recentChangesForTemplate = "- ${escaped_branch}: Added ${escaped_lang}"
-    } elseif ($escaped_framework) {
-        $recentChangesForTemplate = "- ${escaped_branch}: Added ${escaped_framework}"
-    }
-    
-    $content = $content -replace '\[LAST 3 FEATURES AND WHAT THEY ADDED\]',$recentChangesForTemplate
-    # Convert literal \n sequences introduced by Escape to real newlines
-    $content = $content -replace '\\n',[Environment]::NewLine
-
-    # Prepend Cursor frontmatter for .mdc files so rules are auto-included
-    if ($TargetFile -match '\.mdc$') {
-        $frontmatter = @('---','description: Project Development Guidelines','globs: ["**/*"]','alwaysApply: true','---','') -join [Environment]::NewLine
-        $content = $frontmatter + $content
-    }
-
-    $parent = Split-Path -Parent $TargetFile
-    if (-not (Test-Path $parent)) { New-Item -ItemType Directory -Path $parent | Out-Null }
-    Set-Content -LiteralPath $TargetFile -Value $content -NoNewline -Encoding utf8
-    Remove-Item $temp -Force
-    return $true
-}
-
-function Update-ExistingAgentFile {
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$TargetFile,
-        [Parameter(Mandatory=$true)]
-        [datetime]$Date
-    )
-    if (-not (Test-Path $TargetFile)) { return (New-AgentFile -TargetFile $TargetFile -ProjectName (Split-Path $REPO_ROOT -Leaf) -Date $Date) }
-
-    $techStack = Format-TechnologyStack -Lang $NEW_LANG -Framework $NEW_FRAMEWORK
-    $newTechEntries = @()
-    if ($techStack) {
-        $escapedTechStack = [Regex]::Escape($techStack)
-        if (-not (Select-String -Pattern $escapedTechStack -Path $TargetFile -Quiet)) { 
-            $newTechEntries += "- $techStack ($CURRENT_BRANCH)" 
+        if (-not (Test-Path $claudeFile) -and -not (Test-Path $geminiFile) -and -not (Test-Path $copilotFile)) {
+            Write-Output 'No agent context files found. Creating Claude Code context file by default.'
+            Update-AgentFile $claudeFile 'Claude Code'
         }
     }
-    if ($NEW_DB -and $NEW_DB -notin @('N/A','NEEDS CLARIFICATION')) {
-        $escapedDB = [Regex]::Escape($NEW_DB)
-        if (-not (Select-String -Pattern $escapedDB -Path $TargetFile -Quiet)) { 
-            $newTechEntries += "- $NEW_DB ($CURRENT_BRANCH)" 
-        }
-    }
-    $newChangeEntry = ''
-    if ($techStack) { $newChangeEntry = "- ${CURRENT_BRANCH}: Added ${techStack}" }
-    elseif ($NEW_DB -and $NEW_DB -notin @('N/A','NEEDS CLARIFICATION')) { $newChangeEntry = "- ${CURRENT_BRANCH}: Added ${NEW_DB}" }
-
-    $lines = Get-Content -LiteralPath $TargetFile -Encoding utf8
-    $output = New-Object System.Collections.Generic.List[string]
-    $inTech = $false; $inChanges = $false; $techAdded = $false; $changeAdded = $false; $existingChanges = 0
-
-    for ($i=0; $i -lt $lines.Count; $i++) {
-        $line = $lines[$i]
-        if ($line -eq '## Active Technologies') {
-            $output.Add($line)
-            $inTech = $true
-            continue
-        }
-        if ($inTech -and $line -match '^##\s') {
-            if (-not $techAdded -and $newTechEntries.Count -gt 0) { $newTechEntries | ForEach-Object { $output.Add($_) }; $techAdded = $true }
-            $output.Add($line); $inTech = $false; continue
-        }
-        if ($inTech -and [string]::IsNullOrWhiteSpace($line)) {
-            if (-not $techAdded -and $newTechEntries.Count -gt 0) { $newTechEntries | ForEach-Object { $output.Add($_) }; $techAdded = $true }
-            $output.Add($line); continue
-        }
-        if ($line -eq '## Recent Changes') {
-            $output.Add($line)
-            if ($newChangeEntry) { $output.Add($newChangeEntry); $changeAdded = $true }
-            $inChanges = $true
-            continue
-        }
-        if ($inChanges -and $line -match '^##\s') { $output.Add($line); $inChanges = $false; continue }
-        if ($inChanges -and $line -match '^- ') {
-            if ($existingChanges -lt 2) { $output.Add($line); $existingChanges++ }
-            continue
-        }
-        if ($line -match '\*\*Last updated\*\*: .*\d{4}-\d{2}-\d{2}') {
-            $output.Add(($line -replace '\d{4}-\d{2}-\d{2}',$Date.ToString('yyyy-MM-dd')))
-            continue
-        }
-        $output.Add($line)
-    }
-
-    # Post-loop check: if we're still in the Active Technologies section and haven't added new entries
-    if ($inTech -and -not $techAdded -and $newTechEntries.Count -gt 0) {
-        $newTechEntries | ForEach-Object { $output.Add($_) }
-    }
-
-    # Ensure Cursor .mdc files have YAML frontmatter for auto-inclusion
-    if ($TargetFile -match '\.mdc$' -and $output.Count -gt 0 -and $output[0] -ne '---') {
-        $frontmatter = @('---','description: Project Development Guidelines','globs: ["**/*"]','alwaysApply: true','---','')
-        $output.InsertRange(0, $frontmatter)
-    }
-
-    Set-Content -LiteralPath $TargetFile -Value ($output -join [Environment]::NewLine) -Encoding utf8
-    return $true
+    Default { Write-Error "ERROR: Unknown agent type '$AgentType'. Use: claude, gemini, copilot, or leave empty for all."; exit 1 }
 }
 
-function Update-AgentFile {
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$TargetFile,
-        [Parameter(Mandatory=$true)]
-        [string]$AgentName
-    )
-    if (-not $TargetFile -or -not $AgentName) { Write-Err 'Update-AgentFile requires TargetFile and AgentName'; return $false }
-    Write-Info "Updating $AgentName context file: $TargetFile"
-    $projectName = Split-Path $REPO_ROOT -Leaf
-    $date = Get-Date
+Write-Output ''
+Write-Output 'Summary of changes:'
+if ($newLang) { Write-Output "- Added language: $newLang" }
+if ($newFramework) { Write-Output "- Added framework: $newFramework" }
+if ($newDb -and $newDb -ne 'N/A') { Write-Output "- Added database: $newDb" }
 
-    $dir = Split-Path -Parent $TargetFile
-    if (-not (Test-Path $dir)) { New-Item -ItemType Directory -Path $dir | Out-Null }
-
-    if (-not (Test-Path $TargetFile)) {
-        if (New-AgentFile -TargetFile $TargetFile -ProjectName $projectName -Date $date) { Write-Success "Created new $AgentName context file" } else { Write-Err 'Failed to create new agent file'; return $false }
-    } else {
-        try {
-            if (Update-ExistingAgentFile -TargetFile $TargetFile -Date $date) { Write-Success "Updated existing $AgentName context file" } else { Write-Err 'Failed to update agent file'; return $false }
-        } catch {
-            Write-Err "Cannot access or update existing file: $TargetFile. $_"
-            return $false
-        }
-    }
-    return $true
-}
-
-function Update-SpecificAgent {
-    param(
-        [Parameter(Mandatory=$true)]
-        [string]$Type
-    )
-    switch ($Type) {
-        'claude'   { Update-AgentFile -TargetFile $CLAUDE_FILE   -AgentName 'Claude Code' }
-        'gemini'   { Update-AgentFile -TargetFile $GEMINI_FILE   -AgentName 'Gemini CLI' }
-        'copilot'  { Update-AgentFile -TargetFile $COPILOT_FILE  -AgentName 'GitHub Copilot' }
-        'cursor-agent' { Update-AgentFile -TargetFile $CURSOR_FILE   -AgentName 'Cursor IDE' }
-        'qwen'     { Update-AgentFile -TargetFile $QWEN_FILE     -AgentName 'Qwen Code' }
-        'opencode' { Update-AgentFile -TargetFile $AGENTS_FILE   -AgentName 'opencode' }
-        'codex'    { Update-AgentFile -TargetFile $AGENTS_FILE   -AgentName 'Codex CLI' }
-        'windsurf' { Update-AgentFile -TargetFile $WINDSURF_FILE -AgentName 'Windsurf' }
-        'kilocode' { Update-AgentFile -TargetFile $KILOCODE_FILE -AgentName 'Kilo Code' }
-        'auggie'   { Update-AgentFile -TargetFile $AUGGIE_FILE   -AgentName 'Auggie CLI' }
-        'roo'      { Update-AgentFile -TargetFile $ROO_FILE      -AgentName 'Roo Code' }
-        'codebuddy' { Update-AgentFile -TargetFile $CODEBUDDY_FILE -AgentName 'CodeBuddy CLI' }
-        'qodercli' { Update-AgentFile -TargetFile $QODER_FILE    -AgentName 'Qoder CLI' }
-        'amp'      { Update-AgentFile -TargetFile $AMP_FILE      -AgentName 'Amp' }
-        'shai'     { Update-AgentFile -TargetFile $SHAI_FILE     -AgentName 'SHAI' }
-        'tabnine'  { Update-AgentFile -TargetFile $TABNINE_FILE  -AgentName 'Tabnine CLI' }
-        'kiro-cli' { Update-AgentFile -TargetFile $KIRO_FILE     -AgentName 'Kiro CLI' }
-        'agy'      { Update-AgentFile -TargetFile $AGY_FILE      -AgentName 'Antigravity' }
-        'bob'      { Update-AgentFile -TargetFile $BOB_FILE      -AgentName 'IBM Bob' }
-        'vibe'     { Update-AgentFile -TargetFile $VIBE_FILE     -AgentName 'Mistral Vibe' }
-        'generic'  { Write-Info 'Generic agent: no predefined context file. Use the agent-specific update script for your agent.' }
-        default { Write-Err "Unknown agent type '$Type'"; Write-Err 'Expected: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|codebuddy|amp|shai|tabnine|kiro-cli|agy|bob|vibe|qodercli|generic'; return $false }
-    }
-}
-
-function Update-AllExistingAgents {
-    $found = $false
-    $ok = $true
-    if (Test-Path $CLAUDE_FILE)   { if (-not (Update-AgentFile -TargetFile $CLAUDE_FILE   -AgentName 'Claude Code')) { $ok = $false }; $found = $true }
-    if (Test-Path $GEMINI_FILE)   { if (-not (Update-AgentFile -TargetFile $GEMINI_FILE   -AgentName 'Gemini CLI')) { $ok = $false }; $found = $true }
-    if (Test-Path $COPILOT_FILE)  { if (-not (Update-AgentFile -TargetFile $COPILOT_FILE  -AgentName 'GitHub Copilot')) { $ok = $false }; $found = $true }
-    if (Test-Path $CURSOR_FILE)   { if (-not (Update-AgentFile -TargetFile $CURSOR_FILE   -AgentName 'Cursor IDE')) { $ok = $false }; $found = $true }
-    if (Test-Path $QWEN_FILE)     { if (-not (Update-AgentFile -TargetFile $QWEN_FILE     -AgentName 'Qwen Code')) { $ok = $false }; $found = $true }
-    if (Test-Path $AGENTS_FILE)   { if (-not (Update-AgentFile -TargetFile $AGENTS_FILE   -AgentName 'Codex/opencode')) { $ok = $false }; $found = $true }
-    if (Test-Path $WINDSURF_FILE) { if (-not (Update-AgentFile -TargetFile $WINDSURF_FILE -AgentName 'Windsurf')) { $ok = $false }; $found = $true }
-    if (Test-Path $KILOCODE_FILE) { if (-not (Update-AgentFile -TargetFile $KILOCODE_FILE -AgentName 'Kilo Code')) { $ok = $false }; $found = $true }
-    if (Test-Path $AUGGIE_FILE)   { if (-not (Update-AgentFile -TargetFile $AUGGIE_FILE   -AgentName 'Auggie CLI')) { $ok = $false }; $found = $true }
-    if (Test-Path $ROO_FILE)      { if (-not (Update-AgentFile -TargetFile $ROO_FILE      -AgentName 'Roo Code')) { $ok = $false }; $found = $true }
-    if (Test-Path $CODEBUDDY_FILE) { if (-not (Update-AgentFile -TargetFile $CODEBUDDY_FILE -AgentName 'CodeBuddy CLI')) { $ok = $false }; $found = $true }
-    if (Test-Path $QODER_FILE)    { if (-not (Update-AgentFile -TargetFile $QODER_FILE    -AgentName 'Qoder CLI')) { $ok = $false }; $found = $true }
-    if (Test-Path $SHAI_FILE)     { if (-not (Update-AgentFile -TargetFile $SHAI_FILE     -AgentName 'SHAI')) { $ok = $false }; $found = $true }
-    if (Test-Path $TABNINE_FILE)  { if (-not (Update-AgentFile -TargetFile $TABNINE_FILE  -AgentName 'Tabnine CLI')) { $ok = $false }; $found = $true }
-    if (Test-Path $KIRO_FILE)     { if (-not (Update-AgentFile -TargetFile $KIRO_FILE     -AgentName 'Kiro CLI')) { $ok = $false }; $found = $true }
-    if (Test-Path $AGY_FILE)      { if (-not (Update-AgentFile -TargetFile $AGY_FILE      -AgentName 'Antigravity')) { $ok = $false }; $found = $true }
-    if (Test-Path $BOB_FILE)      { if (-not (Update-AgentFile -TargetFile $BOB_FILE      -AgentName 'IBM Bob')) { $ok = $false }; $found = $true }
-    if (Test-Path $VIBE_FILE)     { if (-not (Update-AgentFile -TargetFile $VIBE_FILE     -AgentName 'Mistral Vibe')) { $ok = $false }; $found = $true }
-    if (-not $found) {
-        Write-Info 'No existing agent files found, creating default Claude file...'
-        if (-not (Update-AgentFile -TargetFile $CLAUDE_FILE -AgentName 'Claude Code')) { $ok = $false }
-    }
-    return $ok
-}
-
-function Print-Summary {
-    Write-Host ''
-    Write-Info 'Summary of changes:'
-    if ($NEW_LANG) { Write-Host "  - Added language: $NEW_LANG" }
-    if ($NEW_FRAMEWORK) { Write-Host "  - Added framework: $NEW_FRAMEWORK" }
-    if ($NEW_DB -and $NEW_DB -ne 'N/A') { Write-Host "  - Added database: $NEW_DB" }
-    Write-Host ''
-    Write-Info 'Usage: ./update-agent-context.ps1 [-AgentType claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|codebuddy|amp|shai|tabnine|kiro-cli|agy|bob|vibe|qodercli|generic]'
-}
-
-function Main {
-    Validate-Environment
-    Write-Info "=== Updating agent context files for feature $CURRENT_BRANCH ==="
-    if (-not (Parse-PlanData -PlanFile $NEW_PLAN)) { Write-Err 'Failed to parse plan data'; exit 1 }
-    $success = $true
-    if ($AgentType) {
-        Write-Info "Updating specific agent: $AgentType"
-        if (-not (Update-SpecificAgent -Type $AgentType)) { $success = $false }
-    }
-    else {
-        Write-Info 'No agent specified, updating all existing agent files...'
-        if (-not (Update-AllExistingAgents)) { $success = $false }
-    }
-    Print-Summary
-    if ($success) { Write-Success 'Agent context update completed successfully'; exit 0 } else { Write-Err 'Agent context update completed with errors'; exit 1 }
-}
-
-Main
+Write-Output ''
+Write-Output 'Usage: ./update-agent-context.ps1 [claude|gemini|copilot]'

spec-driven.md

@@ -2,15 +2,15 @@
 
 ## The Power Inversion
 
-For decades, code has been king. Specifications served code—they were the scaffolding we built and then discarded once the "real work" of coding began. We wrote PRDs to guide development, created design docs to inform implementation, drew diagrams to visualize architecture. But these were always subordinate to the code itself. Code was truth. Everything else was, at best, good intentions. Code was the source of truth, and as it moved forward, specs rarely kept pace. As the asset (code) and the implementation are one, it's not easy to have a parallel implementation without trying to build from the code.
+For decades, code has been king. Specifications served code—they were the scaffolding we built and then discarded once the "real work" of coding began. We wrote PRDs to guide development, created design docs to inform implementation, drew diagrams to visualize architecture. But these were always subordinate to the code itself. Code was truth. Everything else was, at best, good intentions. Code was the source of truth, as it moved forward, and spec's rarely kept pace. As the asset (code) and the implementation are one, it's not easy to have a parallel implementation without trying to build from the code.
 
-Spec-Driven Development (SDD) inverts this power structure. Specifications don't serve code—code serves specifications. The Product Requirements Document (PRD) isn't a guide for implementation; it's the source that generates implementation. Technical plans aren't documents that inform coding; they're precise definitions that produce code. This isn't an incremental improvement to how we build software. It's a fundamental rethinking of what drives development.
+Spec-Driven Development (SDD) inverts this power structure. Specifications don't serve code—code serves specifications. The (Product Requirements Document-Specification) PRD isn't a guide for implementation; it's the source that generates implementation. Technical plans aren't documents that inform coding; they're precise definitions that produce code. This isn't an incremental improvement to how we build software. It's a fundamental rethinking of what drives development.
 
-The gap between specification and implementation has plagued software development since its inception. We've tried to bridge it with better documentation, more detailed requirements, stricter processes. These approaches fail because they accept the gap as inevitable. They try to narrow it but never eliminate it. SDD eliminates the gap by making specifications and their concrete implementation plans born from the specification executable. When specifications and implementation plans generate code, there is no gap—only transformation.
+The gap between specification and implementation has plagued software development since its inception. We've tried to bridge it with better documentation, more detailed requirements, stricter processes. These approaches fail because they accept the gap as inevitable. They try to narrow it but never eliminate it. SDD eliminates the gap by making specifications or and their concrete implementation plans born from the specification executable. When specifications to implementation plans generate code, there is no gap—only transformation.
 
 This transformation is now possible because AI can understand and implement complex specifications, and create detailed implementation plans. But raw AI generation without structure produces chaos. SDD provides that structure through specifications and subsequent implementation plans that are precise, complete, and unambiguous enough to generate working systems. The specification becomes the primary artifact. Code becomes its expression (as an implementation from the implementation plan) in a particular language and framework.
 
-In this new world, maintaining software means evolving specifications. The intent of the development team is expressed in natural language ("**intent-driven development**"), design assets, core principles and other guidelines. The **lingua franca** of development moves to a higher level, and code is the last-mile approach.
+In this new world, maintaining software means evolving specifications. The intent of the development team is expressed in natural language ("**intent-driven development**"), design assets, core principles and other guidelines . The **lingua franca** of development moves to a higher-level, and code is the last-mile approach.
 
 Debugging means fixing specifications and their implementation plans that generate incorrect code. Refactoring means restructuring for clarity. The entire development workflow reorganizes around specifications as the central source of truth, with implementation plans and code as the continuously regenerated output. Updating apps with new features or creating a new parallel implementation because we are creative beings, means revisiting the specification and creating new implementation plans. This process is therefore a 0 -> 1, (1', ..), 2, 3, N.
 
@@ -18,7 +18,7 @@ The development team focuses in on their creativity, experimentation, their crit
 
 ## The SDD Workflow in Practice
 
-The workflow begins with an idea—often vague and incomplete. Through iterative dialogue with AI, this idea becomes a comprehensive PRD. The AI asks clarifying questions, identifies edge cases, and helps define precise acceptance criteria. What might take days of meetings and documentation in traditional development happens in hours of focused specification work. This transforms the traditional SDLC—requirements and design become continuous activities rather than discrete phases. This is supportive of a **team process**, where team-reviewed specifications are expressed and versioned, created in branches, and merged.
+The workflow begins with an idea—often vague and incomplete. Through iterative dialogue with AI, this idea becomes a comprehensive PRD. The AI asks clarifying questions, identifies edge cases, and helps define precise acceptance criteria. What might take days of meetings and documentation in traditional development happens in hours of focused specification work. This transforms the traditional SDLC—requirements and design become continuous activities rather than discrete phases. This is supportive of a **team process**, that's team reviewed-specifications are expressed and versioned, created in branches, and merged.
 
 When a product manager updates acceptance criteria, implementation plans automatically flag affected technical decisions. When an architect discovers a better pattern, the PRD updates to reflect new possibilities.
 
@@ -34,13 +34,13 @@ The feedback loop extends beyond initial development. Production metrics and inc
 
 Three trends make SDD not just possible but necessary:
 
-First, AI capabilities have reached a threshold where natural language specifications can reliably generate working code. This isn't about replacing developers—it's about amplifying their effectiveness by automating the mechanical translation from specification to implementation. It can amplify exploration and creativity, support "start-over" easily, and support addition, subtraction, and critical thinking.
+First, AI capabilities have reached a threshold where natural language specifications can reliably generate working code. This isn't about replacing developers—it's about amplifying their effectiveness by automating the mechanical translation from specification to implementation. It can amplify exploration and creativity, it can support "start-over" easily, it supports addition subtraction and critical thinking.
 
 Second, software complexity continues to grow exponentially. Modern systems integrate dozens of services, frameworks, and dependencies. Keeping all these pieces aligned with original intent through manual processes becomes increasingly difficult. SDD provides systematic alignment through specification-driven generation. Frameworks may evolve to provide AI-first support, not human-first support, or architect around reusable components.
 
 Third, the pace of change accelerates. Requirements change far more rapidly today than ever before. Pivoting is no longer exceptional—it's expected. Modern product development demands rapid iteration based on user feedback, market conditions, and competitive pressures. Traditional development treats these changes as disruptions. Each pivot requires manually propagating changes through documentation, design, and code. The result is either slow, careful updates that limit velocity, or fast, reckless changes that accumulate technical debt.
 
-SDD can support what-if/simulation experiments: "If we need to re-implement or change the application to promote a business need to sell more T-shirts, how would we implement and experiment for that?"
+SDD can support what-if/simulation experiments, "If we need to re-implement or change the application to promote a business need to sell more T-shirts, how would we implement and experiment for that?".
 
 SDD transforms requirement changes from obstacles into normal workflow. When specifications drive implementation, pivots become systematic regenerations rather than manual rewrites. Change a core requirement in the PRD, and affected implementation plans update automatically. Modify a user story, and corresponding API endpoints regenerate. This isn't just about initial development—it's about maintaining engineering velocity through inevitable changes.
 
@@ -74,7 +74,7 @@ The key is treating specifications as the source of truth, with code as the gene
 
 The SDD methodology is significantly enhanced through three powerful commands that automate the specification → planning → tasking workflow:
 
-### The `/speckit.specify` Command
+### The `/specify` Command
 
 This command transforms a simple feature description (the user-prompt) into a complete, structured specification with automatic repository management:
 
@@ -83,7 +83,7 @@ This command transforms a simple feature description (the user-prompt) into a co
 3. **Template-Based Generation**: Copies and customizes the feature specification template with your requirements
 4. **Directory Structure**: Creates the proper `specs/[branch-name]/` structure for all related documents
 
-### The `/speckit.plan` Command
+### The `/plan` Command
 
 Once a feature specification exists, this command creates a comprehensive implementation plan:
 
@@ -93,7 +93,7 @@ Once a feature specification exists, this command creates a comprehensive implem
 4. **Detailed Documentation**: Generates supporting documents for data models, API contracts, and test scenarios
 5. **Quickstart Validation**: Produces a quickstart guide capturing key validation scenarios
 
-### The `/speckit.tasks` Command
+### The `/tasks` Command
 
 After a plan is created, this command analyzes the plan and related design documents to generate an executable task list:
 
@@ -121,7 +121,7 @@ Total: ~12 hours of documentation work
 
 ```bash
 # Step 1: Create the feature specification (5 minutes)
-/speckit.specify Real-time chat system with message history and user presence
+/specify Real-time chat system with message history and user presence
 
 # This automatically:
 # - Creates branch "003-chat-system"
@@ -129,10 +129,10 @@ Total: ~12 hours of documentation work
 # - Populates it with structured requirements
 
 # Step 2: Generate implementation plan (5 minutes)
-/speckit.plan WebSocket for real-time messaging, PostgreSQL for history, Redis for presence
+/plan WebSocket for real-time messaging, PostgreSQL for history, Redis for presence
 
 # Step 3: Generate executable tasks (5 minutes)
-/speckit.tasks
+/tasks
 
 # This automatically creates:
 # - specs/003-chat-system/plan.md
@@ -195,7 +195,6 @@ The templates include comprehensive checklists that act as "unit tests" for the
 
 ```markdown
 ### Requirement Completeness
-
 - [ ] No [NEEDS CLARIFICATION] markers remain
 - [ ] Requirements are testable and unambiguous
 - [ ] Success criteria are measurable
@@ -209,14 +208,10 @@ The implementation plan template enforces architectural principles through phase
 
 ```markdown
 ### Phase -1: Pre-Implementation Gates
-
 #### Simplicity Gate (Article VII)
-
 - [ ] Using ≤3 projects?
 - [ ] No future-proofing?
-
 #### Anti-Abstraction Gate (Article VIII)
-
 - [ ] Using framework directly?
 - [ ] Single model representation?
 ```
@@ -352,19 +347,15 @@ The implementation plan template operationalizes these articles through concrete
 
 ```markdown
 ### Phase -1: Pre-Implementation Gates
-
 #### Simplicity Gate (Article VII)
-
 - [ ] Using ≤3 projects?
 - [ ] No future-proofing?
 
 #### Anti-Abstraction Gate (Article VIII)
-
 - [ ] Using framework directly?
 - [ ] Single model representation?
 
 #### Integration-First Gate (Article IX)
-
 - [ ] Contracts defined?
 - [ ] Contract tests written?
 ```