From aegis
Executes implementation plans by dispatching fresh subagents per independent task with two-stage reviews: spec compliance then code quality. Use for current-session multi-task development.
npx claudepluginhub ganyuanran/aegis --plugin aegisThis skill uses the workspace's default tool permissions.
→ Have an implementation plan with independent tasks? → **Fresh subagent per task + two-stage review.**
Executes implementation plans by dispatching fresh subagents for independent tasks in the current session, with two-stage reviews: spec compliance then code quality.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Executes implementation plans by dispatching fresh subagents per independent task, with two-stage reviews (spec compliance then code quality) in the current session.
Share bugs, ideas, or general feedback.
→ Have an implementation plan with independent tasks? → Fresh subagent per task + two-stage review.
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
Why subagents: You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
Use when you have a written implementation plan with mostly independent tasks and want to stay in the current session. For cross-session execution, use executing-plans instead.
Before multi-task plans: load long-task-continuation, create checkpoint, include in every implementer prompt.
Use the least powerful model per role: mechanical (1-2 files, complete spec) → fast/cheap. Integration (multi-file, pattern matching) → standard. Architecture/design/review → most capable.
Each implementer prompt must include:
TodoCheckpointDraftResumeStateHintThe implementer may update task-local evidence, but the controller owns the consolidated checkpoint.
Implementer subagents report one of four statuses. Handle each appropriately:
DONE: Proceed to spec compliance review.
DONE_WITH_CONCERNS: The implementer completed the work but flagged doubts. Read the concerns before proceeding. If the concerns are about correctness or scope, address them before review. If they're observations (e.g., "this file is getting large"), note them and proceed to review.
NEEDS_CONTEXT: The implementer needs information that wasn't provided. Provide the missing context and re-dispatch.
BLOCKED: The implementer cannot complete the task. Assess the blocker:
Never ignore an escalation or force the same model to retry without changes. If the implementer said it's stuck, something needs to change.
./implementer-prompt.md - Dispatch implementer subagent./spec-reviewer-prompt.md - Dispatch spec compliance reviewer subagent./code-quality-reviewer-prompt.md - Dispatch code quality reviewer subagentNever:
If subagent asks questions:
If reviewer finds issues:
After spec compliance and code quality review pass, update the consolidated checkpoint and run a drift check before moving to the next task.
If subagent fails task:
Required workflow skills:
Subagents should use:
Alternative workflow: