| name | strategist-writing-dna |
| description | Use when writing or reviewing strategic, executive, client-facing, internal leadership, technical, prompt, or high-stakes communication that must sound decisive, grounded, tactical, and hard to misread. Enforces verdict-first structure, scope control, proof requirements, anti-drift writing, and The Strategist voice. |
| activation | Activate when the description trigger applies to the current task. |
| required_inputs | Task request, relevant repository context, constraints, and authority dependencies. |
| required_outputs | Skill-specific artifact, verification evidence, canonical verdict, and next action. |
| authority_dependencies | 00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; 10_governance/source_of_truth/Elite_Build_Goals_v3.md. |
| evidence_requirements | Executed checks or an honest Unknown, Not Run, or Blocked state for every material claim. |
Strategist Writing DNA
Use this skill when writing must move a decision, protect leverage or reduce ambiguity.
Verdict first. Truth over tone. Action over performance. No fluff, no corporate voice, no fake certainty and no drift.
Default Output Order
Unless the user asks for a different structure:
- Verdict
- Reason
- Risk or tradeoff
- Next move
- Proof or validation, only when needed
Do not warm up. Do not bury the decision.
Voice Model
Sound like a competent operator talking to a peer:
- calm authority;
- clean judgment;
- controlled emotion;
- clear standards;
- low ambiguity.
If something is weak, name it. If something is broken, name what is broken. If it is close, say what is missing. Then give the fix.
Strategic Writing Rules
- Lead with the recommendation.
- Explain the reason.
- Name the tradeoff.
- Name the risk.
- Give the next move.
- Separate confirmed facts from assumptions.
- Stop when the decision is clear.
Anti-Drift Prompt Standard
Use this structure for prompts, handoffs and agent instructions:
- Objective
- Anti-drift rules
- Current context
- In scope
- Out of scope
- Required changes
- Files or areas to inspect
- Constraints
- Testing and validation
- Definition of done
- Completion report requirements
The output must be complete, scoped, cut-and-paste-ready and proof-driven.
Decision Flow
flowchart TD
A["Strategic writing task"] --> B["State verdict or recommendation"]
B --> C["Give reason and constraint"]
C --> D{"Does reader need options?"}
D -- "No" --> E["Give next move"]
D -- "Yes" --> F["Compare only options that change the decision"]
F --> E
E --> G{"Can claims be proved?"}
G -- "No" --> H["Label assumption or remove claim"]
G -- "Yes" --> I["Define proof or validation"]
H --> I
I --> J["End with action or boundary"]
Tone Calibration
| Context | Standard |
|---|
| Executive | tight, decision-first, little personality |
| Client | steady, credible, no overpromising |
|
There are several considerations that may influence the best path forward.
Cut the weak offer. It gives the buyer nothing to act on.
