LLM-Friendly Context

The goal is stable downstream execution: the next agent should know what to read, what to do, what counts as success, and when to stop or escalate.

This skill governs the clarity of LLM-facing output — prompts, handoffs, and generated artifacts. It does not define which documents to create or their required structure; that is owned by documentation-criteria.

Core Rules

1. Use positive, executable instructions

• State what the next agent should do.
• Convert quality policies into positive criteria.
• Example: "Preserve existing public API behavior across the documented compatibility cases."

1. Make vague instructions concrete

• Replace subjective terms with observable conditions, paths, commands, schemas, examples, or decision rules.
• Terms that often need clarification when they leave a decision to the next agent: appropriate, proper, related, existing behavior, optional, as needed, if needed, per convention, unresolved alternatives, TBD, placeholder.

1. Specify output shape

• Define required sections, fields, table columns, JSON keys, or checklist items.
• For handoffs, include paths to produced artifacts and the exact status fields the caller must inspect.

1. Provide necessary context

• Include the purpose, source artifacts, hard constraints, accepted decisions, and unresolved conditions.
• Prefer concrete file paths and section hints over broad module names.

1. Decompose complex work into verifiable steps

• Split work with 3+ objectives or sequential dependencies into ordered steps.
• Each step needs a checkpoint: what evidence proves it is complete.

1. Permit uncertainty explicitly

• If the source material is missing, contradictory, or not verifiable, state the uncertainty and the required escalation.
• Record unknown business, product, security, or compatibility decisions as blocking unresolved items, each stating the required input to resolve it and the escalation condition.
• Write every blocking unresolved item in one consistent shape, regardless of artifact: Unresolved: <decision needed> — required input: <what or who resolves it> — escalation: <the condition under which the next agent stops rather than guesses>.

1. Keep constraints proportionate

• Add only constraints that reduce ambiguity or preserve a real requirement.
• Keep simple downstream tasks lightweight when the target action, context, and success criteria are already clear.

Rewrite Patterns

Use these rewrites before treating a prompt, handoff, or artifact as complete.

Handoff Checklist

Before sending a prompt or artifact to another agent, verify:

• [ ] The target action is explicit.
• [ ] Required input paths and source artifacts are named.
• [ ] Accepted decisions and constraints are stated once, without alternate wording.
• [ ] Output format or expected status fields are specified.
• [ ] Success criteria are observable.
• [ ] Ambiguous expressions have been rewritten or marked as unresolved.
• [ ] The next agent can complete its scope with explicit choices, decision rules, or blocking unresolved items.

Generated Artifact Checklist

Before writing or finalizing a generated document:

• [ ] Each requirement, claim, task, test skeleton, or review finding has enough source context to trace why it exists.
• [ ] Every executable instruction names the target, action, and expected result.
• [ ] Verification steps say what to run or observe and what result proves success.
• [ ] If an artifact is derived from another artifact, copied decisions stay consistent in wording and meaning.
• [ ] If downstream work is blocked by missing information, the artifact records the missing input and escalation condition.