writing-plans

Transform vague specs into structured task plans with testable criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The writing-plans skill helps teams translate vague specs into actionable, step-by-step implementation plans, ensuring engineers have a clear path from idea to code.

Core Features & Use Cases

  • Plan decomposition: break down a feature into tasks with explicit interfaces and acceptance criteria.
  • Scope mapping: map tasks to files, modules, and testing artifacts to minimize rework.
  • Plan templates: provide reusable plan structures for common domains (web apps, services, data pipelines).

Quick Start

Provide a feature name and a concise spec to generate a complete, task-scoped implementation plan.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
What is the best way to plan task decomposition for a complex feature across a team?

Scope mapping connects planned tasks to specific files, modules, and testing artifacts to minimize rework. It enforces explicit task boundaries and testable criteria, ensuring each implementation step has a clear deliverable.

Do I need a concise feature spec to generate a task-scoped implementation plan?

Yes, you can generate implementation plans for common domains like web apps, services, and data pipelines. It provides reusable plan structures to ensure engineers have a clear path from idea to code across various software engineering contexts.

How do I ensure my implementation plan includes testable deliverables and milestones?

Yes, you need to provide a feature name and a concise spec to generate a complete, task-scoped implementation plan. This input allows the planning process to translate the vague spec into structured, executable work.

Can I generate implementation plans for different software domains like data pipelines?

To ensure testable deliverables, the plan enforces a format with explicit task boundaries and testable acceptance criteria. It applies to projects requiring decomposed work and milestone planning, providing a clear path from idea to code.