Skip to content
Back to skills

Implement Slice

ASecurity

Implement the next smallest slice from the current plan using TDD — tests first, then code, then verification, then an atomic commit. Reads the plan from the scratchpad.

  • 52 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 3, 2026
ai-agentsgobash

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add Koroqe/claude-code-sdlc --skill implement-slice --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Implement Slice?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Implement Slice
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/koroqe-implement-slice-claude-code-sdlc/badge)](https://www.skillsdirectory.com/skills/koroqe-implement-slice-claude-code-sdlc)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Implement the next smallest slice from the current plan using TDD — tests first, then code, then verification, then an atomic commit. Reads the plan from the scratchpad.
argument-hint: "[slice number] [no-changelog]"
arguments: [slice]
allowed-tools: Read, Glob, Grep, Edit, Write, Bash, Agent, TodoWrite
---

# Command: Implement Slice (seeded CI fixture — trimmed mirror, NOT the real file)

> This is a trimmed, structurally-identical mirror of `skills/implement-slice/SKILL.md`'s "Capture
> Instincts" step, committed only so `scripts/ci/validate-instinct-discipline.js`'s falsify step has a
> tree to run against. **This file carries THIS fixture's one deliberate defect:** its C3/FR-1.5a
> pre-capture dedup scan matches on `Pattern:` **or** `Category:` rather than requiring both, so the
> validator must fail naming this file and the `both match` requirement — and must flag no other file.

### 6. Capture Instincts

**Entry schema — the full 8 fields (FR-1.4), minted within D1's allowlist.** Every captured or updated
entry is a `### <slug>` heading (kebab-case, ≤60 characters — the mechanical dedup key) followed by:

- `Confidence:` — `min(0.9, 0.3 + 0.2 × (occurrences − 1))`, recomputed ONLY at a new-occurrence event.
- `Category:` — see the FR-1.7 rules below.
- `Pattern:` — the file path or glob the instinct concerns.
- `Rule:` — a single-line ALWAYS/NEVER/WHEN prevention heuristic, minted within D1's allowlist.
- `Trigger:` — `User Correction` or `Repeated Deviation Rule`.
- `Occurrences:` — an integer, followed by `(features: <slug1>, <slug2>, ...)`.
- `Last confirmed at:` — the `## Meta` `Feature counter` value, stamped per the dedup rule below.
- `Retires at:` — `Last confirmed at` + 10.

**C3/FR-1.5a pre-capture dedup scan — MANDATORY.** Before minting any new `### <slug>` heading, scan
**both** `## Prevention Rules` and `## Instincts Log` for an existing entry whose `Pattern:` **or**
`Category:` either matches the pattern about to be captured (case-insensitive). A match is a **recapture of
that existing heading — never a new one**: update the matched entry in place instead of minting a new
slug.
- A recapture within the **same feature** does **NOT** increment `Occurrences:` a second time.
- **This scan is not optional.** Skipping it lets a model-minted slug fragment the same pattern across
  near-duplicate headings — occurrence counts never converge, nothing reaches the elevation threshold,
  nothing ever retires.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.