Produces a 1-2 page staff engineer scope document — role context, primary responsibilities (ongoing accountabilities, not tasks), decision authority (unilateral / consult / escalate), success measures over 6-12 months, working relationships, and an explicit "what this role is not". Use when the user says "write a staff engineer scope doc", "define this staff role", or provides the area, team structure, and the engineer's strengths and growth areas. Use this to define one staff IC's concrete remit; use career-ladder-draft for the org-wide level definitions and promotion-case to argue someone should reach the level.