One-click install
npx skills add https://github.com/solinumasso/solikit --skill writing-plans-solinumasso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/solinumasso/solikit/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/solinumasso/solikit --skill writing-plans-solinumasso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert a vague or multi-step spec into a clear, step-by-step implementation plan that an engineer can execute without needing prior context.

Core Features & Use Cases

  • Multi-step implementation planning: Breaks a complex task into bite-sized, testable steps so development can start immediately.
  • Codebase-agnostic guidance: Assumes the engineer has little or no context and specifies exactly what files to touch, what to test, and how to commit.
  • Plan documentation for traceability: Saves generated plans into docs/plans/YYYY-MM-DD-<feature-name>.md for consistent reuse and review.

Quick Start

Use the writing-plans skill to create a detailed implementation plan for a new feature by providing your requirements and constraints, and asking for a file-by-file, test-driven task breakdown.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a feature specification into an actionable implementation plan?

To turn a feature specification into an implementation plan, you provide your requirements and constraints to generate a file-by-file, test-driven task breakdown. This process decomposes complex work into bite-sized, testable steps so development can start immediately without prior codebase context.

What is the best way to break down a multi-step engineering task for developers?

The best way to break down a multi-step engineering task is to decompose it into independent subsystems with exact file paths to create, modify, and test. This ensures an engineer can execute the work with minimal context about the existing project architecture.

How does test-driven development planning work for new features?

Test-driven development planning works by validating implementation steps through defined tests within the generated plan. It specifies exactly what files to touch and how to test them, ensuring each bite-sized actionable step is validated before moving forward.

Do I need existing codebase context to generate an implementation plan?

No, you do not need existing codebase context to generate an implementation plan. The planning process is codebase-agnostic, assuming the engineer has little or no context and explicitly specifying exact file paths to touch, test, and commit.

Where should I save generated implementation plans for project traceability?

You should save generated implementation plans under docs/plans/YYYY-MM-DD-<feature-name>.md for consistent reuse and review. This deterministic instruction ensures plan documentation remains traceable throughout the engineering workflow.