writing-plans

Generate step-by-step implementation plans with file changes, tests, and commits.

Updated Dec 22, 2024
One-click install
npx skills add https://github.com/lvstb/nix-config --skill writing-plans-lvstb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/lvstb/nix-config/tree/main/home/opencode/skills/writing-plans
Command: npx skills add https://github.com/lvstb/nix-config --skill writing-plans-lvstb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineers create detailed, step-by-step implementation plans for multi-step tasks, ensuring clarity and reducing ambiguity before coding begins.

Core Features & Use Cases

  • Generates granular tasks: Breaks down complex features into 2-5 minute actionable steps.
  • Enforces best practices: Promotes TDD, DRY, YAGNI, and frequent commits.
  • Provides clear instructions: Specifies exact file paths, code snippets, commands, and expected outputs.
  • Use Case: Before starting a new feature, use this Skill to generate a plan that outlines every test, code change, and commit, ensuring a smooth development process.

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 feature into actionable coding steps?

Breaking down a complex software feature involves outlining specific file modifications, test cases, and minimal code implementations. This approach generates detailed, bite-sized implementation plans that ensure all steps are actionable and verifiable for engineers with no prior context.

What is the best way to create an implementation plan that follows TDD and DRY principles?

Creating an implementation plan that follows TDD and DRY principles requires outlining every test, code change, and commit beforehand. This method enforces best practices by generating granular tasks that specify exact file paths, code snippets, and expected outputs for a smooth development process.

How do I generate a step-by-step task breakdown for a multi-step development task?

Generating a step-by-step task breakdown for a multi-step development task involves dividing complex features into 2-5 minute actionable steps. This process reduces ambiguity before coding begins by providing clear instructions with exact file paths, commands, and expected outputs.

Does writing-plans generate commit messages for implementation steps?

Yes, writing-plans generates commit messages for implementation steps. It outlines specific file modifications, test cases, minimal code implementations, and commit messages, ensuring all steps are actionable and verifiable while adhering to frequent commit practices.

Can I use this approach to plan tasks for engineers with no prior project context?

Yes, you can use this approach to plan tasks for engineers with no prior project context. The generated implementation plans ensure all steps are actionable and verifiable by providing exact file paths, code snippets, commands, and expected outputs, reducing ambiguity before coding begins.