Synthesize goals
Reconcile earlier goals with current steering and print the complete handoff
without activating or executing it. Arguments: $ARGUMENTS.
Read the contract
and output contract. Read other references only
when their step applies. <planner> is
../../scripts/planner.py, resolved from this skill's directory to an absolute
path written literally in every command.
1. Read the originals
Read full goals, specifications, corrections, project rules, and evidence; follow recovery when needed. Resolve target identities, provenance, coverage gaps, and present authority before combining. Use only selected profiles and bindings.
2. Reconcile requirements
Apply the contract's synthesis rules to every input requirement. Write sourced dispositions under prose rules, retaining stable keys, exclusions, holds, and failed findings. Inspect relevant current state and revalidate evidence only where required; preserve accepted unchanged results and completed criteria in the contract.
Orchestration Plan
Drafting and requested saving are authorized. For separately requested preparation that changes project state:
Enter plan mode before the first edit. In Claude Code call EnterPlanMode; in Cursor, Codex, or Gemini use /plan or Shift+Tab. Where plan mode is unavailable, present the plan as text.
Present scope, owned artifacts, checks, and authority under prose rules; wait for approval unless the session already authorizes that plan. Exit plan mode before preparation.
3. Produce the revised contract
Write the revised contract under prose rules. Consult safeguards for concrete risks or selected requirements, and before naming another skill in the goal. Check coverage and challenge unnecessary inherited guarantees without dropping real obligations. Required independent review covers the exact revised contract; unavailable review remains UNVERIFIED.
4. Render and hand off
Follow rendering for host limits, predecessor inputs, immutable revisions, and verification. Reply under output contract and prose rules, printing the whole payload and every requirement's disposition. If the helper returns no payload, print the authored draft and concrete error as incomplete. Stop before native activation, replacement, or execution.
Before sending, check the exact ## Goal and ## Handoff headings, complete
fenced payload, whole-payload count line, and inherited requirement dispositions.
Keep handoff status to one short line, with saved identities and material gaps
in their prescribed places.