Borrowing it
Nothing to install: this file belongs to mtnyilmaz/agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mtnyilmaz/agents/main/.agents/skills/workflow-writing-plans/SKILL.mdgit clone --depth 1 https://github.com/mtnyilmaz/agentsWrote 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/mtnyilmaz/agents/workflow-writing-plans)<a href="https://agentmods.dev/skills/mtnyilmaz/agents/workflow-writing-plans"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/workflow-writing-plans.svg" alt="Measured on agentmods" 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.00053 | $0.02509 |
| Opus 5 | $0.00026 | $0.01255 |
| Sonnet 5 | $0.00011 | $0.00502 |
| Haiku 4.5 | $0.00005 | $0.00251 |
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 8d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Plans
Overview
Write an implementation plan so precise that a disciplined junior engineer with no project context could execute it correctly. Every task has exact file paths, complete code, and a verification step. No placeholders. DRY, YAGNI, TDD, frequent commits.
The plan is the contract between the designer (you + the human) and the executor (another agent, a subagent, or future-you). Vagueness in the plan becomes bugs in the code.
When to Use
- A spec or brainstormed design exists and has been approved
- Work touches multiple files or modules
- Multi-step task that would benefit from checkpoints
- Before dispatching subagents or batch-executing tasks
When NOT to use:
- Single-file, obvious changes (just implement)
- Typo/comment/config-only changes
- Exploratory spikes where the goal is to learn, not ship
Related skills:
methodology-spec-drivenproduces the spec this skill consumesworkflow-executing-plans/workflow-subagent-drivenexecute the plan this skill producesworkflow-git-worktreescreates the isolated workspace the plan runs in
The Workflow
Approved spec ─→ Scope check ─→ File structure ─→ Task decomposition ─→ Self-review ─→ Plan saved
│ │ │
▼ ▼ ▼
Split multi-subsystem Bite-sized (2-5 min) tasks No placeholders
specs into sub-plans with exact code + commands Spec coverage
Where to Save Plans
Save to .agents/plans/YYYY-MM-DD-<feature-name>.md in the product repo. Commit the plan alongside the code it produces so the intent travels with the change.
If the product repo overrides this path (via .agents/project.json or team convention), respect it.
Step 1 — Scope Check
If the spec covers multiple independent subsystems (e.g. "billing + notifications + admin UI"), do not produce one monster plan. Split into one plan per subsystem, each producing working, testable software on its own. Ship in order.
What ships with it
1 file 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.
- 8d ago First seen · 250 lines · 53 tokens per session scan A d9e0cc9646c0
writing-plans is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 2,509 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…