Conops Template
Businessconops-templateConops Template is an Agent Skill for business published in the PurpleAILAB/Decepticon repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Concept of Operations document creation — executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/PurpleAILAB/Decepticon/blob/HEAD/packages/decepticon/decepticon/skills/standard/soundwave/conops-template/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/conops-template, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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"
- Before OPPLAN can be generated
Prerequisites
Read plan/roe.json first — scope and boundaries constrain the CONOPS.
See ../references/schema-quick-reference.md for the CONOPS, ThreatActor, KillChainPhase, and DeconflictionPlan schema fields.
Workflow
Step 1: Interview the User
Round 1 — Threat Model:
- Which threat actor to emulate? (Use
threat-profileskill for detailed profiling)- a) Opportunistic external attacker (low)
- b) Targeted cybercriminal (medium)
- c) APT / nation-state (high)
- d) Insider threat
- e) Custom — describe
- What is the attacker's motivation? (financial, espionage, disruption, hacktivism)
- What initial access vector would this actor use?
Round 2 — Operations: 4. Attack narrative — 2-3 sentence scenario description 5. Ultimate objectives — what does the attacker want to achieve? 6. Communication plan — how does the red team communicate internally and with client? 7. Deconfliction method — how to distinguish red team from real attacks? 8. Success criteria — what constitutes engagement success?
Step 2: Design Kill Chain
Based on RoE scope + threat profile, select applicable phases. See references/kill-chain-templates.md.
Key rule: Don't include phases outside RoE scope. Recon-only engagement → only recon phase.
Step 3: Generate Documents
plan/conops.json— matchingCONOPSschemaplan/deconfliction.json— matchingDeconflictionPlanschema
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
- Communication plan specifies frequency + channel