Skip to content
Back to skills

Writing Plans

ASecurity

Use when the user requests an implementation plan, or unresolved dependencies make a brief execution plan useful before work.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 16, 2026
ai-agents

Security analysis

A100/100

Scanned October 16, 2026

npx -y skills add alleneubank/agent-profile --skill writing-plans --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Writing Plans?

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

Security grade badge for Writing Plans
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/alleneubank-writing-plans/badge)](https://www.skillsdirectory.com/skills/alleneubank-writing-plans)

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: writing-plans
description: Use when the user requests an implementation plan, or unresolved dependencies make a brief execution plan useful before work.
---

# Implementation plans

Name the concrete files or components, order the dependent steps, and state
the check that decides completion.

Keep the plan in the conversation or existing task record. A standalone document
is useful only when requested or needed for coordination or recovery. An existing
campaign uses its own record rather than a second plan.

Name any real prerequisite or high-risk approval before it blocks dependent
work. Do not prescribe every read, test layer, worker round, or post-green
refactor. Update the plan when findings change the work. Once execution is
authorized, implement rather than repeatedly refining the plan.

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.