llm-friendly-context

State the target action explicitly, name required input paths and source artifacts, specify the output format, and define observable success criteria. Replace subjective terms like "appropriate" or "as needed" with measurable conditions and decision rules.

Include only produced artifact paths and status fields that control the next transition, keep accepted decisions in one canonical wording, and record unresolved items with their effect, required input, and decision owner.

Common ambiguity sources include "appropriate", "proper", "related", "existing behavior", "optional", "as needed", "if needed", "per convention", "TBD", and "placeholder". Each should be rewritten into concrete paths, conditions, or measurable criteria.

Keep a prohibition only when it protects an irreversible boundary or shipped contract. It must name the protected condition and the allowed alternative action; otherwise convert the policy into positive, executable criteria.

Skip heavy clarification for simple downstream tasks where the target action, context, and success criteria are already clear. Constraints should stay proportionate and only reduce real ambiguity or preserve actual requirements.