- name
SKILL.md
File skill tetap berada di repositori penerbit.
Tempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add GanyuanRan/Aegis --skill executing-plans -a cursor -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add GanyuanRan/Aegis --skill executing-plans -a claude-code -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add GanyuanRan/Aegis --skill executing-plans -a codex -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add GanyuanRan/Aegis --skill executing-plans -a grok -yKirim pesan yang disalin di chat Grok Bot. Bot mengambil SKILL.md ini dari GitHub dan menambahkannya ke skill yang dipakai bersama oleh semua Bot Anda.
Install this skill: https://github.com/GanyuanRan/Aegis/tree/HEAD/skills/executing-plansDari penerbit
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the executing-plans skill to implement this plan."
For non-trivial execution, include Aegis Visibility: briefly tie the active
slice to its plan, checkpoint, drift or verification boundary. At completion,
pass plan adherence, evidence, complexity and residual risk to
verification-before-completion for the unified receipt.
If subagents are available and the plan has genuinely independent tasks,
prefer subagent-driven-development; lack of subagent support does not block
inline execution. Same-task agents share one workspace, and the coordinator
remains the only Git mutation owner.
Execution Readiness View,
read it before implementation and compare the plan against its intent lock,
scope fence, baseline lock, owner / contract constraints, compatibility
boundary, retirement boundary, test obligations, review gates, drift /
rewind rules, and evidence required before completion.Mode, Decision, Strict authority,
strict signals, light eligibility, Test posture, and verification. Strict
steps require either an explicit user/project request or a recorded auto
decision; plan approval or risk labels alone are not authority. An
off-mode missing record may be repaired only as Mode: off / Decision: skipped without loading TDD. Missing/unsupported auto decisions return to
plan review. An auto-light record is unsupported when any strict signal is
present or when its tiny/low-risk/single-owner/no-behavior-change proof is
incomplete. Only Decision: strict with recorded strict authority may
authorize steps named Write failing test, Verify RED, GREEN, or
REFACTOR. Do not infer strict during execution.TaskStartSnapshot: root, HEAD, branch or
detached state, upstream divergence, staged/unstaged/untracked paths, active
Git operations, and git worktree list --porcelain. Preserve task-preexisting
state; do not stash, reset, clean, or commit it.If the plan has multiple tasks, may span sessions, or includes architecture / contract / workflow changes:
Before a verification-driven unplanned edit, read retained PatchShape,
CanonicalOwner, UpwardDrillSignal, outcome, and evidence refs. Route their
comparison with the candidate to systematic-debugging before editing; it
decides whether the directions converge. A proven independent canonical-owner
root stays on the normal plan path.
For interface/interaction changes, compose ui-ux-governance before affected
edits and verify the plan's scoped experience criteria at the relevant user seam.
For each task:
Mark as in_progress
Follow each step exactly (plan has bite-sized steps)
Before any new source-code path is added by a task, restate the plan's
Change Necessity or create a compact one if the plan failed to carry it
forward. Plan approval is not by itself proof that a new helper, small guard,
new branch, fallback, adapter, or owner is necessary.
Change Necessity:
- User-visible need:
- No-change / non-code option:
- Why code change is necessary:
- Minimum change boundary:
- Decision: no-change | docs/config-only | code-change | needs-clarification
If the decision is not code-change, pause execution and return to plan
review instead of editing. If the decision is code-change, carry the
minimum boundary into the edit and verification scope.
Before any non-trivial source edit, run the plan's
Pre-Edit Complexity Check or create a compact one:
Use using-aegis/references/complexity-governance.md for shared artifact
classes, pressure signals, and over-budget handling.
Complexity Budget:
- Artifact class:
- Target files / artifacts:
- Current pressure:
- Projected post-change pressure:
- Budget result: within-budget | at-risk | over-budget
- Planned governance:
Pre-Edit Complexity Check:
- Target edit file:
- Existing pressure signal:
- Safer edit boundary:
- Decision: edit-in-place | extract helper | add owner file | split task | pause for plan update
Pre-Edit Owner-Fit Decision:
- Edit intent: wiring-only | move-out / extract-first | local-fix-without-new-responsibility | new-responsibility | emergency / compatibility patch
- Owner fit:
- Safer edit boundary:
- Decision: edit-in-place | extract helper | add owner file | split task | pause for plan update
If the check contradicts the plan's file boundary, pause and return to plan
review instead of silently stuffing logic into an overloaded owner. If the
budget result is over-budget and the task does not also govern that
overrun, stop execution and return to plan review rather than pushing the
task through as if it were still atomic.
When the target edit file is over-budget or mixed-purpose,
new-responsibility must not be added in place by default. wiring-only,
move-out / extract-first, and local-fix-without-new-responsibility may
proceed only when they do not add a new responsibility and the verification
boundary is clear. emergency / compatibility patch requires residual risk
and a retirement trigger.
Run verifications as specified
The coordinator is the Git mutation owner. After the coherent Task passes its planned verification, use before a default local commit, stage only task-owned paths, and read back , the committed file list, and remaining task delta. , read-only, no-change, and failed-verification tasks create no normal commit.
After all tasks complete and verified:
aegis:finishing-a-development-branch;verification-before-completion, report the local task commit
and Task clean / Repository clean, and do not invent merge/PR ceremony.STOP executing immediately when:
Ask for clarification rather than guessing.
Return to Review (Step 1) when:
Don't force through blockers - stop and ask.
main/masterRequired workflow skills:
Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-developmen
---name: executing-plansdescription: Use when executing a written implementation plan across sessions or with review checkpoints. Small or…---# skills/executing-plans/SKILL.mdRingkasan umum
Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.
FAQ
Unduh skills/executing-plans/SKILL.md dari penerbit, atau salin path-nya dan buka repositori. PlugMCP hanya mendaftar skill ini dan tidak meng-host filenya.
Penerbit menyimpannya di https://github.com/GanyuanRan/Aegis.
Claude, Cursor, Codex, dan Grok Build bisa membaca SKILL.md yang Anda tambahkan dari repositori penerbit. Grok Bot memasangnya saat Anda mengirim tautan folder GitHub skill tersebut di chat.
verification-before-completionHEADno commitUpdate TodoCheckpointDraft and DriftCheckDraft before marking the task completed.
When an Execution Readiness View exists, the drift check must explicitly
compare the active slice against the view's intent lock, scope fence,
baseline lock, compatibility boundary, retirement boundary, test
obligations, and review gates.
Mark as completed