Enforce Scannable Density
Make complexity easier to find, not merely shorter. Apply the reduction, organization, and time-to-understand passes in references/density-pass.md.
Workflow
- Write the reader’s five highest-value questions.
- Measure whether the answer to each is visible in the title, summary, headings, captions, or first sentence of a section.
- Remove throat-clearing, repeated context, passive constructions, generic process claims, and unsupported praise.
- Group related evidence and give each section one job.
- Move the outcome, constraint, and pivotal decision earlier.
- Choose the lightest fitting form:
- prose for causal explanation;
- bullets for non-sequential factors;
- key-value blocks for compact facts;
- tables only for records with shared comparable fields;
- monospace blocks only for commands, logs, or technical specifications.
- Preserve quantitative data, caveats, ownership, attribution, and evidence labels.
- Run a 30-second scan test and list any answer still difficult to locate.
Never manufacture density by shrinking type, stacking unrelated facts, turning prose into decorative tables, or deleting uncertainty.
Output
Return the revised structure and copy, a cut/move/convert ledger, the five-question scan result, and any evidence weakened by the edit.
Example
Input:
We were very excited to embark on a comprehensive process that involved looking at
many different approaches before ultimately deciding on a new approvals experience.
Expected outcome:
Decision — Replace blanket approvals with risk-based gates.
Evidence needed — alternatives considered, approval threshold, and measured effect.
1---2name: enforce-scannable-density3description: Edit a portfolio case study for high signal, compact hierarchy, and fast scanning without losing evidence. Use when a draft is fluffy, repetitive, slow to navigate, paragraph-heavy, full of generic process language, or needs concise headings, key-value blocks, comparison matrices, captions, and technical spec blocks.4---56# Enforce Scannable Density78Make complexity easier to find, not merely shorter. Apply the reduction, organization, and time-to-understand passes in `references/density-pass.md`.910## Workflow11121. Write the reader’s five highest-value questions.132. Measure whether the answer to each is visible in the title, summary, headings, captions, or first sentence of a section.143. Remove throat-clearing, repeated context, passive constructions, generic process claims, and unsupported praise.154. Group related evidence and give each section one job.165. Move the outcome, constraint, and pivotal decision earlier.176. Choose the lightest fitting form:18 - prose for causal explanation;19 - bullets for non-sequential factors;20 - key-value blocks for compact facts;21 - tables only for records with shared comparable fields;22 - monospace blocks only for commands, logs, or technical specifications.237. Preserve quantitative data, caveats, ownership, attribution, and evidence labels.248. Run a 30-second scan test and list any answer still difficult to locate.2526Never manufacture density by shrinking type, stacking unrelated facts, turning prose into decorative tables, or deleting uncertainty.2728## Output2930Return the revised structure and copy, a cut/move/convert ledger, the five-question scan result, and any evidence weakened by the edit.3132## Example3334Input:3536```text37We were very excited to embark on a comprehensive process that involved looking at38many different approaches before ultimately deciding on a new approvals experience.39```4041Expected outcome:4243```text44Decision — Replace blanket approvals with risk-based gates.45Evidence needed — alternatives considered, approval threshold, and measured effect.46```
jpoindexter