[Extension]: Add Spec Kit Discovery Extension

[bigsmartben]

Extension ID

discovery

Extension Name

Spec Kit Discovery Extension

Version

0.2.0

Description

Run technical discovery commands for feasibility, technology selection, scenario-specific technical decisions, legacy codebase assessment, implementation understanding, and proof-of-concept validation.

Author

bigsmartben

Repository URL

https://github.com/bigsmartben/spec-kit-discovery

Download URL

https://github.com/bigsmartben/spec-kit-discovery/archive/refs/tags/v0.2.0.zip

License

MIT

Homepage (optional)

https://github.com/bigsmartben/spec-kit-discovery

Documentation URL (optional)

https://github.com/bigsmartben/spec-kit-discovery/blob/main/docs/usage.md

Changelog URL (optional)

https://github.com/bigsmartben/spec-kit-discovery/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.1.0

Required Tools (optional)

None. The extension only declares a dependency on the core speckit.specify command.

Number of Commands

6

Number of Hooks (optional)

0

Tags

discovery, workflow, validation, feasibility, decision

Key Features

• Creates evidence-backed feasibility studies before formal planning.
• Compares technologies, libraries, platforms, and architecture options with a selection matrix.
• Assesses legacy codebase risks, reusable assets, constraints, and integration hazards.
• Explains existing API/interface implementations from repository facts for implementation understanding and defect localization.
• Produces bounded proof-of-concept plans and result reports.
• Adds speckit.discovery.decision with type: api|performance|migration|ux|compatibility routing for scenario-specific technical decisions.

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on:

• Windows local environment with Specify CLI v0.11.3.dev0.
• Temporary Spec Kit project with a minimal .specify/ directory.
• Extension release v0.2.0 from https://github.com/bigsmartben/spec-kit-discovery/archive/refs/tags/v0.2.0.zip.

Validation performed:

1. Confirmed GitHub release v0.2.0 exists and is not draft or prerelease.
2. Confirmed the release archive URL redirects to a 200 OK GitHub codeload zip response.
3. Installed the extension from the release archive URL into a temporary Spec Kit project.
4. Ran specify extension list and verified Spec Kit Discovery Extension (v0.2.0) is installed, enabled, and reports Commands: 6 | Hooks: 0.
5. Parsed extension.yml and verified all 6 command files referenced by the manifest exist.
6. Searched the extension repository for removed old slash commands and verified the public command surface is six commands.

The extension commands are Markdown agent commands with no external runtime tools or helper scripts. Installation registered all 6 commands without command-file or manifest errors.

Example Usage

# Install from the release archive
specify extension add discovery --from https://github.com/bigsmartben/spec-kit-discovery/archive/refs/tags/v0.2.0.zip

# Run discovery commands from your AI coding agent
/speckit.discovery.feasibility [goal or idea] [constraints] [success criteria]
/speckit.discovery.techselect [decision to make] [candidate options] [criteria or constraints]
/speckit.discovery.decision type: api|performance|migration|ux|compatibility [scenario] [constraints or risks]
/speckit.discovery.codebase [target area or fuzzy scope] [planned change or integration] [known concerns]
/speckit.discovery.codebase-api-imp [API route, SDK method, topic, command, or capability] [known concern] [source scope]
/speckit.discovery.poc [user stories] [use cases] [core design idea]

Proposed Catalog Entry

{
  "discovery": {
    "name": "Spec Kit Discovery Extension",
    "id": "discovery",
    "description": "Run technical discovery commands for feasibility, technology selection, scenario-specific technical decisions, legacy codebase assessment, implementation understanding, and proof-of-concept validation.",
    "author": "bigsmartben",
    "version": "0.2.0",
    "download_url": "https://github.com/bigsmartben/spec-kit-discovery/archive/refs/tags/v0.2.0.zip",
    "repository": "https://github.com/bigsmartben/spec-kit-discovery",
    "homepage": "https://github.com/bigsmartben/spec-kit-discovery",
    "documentation": "https://github.com/bigsmartben/spec-kit-discovery/blob/main/docs/usage.md",
    "changelog": "https://github.com/bigsmartben/spec-kit-discovery/blob/main/CHANGELOG.md",
    "license": "MIT",
    "category": "process",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=0.1.0"
    },
    "provides": {
      "commands": 6,
      "hooks": 0
    },
    "tags": [
      "discovery",
      "workflow",
      "validation",
      "feasibility",
      "decision"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-06-23T00:00:00Z",
    "updated_at": "2026-06-23T00:00:00Z"
  }
}

Additional Context

This extension is intended as an upstream discovery layer for Spec Kit workflows. It helps teams resolve technical unknowns before formal specify, plan, tasks, and implementation phases.

AI assistance disclosure: I used OpenAI Codex to prepare the repository, verify the official extension submission requirements, run installation/static validation checks, and update this issue body.

[bigsmartben]

I was not able to apply the extension-submission label from this fork account due to repository permission limits. Maintainers: please add that label if this submission is ready for the community extension automation.

[mnriem]

@bigsmartben That is correct. The label will be added by us.

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Pull request created: #3119

Generated by Add Community Extension from Issue Submission · 409.7 AIC · ⌖ 28.5 AIC · ⊞ 32.9K

[mnriem]

Thank you!