Prose Standard

This skill is guidance, not a script. A contract is an obligation, invariant, precondition, postcondition, or compatibility promise that a caller, callee, implementer, producer, or consumer relies on. Write enough to preserve the contract, then remove reasoning transcripts, repetition, and decoration.

When not to use

• Prose that takes the authoring session's vantage, such as dead citations, change narration, or review vantage. Use trim-reasoning-leakage.
• Where documentation lives, its structure, and its audience. Use canonical-docs.
• Commit message shape or type. Use conventional-commit.
• A code or behavior defect. Prose cannot fix it.

Inputs and authorization

• Required: an explicit scope of files, surfaces, or a diff. If it is missing, report it and stop.
• Mode: automatic (default) applies clear edits; interactive asks before rewriting. Enter interactive only when the user asks.
• Authorization: a review or audit is read-only. Edit only when the task asks for a fix or a trim. Treat generated catalogs, snapshots, and fixtures as derivatives: fix the owner, then regenerate.
• Exclude vendored code and frozen records. If the scope contains only excluded paths, report that nothing qualifies.

Method