Skip to content
Back to skills

Write Plan

ASecurity

MUST use after brainstorming and before executing. Creates detailed implementation plans with checkpoints, verification criteria, and execution options.

  • 33 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 30, 2026
testinggo

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add dvcrn/openclaw-skills-marketplace --skill write-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Write Plan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Write Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dvcrn-write-plan/badge)](https://www.skillsdirectory.com/skills/dvcrn-write-plan)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: write-plan
description: "MUST use after brainstorming and before executing. Creates detailed implementation plans with checkpoints, verification criteria, and execution options."
---

# Write Plan

## Overview

Transform validated designs into detailed, actionable implementation plans with checkpoints.

Every plan includes:
- Bite-sized tasks (2-5 minutes each)
- Checkpoints with verification criteria
- Estimated time for each section
- Execution options at the end

## Plan Structure

```markdown
# [Project Name] - Implementation Plan

**Goal:** One sentence describing success
**Approach:** Brief summary of the chosen approach
**Estimated Total Time:** X minutes

## Checkpoint 1: [Milestone Name]
- [ ] Task 1: [Description] (~X min)
  - **Action:** [Specific action]
  - **Verify:** [How to confirm done]
- [ ] Task 2: [Description] (~X min)
  ...

## Checkpoint 2: [Milestone Name]
...

## Verification Criteria
- [ ] All checkpoints complete
- [ ] Quality standards met
- [ ] User approval obtained
```

## Task Granularity

- **Small:** 2-5 minutes of work
- **Specific:** Clear what "done" means
- **Verifiable:** Can confirm completion
- **Independent:** Doesn't block on other tasks in same checkpoint

## Execution Handoff

After saving the plan, offer execution choice:

**"Plan complete and saved to `memory/plans/<filename>.md`. Two execution options:**

**1. Single-Agent (this session)** - I execute tasks sequentially, review at each checkpoint

**2. Dispatch Multiple Agents (parallel)** - Spawn subagents for independent tasks

**Which approach?"**

**If Single-Agent chosen:**
- Stay in this session
- Execute tasks sequentially
- Report progress at each checkpoint

**If Dispatch Multiple Agents chosen:**
- Use dispatch-multiple-agents skill
- Spawn subagents for parallel work
- Integrate results

## Integration with Other Skills

- After **brainstorming** → Use write-plan
- Before **doing-tasks** → Plan must exist
- With **dispatch-multiple-agents** → For parallel execution

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…