writing-plans
Create Detailed Implementation Plans
Complex work is risky when requirements are not broken into clear steps. This skill turns specs into test-focused 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/obra-writing-plans.md and its manifest at https://skillstore.io/api/skills/obra-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 request to add password reset to an existing web app.
Expected outcome:
A dated plan with a goal, architecture notes, file targets, test-first tasks, verification steps, and commit checkpoints.
Using "writing-plans". A request to refactor billing logic without changing behavior.
Expected outcome:
- Characterization tests before implementation.
- Small refactor tasks with exact affected files.
- Regression commands and expected results after each task.
Using "writing-plans". A request to hand work to a separate Claude Code session.
Expected outcome:
A self-contained plan with context, ordered tasks, expected outputs, and clear execution handoff instructions.
Security Audit
SafeThe static external command findings are false positives caused by Markdown code fences and inline code examples in SKILL.md. The skill creates implementation plans and does not contain executable scripts, network access, environment access, or data exfiltration intent.
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/obra-writing-plans/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/obra-writing-plans?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/obra-writing-plans?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/obra-writing-plans/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/obra-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
obra. (2026). writing-plans security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/obra-writing-plans/audits/9BibTeX citation
@techreport{obra-obra-writing-plans-2026,
author = {obra},
title = {writing-plans security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/obra-writing-plans/audits/9},
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 9)"
version: "unspecified"
type: report
authors:
- name: "obra"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/obra-writing-plans/audits/9"
identifiers:
- type: other
value: "skillstore:obra-writing-plans:audit:9"
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
Turn a product spec into ordered tasks with files, tests, and commit checkpoints.
Prepare Agent Handoff
Create a plan that another Claude, Codex, or Claude Code session can execute consistently.
Standardize Test-First Work
Convert unclear requirements into test-first steps with expected results and review points.
Try These Prompts
Create an implementation plan for this feature. Include the goal, likely files, tasks, tests, and commit points.
Use the repository context already gathered. Write a detailed plan with exact file paths, test commands, and expected outcomes.
Plan this refactor using TDD. Separate characterization tests, implementation tasks, regression checks, and review checkpoints.
Create a plan that another session can execute task by task. Include handoff notes, dependencies, verification commands, and rollback guidance.
Best Practices
- Provide the spec, constraints, and affected areas before asking for a plan.
- Ask for exact file paths and test commands when repository context is available.
- Review the plan before execution so outdated assumptions are corrected.
Avoid
- Do not use it as a replacement for reading the codebase.
- Do not accept placeholder paths when exact files are required.
- Do not execute a generated plan without checking assumptions first.