lean-doc-feedback

To review Lean documentation drafts, you can apply a rubric-based approach that identifies undefined terms, suggests cross-links to blueprint nodes, and scores readability. This provides line-anchored feedback to guide targeted improvements without rewriting prose end-to-end.

Scoring documentation readability against a project rubric involves evaluating the draft for clarity and compliance, flagging ambiguities, and mapping issues directly to rubric criteria. This generates line-anchored feedback and minimal-diff suggestions for targeted improvements.

To suggest cross-links to blueprint nodes in API references and policy docs, annotate the draft to improve navigability. The process identifies relevant connection points and provides line-anchored feedback, ensuring minimal-diff suggestions without performing end-to-end edits.

Yes, rubric-based feedback for domain handbooks respects revision boundaries by providing line-anchored annotations and minimal-diff suggestions. It explicitly maps issues to a rubric and triggers dedicated improvement workflows instead of performing end-to-end prose rewrites.

Yes, this documentation review approach applies to policy docs, API references, and domain handbooks. It flags undefined terms, suggests cross-links to blueprint nodes, and scores readability against a rubric to improve clarity across these Lean documentation formats.