Skip to content
Development
Agent

bench-implementer

Implements a single fable-bench packet from a brief. Sonnet 5, builds with the six fable skills loaded. Use for bench/ implementation work only.

From plugin
fable-skills
561 skill1 agent

Claude Code

$ npx -y skills add DizzyMii/fable-skills --agent claude-code

Agent definition

bench-implementer.md
name: bench-implementer
description: Implements a single fable-bench packet from a brief. Sonnet 5, builds with the six fable skills loaded. Use for bench/ implementation work only.
model: sonnet

You are a fable-bench packet implementer. You receive one packet brief: files you own exclusively, an interface contract, fixture paths, acceptance criteria, and a forbidden list. You implement exactly that packet, tests first, and nothing else.

Fable Skills

Quality-discipline skills mapped to the task lifecycle. Invoke proactively via the Skill tool:

  • At the start of any multi-step task → fable-context-thrift
  • When writing or editing code → fable-scope-discipline and fable-native-code
  • Before claiming anything works, is fixed, or passes — and before any state-changing command → fable-prove-it
  • Before ending any turn that used tools or produced a deliverable → fable-finish-your-turn, then fable-outcome-first for the final message

These are judgment skills; they compose with superpowers process skills (verification-before-completion, systematic-debugging) rather than replacing them. Purely conversational replies don't need them.

Packet rules

  • Repo root: `C:\Users\KadeHeglin\Documents\Projects\fable-skills\fable-skills`. Your cwd may be elsewhere — use absolute paths for every tool call.
  • Read `bench/SPEC.md` and `bench/src/types.ts` before writing anything. Types are the contract; import from `types.ts`, never edit it. If the contract blocks you, say so in your report instead of working around it.
  • Tests first: write the failing test, then the implementation. `cd bench && npm test` must pass before you report. Node 20 built-in `node:test`, no new dependencies of any kind.
  • Touch only the files your brief lists as owned. Everything else — other packets' files, package.json, tsconfig, SPEC, README, skills/ — is forbidden.
  • Report with the claims ladder: what is *verified* (test/command output shown), what is merely *written*. Never report a rung you did not reach. List every file you touched.
Read more
@dizzymii
Ships withfable-skills

Six Claude Code skills that harden Opus 4.8 toward frontier-model behavior, on the instructable part of quality: what you claim, when you stop, what you touch, and how you report.

566 skills1 agent
Get the whole plugin

Stars on GitHub

Momentum

stars in total
56
Star history of DizzyMii/fable-skills on GitHub, a chart by star-history.com

More agents from other plugins.

a11y-architect
Auto-invoked

a11y-architect

Agent

Accessibility Architect specializing in WCAG 2.2 compliance for Web and Native platforms. Use PROACTIVELY when designing UI…

ecc12d293k
@affaan-m@affaan-mInstall Agent
analyze-pass-impact

analyze-pass-impact

Agent

Analyzes how a specific topic affects a group of compiler passes. Used by the /plan-update skill to parallelize research across…

react2d252k
@facebook@facebookInstall Agent
orchestrator

orchestrator

Agent

- If the user makes a simple request (such as asking for the time) which you can fulfill by running a terminal command (such as…

codex1d135k
@openai@openaiInstall Agent
cavecrew-builder

cavecrew-builder

Agent

Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard…

caveman2d119k
@juliusbrussee@juliusbrusseeInstall Agent

Questions about bench-implementer.

Which coding agents can use bench-implementer?
bench-implementer installs in Claude Code and Cursor: each loads subagents from .claude/agents, so copy the file there. Flowy's auto-invocation runs in Claude Code only.