writing-plans

Draft implementation plans from specs with files, tests, and verification steps.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ingbyr/lzcode --skill writing-plans-ingbyr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ingbyr/lzcode/tree/main/packages/desktop/src-tauri/lz-assets/skills/writing-plans
Command: npx skills add https://github.com/ingbyr/lzcode --skill writing-plans-ingbyr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing-plans translates a spec or requirements into a concrete, executable plan so engineers can proceed without domain context.

Core Features & Use Cases

  • Create end-to-end task plans that cover files, tests, docs, and verification steps.
  • Enforce best practices like DRY, YAGNI, and TDD during planning.
  • Save plans to a standardized location for easy retrieval and handoffs.

Quick Start

Provide a spec or requirements and have the skill generate a complete, step-by-step implementation plan saved to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn software specs into step-by-step implementation plans?▼

To turn software specs into implementation plans, provide your requirements to generate a concrete, step-by-step plan covering scope, files, tests, docs, and verification steps for zero-context execution.

What is task decomposition in software engineering planning?▼

Task decomposition in software engineering planning breaks down specs into bite-sized executable tasks, applying DRY, YAGNI, and TDD guidance to ensure structured and actionable development steps.

How do I create an end-to-end development plan that includes tests and documentation?▼

Create an end-to-end development plan by transforming requirements into a comprehensive document that explicitly covers files to touch, tests, docs, and verification steps for seamless engineer handoffs.

Where should I save implementation plans for easy retrieval and handoffs?▼

Save implementation plans to a standardized location at docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md to ensure easy retrieval, consistent organization, and smooth team handoffs.

Does the generated plan enforce best practices like TDD and YAGNI?▼

Yes, the generated plan enforces best practices by providing task decomposition guidance that integrates DRY, YAGNI, and TDD principles directly into the actionable development steps.