📦
content-creator
88Create Brand-Consistent Marketing Content
Marketing teams need content that stays consistent across channels. This skill helps plan, write, analyze, and optimize content for brand voice and SEO.
Writing & Content View
Skills writing-plans
📦
writing-plans
Content revision r1 Safe ⚙️ External commands
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.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
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
Safev5 • 7/7/2026 Open versioned report
All 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.
1
Files scanned
117
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
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
Highest Skillstore Score
Author / source Skillstore Score Evidence Confidence Skillstore usage Updated
obra Recommended
obra-writing-plans
Skillstore Score 79
Evidence Confidence High
Skillstore usage 31
Updated
2026-09-09
zhanlincui-writing-plans
Skillstore Score 78
Evidence Confidence High
Skillstore usage 92
Updated
2026-09-09
sickn33 Current
sickn33-writing-plans
Skillstore Score 78
Evidence Confidence High
Skillstore usage 12
Updated
2026-09-09
dmjgilbert-writing-plans
Skillstore Score 78
Evidence Confidence High
Skillstore usage 11
Updated
2026-09-09
cycleaddict-writing-plans
Skillstore Score 78
Evidence Confidence High
Skillstore usage 10
Updated
2026-09-09
davila7-writing-plans
Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated
2026-09-09
cygnusfear-writing-plans
Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated
2026-09-09
codingcossack-writing-plans
Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated
2026-09-09
dyai2025-writing-plans
Skillstore Score 75
Evidence Confidence Medium
Skillstore usage 12
Updated
2026-09-09
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance
What 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
Create a Basic Plan
Use the writing-plans skill to create an implementation plan for this feature: [describe feature]. Include files, tests, commands, and commit steps.
Plan From Requirements
Use the writing-plans skill with this requirement document: [paste requirements]. Create a plan saved under docs/plans with small TDD tasks.
Plan a Refactor
Use the writing-plans skill to plan this refactor: [describe current design and target design]. Include risk areas, tests, and exact files to inspect.
Plan a Multi-Session Handoff
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.
Frequently Asked Questions
Does this skill write code?
No. It creates implementation plans that describe tests, code changes, commands, and handoff steps.
Where does it save plans?
The skill instructs the assistant to save plans under docs/plans with a dated feature filename.
Can I use it with Codex?
Yes. The skill is marked compatible with Claude, Codex, and Claude Code.
Why does it mention TDD?
It structures each task around a failing test, minimal implementation, verification, and commit.
Are the commands safe to run automatically?
No. Treat commands as plan examples and review them before execution.
What input works best?
A clear specification, acceptance criteria, known files, constraints, and any testing requirements produce the best plan.
Developer Details
Author
sickn33License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
f93e9bb0daca99badb6a7e574b97737155d57cb3
Maintenance freshness
7/18/2026
Usage
9 downloads · 146 views
File structure
📄 SKILL.md
More from sickn33
View all📦
prompt-engineering-patterns
85Improve LLM Prompts With Proven Patterns
Inconsistent prompts waste time and make AI outputs hard to trust. This skill guides prompt design with reusable patterns, examples, evaluation steps, and optimization workflows.
Productivity View
📦
senior-architect
81Review Architecture Workflows and Project Paths
Architecture reviews need a consistent starting point and clear project boundaries. This skill provides workspace-scoped tool templates, command examples, and generic design references.
Coding & Development View
📦
senior-fullstack
81Review Fullstack Project Foundations
Fullstack project setup can require many tools and checks. This skill provides basic local wrappers, common commands, and general engineering guidance.
Coding & Development View
📦
prompt-engineer
81Optimize AI Prompts With Prompt Engineer
Writing clear prompts is hard when goals are vague or complex. This skill turns rough requests into structured prompts using proven prompt frameworks.
Productivity View
📦
product-manager-toolkit
80Prioritize Product Work With Research Insights
Product teams need faster ways to rank features, synthesize interviews, and document decisions. This skill provides RICE scoring, interview analysis, and PRD templates for structured planning.
Productivity View
Related Skills
View all📦
project-planner
86Plan Software Projects With Structured Documents
by Dwsy
Software projects often fail when requirements, design choices, and tasks are unclear. This skill turns project ideas into structured planning documents for Claude, Codex, and Claude Code workflows.
Documentation View
📦
doc-coauthoring
79Draft Reader-Tested Documentation
by ZhanlinCui
Complex documents often fail when readers lack the author's context. This skill guides context gathering, section drafting, iterative edits, and reader testing.
Documentation View
📦
crafting-effective-readmes
79Create Audience-Focused READMEs
by softaworks
Generic READMEs often miss the needs of contributors, teammates, or future maintainers. This skill guides Claude, Codex, and Claude Code through audience questions, templates, and quality checks.
Documentation View
📦
docs-write
79Write Clear Metabase Documentation
by metabase
Technical documentation often becomes formal, vague, or difficult to scan. This skill helps Claude, Codex, and Claude Code write clear Metabase documentation with focused steps.
Documentation View
📦
flow-debugging
79Debug Code with Root Cause Discipline
by Dimon94
Bug fixes often fail when teams guess before they understand the cause. This skill guides Claude, Codex, and Claude Code through evidence-based debugging before implementation.
Coding & Development View
📦
organizing-with-labels
86Organize GitHub Issues With Labels
by C0ntr0lledCha0s
Large repositories can lose track of issue priority, scope, and release status. This skill designs label taxonomies, applies labels in bulk, and manages milestones with GitHub CLI workflows.
Productivity View