writing-plans
Create Implementation Plans
Complex development tasks often fail when teams start coding without a shared plan. This skill turns requirements into test-driven implementation plans for Claude, Codex, and Claude Code.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "writing-plans" from https://skillstore.io/skills/sickn33-writing-plans.md and its manifest at https://skillstore.io/api/skills/sickn33-writing-plans/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 "writing-plans". A user asks for a plan to add login rate limiting.
Expected outcome:
The skill produces a dated plan with a goal, architecture notes, task list, target files, failing tests, verification commands, and commit points.
Using "writing-plans". A lead asks for a refactor plan before changing service boundaries.
Expected outcome:
The skill outlines inspection steps, test coverage tasks, minimal implementation phases, expected test results, and a final execution handoff.
Using "writing-plans". A developer needs another session to implement a completed specification.
Expected outcome:
The skill creates a plan that explains context, exact work items, validation steps, and options for subagent or separate-session execution.
Security Audit
SafeAll static findings are false positives caused by markdown backticks, code fences, example file paths, and example test or git commands. No evidence found of executable scripts, command injection, network access, credential access, or prompt injection instructions in the audited file.
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-writing-plans/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-writing-plans?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-writing-plans?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-writing-plans/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-writing-plans.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). writing-plans security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-writing-plans/audits/5BibTeX citation
@techreport{sickn33-sickn33-writing-plans-2026,
author = {sickn33},
title = {writing-plans security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-writing-plans/audits/5},
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: "writing-plans security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-writing-plans/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-writing-plans:audit:5"
description: "Skillstore immutable audit report identifier"
Compare variants
9 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
obra-writing-plans
2026-08-21
zhanlincui-writing-plans
2026-08-21
sickn33-writing-plans
2026-08-21
dmjgilbert-writing-plans
2026-08-21
cycleaddict-writing-plans
2026-08-21
cygnusfear-writing-plans
2026-08-21
codingcossack-writing-plans
2026-08-21
davila7-writing-plans
2026-08-21
dyai2025-writing-plans
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a Feature Build
Convert a feature specification into ordered tasks with file paths, tests, commands, and commit checkpoints.
Prepare Implementation Handoff
Create a plan that another assistant session or developer can follow with limited project context.
Structure Test-Driven Work
Define failing tests, minimal implementation steps, verification commands, and expected results before code changes begin.
Try These Prompts
Use the writing-plans skill to create an implementation plan for this feature: [describe feature]. Include files, tests, commands, and commit steps.
Use the writing-plans skill with this requirement document: [paste requirements]. Create a plan saved under docs/plans with small TDD tasks.
Use the writing-plans skill to plan this refactor: [describe current design and target design]. Include risk areas, tests, and exact files to inspect.
Use the writing-plans skill to create a handoff-ready plan for [project goal]. Include task checkpoints, expected outputs, and execution options.
Best Practices
- Provide the feature specification and any relevant repository context before asking for the plan.
- Review generated file paths, commands, and expected outputs before execution begins.
- Keep each task small enough to test, review, and commit independently.
Avoid
- Do not use the plan as a substitute for understanding production constraints.
- Do not run generated commands blindly without checking the repository state.
- Do not ask for broad plans without requirements, acceptance criteria, or target files.