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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- 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.
03 SKILL.md 正文
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
Nextaction 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 Visibilityto 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
blockedrather than pretending to continue.
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-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.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.