STOP. READ THIS ENTIRE SKILL.MD BEFORE CALLING ANY ENDPOINT.

Best Practices: Task Plans

Conventions for 0N_TASKS.yaml files that /plan produces and /orchestrate executes. /review-plan validates these rules. /plan MUST follow them. No exceptions.

YAML is the source of truth. Every task MUST have: id, title, lane, runner, backend, mode, depends_on, definition_of_done. Plans without these fields will fail /review-plan validation and /orchestrate will refuse to execute them.

Rule 1: Adversarial Testing (NON-NEGOTIABLE)

Every implementation task MUST have a blind test that the coding agent cannot see.

This is not optional. This is not "nice to have". The coding agent that implements the code MUST NEVER see the test source, test assertions, or expected values. The agent sees ONLY the test output: pass/fail and failure descriptions.