planning

Translate requirements specs into executable plans with tasks, dependencies, and milestones.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/OTSOU-CODE/OTSOU --skill planning-otsou-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/OTSOU-CODE/OTSOU/tree/main/.agent/skills/planning
Command: npx skills add https://github.com/OTSOU-CODE/OTSOU --skill planning-otsou-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates a requirements spec into a concrete, executable plan that guides engineers and teams from concept to delivery, reducing ambiguity and rework.

Core Features & Use Cases

  • Comprehensive planning: Generate step-by-step tasks, dependencies, and milestones from a spec.
  • Executive guidance: Document files to touch, tests to write, and review notes to ensure alignment.
  • Use Case: Given a feature request, produce an implementation plan that a skilled dev can follow end-to-end.

Quick Start

Use the planning skill to convert a product requirement into a detailed implementation plan, saved to the project's docs.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I turn feature requirements into an implementation plan?

To turn feature requirements into an implementation plan, provide a requirements spec to generate concrete, executable step-by-step tasks, dependencies, and milestones. This translation process reduces ambiguity and guides development from concept to delivery.

What is the best way to break down a product spec for developers?

Breaking down a product spec involves encoding planning workflows to document files to touch, tests to write, and review notes. This approach ensures a skilled developer can follow the generated implementation plan end-to-end.

Can I generate a project plan with task dependencies and milestones?

Yes, you can generate a project plan with task dependencies and milestones from a requirements spec. The output structure encodes task granularity, testing, and commit guidelines into a reusable, executable plan for engineering contexts.

Does this planning approach work without external dependencies?

Yes, this planning approach works without external dependencies, operating independently to translate requirements into a detailed plan. It encodes task granularity, testing, and commit guidelines directly into a reusable plan structure.

When do I need to translate a spec into a multi-step plan?

You need to translate a spec into a multi-step plan when product development requires clear, step-by-step tasks before coding begins. It is designed for engineering contexts that require executable tasks, dependencies, and milestones to reduce rework.