What problem does it solve?
After harvesting test candidates from an upstream editor repository, teams need a structured way to route every harvested row to the right owner lane and turn it into an actionable, reviewable plan without accidentally executing implementation work.
Core Features & Use Cases
- Lane-Based Row Routing: Classifies every harvest report row as in-lane, out-of-lane, split, duplicate, skip, or unresolved for the
slate-v2 or plate owner lanes.
- Execution-Grade Plan Generation: Produces a
docs/plans/*-harvest-plan.md document with coverage mapping, action values, verification commands, confidence scoring, and a pass-state ledger.
- License-Safe Planning: Enforces fresh-invariant-only wording for behavior-only sources so no upstream test code is copied into versioned output.
- Use Case: After running a test harvester against TinyMCE, invoke this Skill with the
slate-v2 lane to produce a complete plan covering every raw Slate candidate, then hand the accepted plan to the downstream lane skill for execution.
Quick Start
Ask the agent to process the harvest report at docs/editor-test-harvester/tinymce/report.md into a slate-v2 lane execution plan.