spec-kit-builder
/spec-kit-builder
Prowadzi krok po kroku przez budowę całego projektu programistycznego z GitHub Spec Kit, z zatwierdzeniami w kluczowych punktach.
- Autor
- Stanly-Antigravity ↗
- Repozytorium
- spec-driven-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 03.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 6
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 03.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi krok po kroku przez budowę całego projektu programistycznego z GitHub Spec Kit, z zatwierdzeniami w kluczowych punktach.
Oryginalny opis (EN)
Guides a person step by step through building a whole software project with GitHub Spec Kit. Finds or creates the project documents, explains the project back in simple words, checks and installs Git, uv and Spec Kit with the user's consent, runs specify init, then runs constitution, specify, clarify, checklist, plan, tasks, analyze, implement, converge and taskstoissues in that order for every feature, pausing for approval at key points and recording progress so work can resume. Use this skill whenever the user wants to start building a project, continue building one that has phases or spec d
Jak działa
- How you talk (always)
- Inputs and outputs (file contract)
- Step 0. Resume check
- Step 1. Find the project documents
- Step 2. Fill the gaps (one question at a time)
- Step 3. Explain the project back
- Step 4. Tools
- Step 5. init
- Step 6. Foundation phase
- Step 7. constitution
Podgląd SKILL.md
---
name: spec-kit-builder
description: Guides a person step by step through building a whole software project with GitHub Spec Kit. Finds or creates the project documents, explains the project back in simple words, checks and installs Git, uv and Spec Kit with the user's consent, runs specify init, then runs constitution, specify, clarify, checklist, plan, tasks, analyze, implement, converge and taskstoissues in that order for every feature, pausing for approval at key points and recording progress so work can resume. Use this skill whenever the user wants to start building a project, continue building one that has phases or spec documents, or mentions Spec Kit, speckit, spec-driven development, phases, features to build, or "continue the build", even if they do not name this skill. If the project has no spec yet, use spec-writer first.
---
# Spec Kit Builder
Build a project one feature at a time with GitHub Spec Kit. You are the guide: you do the technical work and explain it simply. The person may be a beginner.
## How you talk (always)
- Ask which language the user prefers in your first message (or use the language they write in). Reply in it, in simple words. Explain any technical word in one short sentence the first time.
- ONE question at a time, then stop and wait. Never send a list of questions. Offer 2 to 4 numbered options when useful.
- Before each step: one or two lines on what it is and why. After each step: what you did and what comes next.
- Ask approval ONCE for a batch of setup commands, listing each command with a one-line purpose. Run only what was approved.
- Never delete files, force-push, reset git history or overwrite existing files without explicit approval.
- Never start the next feature without the user saying yes.
- Never invent facts about tools. If a command fails, show the short error, try the documented fallback in `references/troubleshooting.md`, and if still stuck explain simply and ask how to proceed.
- Never write secrets into files or commits.
## Inputs and outputs (file contract)
- **Requires:** `docs/SPEC.md`, `AGENTS.md`, `docs/PHASES.md` (made by `spec-writer`). If any is missing, offer to run `spec-writer`, or build a minimal version with the user (Step 1).
- **Reads when present:** `docs/ARCHITECTURE.md`; `docs/ui/UI-BRIEF.md`, `UX-FLOWS.md`, `DESIGN-SYSTEM.md`, `SCREENS.md` (UI skills); `docs/BUILD-STATE.md`.
- **Writes:** `docs/BUILD-STATE.md`, `.specify/` and Spec Kit's agent skills (via Spec Kit), code, tests, `CHANGELOG.md`; marks phases "done" in `docs/PHASES.md`; updates screen statuses ("built", "verified") and the "Built in" column in `docs/ui/SCREENS.md` for UI phases.
- **UI rule:** if a phase's "UI surfaces" field lists screens, every one of them must be at least "designed" in `docs/ui/SCREENS.md` before `specify`. If not, stop and offer `ui-designer` or `ui-prompt-writer` for exactly those sections.
## Step 0. Resume check
Look for `docs/BUILD-STATE.md`. If it exists, read it, tell the user in 3 lines where work stopped, ask "continue from there?" and jump to the recorded step. Otherwise start at Step 1. Update `docs/BUILD-STATE.md` after EVERY step (format at the bottom).
## Step 1. Find the project documents
Look in the project folder for:
1. Spec-writer outputs: `docs/SPEC.md`, `AGENTS.md`, `docs/PHASES.md` (and `docs/ARCHITECTURE.md`). Best case. If the project has a UI, also look for `docs/ui/` (UI-BRIEF, UX-FLOWS, DESIGN-SYSTEM, SCREENS, PROMPTS) made by `ui-designer` or `ui-prompt-writer`.
2. One large "main document" (a markdown file with plan, rules and phases).
3. Nothing.
Cases:
- Case 1: read them, continue.
- Case 2: ask where it is (path) or ask the user to paste it. Copy it into `docs/` without overwriting. Split it into `docs/SPEC.md`, `AGENTS.md` and `docs/PHASES.md` ONLY if its structure makes that clear; otherwise ask. Keep the original as `docs/BUILD-GUIDE.md`.
- Case 3: say that a good build needs a written plan, and ask: (1) run the `spec-writer` skill now (recommended), (2) write a short brief together now, (3) the user provides files. If the `spec-writer` skill is not installed, do option 2 using a minimal brief: one-liner, users, stack, must-haves, non-goals, hard rules, and a phase list you propose and the user approves; write it as `docs/SPEC.md`, `AGENTS.md` and `docs/PHASES.md` in the same format (see `../spec-writer/templates/` if available).
## Step 2. Fill the gaps (one question at a time)
Ask only what is still unknown: project folder path (default: current workspace), which AI coding agent they use (detect from folders such as `.agents`, `.claude`, `.gemini`; for Google Antigravity the Spec Kit key is `agy`), whether there is a GitHub repository (only needed for taskstoissues), and stack versions if missing.
## Step 3. Explain the project back
Write a friendly summary: what we are building and for whom; the big parts and build order (the phase list); what the project needs (tools to install, accounts, folders, open decisions); how the work will go (for every feature the Spec Kit steps, with pauses for the user). Ask "Did I understand correctly?" and wait.
## Step 4. Tools
Follow `references/setup-commands.md`: check Git, uv and Spec Kit (`specify`), plus the stack's own tools named in the docs. Show the user what is missing and the exact commands to install it, ask approval once, then install. If a new terminal is needed, ask the user to restart it (or the agent) and resume from `docs/BUILD-STATE.md`. Warn if the user's agent version may be too old for Spec Kit skills (for Antigravity: CLI 1.0.0+ or IDE 2.0.0+).
## Step 5. init
Run `specify init . --integration <key>` in the project folder (fallbacks in `references/setup-commands.md`). Say: "This turns Spec Kit on in your project folder." Verify the `.specify/` folder and the agent skills folder exist. Ask the user to restart the agent so the new commands load, then resume. If the folder is not a git repository, ask approval to run `git init`, then make a first commit "chore: spec kit init".
## Step 6. Foundation phase
If `docs/PHASES.md` has Phase 0 (setup and quality tools) and 0b (architecture check), run them exactly as written, as plain tasks (not as Spec Kit features). A "UI foundation" phase is also not a Spec Kit feature: run it with the `ui-designer` or `ui-prompt-writer` skill (ask which, if not already decided), then continue. If there is no such phase, propose a short list of quality tools suited to the stack (linter, test runner, architecture check), ask approval, set them up, run each once to prove it works, and commit.
## Step 7. constitution
Say: "This writes the permanent rules every feature must follow." Run the Spec Kit `constitution` step with input built from `AGENTS.md`, `docs/SPEC.md` (decisions, naming, security) and `docs/ARCHITECTURE.md`. Do not weaken any rule. Show the user a 5-line summary of the principles. Commit.
## Step 8. Feature loop
For every phase marked as a feature, follow `references/feature-loop.md` exactly: specify, clarify, checklist, plan, tasks, analyze, implement, the user's manual tests, converge, taskstoissues, commit. After each feature update `docs/BUILD-STATE.md` and ask whether to continue with the next one.
## How to run a Spec Kit step
Spec Kit installs each step as an agent skill or command. For skills-based agents (for example Antigravity) the file is `.agents/skills/speckit-<step>/SKILL.md`; for other agents look in the folder created by init. To run a step: read that file and follow it exactly with the input you prepared; or use the slash command (`/speckit-<step>` or `/speckit.<step>`, the separator depends on the agent and version). If the step is not found, tell the user simply that Spec Kit commands are not loaded, ask for an agent restart, and if still missing re-run init.
## Build state file (`docs/BUILD-STATE.md`)
```
# Build state
Project: <name>
Language: <user language>
Agent key: <agy|claude|codex|copilot|gemini|...>
Documents: SPEC=<path> AGENTS=<path> PHASES=<path> ARCHITECTURE=<path>
Spec writing: <not started|in progress|done>
Features:
1. <name> - <not started|in progress|done>
Current feature: <number and name>
Current step: <docs|tools|init|foundation|constitution|specify|clarify|checklist|plan|tasks|analyze|implement|manual-test|converge|taskstoissues|commit>
Decisions made during the build: <short list>
Last update: <date>
```
Pliki w paczce (6)
- README.fa.md 4 KB
- README.md 3 KB
- SKILL.md 8 KB
- references/feature-loop.md 5 KB
- references/setup-commands.md 3 KB
- references/troubleshooting.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie spec-kit-builder.
Migawka bazy z 13.11.2026 · wersja paczki fb44c7061042 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100spec-kit
Instaluje GitHub Spec Kit w projekcie, aby agent kodujący budował funkcje ze specyfikacji: specify, plan, tasks, implement i zbieżność ze specyfikacją, z procesami naprawy błędów i oceny pomysłu. - 90kickstart-feature
Prowadzi funkcję od prostego opisu do działającego kodu zgodnego ze specyfikacją i testami napisanymi najpierw. - 100spec-driven-development
Buduje oprogramowanie metodą spec-driven z użyciem spec-kit: zapisuje cel, dobiera stos i iteruje implementację, aż testy przejdą. - 100extend-spec-kit
Prowadzi autora przez tworzenie, testowanie i publikowanie rozszerzeń, presetów, workflowów i integracji agentów w Spec Kit. - 90step-by-step-web-project-builder
Prowadzi krok po kroku przez budowę aplikacji webowych, takich jak lista zadań, portfolio czy dashboard, gdy użytkownik dopiero się uczy. - 90context-kit
Prowadzi od pomysłu do specyfikacji: najpierw rozmowa o projekcie, potem siedem plików kontekstu, a kod dopiero po akceptacji.