using-superhackers

Orchestrate a pentest flow by loading this skill first to route security tasks to correct sub-skills, enforcing a pipeline from recon to reporting. It coordinates phases and passes findings between them to maintain context.

Maintain state persistence across security engagement phases by persisting engagement state and routing outputs between sub-skills. This preserves context and ensures findings from recon are available during testing, verification, and reporting.

Yes, you can enforce guardrails so recon precedes testing in your security workflow. This skill enforces the engagement workflow, ensuring recon happens before testing and verification before reporting to reduce misrouting and scope creep.

Task routing for security engagements works by determining the applicable security skill chain and loading sub-skills in the correct order. It acts as the entry point, routing tasks and passing outputs between recon, testing, verification, and reporting phases.

No, you do not need to load sub-skills manually. This skill determines the applicable security skill chain, ensures skills are loaded and read before execution, and enforces the engagement workflow automatically.

Security engagements lose context between recon and reporting phases without state persistence. This skill solves that by maintaining engagement state and passing findings between skills to preserve context across the entire workflow.