# Writing Plans

Use when you have an approved spec or written requirements for a multi-step task that...

- Repository: https://github.com/GanyuanRan/Aegis (1408 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-25
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add GanyuanRan/Aegis --skill writing-plans -g -a claude-code -y`
Codex: `npx skills add GanyuanRan/Aegis --skill writing-plans -g -a codex -y`
Cursor: `npx skills add GanyuanRan/Aegis --skill writing-plans -g -a cursor -y`
Gemini CLI: `npx skills add GanyuanRan/Aegis --skill writing-plans -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add GanyuanRan/Aegis`

## Description

Use when you have an approved spec or written requirements for a multi-step task that needs a durable plan document before touching code. Small, single-owner, or fast-path tasks do not need this skill.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<EXPLICIT-MODE-GATE>
If activation mode is explicit (`~/.config/aegis/config.toml` has
`activation_mode = "explicit"`, or `AEGIS_ACTIVATION_MODE=explicit` is visible
in the environment) and the current user request did not explicitly invoke
Aegis or this skill by name, exit back to the fast path: answer concisely
without this workflow's checklist, ceremony, or document requirements. If the
user explicitly named Aegis or this skill, proceed normally.
</EXPLICIT-MODE-GATE>

# Execute

→ Existing parent plan/spec and a tiny execution slice? → **Use Planless Slice Lane.**
→ Mechanical or bounded change with no durable boundary (no new owner,
  contract, schema, public API, migration, or compat surface)? → **Use
  Planless Slice Lane without a parent document.**
→ Approved spec/requirements for a new workstream or an escalation trigger? →
  **Write an implementation plan for an engineer with no prior task context.**

For a durable plan: confirm scope and acceptance, map current owners/files,
record the TDD route, decompose into executable tasks, define verification and
retirement, self-review, save, then select the execution route. Proceed unless
a real authorization or safety boundary requires the user.

Bind tasks to the requested user outcomes: object, actions, conditions, and
deliverables. Include the final delivery step and evidence at the user-visible
seam, not only implementation/tests. Keep unmet needs and dependencies explicit;
project-wide goals do not authorize work outside this request. Reuse the
existing scope/acceptance slots; no extra goal artifact is required.

Escalate from Planless Slice Lane when the work adds a new owner, contract,
schema, public API, architecture boundary, migration, persistence,
security/permission, distribution/release surface, or an unclear verification
boundary.

# Writing Plans

The rest: https://github.com/GanyuanRan/Aegis/blob/HEAD/skills/writing-plans/SKILL.md