implement-slice-complement

Execute bounded micro-delta fixes within an existing implementation slice and record evidence in task state files.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill implement-slice-complement-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-slice-complement
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/implement-slice-complement
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill implement-slice-complement-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a slice is implemented or reviewed, small gaps surface: a bug, a typo, a missing test, a log line, or a batch of review-feedback fixes. Without a dedicated step, these fixes get applied ad hoc with no record, and task memory drifts from reality. This Skill executes those narrow follow-ups as an explicit, auditable micro-delta that stays inside the original slice intent and DECISIONS.md. ## Core Features & Use Cases - Bounded micro-delta execution: Applies 1-7 outcome-oriented fixes against a named anchor slice with a declared file touch set, refusing anything that qualifies as net-new scope. - Net-new admission gate: Compares each delta against deferred and out-of-scope plan items before editing, routing genuine new work to implementation-plan instead of silently expanding scope. - Evidence recording: Writes a Complement subsection into the anchor slice notes and updates TASK_STATE.md only when routing or blockers change, keeping the audit trail intact. - Use Case: A review pass on a completed slice returns six small fixes. Invoke this Skill with the slice path and the fix list; it applies each fix, runs validation, records Layer-2 coverage status, and hands off to slice-closure or review-hard. ## Quick Start Apply these three review fixes as a micro-delta complement to slice 03_checkout-form and record the evidence in the slice notes.

Frequently Asked Questions about implement-slice-complement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply small fixes to an already implemented slice?▼

Invoke implement-slice-complement with the anchor slice path, a numbered list of 1-7 outcome-oriented micro-deltas, and the expected file touch set. It applies the fixes, validates them, and records a Complement subsection in the slice notes.

How do I handle a batch of code review findings on a finished slice?▼

Route the raw feedback through pr-feedback-ingest first, then run implement-slice-complement once per fix batch. Each batch stays inside the anchor slice's intent and leaves its own record in the slice notes.

When should I not use implement-slice-complement?▼

Do not use it for net-new scope, open correctness-critical ambiguity, changes that alter signed-off decisions, or pure state-memory updates. Those route to implementation-plan, decision-interview, post-review-pivot, or sync-task-state respectively.

What happens if a fix turns out to be new scope mid-edit?▼

The net-new admission check runs before any edit and refuses deltas matching deferred or out-of-scope plan items. If spill is discovered mid-execution, the run stops, summarizes the spill, and hands off to implementation-plan or implement-approved-slice.

Does implement-slice-complement update TASK_STATE.md automatically?▼

It updates TASK_STATE.md only when routing or blockers materially change. Otherwise it records evidence in the slice notes and recommends running sync-task-state afterward for memory-only updates.