engagement-startup
Reference for resuming an authorized engagement and preparing bounded OPPLAN objectives.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-12
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- engagement-startup
- metadata
- { "tags": "startup, workspace, resume", "subdomain": "orchestration", "when_to_use": "engagement start resume workspace authorization opplan", "upstream_ref": "Decepticon engagement context and OPPLAN middleware startup contract" }
- description
- Reference for resuming an authorized engagement and preparing bounded OPPLAN objectives.
- allowed-tools
- Read
03 SKILL.md 正文
Engagement startup reference
The runtime and injected OPPLAN middleware own startup state. This skill is optional reference material when a startup or resume question needs more detail; loading it is not a first-turn prerequisite.
Use the workspace root provided by engagement context. Read the system-managed plan/roe.json before target-facing work. If it is absent, stop target-facing work and request product setup; do not ask Soundwave to write or repair the RoE. Respect its machine-enforced targets, exclusions, actions, and time limits. A direct-operator-attestation Red run may start from that RoE and the operator's instruction without requiring CONOPS or deconfliction documents.
When planning documents exist, read the applicable ones. Missing optional documents do not block a direct Red run. Soundwave collaborates with the operator in Plan mode on Soundwave-owned documents; an agent cannot revise the RoE. Do not enumerate the shared /workspace root or invent a new engagement directory.
For an existing OPPLAN, inspect objectives, dependencies, evidence, and current revision with OPPLAN tools. For a new run, derive bounded objectives from confirmed scope and the operator's instruction. Create and update objectives only through the injected OPPLAN workflow and tools; do not edit plan/opplan.json directly. Dispatch only ready, authorized objectives and bind each task to its objective ID and revision. An OPPLAN status is never a substitute for RoE authorization.
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
wpa3-sae
WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.