planning

Convert approved specifications into structured plans, data models, and API contracts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zeeshan080/ezee-erp --skill planning-zeeshan080
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/zeeshan080/ezee-erp/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/zeeshan080/ezee-erp --skill planning-zeeshan080

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and engineering teams spend excessive time turning approved specifications into concrete implementation plans, data models, and API contracts. This Skill provides structured workflows, templates, and design patterns to streamline technical planning from proposal to execution.

Core Features & Use Cases

  • Generate implementation plans using plan-template.md
  • Derive data models and API contracts directly from user specifications
  • Produce a dependency-ordered task breakdown via /sp.tasks, grouped by user story
  • Apply templates from .specify/templates/ to ensure consistent planning outputs

Quick Start

Use the planning skill by supplying an approved specification in spec.md to trigger plan generation, data-model creation, and contract scaffolding.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I generate an implementation plan from an approved specification?

To generate an implementation plan, supply an approved specification in spec.md to trigger automated plan generation. The process produces structured outputs including plan.md, data-model.md, and contract scaffolding using predefined repository templates.

Can I derive data models and API contracts directly from a project specification?

Yes, you can derive data models and API contracts directly from a specification. The workflow converts approved specs into structured plans, generating data-model.md files and scaffolding contracts/ directories while performing constitution checks.

What is the best way to break down software architecture tasks into a dependency-ordered list?

The best way to break down architecture tasks is using automated task decomposition, which produces a dependency-ordered task breakdown grouped by user story. This guides design and execution from plan inception through implementation.

Do I need external software installation to use these planning templates and workflows?

No external software installation is required to use these planning templates and workflows. The process relies entirely on documented repository workflows and templates from .specify/templates/ to ensure consistent planning outputs.

What artifacts are generated when converting a specification into a technical plan?

Converting a specification generates plan.md, data-model.md, contracts/ directories, and research artifacts. These structured outputs ensure consistent planning and architectural design from proposal through execution.