writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Security Assessment
About writing-plans
The writing-plans skill is designed to streamline the process of creating comprehensive implementation plans for multi-step tasks in software development. It addresses the challenge of onboarding engineers who may be unfamiliar with a given codebase or the specific requirements of a project. By providing structured, bite-sized tasks, this skill ensures that developers can follow clear instructions without needing prior context, thereby reducing the risks associated with miscommunication and inefficiency in coding practices.
This skill emphasizes best practices such as DRY (Don't Repeat Yourself), YAGNI (You Aren't Gonna Need It), and TDD (Test-Driven Development). It breaks down tasks into manageable steps, ensuring that each action can be completed in a short time frame. Each implementation plan is meticulously documented and includes detailed instructions on which files to modify, how to test the changes, and what commands to use, making it easier for developers to contribute effectively.
Target users of the writing-plans skill include software engineers who are new to a project, teams looking to improve their development workflows, and organizations that prioritize clear documentation and code quality. This skill is particularly useful for teams that employ agile methodologies or rapid development cycles, allowing for consistent execution and review of implementation tasks.
FAQ
How do I use the writing-plans skill?
Start by announcing that you are using the writing-plans skill to create an implementation plan and ensure you are in a dedicated worktree.
What are the requirements to use this skill?
The skill requires a skilled developer familiar with coding but with little context about the toolset or project.
Can I use this skill for any programming language?
The skill is designed with a focus on Python but can be adapted for other languages as long as the structure is followed.
What are the limitations of this skill?
The skill assumes that the user has a basic understanding of development practices but may not know good test design.
Is there a specific format I need to follow when documenting plans?
Yes, every plan must start with a specific header and include a detailed task structure as outlined in the documentation.
Install writing-plans
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
davila7/claude-code-templates