harness-gap-analysis

Use when mapping PonyBunny's current state against harness-first best-practice gaps and turning those gaps into actionable engineering inputs.

SKILL.md

GitHub

Harness Gap Analysis

Use this skill when

  • reviewing an existing gap list
  • converting gap findings into engineering actions
  • prioritising harness-oriented migration work
  • deciding what should be fixed first

Goals

  • classify gaps clearly
  • identify likely root causes
  • connect gaps to affected subsystems
  • prioritise work rationally
  • prepare the gaps for planning

Process

  1. List the identified gaps.
  2. Group them by theme.
  3. For each gap, identify the likely root cause.
  4. Identify the affected subsystem or workflow.
  5. Estimate migration priority.
  6. Identify what evidence is needed to confirm the gap.
  7. Recommend the next best owner or subagent.

Output contract

For each gap, return:

  • gap name
  • category
  • root cause hypothesis
  • affected area
  • priority
  • required evidence
  • recommended next step