implement-slice
/implement-slice
Use when writing code with an AI agent for a slice that already has a spec, or when fixing a bug: test first, smallest change, small commits, one agent per task.
- Author
- afonsoalrocha ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when writing code with an AI agent for a slice that already has a spec, or when fixing a bug: test first, smallest change, small commits, one agent per task.
Original author description
Use when writing code with an AI agent for a slice that already has a spec, or when fixing a bug: test first, smallest change, small commits, one agent per task.
How it works
- Invariant rules
- Routes
SKILL.md preview
--- name: implement-slice description: "Use when writing code with an AI agent for a slice that already has a spec, or when fixing a bug: test first, smallest change, small commits, one agent per task." --- # Implement a slice Objective: make the slice's acceptance tests pass, in small steps that have been proven. ## Invariant rules - One agent, one task per session. When the context has swollen, hand off or compact. - A test first, failing for the expected reason, at the agreed test point. Then the smallest change that passes. - While implementing, only make it pass. The tidying comes in `refactor-slice`, before the merge. - Keep a comment when it is useful. It explains why, and the origin (a bug, an issue, an external constraint), never the obvious. - Small commits that say why, what changed, and how it was proven. - A bug is fixed only after it has been reproduced, with a regression test written before the fix. - Robustness (timeouts, retry, idempotency, locks) is requested explicitly. See `design-architecture`. ## Routes | If | Read | |---|---| | the test and implementation cycle, and the testing rules | `references/tdd-cycle.md` | | fixing a bug | `references/fix-bug.md` | | creating or updating the repository AGENTS.md | `references/agents-md.md` | | the module touches money, data, or a critical rule | `references/mutation-testing.md` |
Files in this package (5)
- SKILL.md 1 KB
- references/agents-md.md 1 KB
- references/fix-bug.md 1 KB
- references/mutation-testing.md 1 KB
- references/tdd-cycle.md 1 KB
Versions
The database has no other skills named implement-slice.
Database snapshot: 13.11.2026 · package version 0876156be2b0 (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
- 100implement-feature
Implement exactly one criterion of an already-specced slice — write its token-tagged tests first, make them green, run the per-criterion checks-gate, and commit on green. On a slice with nothing built yet, that one criterion is the tracer. Use when a linted SPEC.md exists and… - 100feature
Build or change a feature one session at a time — ask the slice's folder what stage the work is at, then run that one stage: plan and spec it with the human, or implement exactly one criterion and commit it on a green gate. Use when the user wants to build, implement, or spec a… - 92implement
Implement a settled plan test-first, one small slice at a time. Read this skill before you write code for a spec or a settled plan. Read it also when the plan is small. Use it when the user says \"implement this\" or \"build it\", or names a spec to implement. - 100implement
Implement a slice, spec or ticket from its acceptance criteria - agree the seams, build it test-first by running the tdd loop on each criterion - then check the result against the spec, simplify it, review it with /code-review and kets-review, guard the quality floor and commit.… - 100implement-approved-slice
Implement only the approved slice with minimal changes, then persist execution evidence in slice notes and TASK_STATE.md. The official execution path. Opt-in test-first mode via --tdd. Use when the plan and slice are approved, ambiguity is resolved and files in scope are known.… - 90build-slice
Build ONE vertical slice of an approved feature design. First agree the code-level implementation choices with the user, then write and get approval for a code-level slice plan (slices/slice-N.md), then build test-first, following the plan exactly, with verification,…