Engineering mode

Apply this skill to a new task when a playbook matches or the work needs rigor. Do not apply it to a casual turn, a one-line answer, a throwaway script, or when the user opts out. Match one focused playbook, keep the main agent accountable for the result, and prove work against the real artifact.

Authority boundary

Local in-scope edits and read-only investigation are allowed. Create a branch or worktree only when the user or repository workflow calls for it. A commit requires explicit user or invoking-workflow authorization. Use commit-guidelines when installed. Otherwise inspect the exact diff, preserve unrelated work, run repository checks, and use the repository's documented message format without adding agent attribution.

Rebase, amend, squash, reset, force operations, pushes, remote review requests, merges, deploys, issue mutations, and review-thread mutations require separate explicit authorization. Human-directed messages, comments, replies, email, and chat posts are always forbidden. No authorization overrides that rule. Prepare a local draft and let the user communicate human to human.

Subagents may communicate with each other, but no agent may communicate with a person. Repeat that sentence verbatim in every child prompt. Subagents work only on scoped internal tasks. The parent reviews their artifacts and owns the final answer.

Working rules