start-planning

Discover existing specs and invoke the technical-planning skill.

27|1|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/leeovery/claude-technical-workflows --skill start-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-planning
Source: https://github.com/leeovery/claude-technical-workflows/tree/main/skills/start-planning
Command: npx skills add https://github.com/leeovery/claude-technical-workflows --skill start-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill initiates the planning phase from an existing specification by discovering available specs, gathering context, and invoking the technical-planning skill.

Core Features & Use Cases

  • Discover and surface the scope of an existing specification to prepare planning inputs.
  • Gather contextual details from the specification to inform task breakdown, acceptance criteria, and timelines.
  • Route to the technical-planning skill to generate a concrete plan from the prepared context.

Quick Start

Run the planning workflow from an existing specification to begin the planning phase and hand off to technical planning.

Frequently Asked Questions about start-planning

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

FAQPage Schema
How do I start planning a software feature from an existing specification?

To start planning a software feature from an existing specification, you discover available specs, gather contextual details for task breakdown, and invoke technical planning to generate a concrete plan.

What is the workflow for converting a specification into a technical plan?

The workflow for converting a specification into a technical plan involves surfacing the spec scope, extracting contextual details to inform timelines and acceptance criteria, and routing to a technical planning skill.

Can I use this planning workflow if my specification is not yet concluded?

No, this planning workflow applies only when a concluded specification exists and a planning workflow needs to be created or continued from that finalized document.

How does gathering context from a specification improve software planning?

Gathering context from a specification improves software planning by extracting details that directly inform task breakdown, establish acceptance criteria, and define accurate project timelines.

What is the best way to hand off context to technical planning?

The best way to hand off context to technical planning is to discover available specs, prepare the gathered contextual inputs, and invoke the technical planning skill to generate the plan.

Do I need any specific tools to initiate the planning phase from a spec?

To initiate the planning phase from a spec, you require access to specifications, a discovery tool to surface available specs, and the ability to invoke the technical planning skill.