development_planning

Translate system architecture into a concrete development plan with WBS and task files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ukrsite/kiro-workflows --skill development-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development_planning
Source: https://github.com/ukrsite/kiro-workflows/tree/main/skills/sdlc/developer_planning
Command: npx skills add https://github.com/ukrsite/kiro-workflows --skill development-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires architecture_design, and includes references (resource) components.

What problem does it solve?

Transforms architecture into an actionable development plan, turning high-level design into concrete work packages.

Core Features & Use Cases

  • Work Breakdown Structure generation from architecture
  • Flat task file creation with role squads
  • Resource planning and risk management
  • Quality planning and Sprint 0 setup

Quick Start

Create an actionable development plan from the approved architecture and generate WBS, flat task files, resource plan, risk register, QA plan, and Sprint 0 setup.

Frequently Asked Questions about development_planning

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

FAQPage Schema
How do I create an actionable development plan from system architecture?

To create an actionable development plan from system architecture, you generate a Work Breakdown Structure (WBS), flat task files, resource plans, and a risk register to transform high-level design into executable work packages.

What is included in Sprint 0 setup for early-stage SDLC planning?

Sprint 0 setup for early-stage SDLC planning includes generating a Work Breakdown Structure, resource plan, risk register, QA plan, CI/CD design, and governance artifacts to establish cross-functional team coordination.

Does this development planning process generate source code or only project artifacts?

The development planning process generates project artifacts only, strictly enforcing non-code generation to focus on producing WBS, task files, risk management, and quality planning deliverables.

Can I generate a Work Breakdown Structure and resource plan without an existing architecture?

Generating a Work Breakdown Structure and resource plan requires an approved architecture design as a prerequisite dependency, ensuring the resulting development plan accurately translates established system design into concrete tasks.

What is the best way to coordinate cross-functional teams during early-stage software planning?

The best way to coordinate cross-functional teams during early-stage software planning is by producing a comprehensive WBS, flat task files with role squads, and governance artifacts to align resource and risk management.