.agents/skills/slate-ar-next/SKILL.md
Handle $ARGUMENTS.
Use this as the default "do the next useful Slate v2 AR thing" command. The user should not need to remember whether the next owner is status, gate, patch, perf, quality, or finalize.
This is the daily driver, not a new lane. If the next step is clearly broad,
route to slate-ar-perfect instead of making the user assemble fast,
stabilize, quality, and gate by hand.
Load slate-ar first and inspect read-only status before choosing any mutating
owner.
Default behavior:
slate-ar-status behavior;If the current state is too broad for one useful step and the user asked to
continue improving the surface, start or recommend slate-ar-perfect <surface>
instead of stopping at a menu of expert skills.
slate-ar-ship.slate-patch.slate-ar-gate.slate-patch or tdd.slate-ar-perf.slate-ar-quality.slate-ar-perfect <surface>.slate-ar-recipe.slate-ar-ship.If the chosen path becomes multi-step, stop after the first meaningful packet or fix unless the user asked for a durable loop. Do not create a goal by default.
Do create or continue a goal when the user asks to keep going until a measurable
state, parity, stability, or "perfect" surface is reached. In that case,
slate-ar-next should hand off to slate-ar-perfect, slate-ar-fast, or
slate-ar-stabilize with the inferred surface.
Report: