increment
/increment
Planuje przyrost w SpecWeave: problem, zakres, numerowane kryteria akceptacji i zadania, zanim powstanie kod.
- Autor
- anton-abyzov ↗
- Repozytorium
- specweave ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 1
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Planuje przyrost w SpecWeave: problem, zakres, numerowane kryteria akceptacji i zadania, zanim powstanie kod.
Wyzwalacze z opisu
Argumenty
/increment \"<title>\" [--supersedes NNNN]
Oryginalny opis (EN)
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use for "plan a feature", "new increment", "let's build X".
Jak działa
- Before writing
- Decide
- Create it
- spec.md
- Then
Podgląd SKILL.md
---
description: Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use for "plan a feature", "new increment", "let's build X".
argument-hint: "\"<title>\" [--supersedes NNNN]"
metadata:
version: "3.1.0"
---
<!-- Generated from skills/sw-increment/SKILL.md by scripts/build/generate-skills.mjs. Edit the source, then npm run build. -->
# sw-increment: plan the unit of work
An increment is one folder, `.specweave/increments/NNNN-slug/`, with one file you write:
`spec.md`. `ledger.jsonl` beside it holds task state and is only appended to;
`metadata.json` is machine state you never need to read. One increment is one branch
and one PR.
## Before writing
- A small self-contained fix needs no increment. Just do it.
- An open increment already owns the files this touches (`specweave task list`)? Add
ACs and tasks to its spec.md instead of opening another.
- Read the code the change touches before writing Approach. If `GLOSSARY.md` exists,
write the spec in its terms.
- Unsure what to build at all, or the user says "grill me": run sw-grill-me first.
## Decide
Intent first: settle what the user wants and how a machine will check it before
writing ACs. `planning.deepInterview` sets the depth: `critical` (default) as below,
`deep` runs sw-grill-me, `off` states defaults and asks nothing.
1. **Think first.** Read the code and config; settle every fact yourself.
2. **Triage** each open decision: *fact* (look it up, never ask), *my call*
(reversible or low impact: pick a default), *theirs* (hard to reverse, costly, taste).
3. **Ask** only "theirs", at most 5, highest impact first. Each gets one clause on why
it matters and 2 to 4 options, your recommendation first; "yes" accepts it. Use your
tool's structured question tool when it has one. A clear request asks nothing.
4. **Record** in `## Decisions`: Asked, Defaulted (list every default: one the user
never saw is one they could not reject) and Open. Keep a line only when a later
change could contradict it: hard to reverse, surprising without context, or a real
trade-off. Apply each answer to Scope, ACs and Approach.
## Create it
`specweave create-increment "Add rate limiting"` prints the new folder with a scaffolded
spec.md; replace every `[bracket]`. Add `--supersedes 0031` when this replaces an older
increment (that one is abandoned for you), `--planned` for backlog work.
Manual path (no CLI): next id = highest folder number + 1, zero-padded to 4. Create
`NNNN-kebab-slug/` with `spec.md`, an empty `ledger.jsonl` and this `metadata.json`:
```json
{"id":"0042-ledger-fold","status":"active","type":"feature","created":"2026-09-02T10:00:00Z","lastActivity":"2026-09-02T10:00:00Z"}
```
Write UTF-8 without a BOM; in PowerShell use
`[IO.File]::WriteAllText($p, $body, [Text.UTF8Encoding]::new($false))`, never `>`.
## spec.md
```markdown
# 0042 Ledger fold
## Problem
Two agents can both believe they own T-01. Who hits it, and the evidence.
## Scope
In: claim ordering, malformed lines. Out: a ledger server.
## Acceptance Criteria
- [ ] AC-01: Two agents claiming the same task never both get it
- [ ] AC-02: A malformed ledger line is skipped and counted, never fatal
## Approach
Files that change and in what order, decisions, rejected alternatives, risks.
## Decisions
### Asked
- D-01 Claim tie-break? → earliest ledger line wins (user).
### Defaulted (change any before sw-do)
- D-02 Malformed-line report → a count in `task list` (reversible).
### Open
- none
## Tasks
### T-01 Fold the ledger
- AC: AC-01 | Files: src/core/tasks/ledger.ts, tests/e2e/double-claim.e2e.ts | Test: npm run test:e2e -- double-claim
### T-02 Skip malformed lines
- AC: AC-02 | Files: src/core/tasks/ledger-parse.ts, tests/e2e/malformed-ledger.e2e.ts | Test: npm run test:e2e -- malformed-ledger
```
- ACs are observable: "p95 of /search under 300 ms with 10k rows", not "faster".
- Every AC is covered by at least one task; every task names its `Files` and a `Test`
command a machine can run.
- A `Test` checks the AC from the outside: the CLI, HTTP route, UI or public API a user
or caller touches, run with the repo's own test command. A new test file goes in the
task's `Files`. Reuse existing tests; plan new unit or integration tests only when the
user, the project's `testing` config or its conventions ask for them. The
human-approved AC is the oracle, not a test the agent wrote.
- `Files` is the ownership unit: two tasks that edit one file cannot run in parallel,
so merge them. Shared contracts (types, schema) go in an early task.
- An AC is met when every task covering it is done. Nobody ticks the boxes; never
write state into spec.md.
- `plan.md` is optional overflow for a genuinely large design.
## Then
Show the ACs and tasks. Unless the user asked to review the plan first, carry on with
sw-do (one agent, or parallel lanes for three or more disjoint groups of tasks).
Opening an increment makes closing it part of the same job: any plan or checklist you
show ends with "Verify and close 0042", and sw-do closes it through sw-done once the last
task is done. When the plan waits for the user's review, say the increment stays open
until they answer.
Pliki w paczce (2)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
Wersje
W bazie nie ma innych skilli o nazwie increment.
Migawka bazy z 13.11.2026 · wersja paczki 51b91e774e9e (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
- 84sw-increment
Planuje przyrost w SpecWeave: problem, zakres, numerowane kryteria akceptacji, podejście i zadania, zanim powstanie kod. - 84done
Zamyka przyrost SpecWeave: sprawdza, czy zadania są zakończone, uruchamia weryfikację, przegląd i zamknięcie. - 90write-spec
Pisze specyfikację funkcji z ponumerowanymi kryteriami akceptacji, zanim powstanie plan albo kod. - 100sprint-review
Prowadzi przegląd sprintu: prezentuje przyrost, ocenia postęp wobec celu produktu i zapisuje zmiany w backlogu. - 90feature-edit
Wprowadza zmiany w trwającej funkcji, gdy zakres się przesuwa, kryteria akceptacji są poprawiane lub plan ewoluuje. - 90pfb-spec-new
Przygotowuje nową specyfikację funkcji w trzech plikach, prowadząc rozmowę zaczynającą od pytań, zanim powstanie kod.