Writing Plans

Before you write any code for a multi-step feature, this generates a comprehensive implementation plan broken into 2-5 minute tasks following strict TDD workflow. Each task includes exact file paths, complete code snippets, test commands with expected output, and commit messages. It assumes you're a skilled dev who knows nothing about the codebase or domain, so it documents everything. Plans get saved to `docs/plans/` and you can either execute them with subagents in the same session or hand off to a parallel session using the executing-plans skill. The granularity is aggressive: write test, run test, implement, run again, commit are separate steps. Useful when you have clear requirements but need to enforce disciplined incremental development.

skills.sh installs: 735
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill writing-plans --agent claude-code

Installs into .claude/skills of the current project.

Files

Writing Plans

Overview

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.

Announce at start: "I'm using the writing-plans skill to create the implementation plan."

Context: Use the project's existing planning location and workflow. A dedicated worktree is useful when code isolation is needed, but planning does not require an unavailable brainstorming skill or authorize implementation.

Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md