harness-design
Use when designing or reviewing PonyBunny as a harness-first system, especially around boundaries, evaluation flow, observability, and migration structure.
SKILL.md.claude/skills/harness-design/SKILL.md
GitHubHarness Design
Use this skill when
- defining harness-first architecture
- reviewing whether a design is truly harness-oriented
- deciding where evaluation and handoff should live
- improving observability and recovery behaviour
Goals
- enforce harness-first thinking
- keep evaluation separate from generation
- make progress measurable
- make failures diagnosable
- make future sessions easier to continue
Core principles
- generation is not verification
- every important change needs an evidence path
- session handoff must be structured
- traces must support failure reconstruction
- contracts must be explicit
- migrations should be phased and safe
Process
- Define the target outcome.
- Identify current weaknesses.
- Define the desired role boundaries.
- Define required artefacts and evidence points.
- Define migration phases.
- Define how correctness will be evaluated.
- Define likely risks.
Output contract
Return:
- harness-oriented design summary
- role boundaries
- required artefacts
- evaluation points
- migration steps
- risks and trade-offs