write-plan
Deprecated - use the aegis:writing-plans skill instead
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/GanyuanRan/Aegis/HEAD/commands/write-plan.md -o ~/.claude/commands/write-plan.mdwrite-plan.md
Tell your human partner that this command is deprecated and will be removed in the next major release. They should ask you to use the "aegis writing-plans" skill instead.
|
Deprecated - use the aegis:brainstorming skill instead
Deprecated - use the aegis:executing-plans skill instead
Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.
Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path.
Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.
Use when facing 2+ independent tasks without a written plan, with no shared state or sequential dependencies, where parallel delegation beats inline cost; otherwise inline. Planned tasks use subagent-driven-development.
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.