Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Aimeerrhythm/enterprise-change-workflow --skill writing-plansgit clone --depth 1 https://github.com/Aimeerrhythm/enterprise-change-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/writing-plans)<a href="https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/writing-plans"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/writing-plans/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/writing-plans"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/writing-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.02312 |
| Opus 5 | $0.00015 | $0.01156 |
| Sonnet 5 | $0.00006 | $0.00462 |
| Haiku 4.5 | $0.00003 | $0.00231 |
Grade A, and why
writing-plans scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Plans
Overview
Write comprehensive implementation plans assuming the engineer has zero context for the codebase. Document everything: which files to touch, code, testing, how to verify. Give bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume the engineer is skilled but knows almost nothing about the project's toolset or problem domain.
Announce at start: "Using ecw:writing-plans to create the implementation plan."
Plan Mode — Do Not Use
Do NOT call EnterPlanMode or ExitPlanMode. This skill writes plans directly to .claude/plans/ via the Write tool. Claude Code's built-in plan mode is a separate mechanism not used by ECW. After writing the plan file, use AskUserQuestion to confirm with the user.
Risk-Aware Detail Level
Read .claude/ecw/session-data/{workflow-id}/session-state.json for risk level and affected domains. If unavailable (standalone invocation), default to P0 (full detail mode).
| Risk Level | Plan Detail | Task Granularity |
|---|---|---|
| P0 | Full steps with test code + verification commands + rollback notes | 2-5 min per step, no merging |
| P1 | Full steps with test code + verification commands | 2-5 min per step, no merging |
| P2 | Simplified steps, can merge single-file + no-branch-logic tasks | 5-10 min per step |
| P3 | Minimal outline (typically no formal plan needed) | — |
Task merging rule (P2 only): See workflow-routes.yml impl_strategy section.
Domain Context Injection
Note: When Subagent Dispatch is active (≥ 2 domains or ≥ 3 knowledge files), these steps are executed inside the subagent, not by the coordinator. The coordinator only passes file paths.
Before writing the plan:
- Read
.claude/ecw/routing/path-mappings.mdto understand code path → domain mappings - For each affected domain, read its
business-rules.mdto understand constraints (state machines, validation rules, concurrency controls) - If
knowledge-summary.mdexists (from domain-collab), read it for cross-domain dependency context
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 162 lines · 31 tokens per session scan A a40c7958ea1d
writing-plans is a skill published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 2,312 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
g-review
Run the review gate on the current branch diff. Runs the test suite, captures the diff, and dispatches code-lead, which verifies done conditions and reviews the diff itself. Issues MERGE READY or HOLD.
g-audit
Full-codebase or targeted code quality audit. Detects SOLID violations, code smells, architectural drift, dead code, and test coverage gaps. Targeted scope produces an inline report. Whole-codebase scope produces a prioritised roadmap milestone.
g-refactor
Guided refactor workflow — identify target, pre-analyse, spec, approve, execute, review. Accepts a scope path, an audit milestone file, or runs interactively. Safe-by-default: checks test coverage before execution and runs the full review gate after.
g-blast-radius
Analyse the blast radius of a planned change. Inputs a file path, feature name, or list of paths from a plan. Outputs the set of dependent files (forward and reverse references), a per-file volatility score (commit frequency proxy), and a total blast-radius rating (low / moderate / wide). Read-only.
cross-verify
A cross-checking skill that reviews decisions, designs, documents, and implementations from four viewpoints.
decompose
Break a large goal into 3–8 sequenced tasks, each one /eng → /tdd cycle. Writes to specs/{slug}.todos.md when a spec exists, root TODOS.md otherwise. /decompose — decompose a feature or goal /decompose re-entry — resume where you left off (auto-detected).