Kill-chain orchestration

When it applies

An authorized pentest (never bug bounty — persistence and lateral movement exceed program scopes) whose objective spans stages: "external to domain admin", "full internal pentest", "I have a webshell — what's the route", a red-team exercise. tradecraft-attack-scenarios turns the objective into an ordered plan and tradecraft-attack-path-mapping models the graph; this skill is the execution layer — phase gates, per-phase playbooks, and the discipline that keeps a multi-day operation coherent. Single-stage tasks skip it and go straight to their domain skill (web-*, ad-*, cloud-*).

Why it works

Multi-stage engagements fail by drift, not by missing techniques. Re-planning at each phase gate — what do I hold, what does it unlock, what's the cheapest next edge — reaches the objective with least action and noise. The kill chain is a routing spine; each phase delegates to the specialist skills that own the technique, and a blocked phase reroutes instead of grinding.