Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

kickstart-feature

/kickstart-feature

Prowadzi funkcję od prostego opisu do działającego kodu zgodnego ze specyfikacją i testami napisanymi najpierw.

Licencja
MIT
Ostatnia zmiana repozytorium
06.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
12
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Prowadzi funkcję od prostego opisu do działającego kodu zgodnego ze specyfikacją i testami napisanymi najpierw.

Wyzwalacze z opisu

add a feature\build X\implement Y\I want users to be able to…\write a spec\plan this\
Oryginalny opis (EN)

Spec-driven feature workflow for a kickstarted project. Takes a plain-language request through specify, clarify, plan, tasks, a consistency check, implement and converge, writing spec.md, plan.md, tasks.md and design files under specs/NNN-feature/. Every plan is gated against .kickstart/constitution.md and the compliance checklist; tests come first; the loop ends only when the code is shown to satisfy the spec. Picks up wherever the feature left off. Use when the user says \"add a feature\", \"build X\", \"implement Y\", \"I want users to be able to…\", \"write a spec\", \"plan this\", \"break

Jak działa

  1. Stages
  2. Step 0: Load context and find the stage
  3. Review checkpoints
  4. Rules that apply to every stage
  5. Finish
Sekcje z nagłówków SKILL.md, w oryginale · 74 linii, 804 słów
Podgląd SKILL.md
---
name: kickstart-feature
description: "Spec-driven feature workflow for a kickstarted project. Takes a plain-language request through specify, clarify, plan, tasks, a consistency check, implement and converge, writing spec.md, plan.md, tasks.md and design files under specs/NNN-feature/. Every plan is gated against .kickstart/constitution.md and the compliance checklist; tests come first; the loop ends only when the code is shown to satisfy the spec. Picks up wherever the feature left off. Use when the user says \"add a feature\", \"build X\", \"implement Y\", \"I want users to be able to…\", \"write a spec\", \"plan this\", \"break this into tasks\", \"continue the feature\", or any request to change product behaviour."
---

# kickstart-feature

Every feature goes through the same stages, leaving reviewable files behind. The user only has to describe what they want; this skill works out which stage comes next.

Adapted from GitHub Spec Kit's Spec-Driven Development workflow (MIT), with kickstart's additions: mandatory tests, the compliance checklist, and the freshness rule. See `docs/ATTRIBUTION.md` in the kickstart repository.

## Stages

| Stage | Output | Procedure | Pet projects |
|---|---|---|---|
| 1. Specify | `specs/NNN-slug/spec.md` | `references/specify.md` | Yes, shorter |
| 2. Clarify | answers written into `spec.md` | `references/clarify.md` | Up to 3 questions |
| 3. Plan | `plan.md`, plus `research.md`, `data-model.md`, `contracts/`, `quickstart.md` | `references/plan.md` | `plan.md` only, unless the feature has an API or new tables |
| 4. Tasks | `tasks.md` | `references/tasks.md` | Yes |
| 5. Check | consistency report (read-only) | `references/analyze.md` | Yes, quick |
| 6. Implement | code, tests, ticked `tasks.md` | `references/implement.md` | Yes |
| 7. Converge | appended tasks, or "Converged" | `references/converge.md` | Yes |
| Optional: requirements checklist | `checklists/<domain>.md` | `references/checklist.md` | When asked |

Read only the reference file for the stage you are running.

## Step 0: Load context and find the stage

Read silently:

- `.kickstart/project.md` for stack, commands, scale and enforcement.
- `.kickstart/constitution.md` for the rules. If it is missing, run `kickstart-constitution` first; if the user declines, continue and say plans are not gated.
- `.kickstart/compliance.md` for the controls.

Then decide where to start:

- **From an assessment:** if `.kickstart/assessments/<slug>/decision.md` says `go` and targets `kickstart-feature`, use its handoff block as the request: problem, chosen approach, scope, success metrics, compliance findings and open questions. Link the decision from `spec.md`. Turn carried-forward open questions into `[NEEDS CLARIFICATION]` markers or assumptions.
- **New request** with no matching folder under `specs/`: create the next number, `specs/NNN-slug/`, three digits, slug from the request in 2–4 words. Start at Stage 1. If the repo uses git, create the branch `NNN-slug` unless the user works on one branch.
- **Existing feature** (the user names it, or the current branch matches `NNN-slug`): pick the first stage whose output is missing or stale:
  - no `spec.md`, start at 1
  - `spec.md` has `[NEEDS CLARIFICATION]` markers, run 2
  - no `plan.md`, or `spec.md` changed after `plan.md`, run 3
  - no `tasks.md`, or `plan.md` changed after `tasks.md`, run 4 then 5
  - unticked tasks in `tasks.md`, run 6
  - all ticked, run 7
- **Explicit request** ("clarify the spec", "just plan it", "check consistency", "converge"): run that stage.

## Review checkpoints

Pause for the user at three points, with a short summary and the file links:

1. After Stages 1–2: "Here is the spec. Approve, or tell me what to change."
2. After Stages 3–5: "Here is the plan and the task list. The check found <n> issues. Approve to start building."
3. After Stage 7: either "Converged" or the list of appended tasks.

If the user says "go all the way" or "don't stop", run straight through, but still stop on any CRITICAL finding from Stage 5 or Stage 7.

## Rules that apply to every stage

- **Constitution first.** A conflict with a MUST principle is CRITICAL. Fix the spec, plan or tasks. Never reinterpret the principle. If the principle itself should change, use `kickstart-constitution`.
- **Tests are mandatory.** Unlike Spec Kit, where tests are optional, every requirement and acceptance scenario gets a test, written before the code.
- **Compliance is part of the plan.** If the feature touches personal data, auth, payments, logging, file upload, third-party sharing or AI calls, `kickstart-compliance` re-verifies the affected framework records when they are more than 60 days old and lists the controls. The plan states how each is met. Never cite a deadline or obligation from memory.
- **Stack facts are fresh.** Any library or API version in the plan is checked on its official page within 24 hours, under the freshness rule in `kickstart-stack-advisor`.
- **Stable IDs.** Requirements are `FR-001…`, success criteria `SC-001…`, acceptance scenarios `US1/AC1…`, tasks `T001…`, checklist items `CHK001…`. Never renumber. Append.
- **What, then how.** `spec.md` says what and why, with no languages, frameworks or APIs. `plan.md` says how.
- **Small slices.** If the spec has more than about five user stories or the plan exceeds roughly two days, split into several features and deliver P1 first.

## Finish

When converged:

- Set `status: done` in `spec.md`.
- Add a line under `Unreleased` in `CHANGELOG.md`.
- Update `.kickstart/compliance.md` rows the feature touched, with evidence.
- Commit with Conventional Commits. For `scale`, offer to open a pull request whose body links the spec, lists the tests, and names the compliance rows changed.

Tell the user in under ten lines: what was built, how to try it (from `quickstart.md` when it exists), what the tests cover, compliance rows changed, and anything deferred.
Pliki w paczce (12)
  • SKILL.md 6 KB
  • references/analyze.md 2 KB
  • references/checklist.md 2 KB
  • references/clarify.md 2 KB
  • references/converge.md 3 KB
  • references/implement.md 2 KB
  • references/plan.md 3 KB
  • references/specify.md 2 KB
  • references/tasks.md 2 KB
  • templates/plan-template.md 2 KB
  • templates/spec-template.md 2 KB
  • templates/tasks-template.md 1 KB

Wersje

W bazie nie ma innych skilli o nazwie kickstart-feature.

Migawka bazy z 13.11.2026 · wersja paczki f03786465a4b (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

  • 90kickstart-constitution
    Tworzy i zmienia konstytucję projektu, czyli krótki zbiór zasad MUST i SHOULD sprawdzany przy każdej specyfikacji i zmianie.
  • 100blueprint
    Tworzy plan techniczny dla napisanej specyfikacji funkcji, na przykład gdy w specs/ jest spec bez pliku plan.md albo zmiana specyfikacji lub konstytucji unieważniła plan.
  • 90build-feature
    Pomaga dodać funkcję, ekran lub zachowanie, których jeszcze nie ma, od historyjki użytkownika aż do działającego kodu.
  • 100spec-driven
    Stosuje konwencje pracy ze specyfikacjami: przepływ spec, plan i zadania, formaty plików, statusy i zasadę dryfu.
  • 100spec-kit-builder
    Prowadzi krok po kroku przez budowę całego projektu programistycznego z GitHub Spec Kit, z zatwierdzeniami w kluczowych punktach.
  • 100feature-implement
    Realizuje funkcję od opisu do wdrożenia: research i śledzenie kodu, plan zatwierdzany przez użytkownika, fazy z testami, przegląd, weryfikacja i synchronizacja dokumentacji.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.