Workflow
brianlovin/agent-config
Workflow orchestration for complex coding tasks. An agent skill from brianlovin/agent-config.
Structured task planning with clear breakdowns, dependencies, and verification criteria.
Install Plan Writing
$ npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install xenitV1/Antigravity-Workflows plan-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plan-writing .claude/skills/plan-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plan-writing" agent skill from https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/plan-writing into .claude/skills/plan-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/plan-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install xenitV1/Antigravity-Workflows plan-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plan-writing .agents/skills/plan-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-writing" agent skill from https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/plan-writing into .agents/skills/plan-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install xenitV1/Antigravity-Workflows plan-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plan-writing .cursor/skills/plan-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-writing" agent skill from https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/plan-writing into .cursor/skills/plan-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/xenitV1/Antigravity-Workflows.git --path skills/plan-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install xenitV1/Antigravity-Workflows plan-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plan-writing .gemini/skills/plan-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-writing" agent skill from https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/plan-writing into .gemini/skills/plan-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install xenitV1/Antigravity-Workflows plan-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plan-writing .github/skills/plan-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-writing" agent skill from https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/plan-writing into .github/skills/plan-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install xenitV1/Antigravity-Workflows plan-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plan-writing .opencode/skills/plan-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-writing" agent skill from https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/plan-writing into .opencode/skills/plan-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan-writing- GitHub stars
- 130
- Used in
- 8 other repos
- Token cost
- ~994 tokens
- SKILL.md length
- 366 words
- Files
- 1
- Skills in repo
- 42
- Repo updated
- First seen
- Licence
- MIT
At a glance
Structured task planning with clear breakdowns, dependencies, and verification criteria.
- Works in 4 steps: Small, Focused Tasks → Clear Verification → Logical Ordering → …
- Implementing features
- SKILL.md covers Overview, Task Breakdown Principles, Planning Principles (NOT… and Plan Structure (Flexible, Not…, plus 1 more section
- Calls npx and npm
What it does
Plan Writing is an agent skill from xenitV1/Antigravity-Workflows. Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Planning and Refactoring. The licence is MIT.
When your agent uses it
- Implementing features
- Any multi-step work
Example prompts
- “/plan-writing”
Requirements
- Node.js
- Pre-approved tools (allowed-tools): Read, Glob, Grep
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit f0a1fa7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npxnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plan Writing loads about 994 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 366 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from xenitV1/Antigravity-Workflows at commit f0a1fa7, republished under its MIT licence (© xenitV1). 366 words, ~994 tokens.
Download SKILL.mdSave it as
.claude/skills/plan-writing/SKILL.md (or your agent's skills folder).- name
- plan-writing
- description
- Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
- allowed-tools
- Read, Glob, Grep
Plan Writing
Source: obra/superpowers
Overview
This skill provides a framework for breaking down work into clear, actionable tasks with verification criteria.
Task Breakdown Principles
1. Small, Focused Tasks
- Each task should take 2-5 minutes
- One clear outcome per task
- Independently verifiable
2. Clear Verification
- How do you know it's done?
- What can you check/test?
- What's the expected output?
3. Logical Ordering
- Dependencies identified
- Parallel work where possible
- Critical path highlighted
- Phase X: Verification is always LAST
4. Dynamic Naming in Project Root
- Plan files are saved as
{task-slug}.mdin the PROJECT ROOT - Name derived from task (e.g., "add auth" →
auth-feature.md) - NEVER inside
.claude/,docs/, or temp folders
Planning Principles (NOT Templates!)
🔴 NO fixed templates. Each plan is UNIQUE to the task.
Principle 1: Keep It SHORT
| ❌ Wrong | ✅ Right |
|---|---|
| 50 tasks with sub-sub-tasks | 5-10 clear tasks max |
| Every micro-step listed | Only actionable items |
| Verbose descriptions | One-line per task |
Rule: If plan is longer than 1 page, it's too long. Simplify.
Principle 2: Be SPECIFIC, Not Generic
| ❌ Wrong | ✅ Right |
|---|---|
| "Set up project" | "Run npx create-next-app" |
| "Add authentication" | "Install next-auth, create /api/auth/[...nextauth].ts" |
| "Style the UI" | "Add Tailwind classes to Header.tsx" |
Rule: Each task should have a clear, verifiable outcome.
Show full SKILL.md (170 more words)Show less
Principle 3: Dynamic Content Based on Project Type
For NEW PROJECT:
- What tech stack? (decide first)
- What's the MVP? (minimal features)
- What's the file structure?
For FEATURE ADDITION:
- Which files are affected?
- What dependencies needed?
- How to verify it works?
For BUG FIX:
- What's the root cause?
- What file/line to change?
- How to test the fix?
Principle 4: Scripts Are Project-Specific
🔴 DO NOT copy-paste script commands. Choose based on project type.
| Project Type | Relevant Scripts |
|---|---|
| Frontend/React | ux_audit.py, accessibility_checker.py |
| Backend/API | api_validator.py, security_scan.py |
| Mobile | mobile_audit.py |
| Database | schema_validator.py |
| Full-stack | Mix of above based on what you touched |
Wrong: Adding all scripts to every plan Right: Only scripts relevant to THIS task
Principle 5: Verification is Simple
| ❌ Wrong | ✅ Right |
|---|---|
| "Verify the component works correctly" | "Run npm run dev, click button, see toast" |
| "Test the API" | "curl localhost:3000/api/users returns 200" |
| "Check styles" | "Open browser, verify dark mode toggle works" |
Plan Structure (Flexible, Not Fixed!)
# [Task Name]
## Goal
One sentence: What are we building/fixing?
## Tasks
- [ ] Task 1: [Specific action] → Verify: [How to check]
- [ ] Task 2: [Specific action] → Verify: [How to check]
- [ ] Task 3: [Specific action] → Verify: [How to check]
## Done When
- [ ] [Main success criteria]That's it. No phases, no sub-sections unless truly needed. Keep it minimal. Add complexity only when required.
Notes
[Any important considerations]
---
## Best Practices (Quick Reference)
1. **Start with goal** - What are we building/fixing?
2. **Max 10 tasks** - If more, break into multiple plans
3. **Each task verifiable** - Clear "done" criteria
4. **Project-specific** - No copy-paste templates
5. **Update as you go** - Mark `[x]` when complete
---
## When to Use
- New project from scratch
- Adding a feature
- Fixing a bug (if complex)
- Refactoring multiple files© xenitV1, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/plan-writing of xenitV1/Antigravity-Workflows.
Open the folder on GitHubat commit f0a1fa7
Used in 8 other repositories
We found 17 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 8 other GitHub owners. This page covers the copy in xenitV1/Antigravity-Workflows, which our catalogue first saw on October 7, 2026.
- AratKruglik/claude-laravel.claude/skills/plan-writing
- davila7/claude-code-templatescli-tool/components/skills/productivity/plan-writing
- aiskillstore/marketplaceskills/sickn33/plan-writing
- sickn33/agentic-awesome-skillsskills/plan-writingplugins/agentic-awesome-skills/skills/plan-writing+1 more
- agent-skills-hub/agent-skills-hubskills/plan-writing
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/plan-writingantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/plan-writing+1 more
- benjaminasterA/antigravity-awesome-skillsskills/plan-writing
- henryalouf/ruflow.agents/skills/plan-writing.agents/skills/antigravity-awesome-skills/skills/plan-writing+4 more
Compare with similar skills
Plan Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan Writing this skillxenitV1/Antigravity-Workflows | 130 | 8 repos | ~994 | Automated safety check: Pass | MIT | |
| Workflowbrianlovin/agent-config | 377 | 1 repos | ~687 | Automated safety check: Pass | None | |
| Write Specdzhng/skills | 1k | — | ~4.7k | Automated safety check: Pass | MIT | |
| Evanflow Improve Architectureevanklem/evanflow | 418 | — | ~950 | Automated safety check: Pass | Custom licence | |
| Improvefossasia/eventyay-interpretation | 1.6k | 10 repos | ~3.7k | Automated safety check: Warn | MIT | |
| Claude Code Clawdbotwin4r/claude-code-clawdbot-skill | 123 | — | ~2.5k | Automated safety check: Warn | None |
Similar skills
Write Spec
dzhng/skills
Break large features into independently verifiable, human-reviewable slices under a feature directory in specs/.
Evanflow Improve Architecture
evanklem/evanflow
Identify refactoring opportunities by surfacing architectural friction.
Improve
fossasia/eventyay-interpretation
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.
Claude Code Clawdbot
win4r/claude-code-clawdbot-skill
Run Claude Code (Anthropic) from this host via the claude CLI (Agent SDK) in headless mode (-p) for codebase analysis, refactors, test fixing, and structured output.
One Three One Rule
Tommy-yw/RunbookHermes
Structured decision-making framework for technical proposals and trade-off analysis.
More from xenitV1/Antigravity-Workflows
All 42 skills in this repoParallel Agents
xenitV1/Antigravity-Workflows
Native multi-agent orchestration using Claude Code's Agent Tool.
Mobile Design
xenitV1/Antigravity-Workflows
Mobile-first design thinking and decision-making for iOS and Android apps.
Bash Linux
xenitV1/Antigravity-Workflows
Bash/Linux terminal patterns. An agent skill from xenitV1/Antigravity-Workflows.
Performance Profiling
xenitV1/Antigravity-Workflows
Performance profiling principles. An agent skill from xenitV1/Antigravity-Workflows.
Behavioral Modes
xenitV1/Antigravity-Workflows
AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate).
I18n Localization
xenitV1/Antigravity-Workflows
Internationalization and localization patterns. An agent skill from xenitV1/Antigravity-Workflows.
Related
Categories
Questions about Plan Writing
What does Plan Writing do?
Structured task planning with clear breakdowns, dependencies, and verification criteria. Plan Writing is an agent skill from xenitV1/Antigravity-Workflows. Structured task planning with clear breakdowns, dependencies, and verification criteria.
When should I use Plan Writing?
Plan Writing fits situations like: implementing features; any multi-step work.
How do I install Plan Writing in Claude Code?
Run `npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a claude-code`. Or copy the skill folder (skills/plan-writing in xenitV1/Antigravity-Workflows) into .claude/skills/plan-writing in your project. Claude Code loads it when a task matches its description.
How do I install Plan Writing in Codex?
Run `npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a codex`. Or copy the skill folder (skills/plan-writing in xenitV1/Antigravity-Workflows) into .agents/skills/plan-writing in your project. Codex loads it when a task matches its description.
Can I use Plan Writing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add xenitV1/Antigravity-Workflows --skill plan-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-writing, .gemini/skills/plan-writing, .github/skills/plan-writing and .opencode/skills/plan-writing in your project.
What does Plan Writing need to run?
Going by SKILL.md and its folder, Plan Writing needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Glob, Grep.
Does Plan Writing access the network?
SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Plan Writing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plan Writing use?
Plan Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plan Writing use?
About 994 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Plan Writing?
Skills that share tags, products or a category with Plan Writing: Workflow (brianlovin/agent-config, 377 stars), Write Spec (dzhng/skills, 1k stars), Evanflow Improve Architecture (evanklem/evanflow, 418 stars) and Improve (fossasia/eventyay-interpretation, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan Writing?
xenitV1 (a GitHub user) maintains it in xenitV1/Antigravity-Workflows, which has 130 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on January 14, 2026.
Source: xenitV1/Antigravity-Workflows on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.