writing-plans

Convert approved requirements into implementation plans with tasks and verification steps.

2|Updated May 5, 2026
One-click install
npx skills add https://github.com/OrestesK/pi --skill writing-plans-orestesk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/OrestesK/pi/tree/main/skills/writing-plans
Command: npx skills add https://github.com/OrestesK/pi --skill writing-plans-orestesk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns approved requirements and designs into precise implementation plans, preventing hidden assumptions, unclear ownership, and incomplete verification steps.

Core Features & Use Cases

  • Structured Task Breakdown: Decomposes work into small, executable tasks with likely implementation owners and affected locations.
  • Behavioral Proof Strategy: Selects appropriate tests, reproductions, checks, or live verification to prove each material behavior.
  • Safe Planning Boundaries: Records assumptions, uncertainties, risks, non-goals, review checkpoints, and stop conditions without modifying source code or prescribing mutating Git operations.
  • Use Case: When a feature design is approved, use this Skill to produce a durable plan in the project’s scratch planning area that another developer can execute without making implicit design decisions.

Quick Start

Use the writing-plans skill to create an implementation plan for the approved feature requirements, including tasks, verification commands, risks, and review checkpoints.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn approved software requirements into an implementation plan with task breakdowns?

Implementation planning converts approved requirements into durable task breakdowns by defining executable steps, affected code locations, implementation owners, and behavioral verification checks without modifying source files.

What is behavioral verification in software implementation planning?

Behavioral verification in implementation planning selects appropriate tests, reproductions, and project checks to prove each material behavior defined in the task breakdown, ensuring durable and verifiable execution.

How do I document assumptions and stop conditions during codebase analysis for a feature plan?

Codebase analysis for feature planning records explicit assumptions, uncertainties, non-goals, and stop conditions in the project's scratch planning area to establish safe boundaries without prescribing mutating Git operations.

Can I use implementation planning to generate review checkpoints for another developer to execute?

Implementation planning generates review handoffs by creating durable plans with explicit review checkpoints, allowing another developer to execute tasks without making implicit design decisions or modifying source code during planning.

What do I need to prepare before creating an implementation plan from a feature design?

Before creating an implementation plan, you need documented constraints, affected code locations, discoverable project checks, and explicit assumptions to ensure the feature design is fully approved and ready for durable task breakdown.