LLM-Friendly Context

Purpose

Use this skill when writing or revising any content another agent will execute or judge: prompts, handoffs, planning artifacts, review findings, completion reports, generated instructions, test skeleton comments, work plans, and task files.

The goal is stable downstream execution. The next agent should know the target action, required inputs, accepted decisions, observable success criteria, and the condition that requires escalation.

Core Rules

1. Use positive, executable instructions

   • State the action the next agent should perform.
   • Convert quality policies into observable acceptance criteria.
   • Example: Preserve existing public API behavior across the documented compatibility cases.

2. Make vague instructions concrete

   • Replace subjective terms with observable conditions, paths, commands, schemas, examples, or decision rules.
   • Terms that usually need clarification before handoff: appropriate, proper, related, existing behavior, optional, as needed, if needed, per convention, unresolved alternatives, TBD, and placeholder.