writing-plans

Convert product specs into structured implementation plans with files, tests, and commits.

1|1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/orbtyapp/orbty-eazy --skill writing-plans-orbtyapp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/orbtyapp/orbty-eazy/tree/main/skills/writing-plans
Command: npx skills add https://github.com/orbtyapp/orbty-eazy --skill writing-plans-orbtyapp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers convert vague requirements into structured, task-based implementation plans, ensuring clarity, coverage, and traceable work items.

Core Features & Use Cases

  • Comprehensive Plan Generation: Produce a complete plan detailing files to touch, tests to write, docs to update, and commit steps.
  • TDD Alignment: Emphasize test-driven development and incremental delivery with frequent commits.
  • Worktree Isolation: Encourages using dedicated worktrees to isolate planning from active development setups.

Quick Start

Announce at start that you're using the writing-plans skill to create the implementation plan. Then outline the feature, goals, and required tests to drive the plan.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert a product spec into an actionable implementation plan?▼

Converting a product spec into an implementation plan involves outlining required files, tests, docs, and commits into a structured, task-based document. This ensures traceable work items and incremental delivery.

How does task-breakdown work with TDD and worktree isolation?▼

Task-breakdown with TDD and worktree isolation works by generating incremental delivery steps that emphasize test-driven development, while using dedicated worktrees to isolate the planning process from active development.

Can I generate a plan that outlines required files and commits for multi-step features?▼

Yes, you can generate comprehensive plans for multi-step features. The plan details exactly which files to touch, tests to write, docs to update, and the required commit steps for full coverage.

Do I need a specific template to save implementation plans?▼

Yes, you need to adhere to a specific plan document template. Plans must be saved under the docs/plans/YYYY-MM-DD-<feature-name>.md directory structure to maintain traceable work items.

What's the best way to structure an implementation plan for incremental delivery?▼

The best way to structure an implementation plan for incremental delivery is to align with test-driven development practices and outline frequent commits. This approach ensures clarity and coverage across all task items.