What is writing-plans?

A guide for turning an idea or specification into a detailed, step-by-step implementation plan. It covers technical, writing, and organizational work with files, commands, checks, and expected results.

Use it to plan software changes, content projects, migrations, and other work that needs ordered tasks and verification.

It breaks large or unclear tasks into concrete actions that another person or agent can follow later.

writing-plans — Skill for Claude Code and Codex by AlekseiUL

Install

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.

Any agent

npx skills add AlekseiUL/sprut-agent-kit --skill writing-plans

Clone the repo

git clone --depth 1 https://github.com/AlekseiUL/sprut-agent-kit

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alekseiul/sprut-agent-kit/writing-plans/github.svg)](https://agentmods.dev/skills/alekseiul/sprut-agent-kit/writing-plans)

Your own site

<a href="https://agentmods.dev/skills/alekseiul/sprut-agent-kit/writing-plans"><img src="https://agentmods.dev/badge/skills/alekseiul/sprut-agent-kit/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alekseiul/sprut-agent-kit/writing-plans"><img src="https://agentmods.dev/badge/skills/alekseiul/sprut-agent-kit/writing-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 753 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00079	$0.00753
Opus 5	$0.00039	$0.00377
Sonnet 5	$0.00016	$0.00151
Haiku 4.5	$0.00008	$0.00075

Measured 9d ago against content hash 73f997189152, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

skills/writing-plans/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Планирование реализации

Превращай идеи и спеки в пошаговые планы с конкретными действиями.

Принцип

Пиши план так, будто его будет выполнять будущий-ты после рестарта - без контекста текущей сессии. Каждый шаг должен быть самодостаточным.

Структура плана

Шапка (обязательно)

# [Название] - План реализации

**Цель:** Одно предложение - что получим в итоге
**Срок:** Оценка времени
**Зависимости:** Что нужно до начала (инструменты, доступы, данные)

---

Задачи

Каждая задача - один атомарный шаг (2-10 минут):

### Шаг N: [Действие]

**Что делаем:** Конкретное описание
**Файлы:** Точные пути (создать/изменить/удалить)
**Команды:** Точные команды если есть
**Проверка:** Как убедиться что шаг выполнен
**Результат:** Что получаем после этого шага

Гранулярность

Масштабируй под задачу:

Техническая задача (скрипт, автоматизация):

Шаг = одно действие: написать, запустить, проверить, закоммитить
Точные пути к файлам
Точные команды
Ожидаемый вывод

Контентная задача (пост, видео):

Шаг = один этап: исследование, драфт, правка, публикация
Ссылки на скилы (copywriter, youtube-seo)
Референсы и источники

Организационная задача (переезд, документы):

Шаг = одно действие: позвонить, заполнить, отнести
Контакты и адреса
Дедлайны

Правила

Конкретные пути - не "файл конфига", а ~/.config/agent/config.json
Конкретные команды - не "запусти тест", а bash scripts/memory-benchmark.sh
Проверка каждого шага - как понять что сделано правильно
Нет "потом разберёмся" - каждый шаг завершён и проверен
YAGNI - только необходимые шаги, без "на всякий случай"
DRY - если шаг повторяется, вынеси в скрипт

Куда сохранять план

Технический → memory/plans/YYYY-MM-DD-название.md (шаблон: дата + краткое название)
Контентный → в daily notes
Разовый простой → прямо в чат, без файла

После плана

Предложи выбор:

Сделать сейчас - пошагово в этой сессии
Субагент - sessions_spawn для автономного выполнения
Крон - если задача по расписанию
Сохранить на потом - записать и вернуться

Read the full file on GitHub · 84 lines

Changes

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.

9d ago First seen · 84 lines · 79 tokens per session scan A 73f997189152

Subscribe to this mod's changes

writing-plans is a skill published in the GitHub repository AlekseiUL/sprut-agent-kit (63 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 753 once invoked, about $0.0004 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-30.

Claude Code Planning agent-skills ai-agents ai-assistant automation claudeclaw

weather

Get current weather and forecasts (no API key required).

netease-youdao/LobsterAI · 13 tokens

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

netease-youdao/LobsterAI · 59 tokens

writing-plans