Gabriel mode

Build one already precise ticket through bounded worker slices. Each implementing worker runs /review on its own contribution. The main agent independently checks correctness and omissions against the ticket and project rules, and returns fixes to that worker. Finish with review of the combined changes, then verification.

Inspired by pstack's poteto-mode. This skill owns orchestration only. Existing pack skills own implementation standards, tests, review evidence, verification, and shipping permissions.

Read when

• At entry: read the project's instructions, the ticket and relevant decisions, /task, its doctrine and reference, and the execution context.
• Before a delegation or correctness decision: open principles.md and main-context.md, then the applicable project rules. Pass those rule paths to workers. A verdict without checking the governing rules is incomplete.
• Before implementation or review: apply code-quality.md and code-structure.md. Open strong-foundation.md for a Feature, and user-experience.md plus the project's docs/design.md for user-facing work.
• When tests are specified: read /task-with-tests, its reference, no-unrequested-tests.md, and testing.md.
• At each review or verification: follow /review or /verification, including their required reads.
• Before writing or asking: follow Plain language and Asking the user.

Local orchestration contract

Use the selected task route's contracts and standards, not a second complete /task run inside each worker. These differences apply only during an explicit /gabriel-mode run: