Writing Plans
Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill writing-plansgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/writing-plans ~/.claude/skills/writing-plansPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Writing Plans ## Core Principle After brainstorming and getting user approval, break the work into a detailed, step-by-step plan BEFORE coding. ## When to Use This Skill - After completing `brainstorming` skill and getting user approval - User explicitly asks for an implementation plan - Task has 3+ distinct steps - Work involves multiple files or systems - Dependencies between tasks exist ## The Iron Law **NEVER start implementation without a written plan for non-trivial work.** A plan: - Forces you to think through the full scope - Identifies dependencies and potential issues early - Gives the user visibility into your approach - Provides checkpoints to verify progress - Prevents "I forgot to do X" mistakes ## Plan Writing Protocol ### Step 1: Announce the Planning Phase **Template:** ``` Great! Now let me create a detailed implementation plan. I'm using the writing-plans skill to break this down into discrete tasks. ``` ### Step 2: Break Down into Tasks Each task should be: - **Discrete**: Can be completed independently - **Actionable**: Clear what to do - **Verifiable**: Clear how to verify it's done - **Appropriately sized**: 5-30 minutes of work **Task Format:** ``` ## Task [Number]: [Clear, action-oriented name] **Purpose**: What this accomplishes **Actions**: - [Specific step 1] - [Specific step 2] **Files affected**: [List of files] **Verification**: How to confirm this works **Dependencies**: Requires Task X to be completed first ```
Details
- Skill name
writing-plans- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/writing-plans/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Writing Plans skill do?
Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.
How do I install the Writing Plans skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Writing Plans popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Writing Skills
8Freddy-CHEN-ux/00_claude_skills
Use when creating reusable process documentation. Apply TDD: baseline without skill → document failures → write skill → test → iterate. Four types: Discipline, Technique, Pattern, Reference. Iron Law: No skill without failing test first.
Value Stream Mapping
5vnovakovits/claude-skills
Map how a request flows from ask to value — Mike Rother & John Shook's "Learning to See" (1999) and Karen Martin & Mike Osterling's "Value Stream Mapping" (2013), adapted to software and knowledge work. Covers scoping one value stream, the map grammar (process boxes with lead time, process time and %C&A, queue triangles, push and pull arrows, information flow, the timeline ladder, kaizen bursts), collecting real numbers from tracker state history instead of opinions, the summary metrics (total lead time, process time, flow efficiency or activity ratio, rolled %C&A), the future-state questions,
Content Brief
5eshmith7/claude-skills-library
Turn a vague content request into a brief a writer can execute without a second conversation: one question, reader, intent, angle, structure, evidence required. Use for content briefs.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.