Engagement Startup

No existing engagements found. Let's set up a new one.
What is the target or scope for this engagement?

Step 3A: Resume Existing Engagement

1. Read planning documents:

   read_file("<engagement>/plan/opplan.json")
   read_file("<engagement>/plan/roe.json")
   read_file("<engagement>/findings.md")
   

2. Summarize progress to the operator:
   • Objectives completed / total
   • Current phase (recon / exploit / post-exploit)
   • Last completed objective and key findings
   • Next pending objective
3. Ask: "Continue from where we left off?"
4. Begin the Ralph execution loop

Step 3B: Start New Engagement

1. Ask the operator for target/scope (if not already provided)
2. Determine a descriptive slug from the target scope:
   • Format: <org>-<type>-<period> (e.g., acme-external-2026, internal-audit-q1)
   • Keep it short, lowercase, hyphenated
3. Create workspace structure:

   bash(command="mkdir -p /workspace/<slug>/{plan,recon,exploit,post-exploit}")
   

4. Delegate to planner sub-agent to generate engagement documents:

   task("planner", "New engagement. Workspace: /workspace/<slug>/. Target: <target>. Interview the operator and generate RoE, CONOPS, and OPPLAN.")
   

5. Once planner completes → verify documents exist in <slug>/plan/
6. Check C2 Infrastructure — If opplan.json contains post-exploitation objectives:

   bash(command="nc -z c2-sliver 31337 2>/dev/null && echo 'C2_REACHABLE' || echo 'C2_UNREACHABLE'")
   

   • If C2_REACHABLE → C2 framework is Sliver (server: c2-sliver, gRPC port 31337). Include this in ALL sub-agent delegations.
   • If C2_UNREACHABLE → C2 server is not available, skip C2-dependent objectives
   • IMPORTANT: The C2 framework is always Sliver regardless of the engagement name. Do NOT assume Metasploit from engagement names containing "msf".
7. Begin the Ralph execution loop