implement-slice

A workflow for implementing one focused vertical slice, meaning a small feature change that runs through the relevant parts of the system from start to finish.

In plain words
What is it for?
It reads the project plan and architecture, makes the smallest needed code changes, adds or updates behavior tests, runs the required checks, updates feature evidence and status, and reports any gaps or failures.
Why use it?
It keeps implementation limited to an already agreed feature, while requiring tests, verification, and status updates.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/cadeyu/vibe-harness/implement-slice
Any agent
npx skills add CadeYu/vibe-harness --skill implement-slice
Clone the repo
git clone --depth 1 https://github.com/CadeYu/vibe-harness

Made for: Claude Code, Codex.

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 403 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.00403
Opus 5 $0.00009 $0.00201
Sonnet 5 $0.00004 $0.00081
Haiku 4.5 $0.00002 $0.00040

Measured 3d ago against content hash 2321ea051b68, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement-slice scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/implement-slice/SKILL.md · 55 lines

What it actually says

实现 Slice

实现一条聚焦的 vertical slice,并补齐 tests、验证和状态更新。

触发时机

以下情况使用这个 skill:

  • docs/plans/active.md 已定义当前 slice。
  • 用户要求实现一个已经定框的功能。
  • 下一步应该写代码,而不是继续规划。

必读材料

  • AGENTS.md
  • docs/product.md
  • docs/architecture.md
  • docs/plans/active.md
  • feature_list.json
  • 相关源码文件。
  • 相关 tests。

流程

  1. 简要复述当前 feature、slice 和验收标准。
  2. 编辑前先检查现有代码模式。
  3. 在实际可行时,先添加或更新行为 tests。
  4. 用最小改动满足 slice。
  5. 运行 ./scripts/check.sh
  6. 更新 feature evidence 后运行 ./scripts/validate-feature-list.sh .
  7. 当改动触及构建、集成、持久化或公开行为时,运行 ./scripts/verify.sh
  8. 更新 docs/status.md:改动、feature 状态、已运行命令、结果、风险、下一步。
  9. 如果出现重复失败,进入 mistake ratchet。

产出

  • 聚焦当前 slice 的代码改动。
  • Tests,或明确说明测试缺口。
  • 验证证据。
  • 更新后的 feature state。
  • 更新后的 status。
  • 建议的 commit message。

边界

  • 没有新 plan,不要扩展任务。
  • 不要同时推进多个 feature。
  • 没有证据,不要声称命令已经运行。
  • 不要静默忽略失败的检查。
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 55 lines · 18 tokens per session scan A 2321ea051b68

Subscribe to this mod's changes

implement-slice is a skill published in the GitHub repository CadeYu/vibe-harness (5 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 403 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens