# Goal Planner Print

> Use when explicitly asked to print or draft a goal with preserved scope, measurable acceptance, and optional numbered goal specifications.

- Skill: `tony/goal-planner-print` (Agent Skill, multi-file: 10 files)
- Install (CLI): `npx get-skill add tony/goal-planner-print`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tony/goal-planner-print/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tony (https://skillmd.com/u/tony)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/tony/goal-planner-print

---


# Print a goal

Draft and print a complete handoff without activating or executing it.
Arguments: `$ARGUMENTS`.

Read [the contract](references/contract.md)
and [output contract](references/output.md). Read other references only
at the applicable step below.

`<planner>` is `references/planner.py`, resolved from this skill's directory
to an absolute path written literally in every command.

## 1. Resolve the request

Resolve outcome, target, delivery host, output mode, authorization, and holds
from the request, project instructions, and supplied goals. Use only explicitly
selected [profiles and bindings](references/profiles.md). Follow
[recovery](references/recovery.md) when requested, needed, or selected by
that profile. Inspect current evidence only as needed for the contract.

Infer ordinary choices; ask only about missing decisions that materially
affect scope, authority, conflicting requirements, or a required companion.
Apply the contract's reconciliation and coverage rules to recovered material.

## 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](references/prose-rules.md); wait for approval unless the
session already authorizes that plan. Exit plan mode before preparation.

## 2. Draft and review

Write outcome, scope, authority, and acceptance under
[prose rules](references/prose-rules.md). For a concrete risk or selected
requirement, or before naming another skill in the goal, consult
[safeguards](references/safeguards.md). Review coverage against the
originals; arrange independent review only when required. Preserve failures
and repair gaps without inventing blockers.

## 3. Render, verify, and print

Follow [rendering](references/rendering.md) for host limits, helper input,
revision allocation, and verification. Answer under
[output contract](references/output.md) and
[prose rules](references/prose-rules.md), printing the whole exact payload
even when saved or incomplete. If the helper returns no payload, print the
authored draft and concrete error without claiming readiness. Stop at handoff;
never call native goal creation/update tools to test or activate it.

Before sending, check the exact `## Goal` and `## Handoff` headings, complete
fenced payload, and whole-payload count line. Keep ordinary handoff status to
one short line; include other sections only when the output contract requires
them.


## Portability notes

- `$ARGUMENTS` — the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.
- Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.

