writing-plans

Generate detailed implementation plans from project specs with steps and tests.

3|Updated Jun 3, 2022
One-click install
npx skills add https://github.com/Hohlas/SoSimple --skill writing-plans-hohlas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Hohlas/SoSimple/tree/main/.kilocode/skills/writing-plans
Command: npx skills add https://github.com/Hohlas/SoSimple --skill writing-plans-hohlas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps teams convert vague or incomplete specs into comprehensive, actionable implementation plans that guide engineers through tasks, tests, and documentation.

Core Features & Use Cases

  • Creates step-by-step task breakdowns covering files to touch, tests to write, and documentation to update.
  • Supports test-driven development by outlining minimal code changes and verification steps.
  • Useful for onboarding, project scoping, and ensuring alignment between engineers, product managers, and stakeholders.

Quick Start

Provide a project spec and I will generate a complete implementation plan saved to docs/plans/YYYY-MM-DD-writing-plans.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan from a software specification?

To create an implementation plan from a specification, provide the project spec to generate a detailed, task-focused breakdown saved to docs/plans/. The plan documents files to touch, testing strategies, and milestones to guide engineers.

How do I break down feature development tasks for engineers?

Break down feature development tasks by converting vague specs into actionable step-by-step instructions. The generated plan outlines minimal code changes, verification steps, and documentation updates to ensure alignment across the team.

Can I generate a test-driven development plan for an existing codebase?

Yes, you can generate a test-driven development plan for an existing codebase. The plan supports TDD by outlining minimal code changes required and detailing specific verification steps and tests to write.

What is the best way to document project scoping for onboarding engineers?

The best way to document project scoping for onboarding is generating a comprehensive implementation plan. It converts incomplete specs into clear steps, tests, and milestones, ensuring alignment between engineers, product managers, and stakeholders.

Does this implementation plan generator work for bug fixes and enhancements?

Yes, this implementation plan generator works for bug fixes and enhancements across codebases. It applies the planning mechanism to any feature development or maintenance task, producing reproducible steps and testing strategies.

What format does the generated implementation plan use?

The generated implementation plan uses a Markdown file format saved directly to the docs/plans/ directory. It is named with the current date and title, ensuring reproducible documentation for your codebase.