writing-plans

Generate step-by-step implementation plans with file paths, code snippets, and commit messages.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/Jotures/Brain_OS --skill writing-plans-jotures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Jotures/Brain_OS/tree/main/skills/_archive/writing-plans
Command: npx skills add https://github.com/Jotures/Brain_OS --skill writing-plans-jotures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating clear, actionable, and detailed implementation plans for software development tasks, especially when the engineer has limited context about the codebase or domain.

Core Features & Use Cases

  • Structured Plan Generation: Creates comprehensive plans with bite-sized tasks, including file modifications, test writing, and commit messages.
  • Contextual Guidance: Assumes an engineer with good coding skills but minimal project-specific knowledge.
  • Use Case: Before starting a new feature, use this Skill to generate a step-by-step plan that guides the developer through writing tests, implementing code, and committing changes, ensuring consistency and adherence to best practices like TDD.

Quick Start

Use the writing-plans skill to create a detailed implementation plan for the new user authentication feature.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an implementation plan for a multi-step software development task?

To generate an implementation plan, this Skill creates step-by-step instructions for multi-step software development tasks. It provides granular guidance including exact file paths, code snippets, testing commands, and commit messages to ensure consistent development workflows.

What is the best way to break down a feature into bite-sized development tasks?

The best way to break down a feature is to create structured plans with bite-sized tasks encompassing file modifications, test writing, and commit messages. This approach assumes good coding skills but minimal project-specific knowledge, contextualizing each step.

How do I create a TDD implementation plan for engineers with limited codebase context?

Creating a TDD implementation plan involves generating step-by-step instructions that emphasize Test-Driven Development, DRY, and YAGNI principles. The plan guides developers sequentially through writing tests, implementing code, and committing changes.

Does this implementation plan generator include specific file paths and testing commands?

Yes, the implementation plan generator includes exact file paths, code snippets, testing commands, and commit messages. This provides granular instructions that facilitate efficient and consistent development workflows for engineers.

Can I use this for task breakdown before starting a new user authentication feature?

Yes, you can use this for task breakdown before starting a new feature like user authentication. It generates a comprehensive, step-by-step plan that guides the developer through writing tests, implementing code, and committing changes.

What are the limitations of generating detailed implementation plans for software development?

A limitation of generating detailed implementation plans is that it assumes the engineer has good coding skills but minimal project-specific knowledge. It focuses on providing granular instructions rather than building the underlying codebase context required for broader architectural decisions.