cognitive-doc-design

Lead with the answer or decision first, then add context. Use progressive disclosure by starting with the happy path, chunk related information into small sections, and prefer tables, checklists, and examples over long prose.

State what to review first, declare what is intentionally out of scope, and link previous and next PRs when work is chained. Keep each section focused on one decision and use checklists for acceptance criteria and verification.

Progressive disclosure means presenting the happy path first, then layering in details, edge cases, and references. Readers get the essential outcome immediately and only dig deeper when they need to.

Run gh pr view <PR_NUMBER> --json additions,deletions,changedFiles to inspect the changed-line count. Large diffs increase cognitive load, so consider splitting the work into smaller chained PRs.

Skip the default structure when the repository already provides a stronger template or convention. The cognitive patterns still apply, but consistency with existing project docs takes priority over imposing a new format.