What problem does it solve?
Editor-behavior planning for the Plate rich-text editor framework often drifts: specs go stale, authority maps become unclear, and plans get approved without evidence. This Skill enforces a pass-gated planning workflow that turns behavior ideas, review findings, or spec drift into scored, evidence-cited plans and updated editor-behavior law before any implementation begins.
Core Features & Use Cases
- Pass-Gated Planning: Runs a structured multi-pass review (current-state read, intent/boundary, research refresh, authority and protocol passes, objection ledger, closure gates) with a weighted confidence scorecard that must reach 0.92 before a plan is considered ready.
- Editor-Behavior Law Maintenance: Updates the spec stack under docs/editor-behavior/ — standards, readable law, protocol matrix, parity gates, roadmap, and reference audit — in a required edit order.
- Decision Discipline: Requires intent/boundary records, decision briefs with viable options and rejected alternatives, objection ledgers, and current-state grounding against live source files.
- Use Case: A maintainer wants to add a new markdown interaction family to Plate. Invoke this Skill to classify the request, lock the node model and affinity, map the permanent home (core vs. feature package), update protocol and parity rows, and produce a scored plan ready for user review.
Quick Start
Ask the AI to run plate-plan on a behavior topic such as "plan the backspace behavior spec for markdown shortcuts in the Plate editor".