Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From aegis
Creates a goal frame with success evidence, stop conditions, and routing for Aegis task execution. Useful when defining task boundaries before work.
npx claudepluginhub ganyuanran/aegis --plugin aegisHow this skill is triggered — by the user, by Claude, or both
Slash command
/aegis:goal-framingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to create a thin goal frame before execution. It is opt-in and
Parses a goal statement, extracts measurable success criteria, and saves them to a file without executing. Use to define goals for later execution.
Supervises multi-goal missions by reading the mission charter and prior goal artifacts, then deciding whether to proceed with the next goal, declare the mission done, or escalate to the user.
Loads Aegis skill discipline: checks relevance, classifies tasks, enforces hot-path rules for goal framing, baselines, and architecture review flags.
Share bugs, ideas, or general feedback.
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:.
Current owner:
Not owned here:
GateDecisionTreat these as equivalent:
/aegis-goal <task description>Aegis goal: <task description>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.
Produce the smallest useful frame:
TaskIntentDraft:
- Requested outcome:
- Goal:
- Success evidence:
- Stop condition:
- Non-goals:
- Constraints:
- Scope:
- Risk hints:
- Route:
- Next:
Stop condition must distinguish:
State set: done, blocked, needs-verification, scope-exceeded.
done: success evidence is satisfiedblocked: required dependency, permission, or information is missingneeds-verification: implementation exists but evidence is insufficientscope-exceeded: continuing would exceed the goal or non-goalsAfter framing:
brainstormingwriting-planslong-task-continuationsystematic-debugging| 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.
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.
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.