Conciseness

The body is efficient and operator-focused ('Don't include phases outside RoE scope. Recon-only engagement → only recon phase', 'Timeline uses absolute dates — never relative') with no padding or explanations of concepts Claude already knows. Minor trimmable redundancy: the communication_plan deprecation is stated three times ('Coordination belongs in ContactPlan; CONOPS.communication_plan is deprecated', 'communication_plan is DEPRECATED', and the schema table row), and Generation Rules partly repeat the Validation checklist.

Actionability

Concrete, executable guidance throughout: exact file paths ('Create or revise plan/conops.json'), full schema tables with field names, types, and allowed values ('one of recon, initial-access, post-exploit, c2, exfiltration, reporting'), and specific content rules ('All MITRE ATT&CK technique IDs are valid'). Falls short of 5 because 'select applicable phases using the active planning schema' is abstract and there is no example conops.json output showing the schema applied.

Workflow Clarity

Clear sequence — Prerequisites ('Read plan/roe.json first') → threat model/narrative → kill-chain design → Output → Validation — with an explicit validation checklist ('At least 2 success criteria defined'). Not 5 because there is no error-recovery feedback loop (what to do when a validation check fails) and the Output step defers to a vague 'selected planning workflow' rather than concrete publication steps.

Progressive Disclosure

The body is well-sectioned, but the one bundled reference file (references/kill-chain-templates.md, which contains exactly the phase-selection tables the kill-chain design section needs) is never referenced or linked. Instead the body leans on non-bundled siblings ('the tier table ... in threat-profile/SKILL.md', 'The deconfliction-template skill describes DeconflictionPlan') and warns against depending on files 'Skillogy cannot return', so the structure is present but navigation to the actual bundle is unclear.

Specificity

The description lists multiple specific concrete actions covering the document's components: 'executive summary, threat actor profiling, attack narrative, kill chain design, communication plan, deconfliction'. This matches the anchor for comprehensive coverage of specific actions; it is not the level below because coverage of the CONOPS sub-tasks is broad, not partial.

Completeness

The 'what' is clear (Concept of Operations document creation with named components), but the description contains no 'Use when...' clause or equivalent explicit trigger guidance — 'create CONOPS'/'plan attack' triggers live only in metadata.when_to_use, not the description. Per the judging guideline, a missing explicit trigger clause caps completeness at 3; it is not 2 because the 'what' half is fully explicit.

Trigger Term Quality

Good natural keywords: 'kill chain', 'threat actor', 'Concept of Operations', 'deconfliction' are terms a red-team operator would say. Missing the most common synonym — the acronym 'CONOPS' itself appears only in the name field, not the description — plus common variants like 'red team' or 'operation plan', so it falls just short of the comprehensive-synonyms anchor.

Distinctiveness Conflict Risk

'Concept of Operations' with 'kill chain design' and 'deconfliction' is a distinct niche with minimal conflict against generic skills. It is not 5 because the threat-modeling and deconfliction components overlap with sibling planning skills (e.g., a threat-profile or deconfliction-template skill), creating minor wrong-skill trigger risk.