skills.rest
stencila
stencilaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

software-plan-creation

Create phased delivery plans with TDD slices from software design specifications.

902|58|Updated May 31, 2012
Search Tags:#TDD#task breakdown#implementation plan#test plan#software planning#delivery plan#phased delivery
One-click install
npx skills add https://github.com/stencila/stencila --skill software-plan-creation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-plan-creation
Source: https://github.com/stencila/stencila/tree/main/.stencila/skills/software-plan-creation
Command: npx skills add https://github.com/stencila/stencila --skill software-plan-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a software design specification into an actionable implementation roadmap is time-consuming and error-prone. This Skill reads a design spec and produces a structured delivery plan with phases, tasks, testing strategy, and risks, so teams can start building with a clear path.

Core Features & Use Cases

  • Phased Delivery Planning: Breaks a design spec into ordered phases, each with scope, tasks, testing approach, and exit criteria.
  • TDD Slice Sizing: Structures red-green-refactor slices around meaningful behaviors, avoiding both micro-slices and overly broad batches.
  • Risk and Prerequisite Tracking: Surfaces open questions and assumptions from the design as risks, prerequisites, and a definition of done.
  • Use Case: After writing a design spec for a user authentication flow, ask for a delivery plan and receive a Markdown plan in .stencila/plans/ with phased tasks, TDD slices, and documentation requirements.

Quick Start

Create a delivery plan for the latest design spec using a test-driven development approach.

Frequently Asked Questions about software-plan-creation

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

FAQPage Schema
How do I create an implementation plan from a design spec?▼

Place your design spec in .stencila/designs/ and ask for a delivery plan. The Skill reads the latest design by default, breaks the work into phases with tasks and exit criteria, and writes the plan to .stencila/plans/ as a Markdown file.

How to plan a project using test-driven development?▼

Request a plan with TDD and the Skill structures work into red-green-refactor slices per phase. Each slice covers one meaningful behavior or acceptance-criterion-sized increment, avoiding trivial micro-slices and overly broad batches.

What happens if no design spec exists for my feature?▼

The Skill does not refuse. It explains that plans work best from a design spec, suggests creating a design first, or produces a lightweight preliminary plan with explicit assumptions and caveats about missing design decisions.

Does the plan overwrite an existing plan for the same design?▼

No. The Skill checks .stencila/plans/ for existing plans and asks whether to replace, update, or create a new plan alongside it. Updates prefer edit_file or apply_patch over full rewrites.

When is TDD not appropriate in a delivery plan?▼

TDD is less suitable for exploratory work, heavy UI prototyping, or features depending on hard-to-mock external systems. In those cases the Skill proposes alternatives such as integration tests, manual verification, or end-to-end tests.

Related Skills

Explore More Software Engineering Skills→
ddobrinddobrin
8

spec-validator

Identify ambiguity, missing requirements, contradictions, and untestable criteria in software specifications.

Community
Advanced
humansyshumansys
71

rai-story-implement

Execute story plan tasks with TDD cycles and verification gates.

Official
Advanced
KjellKodKjellKod
36

plan-reviewer

Automate evaluation of implementation plans and PR specs for testable acceptance criteria.

Community
Intermediate
cipriantitirecipriantitire

sprint-planner

Plan agile sprints with story estimation and capacity planning.

Community
Intermediate