laya-decision

Design before implementing: ground the change, have independent runners sketch at least two structurally distinct designs (caller usage first, then types…

Make a report, summary, status or progress page, chart, graph, diagram, flow, path or architecture view, timeline, incident or bug timeline, kanban or triage…

Adversarial multi-reviewer pass on a diff: independent reviewers on the current host's model get the same intent, rubric, and code-quality lens, and the lead…

Run unattended everywhere except four named cases: unresolved blocker, acceptance-criteria ambiguity, irreversible action, credential problem.

Design and create a new agent for Claude Code, Codex, or OpenCode: ask a few preference questions, write a tight persona with one job, one voice, and explicit…

Cite file:line, command output, or a captured artifact for every claim; treat should/presumably/likely as unfinished work.

Keep a live line to Figma while implementing a design: resolve the file key and node id for every frame, ask precisely for any missing URL, node id…

Treat the cause rather than the symptom, and record a workaround as an explicit decision when one is unavoidable.

Design lifecycle steps, commands, and monitor loops to converge after crashes, retries, and duplicate execution.

Treat context as the scarce resource.

Every git remote, clone, fetch, submodule, and vendored copy stays within the project organization and its approved repositories.

Consult the advisor at the three moments that change a run's outcome — before committing to a large plan, when the same error comes back, and before calling a…