ros/spec-kit
1
0
Fork 0
mirror of https://github.com/github/spec-kit.git synced 2026-03-26 15:23:09 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
36019ebf1baf6a0a7e11f0705d25fc62b1e9b1aa
spec-kit/extensions
History
Dhilip 36019ebf1b feat: Auto-register ai-skills for extensions whenever applicable (#1840) 
* feat: Auto-register ai-skills for extensions whenever applicable

* fix: failing test

* fix: address copilot review comments – path traversal guard and use short_name in title

* fix: address remaining copilot review comments – is_file guard, skills type-validation, and exact extension ownership check on fallback rmtree

* fix: address copilot round-3 comments – align skill naming with presets.py convention, safe rmdir on fail, require SKILL.md for fallback rmtree, normalize skill_count in CLI

* fix: is_dir() guard in fast-path rmtree and fix ghost-skill assertion naming

* fix: path-traversal guard on skill_name in both rmtree paths of _unregister_extension_skills

* fix: add SKILL.md ownership check to fast-path rmtree and alias shadowed _get_skills_dir import
2026-03-25 07:48:36 -05:00
..
selftest
Add /selftest.extension core extension to test other extensions (#1758)
2026-03-13 07:26:01 -05:00
template
Add modular extension system (#1551)
2026-02-10 14:27:20 -06:00
catalog.community.json
Add AIDE, Extensify, and Presetify to community extensions (#1961)
2026-03-24 13:18:30 -05:00
catalog.json
Add /selftest.extension core extension to test other extensions (#1758)
2026-03-13 07:26:01 -05:00
EXTENSION-API-REFERENCE.md
feat(commands): wire before/after hook events into specify and plan templates (#1886)
2026-03-19 06:37:03 -05:00
EXTENSION-DEVELOPMENT-GUIDE.md
docs: move community extensions table to main README for discoverability (#1959)
2026-03-24 12:34:32 -05:00
EXTENSION-PUBLISHING-GUIDE.md
docs: move community extensions table to main README for discoverability (#1959)
2026-03-24 12:34:32 -05:00
EXTENSION-USER-GUIDE.md
feat: Auto-register ai-skills for extensions whenever applicable (#1840)
2026-03-25 07:48:36 -05:00
README.md
docs: move community extensions table to main README for discoverability (#1959)
2026-03-24 12:34:32 -05:00
RFC-EXTENSION-SYSTEM.md
feat(extensions,presets): add priority-based resolution ordering (#1855)
2026-03-17 09:44:34 -05:00

README.md

Spec Kit Extensions

Extension system for 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:

# 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:

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

See the Community Extensions section in the main README for the full list of available community-contributed extensions.

For the raw catalog data, see catalog.community.json.

Adding Your Extension

Submission Process

To add your extension to the community catalog:

  1. Prepare your extension following the Extension Development Guide
  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 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:

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