speckit-scripts
/speckit-scripts
Bundled Spec Kit automation scripts (bash + PowerShell) and artifact templates that back the /speckit:* commands. Use when a spec-driven workflow needs to create a feature, set up plan/tasks, or check prerequisites, and the target project has no .specify/ yet.
- Author
- ahmet-cetinkaya ↗
- Repository
- dotfiles ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 17
- Scripts
- 10
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 10 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/bash/check-prerequisites.sh, scripts/bash/common.sh, scripts/bash/create-new-feature.sh, scripts/bash/setup-plan.sh, scripts/bash/setup-tasks.sh, scripts/powershell/check-prerequisites.ps1, scripts/powershell/common.ps1, scripts/powershell/create-new-feature.ps1, scripts/powershell/setup-plan.ps1, scripts/powershell/setup-tasks.ps1
What it does and when to use it
Bundled Spec Kit automation scripts (bash + PowerShell) and artifact templates that back the /speckit:* commands. Use when a spec-driven workflow needs to create a feature, set up plan/tasks, or check prerequisites, and the target project has no .specify/ yet.
Original author description
Bundled Spec Kit automation scripts (bash + PowerShell) and artifact templates that back the /speckit:* commands. Use when a spec-driven workflow needs to create a feature, set up plan/tasks, or check prerequisites, and the target project has no .specify/ yet.
How it works
- What's bundled
- How the commands use these
- Setup (when a project has no .specify/)
- Boundaries
SKILL.md preview
--- name: speckit-scripts description: Bundled Spec Kit automation scripts (bash + PowerShell) and artifact templates that back the /speckit:* commands. Use when a spec-driven workflow needs to create a feature, set up plan/tasks, or check prerequisites, and the target project has no .specify/ yet. metadata: origin: github-spec-kit source: github.com/github/spec-kit --- # Spec Kit Scripts & Templates This skill bundles the automation layer behind the `/speckit:*` commands: the shell scripts that create feature branches/dirs and wire up plan/tasks, plus the artifact templates (`spec`, `plan`, `tasks`, `constitution`, `checklist`) they render. ## What's bundled ### `scripts/bash/` (and `scripts/powershell/` mirror) | Script | Purpose | |--------|---------| | `common.sh` | Shared helpers: locate `.specify/` root, resolve feature paths, JSON output. Sourced by the others. | | `create-new-feature.sh` | Create a feature (branch + `specs/<n>/` dir + `spec.md` from template). Used by `/speckit:specify`. | | `setup-plan.sh` | Scaffold `plan.md` from the plan template for the current feature. Used by `/speckit:plan`. | | `setup-tasks.sh` | Scaffold `tasks.md` for the current feature. Used by `/speckit:tasks`. | | `check-prerequisites.sh` | Validate that required artifacts exist (`--require-tasks`, `--paths-only`, `--json`). Used by `analyze`, `clarify`, `implement`, `converge`, `checklist`. | ### `templates/` `spec-template.md`, `plan-template.md`, `tasks-template.md`, `constitution-template.md`, `checklist-template.md`, `vscode-settings.json` — the canonical artifact shapes the scripts and commands fill in. ## How the commands use these The `/speckit:*` command frontmatter references scripts by a project-relative path, e.g.: ```yaml scripts: sh: scripts/bash/setup-plan.sh --json ps: scripts/powershell/setup-plan.ps1 -Json ``` At runtime these resolve against the **target project's** `.specify/` directory — Spec Kit installs a copy of these scripts and templates into `.specify/` when the project is initialized. So the canonical execution path is `.specify/scripts/bash/<script>.sh`, not this skill's copy. ## Setup (when a project has no `.specify/`) Spec-driven commands require the project to be initialized once: ```bash specify init . --ai claude # creates .specify/ with scripts + templates ``` `/ac:index` already runs this as part of repo initialization. If `specify` (the CLI) is not available, this skill's `scripts/` and `templates/` are the reference copies to seed `.specify/` manually: ```bash mkdir -p .specify/scripts .specify/templates cp -r <this-skill>/scripts/* .specify/scripts/ cp -r <this-skill>/templates/* .specify/templates/ ``` ## Boundaries - These scripts operate on `.specify/`-structured projects. Running them outside such a project (no `.specify/` marker found by `common.sh`) will fail fast — initialize first. - The bash and powershell trees are mirrors; use whichever matches the host shell. - Do not edit the bundled scripts to hardcode a project path — resolution is dynamic via `common.sh`'s `.specify/` upward search.
Files in this package (17)
- SKILL.md 3 KB
- scripts/bash/check-prerequisites.sh 6 KB
- scripts/bash/common.sh 25 KB
- scripts/bash/create-new-feature.sh 11 KB
- scripts/bash/setup-plan.sh 2 KB
- scripts/bash/setup-tasks.sh 3 KB
- scripts/powershell/check-prerequisites.ps1 5 KB
- scripts/powershell/common.ps1 22 KB
- scripts/powershell/create-new-feature.ps1 9 KB
- scripts/powershell/setup-plan.ps1 2 KB
- scripts/powershell/setup-tasks.ps1 3 KB
- templates/checklist-template.md 1 KB
- templates/constitution-template.md 2 KB
- templates/plan-template.md 4 KB
- templates/spec-template.md 4 KB
- templates/tasks-template.md 9 KB
- templates/vscode-settings.json 1 KB
Versions
The database has no other skills named speckit-scripts.
Database snapshot: 13.11.2026 · package version 7c7e800701be (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90speckit-orchestrator
Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation. - 100spec-kit
Spec Kit is GitHub's open-source toolkit that installs a set of agent commands into a project so a coding agent builds features from a written specification: specify, plan, tasks, implement, then converge against the spec. It also ships optional processes for bug fixing and for… - 100speckit-workflow
End-to-end Spec Kit lifecycle orchestrator that drives a single feature in an isolated git worktree from specification through planning, task generation, TDD implementation, verification, and automated pull request creation. Use when the user asks to "run speckit workflow",… - 100speckit
Specification-Driven Development (SDD) toolkit. Transforms ideas into executable specifications, implementation plans, and task lists. Use for feature planning, PRD creation, or when user invokes /speckit.specify, /speckit.plan, /speckit.tasks commands. - 86next
Show a spec-kit feature's progress (a task is done when its issue is closed) and start the next open task with /speckit-implement; with several features, asks which. Use when the user asks what's next or has just merged a task PR. - 100speckit-specify
Create or update feature specifications from natural language descriptions. Use when starting new features or refining requirements. Generates spec.md with user stories, functional requirements, and acceptance criteria following spec-driven development methodology.