Menu

Individual skill

deconfliction-template

0upvotes

Deconfliction plan generator: distinguish authorized engagement activity from real incidents.

packages/decepticon/decepticon/skills/standard/soundwave/deconfliction-template/SKILL.md

Read pinned source

Source commit df879550544d36b6b1e69062f05adae28537adf2

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
6,574
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Deconfliction Plan Generator

## When to Use

When designing or revising deconfliction, use the system-provided `plan/roe.json` and any current CONOPS and contact plan as context.

## Workflow

1. Preserve confirmed decisions from an existing plan. Use the same `engagement_name` as RoE.
2. Record approved source IPs, user-agent markers, tool hashes, or testing windows in `identifiers`. Each entry needs `type` and `value`; put context in `description`. Do not invent infrastructure or claim a marker is configured when it is only proposed.
3. Set `notification_procedure` for the active phases authorized by RoE. Use the confirmed SOC contact from the contact plan when one exists. An absent contact or endpoint does not authorize contacting a third party.
4. Populate `deconfliction_code` only with an operator-confirmed code; otherwise retain its empty default. Identify missing material coordination decisions.
5. Validate `plan/deconfliction.json` against `DeconflictionPlan`. Deconfliction identifiers never expand scope or override abort triggers. Bundle publication follows the selected planning workflow.
Back to top