writing-style
Elements of Style for decision artifacts - executive shortform and strategic longform
What this skill does
# Writing Style for Decision Artifacts
Apply these principles to all decision outputs. Choose shortform or longform based on artifact type.
## When to Use Each
| Artifact | Style | Typical Length |
|----------|-------|----------------|
| Executive Summary | Shortform | 1 page / 250 words |
| Email/Memo | Shortform | 3-5 sentences |
| Business Case | Longform | 10-20 pages |
| M&A Memo/CIM | Longform | 20-30 pages |
| Full Decision Artifact | Longform | 5-15 pages |
| Counter-Case | Shortform | 2-3 pages |
---
## Shortform: Executive Style
**Tone:** Confident, approachable, actionable.
### Core Rules
1. **Front-load decisions** - Inverted pyramid. Key info first.
2. **Active voice** - Strong verbs. No passive constructions.
3. **Positive framing** - Focus on solutions, not problems.
4. **Short paragraphs** - 3 lines max. Bullets for lists.
5. **Clear CTA** - What decision or action is needed?
6. **Concrete numbers** - Quantify claims. No vague language.
7. **No jargon** - Unless industry-standard.
### Structure: 1-Page Memo
```
SUBJECT: [Decision-oriented, 6-8 words]
PURPOSE: [1 sentence - why are we here]
BACKGROUND: [2-3 sentences - context only]
RECOMMENDATION: [Bold. Clear. Actionable.]
RISKS/ALTERNATIVES:
- [Bulleted]
- [Concise]
NEXT STEPS:
- [Who] will [what] by [when]
```
### Email Format
- **Subject:** 6-8 words, action/results focused
- **Body:** 3-5 sentences + bullets
- **Tone:** Positive, clear ask, specific deadline
- **Close:** Direct + contact info
---
## Longform: Strategic Style
**Tone:** Strategic, authoritative, data-driven.
### Core Rules
1. **Executive Summary first** - 1 page max. Problem, Recommendation, Financials, CTA.
2. **Structured sections** - Clear headers, logical flow.
3. **Data-driven** - Charts, tables, metrics throughout.
4. **Rationale explicit** - Don't assume reader agrees; justify.
5. **Risks visible** - Table format with mitigations.
6. **Appendices for depth** - Keep main body scannable.
### Structure: Business Case / Strategy Doc
```
1. EXECUTIVE SUMMARY (1 page)
- Problem/Opportunity
- Recommendation
- Key Financials
- Call to Action
2. SITUATION ANALYSIS
- Market data
- Competitive landscape
- Charts/visuals encouraged
3. STRATEGY / RECOMMENDATION
- 3-5 priorities (bulleted)
- Rationale for each
- What we're NOT doing (and why)
4. IMPLEMENTATION
- Timeline (Gantt or table)
- Owners
- KPIs / Success Metrics
5. RISKS & MITIGATIONS
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
6. FINANCIAL IMPACT
- Investment required
- Expected returns
- Sensitivity analysis
7. APPENDICES
- Detailed financials
- Supporting research
- Due diligence items
```
### Structure: M&A Memo / CIM
```
1. EXECUTIVE SUMMARY (1 page)
- Deal thesis
- Valuation range
- Key synergies
2. COMPANY OVERVIEW
- Business model
- Products/Services
- Customer base
3. MARKET & COMPETITION
- TAM/SAM/SOM
- Competitive positioning
- Market trends
4. FINANCIAL PERFORMANCE
- 3-year P&L (table)
- Key metrics
- Projections with assumptions
5. TRANSACTION RATIONALE
- Strategic fit
- Synergy estimates
- Integration considerations
6. RISKS
- Deal risks
- Integration risks
- Market risks
7. APPENDIX
- Due diligence checklist
- Detailed financials
```
---
## Universal Principles
### Always
- Front-load the key message
- Use active voice
- Quantify when possible
- End with clear next steps
- Tables > paragraphs for comparisons
### Never
- Passive voice for key points
- Vague language ("significant," "substantial")
- Jargon without definition
- Buried conclusions
- Walls of text
### Formatting
- **Bold** for key terms and recommendations
- Bullets for lists of 3+ items
- Tables for comparisons and data
- Headers for scanability
- White space for readability
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.