What is writing-plans?

A skill for turning an approved idea or scope into a concrete coding plan. It identifies affected files, the order of changes, dependencies, risks, owners, and checkpoints.

Use it to map a codebase, list new or changed files, break work into tasks, identify dependencies, and prepare an executable implementation plan.

It removes uncertainty about what needs to change before implementation begins. The resulting plan can guide execution or parallel work by agents.

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

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 omergocmen/vibe-coder-kit --skill writing-plans

Clone the repo

git clone --depth 1 https://github.com/omergocmen/vibe-coder-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/omergocmen/vibe-coder-kit/writing-plans/github.svg)](https://agentmods.dev/skills/omergocmen/vibe-coder-kit/writing-plans)

Your own site

<a href="https://agentmods.dev/skills/omergocmen/vibe-coder-kit/writing-plans"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-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/omergocmen/vibe-coder-kit/writing-plans"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/writing-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,685 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.00000	$0.01685
Opus 5.5	$0.00000	$0.00674
Sonnet 5.5	$0.00000	$0.00337
Haiku 4.5	$0.00000	$0.00169

Measured 1mo ago against content hash 316d0b7266c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

.agent/skills/writing-plans/SKILL.md · 191 lines

How it starts

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

name: writing-plans description: > Turns an approved scope or idea into a concrete, executable implementation plan. Defines what changes, in what order, with what dependencies, risks flagged, and checkpoints marked. Output feeds directly into executing-plans or dispatching-parallel-agents.

Writing Plans Skill

Ön Koşul

Bu skill başlamadan önce şunlar hazır olmalı:

brainstorming tamamlandı ve scope doc var → .agent/SCOPE-<slug>.md
Başarı kriterleri netleşti
Tech stack kararı verildi

Scope doc'u yükle: .agent/SCOPE-*.md patterninde arama yap ve en son tarihli olanı oku. Bunlar yoksa önce brainstorming skill'ini çalıştır.

Süreç

Adım 1: Etkilenen Alanları Haritala

Mevcut kod tabanını tara ve neyin değişeceğini belirle:

src/
├── components/     ← Yeni komponent: UserCard
├── services/       ← Değişecek: userService.ts
├── api/            ← Yeni endpoint: POST /api/users
├── db/migrations/  ← Yeni migration: add_users_table
└── tests/          ← Yeni testler: userService.test.ts

Her etkilenen dosya için:

Yeni mi, değişiyor mu, siliniyor mu?
Başka ne bu dosyaya bağımlı? (kırmadan değiştirilebilir mi?)

Adım 2: Görevleri Atomik Parçalara Böl

Her görev:

Tek bir şey yapar
Bağımsız commit olabilir
Test edilebilir (tamamlandığını nasıl anlarsın?)
2 saatten kısa (daha uzunsa böl)

## Görev Listesi

### T1: Database migration — users tablosu
- Dosya: db/migrations/001_create_users.sql
- İçerik: id, email, password_hash, created_at, deleted_at
- Bağımlılık: Yok (ilk adım)
- Test: Migration up/down çalışıyor

### T2: User model ve repository
- Dosya: src/db/repositories/userRepository.ts
- İçerik: findById, findByEmail, create, softDelete
- Bağımlılık: T1 (migration olmalı)
- Test: repository unit testleri geçiyor

### T3: UserService — iş mantığı
- Dosya: src/services/userService.ts
- İçerik: createUser (hash password), getUser, deleteUser
- Bağımlılık: T2
- Test: service unit testleri geçiyor

### T4: API endpoint — POST /api/users
- Dosya: src/api/routes/users.ts
- İçerik: validation, auth middleware, service çağrısı
- Bağımlılık: T3
- Test: integration test geçiyor

### T5: Frontend — UserCard komponenti
- Dosya: src/components/UserCard/
- İçerik: komponent + test + storybook
- Bağımlılık: T4 (API mock veya gerçek)
- Test: komponent testleri geçiyor

Read the full file on GitHub · 191 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.

1mo ago First seen · 191 lines · 0 tokens per session scan A 316d0b7266c2

Subscribe to this mod's changes

writing-plans is a skill published in the GitHub repository omergocmen/vibe-coder-kit (97 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,685 tokens. 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.

Planning ai ai-agents ai-skills antigravity antigravity-rules antigravity-skills

tdd

Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/ /, verify APIs via web search, then implement in tiny test-verified steps.

Shelpuk-AI-Technology-Consulting/agent-skill-tdd · 59 tokens

electron-desktop-builder

Converts a web app (Express, React, Vite, Next.js) into an Electron desktop app. Use when starting a new Electron project from an existing web app, when setting up electron-builder for the first time, when creating main.ts/preload.ts boilerplate, when generating icon assets, or when configuring NSIS installers.…

smartbrainactivity/electron-desktop-builder · 109 tokens

writing-plans