agentleFS
tt-a1itt-a1i/matt-skills-with-to-goal/skills/engineering/to-goal/SKILL.md

to-goal

Skill192 starsChanged 22 days agoMITView on GitHub

Turn approved planning evidence or partially completed work into a portable, verifiable execution goal. Use when work needs to cross sessions, people, agents, or harnesses; no other skill or tracker setup is required.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the latest approved conversation, spec, issue URL, or local document, including later corrections and relevant linked decisions.

    line 13
  2. Distinctive:

    Default to one bounded, unblocked outcome.

    line 15
  3. Distinctive:

    Do not append a readiness ceremony, a mandatory capability taxonomy, or generic model advice.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

To Goal

Compile approved work and its current state into a contract for a fresh execution session. Stay read-only: generating the goal does not implement work, edit a tracker, create a branch, or modify files.

Source and scope

Use the latest approved conversation, spec, issue URL, or local document, including later corrections and relevant linked decisions. For tickets, read comments and dependencies rather than trusting labels. When no source is named, use the current conversation and repository evidence.

Default to one bounded, unblocked outcome. Preserve approval decisions; report missing decisions or blockers instead of reopening an interview. If several eligible outcomes are equally plausible, ask the user to choose. Work without tickets is equally valid.

--all <parent> explicitly selects a cross-ticket contract: preserve dependency order, distinguish the current frontier from later work, and state that execution needs a harness able to renew context. Otherwise keep the goal suitable for one fresh context.

Evidence to carry

Inspect the target repository's instructions, branch, HEAD, dirty/untracked files, relevant implementation and validation entrypoints. Record HEAD as the review baseline. Against the approved criteria, distinguish evidence-backed completion, known remaining work, and unverified claims. A commit message alone does not prove completion.

The goal must preserve:

  • The intended outcome and approved source, with enough context to locate the work.
  • Current state, baseline and unrelated work to protect. Do not ask the executor to redo verified work or hide unverified gaps.
  • Observable completion criteria and the relevant validation path. Preserve required product or human acceptance separately from automated checks.
  • Scope and external-action permissions inherited from the user. Generating a goal grants no new authority; record actions requiring a later decision.
  • Dependency order where it matters, especially for --all.

Output

Return one concise, copyable goal. Plain Markdown is sufficient; adapt it to a known target harness when helpful. Include only the evidence, constraints and context needed for that work, rather than a fixed checklist or repeated policy text. If a source is not ready, return its concrete blockers or missing decisions instead.

Do not append a readiness ceremony, a mandatory capability taxonomy, or generic model advice. Preserve an explicit execution preference; make a recommendation only when requested.

This skill compiles an approved handoff. goal-crafter helps author a goal from an idea, while spec-executor executes approved work. Neither is a prerequisite.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.