SkillAgentSearch skills...

goal-framing

Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or task boundaries before work.

Install / Use

npx skills add GanyuanRan/Aegis --skill goal-framing

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Tags

Our assessment of goal-framing

goal-framing scores 87/100 on our quality scale, 2185th of 4,700 Development & Engineering skills we index (top 47%).

Its SKILL.md is 4.5 KB long, well organised into 8 sections with 3 code examples: a solid amount of guidance for an agent.

With 1,273 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so goal-framing is actively maintained.
  • Our last check on 2026-10-11 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

goal-framing compared with similar skills

All 4 of these similar skills score higher than goal-framing; compare them before choosing.

SkillScoreStarsUpdatedFormat
goal-framing (this skill)by GanyuanRan871.3k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install goal-framing?
Run npx skills add GanyuanRan/Aegis --skill goal-framing. The install tabs above show the steps for each supported agent.
Which AI agents does goal-framing work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is goal-framing safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is goal-framing still maintained?
The repository was last updated about 2 months ago, so goal-framing is actively maintained.

name: goal-framing description: "Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or task boundaries before work."

Aegis Goal Framing

Use this skill to create a thin goal frame before execution. It is opt-in and boundary-setting only.

Do not use it for tiny edits, one-command checks, or ordinary fast-path Q&A unless the user explicitly asks for /aegis-goal or Aegis goal:.

Authority Boundary

Current owner:

  • Method Pack task framing

Not owned here:

  • authoritative GateDecision
  • final evidence sufficiency
  • final completion authority is not owned here
  • host daemon / automatic stop enforcement

Input Forms

Treat these as equivalent:

  • /aegis-goal <task description>
  • Aegis goal: <task description>
  • "Define the goal / stop condition before we start"

Slash commands are optional host shortcuts. The natural-language form is the portable fallback.

Example:

Aegis goal: Fix the auth refresh bug without rewriting the auth system.

Output

Produce the smallest useful frame, then continue into the routed workflow in the same turn.

TaskIntentDraft:
- Requested outcome:
- Goal:
- Success evidence:
- Stop condition:
- Non-goals:
- Constraints:
- Scope:
- Risk hints:
- Aegis Visibility:
- Route:
- Next:

Default behavior:

  • Do not stop after TaskIntentDraft.
  • Treat the frame as the start protocol for execution, not as the final answer.
  • After the compact frame, immediately take the Next action for the selected route when the user asked to do the work.
  • Keep the visible frame natural and short when the goal is clear; do not emit a large internal-looking card unless the user asked for a formal frame.
  • Use Aegis Visibility to say why the goal frame constrains the route, stop condition, or non-goals. Do not add trace ceremony unless the user explicitly asks for auditability.

Frame-only behavior:

  • Stop at the frame only when the user explicitly asks to only define the goal, only define the stop condition, not execute, not implement, not write a plan, or wait for confirmation before continuing.
  • If required information is missing, state the missing input and stop with blocked rather than pretending to continue.

Stop condition must distinguish:

State set: done, blocked, needs-verification, scope-exceeded.

  • done: success evidence is satisfied
  • blocked: required dependency, permission, or information is missing
  • needs-verification: implementation exists but evidence is insufficient
  • scope-exceeded: continuing would exceed the goal or non-goals

Routing

After framing:

  • Low-risk single-owner work continues through the normal fast path or TDD
  • Ambiguous product / architecture / contract work routes to brainstorming
  • Approved requirements route to writing-plans
  • Multi-step, compaction-prone, handoff, or subagent work routes to long-task-continuation
  • Bug diagnosis routes to systematic-debugging

Route Matrix

| Goal signal | Route | | --- | --- | | single-owner, low-risk, clear verification | fast path or test-driven-development | | bug, failure, regression, unexpected behavior | systematic-debugging | | ambiguous product, architecture, contract, cross-module behavior | brainstorming | | approved spec, stable requirements, implementation slicing | writing-plans | | multi-step, compaction-prone, handoff, subagent work | long-task-continuation | | completion, release, handoff, "is this done?" | verification-before-completion |

Only create docs/aegis/ records when the routed workflow needs persistent evidence. Goal framing alone does not create project files.

Subagent Context Packet

When delegating work, pass a compact packet instead of the full conversation:

SubagentContextPacket:
- Task:
- Goal:
- Stop condition:
- Relevant baseline refs:
- Relevant files:
- Known facts:
- Unknowns:
- Non-goals:
- Expected output:
- Verification expected:
- Must-read excerpts:
- Unsafe assumptions:

The packet reduces repeated file reading, but it does not replace evidence. Subagents should still read the smallest raw file/log/test excerpt needed to verify critical facts.

Do not paste full chat transcripts, full session history, or unbounded logs into the packet. If a fact matters, include a file ref, line/window hint, or compact must-read excerpt.

Drift Rule

If the goal changes mid-task, do not silently overwrite it. Record old goal, new goal, changed scope, new risks, and route through DriftCheckDraft when a long-task record exists.

Related Skills

View on GitHub
GitHub Stars1.3k
CategoryDevelopment
Updated1mo ago
Forks64

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions