ros/spec-kit
1
0
Fork 0
mirror of https://github.com/github/spec-kit.git synced 2026-03-17 19:03:08 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
abf4aebdb34983ffab111fc0bc6fb393aa3d2461
spec-kit/presets/scaffold/commands/speckit.specify.md
Manfred Riem abf4aebdb3 feat(presets): pluggable preset system with template/command overrides, catalog, and resolver 
- Rename 'template packs' to 'presets' to avoid naming collision with core templates
- PresetManifest, PresetRegistry, PresetManager, PresetCatalog, PresetResolver in presets.py
- Extract CommandRegistrar to agents.py as shared infrastructure
- CLI: specify preset list/add/remove/search/resolve/info
- CLI: specify preset catalog list/add/remove
- --preset option on specify init
- Priority-based preset stacking (--priority, lower = higher precedence)
- Command overrides registered into all detected agent directories (17+ agents)
- Extension command safety: skip registration if target extension not installed
- Multi-catalog support: env var, project config, user config, built-in defaults
- resolve_template() / Resolve-Template in bash/PowerShell scripts
- Self-test preset: overrides all 6 core templates + 1 command
- Scaffold with 4 examples: core/extension template and command overrides
- Preset catalog (catalog.json, catalog.community.json)
- Documentation: README.md, ARCHITECTURE.md, PUBLISHING.md
- 110 preset tests, 253 total tests passing
2026-03-10 14:17:44 -05:00

707 B
Raw Blame History

description, scripts
description scripts
Create a feature specification (preset override)
sh ps
scripts/bash/create-new-feature.sh "{ARGS}" scripts/powershell/create-new-feature.ps1 "{ARGS}"

User Input

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