/engage.status
Show current engagement status and pipeline progress
> /plugin marketplace add hypnguyen1209/offensive-claude > /plugin install offensive-claude@offensive-claude-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/engage.status
Context preview
What this command does when you run it.
Show current engagement status and pipeline progress
Command definition
engage.status.mddescription: Show current engagement status and pipeline progress
/engage.status
Displays the current state of the active engagement workflow.
Usage
`/engage.status`
Output
Shows:
- **Engagement Info**: Client name, workflow type, start date
- **Current Phase**: Active phase name and number (0-8)
- **Completed Phases**: List of phases that passed gate validation
- **Gate Status**: Current phase gate validation status (pass/fail/pending)
- **Findings Count**: Total findings across all phases
- **Evidence Collected**: Count of screenshots, pcaps, logs
- **Suggested Next Action**: Recommended next command to run
Phase Status Indicators
- ✓ Phase completed and gate passed
- → Current active phase
- ○ Phase not yet started
- ✗ Phase gate validation failed
Example Output
Engagement: ACME Corp Web Application Pentest Workflow: web-app Started: 2026-05-28 Pipeline Status: ✓ Phase 0: Scope Definition ✓ Phase 1: Reconnaissance → Phase 2: Weaponization (IN PROGRESS) ○ Phase 3: Delivery ○ Phase 4: Exploitation Current Phase Gate: PENDING Findings: 12 total (3 critical, 5 high, 4 medium) Evidence: 47 screenshots, 8 pcaps, 23 logs Suggested Next Action: Complete payload configuration, then run /engage.gate
Notes
Run this command frequently to track progress and ensure you're following the workflow sequence.
A spec-driven offensive security framework for Claude Code — structured engagement workflows based on the Cyber Kill Chain, 31 kill-chain skills (multi-file progressive-disclosure) plus a discipline layer (a SessionStart dispatcher + 6 process/discipline
Repo: hypnguyen1209/offensive-claude
Other commands on offensive-claude.
- /engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement
Open command - /engage.c2
Execute Phase 6 - Command and Control Infrastructure Setup
Open command - /engage.crash
Crash → root cause → reachability → empirical exploitability verdict (native bugs)
Open command - /engage.cvediff
Find the canonical fix commit(s) for a CVE across sources, then diff for root cause
Open command - /engage.deliver
Execute Phase 3 - Delivery and Payload Deployment
Open command - /engage.exploit
Execute Phase 4 - Exploitation and Access Establishment
Open command

