writing-plans

Generate detailed implementation plans with file paths, tests, and commit messages.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/loganylchen/skills --skill writing-plans-loganylchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/loganylchen/skills/tree/main/writing-plans
Command: npx skills add https://github.com/loganylchen/skills --skill writing-plans-loganylchen

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill generates comprehensive, step-by-step implementation plans for multi-step tasks, ensuring engineers with no prior context can execute them efficiently.

Core Features & Use Cases

  • Detailed Task Breakdown: Creates bite-sized, actionable tasks for development.
  • Contextual Guidance: Specifies files to modify, code snippets, testing procedures, and documentation references.
  • Use Case: When starting a new feature, use this skill to generate a plan that outlines every test, code change, and commit needed for its successful implementation.

Quick Start

Use the writing-plans skill to create an implementation plan for adding user authentication.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a complex software development task into actionable steps?

Implementation plans break down complex software development tasks into granular, executable steps specifying file modifications, test cases, code implementation, and commit messages. This ensures developers without prior context can execute tasks efficiently by providing exact paths, commands, and expected outcomes.

What is the best way to generate a detailed implementation plan for a new feature?

Generating a detailed implementation plan involves outlining every test, code change, and commit needed for successful feature implementation. This provides contextual guidance by specifying files to modify, testing procedures, and documentation references, adhering to TDD and DRY principles.

Does implementation planning work with test-driven development and DRY principles?

Yes, implementation planning works with test-driven development and DRY principles by ensuring clarity for developers through exact paths, commands, and expected outcomes. The generated plan specifies testing procedures and code implementation steps that adhere to these software development methodologies.

Can I use an implementation plan for task breakdown if my team has no prior project context?

Yes, you can use an implementation plan for task breakdown even without prior project context. The plan generates comprehensive, step-by-step instructions that ensure engineers can execute multi-step tasks efficiently by providing exact file paths, commands, and expected outcomes.

What should be included in a software development implementation plan to ensure successful execution?

A software development implementation plan should include bite-sized, actionable tasks specifying files to modify, code snippets, testing procedures, and documentation references. It must provide exact paths, commands, and expected outcomes to ensure successful execution by developers.

How do I structure commit messages and test cases when planning a new feature?

To structure commit messages and test cases when planning a new feature, generate a detailed implementation plan that breaks down the feature into granular steps. The plan specifies exact testing procedures, code implementation, and commit messages needed for successful execution of each step.