What problem does it solve?
Improving a rich-text editor surface beyond a single bug requires systematic discovery of API, DX, architecture, documentation, and test coverage gaps, which is tedious to do manually. This Skill automates that discovery by running deep-research and quality-gap loops against a Slate v2 checkout and routing accepted findings to the right remediation workflow.
Core Features & Use Cases
- Quality-Gap Research Loops: Runs Autoresearch research-setup, quality-gap, and gap-candidates commands against a Slate v2 working directory to surface API/DX, architecture, behavior coverage, docs, and example gaps.
- Finding Routing: Routes accepted gaps to the appropriate follow-up workflow: slate-patch for correctness gaps, slate-ar-gate for test suite gaps, slate-ar-perf for performance gaps, and slate-plan for public API or architecture gaps.
- Durable Research State: Keeps research state under .tmp/slate-v2/autoresearch.research/<slug>/ so quality-gap progress persists across sessions.
- Use Case: A maintainer wants to harden the Slate v2 editor API before release. They invoke this Skill with a topic slug, review the generated gap candidates, apply the safe ones, and dispatch each accepted finding to the correct patch, plan, gate, or perf workflow.
Quick Start
Ask the assistant to run a Slate v2 quality-gap research loop for a given topic slug and route the accepted findings to the appropriate remediation skills.
