forced-reading-protocol

Complete line-by-line reading enforces sequential reading of all lines in a document, with line-count verification to confirm total_lines equals lines_read before you proceed to analysis or synthesis.

Markdown specifications and plans over 3000 lines, SPEC_* and PLAN_* critical files, /SKILL.md definitions, and prompts longer than ~500 words all require complete reading verification to prevent incomplete understanding from skim reading.

Use the /shannon:read_complete <file-path> command to enforce complete line-by-line reading, or rely on automatic activation for large documents that exceed the defined thresholds.

Quantitative verification that lines_read equals total_lines prevents superficial analysis by ensuring you've actually reviewed all content sequentially, blocking premature synthesis until reading is demonstrably complete.

No—the protocol enforces complete sequential reading of SPEC_*, PLAN_*, and other critical files, blocking any analysis or conclusions until every line is verified as read.

Standard review often relies on skimming; this protocol enforces pre-counting total lines, sequential reading of every line, explicit verification of completeness, and synthesis only after confirmation—eliminating gaps from selective reading.