Skip to content

docs(pao): add SCANNABILITY REVIEW hard rule to PAO charter#358

Merged
bradygaster merged 1 commit intobradygaster:mainfrom
diberry:squad/pao-scannability-guidance
Mar 13, 2026
Merged

docs(pao): add SCANNABILITY REVIEW hard rule to PAO charter#358
bradygaster merged 1 commit intobradygaster:mainfrom
diberry:squad/pao-scannability-guidance

Conversation

@diberry
Copy link
Copy Markdown
Collaborator

@diberry diberry commented Mar 12, 2026

Summary

Adds a SCANNABILITY REVIEW hard rule to PAO's charter. PAO now applies a mandatory format-decision framework when reviewing all content changes.

The Framework

Format When to use
Paragraphs Narrative flow, conceptual explanations, 'why' context. Limit 3-4 sentences.
Bullet lists Features, options, scannable items. Parallel structure required.
Tables Comparisons, structured reference data, attribute grids.
Quotes/indents Warnings, callouts, citations. Reserve for visual separation.

Decision Test

  • If a reader hunts for one specific item in a paragraph → convert to bullets or table
  • If explaining relationships between concepts → keep as paragraph
  • If comparing options → use table

Changes

  • .squad/agents/pao/charter.md\ — Added SCANNABILITY REVIEW hard rule under How I Work
  • .squad/agents/pao/history.md\ — Documented scannability framework as reusable pattern

Requested by Brady.

Adds a mandatory scannability framework for all content reviews:
- Paragraphs: narrative flow, conceptual explanations (3-4 sentences max)
- Bullet lists: features, options, scannable items (parallel structure)
- Tables: comparisons, structured reference data, attribute grids
- Quotes/indents: warnings, callouts, cited material
- Decision test: hunt-for-one-item = convert to bullets/table

PAO applies this on every PR with documentation impact.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@diberry
Copy link
Copy Markdown
Collaborator Author

diberry commented Mar 12, 2026

@bradygaster the scan-ability will help as the product and docs grow.

bradygaster added a commit that referenced this pull request Mar 13, 2026
Adds mandatory scannability framework for content review. Defines when to use paragraphs, bullets, tables, and callouts. Includes decision test for format selection.

Co-authored-by: Dina Berry <41597107+diberry@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@bradygaster bradygaster merged commit 36ea599 into bradygaster:main Mar 13, 2026
1 check passed
tamirdresher pushed a commit to tamirdresher/squad that referenced this pull request Mar 16, 2026
* chore(squad): Phase 2 launch — thinking feedback, P0 bugs, dual telemetry

Phase 1 complete: 5 issues closed (bradygaster#325, bradygaster#326, bradygaster#327, bradygaster#328, bradygaster#329), 5 PRs merged.
Phase 2 launched with Cheritto (thinking feedback), Hockney (P0 bugs), Saul (dual telemetry).
Decision inbox merged and archived.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* chore(squad): Phase 2 Wave 1 merged, Wave 2 launched

Session: 2026-02-23T2145-phase2-wave2
Phase 2 Wave 1 complete (PRs bradygaster#351, bradygaster#352, bradygaster#353 merged).
Wave 2 launched: Cheritto on ghost response detection (bradygaster#332), Hockney on error hardening (bradygaster#334).

Changes:
- Session log created: 2026-02-23T2145-phase2-wave2.md
- Merged 3 inbox decisions (Cheritto, Hockney, Saul)
- Deleted inbox files post-merge

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants