plan-writing
Create Focused Implementation Plans
Multi-step coding work can become vague, large, and hard to verify. This skill helps Claude, Codex, and Claude Code create short plans with clear tasks, order, and checks.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "plan-writing" from https://skillstore.io/skills/sickn33-plan-writing.md and its manifest at https://skillstore.io/api/skills/sickn33-plan-writing/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "plan-writing". Add password reset to an existing web application.
Expected outcome:
- Goal: Add a secure password reset flow.
- Tasks: confirm current auth flow; add request step; add reset step; connect email delivery; verify valid and invalid token behavior.
- Done when users can reset passwords and invalid tokens fail safely.
Using "plan-writing". Refactor the settings area into smaller modules.
Expected outcome:
- Goal: Split settings code without changing user behavior.
- Tasks: map current settings flow; extract shared state; move each section; update imports; verify settings still save correctly.
- Done when existing settings behavior passes manual and automated checks.
Using "plan-writing". Fix an intermittent checkout failure.
Expected outcome:
- Goal: Identify and fix the checkout failure path.
- Tasks: reproduce the failure; inspect payment and cart state; patch the root cause; add a regression check; verify successful checkout.
- Done when the failure no longer reproduces under the documented scenario.
Security Audit
SafeStatic analysis flagged Markdown backticks as possible Ruby or shell execution. Review confirms they are inline filenames, command examples, script names, and fenced plan text in SKILL.md. No executable code, prompt injection, network access, or data exfiltration intent was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-plan-writing/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-plan-writing?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-plan-writing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-plan-writing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-plan-writing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). plan-writing security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-plan-writing/audits/4BibTeX citation
@techreport{sickn33-sickn33-plan-writing-2026,
author = {sickn33},
title = {plan-writing security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-plan-writing/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "plan-writing security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-plan-writing/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-plan-writing:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a feature build
Create a short implementation plan with ordered tasks, affected areas, and verification checks.
Organize a refactor
Break a refactor into safe steps with dependencies, review points, and clear completion criteria.
Clarify a bug fix
Turn a complex defect into a focused fix plan with root cause checks and test expectations.
Try These Prompts
Use plan-writing to create a short plan for this task: [describe task]. Include a goal, tasks, and done criteria.
Use plan-writing for this feature: [feature]. Include likely affected files, dependencies, task order, and verification checks.
Use plan-writing to plan this refactor: [scope]. Keep tasks small, identify dependencies, and define safe verification after each step.
Use plan-writing to create a concise delivery plan for [project]. Include critical path, parallel work, risk checks, and final verification.
Best Practices
- Provide the task goal, stack, known files, and acceptance criteria before planning.
- Keep every task tied to one clear verification check.
- Revise the plan when discovery changes the scope or order.
Avoid
- Requesting a long template when the task needs a short checklist.
- Using generic setup steps without naming the actual project context.
- Treating the plan as complete when verification criteria are missing.