conops-template
Concept of Operations document creation — executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-12
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- conops-template
- metadata
- { "tags": "conops, kill-chain, threat-model, operation-design", "subdomain": "planning", "when_to_use": "create CONOPS, design operation, threat model, plan attack", "upstream_ref": "Soundwave CONOPS template — Concept of Operations document generator" }
- description
- Concept of Operations document creation — executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction.
- allowed-tools
- Read Write Edit
02 资源文件 1
- 参考文档references/kill-chain-templates.md2.8 KB
03 SKILL.md 正文
Concept of Operations (CONOPS) Generator
The CONOPS bridges the legal RoE and the tactical OPPLAN. It must be readable by a CEO while containing enough detail for operators.
When to Use
- After
plan/roe.jsonexists - User says "create CONOPS", "design the operation", "build threat model"
- When the operator wants to design or revise a CONOPS. A direct Red run may build OPPLAN from the system RoE without this optional document.
Prerequisites
Read plan/roe.json first — scope and boundaries constrain the CONOPS.
Use the active planning schema and the Soundwave system prompt for CONOPS, ThreatActor, KillChainPhase, and DeconflictionPlan fields. Skillogy returns this skill body without sibling reference files.
Workflow
Step 1: Interview the User
Use the tier table and RoE Constraint→Profile Implication table in threat-profile/SKILL.md to propose a threat profile. Ask the operator about material choices such as motivation, initial access, operation sequence, and success criteria when these are not already confirmed.
Question 1 — Threat actor tier (single-select, use threat-profile skill for detailed profiling):
- a) Opportunistic external attacker (low)
- b) Targeted cybercriminal (medium)
- c) APT / nation-state (high)
- d) Insider threat
- e) Custom — describe
Propose motivation and initial access vector from the operator's confirmed context, then confirm them when they affect the operation.
Question 2 — Success criteria — the crown-jewel / measurable win condition. Required; no default (every engagement needs an explicit end-state).
Agent-drafted, not asked:
- Attack narrative — write the 2-3 sentence scenario yourself from RoE scope + tier + success criteria. This is the agent's job, not the operator's homework.
- Ultimate objectives — derive from success criteria; do not ask as a separate dimension.
Communication plan— REMOVED.CONOPS.communication_planis DEPRECATED (see SCHEMA_REFERENCE in soundwave.md);ContactPlan(contact-template skill) owns this now. Asking about it here duplicates a question and writes to a dead field.- Deconfliction method — default to standard red-team markers/headers (see
deconfliction-templatereference) unless the operator's RoE/contact answers already flagged a SOC integration endpoint; do not spend a dedicated question on it.
Step 2: Design Kill Chain
Based on RoE scope + threat profile, select applicable phases using the active planning schema; do not depend on a sibling reference file that Skillogy cannot return.
Key rule: Don't include phases outside RoE scope. Recon-only engagement → only recon phase.
Step 3: Generate Documents
- Create or revise
plan/conops.jsonwith the matchingCONOPSschema. - Create or revise
plan/deconfliction.jsononly when the operator is also designing that document; otherwise keep its existing content.
Step 4: Validate
- Executive summary contains no jargon or tool names
- Kill chain phases align with RoE scope
- All MITRE ATT&CK technique IDs are valid
- Timeline has concrete date ranges
- At least 2 success criteria defined
Generation Rules
- Executive summary = non-technical — no tool names, no jargon
- Threat actor TTPs must reference MITRE ATT&CK IDs
- Kill chain scoped to RoE — no exploitation phase in recon-only engagement
- Timeline uses absolute dates — never relative
- Deconfliction defaults to standard red-team markers/headers unless a SOC integration endpoint was already flagged;
communication_planis DEPRECATED — write coordination details toContactPlaninstead
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.