Software Plan Creation

Overview

Produce a delivery plan that turns a software design specification into an actionable sequence of implementation, testing, and documentation work. The primary input is a persisted design spec read from .stencila/designs/. The primary output is a Markdown plan written to .stencila/plans/.

Use this skill when the user wants a delivery plan, implementation plan, task breakdown, phased roadmap, or test-driven development strategy for a design spec. Do not use it when the main task is to write production code, create a design from scratch, review code, or build a workflow.

Steps

1. Identify the design to plan against:

   • use glob with pattern .stencila/designs/*.md to discover available design specs (results are sorted newest first)
   • if the user names a specific design, locate it in the results
   • if the user does not name a design, use the first result (most recent)
   • use read_file to load the full design content
   • if no designs exist and the user is asking to plan an undesigned feature, handle the no-design case (see Edge Cases below)

2. Check for existing plans:

   • use glob with pattern .stencila/plans/*.md to see whether a plan already exists for the target design
   • if a matching plan exists, use read_file to load it and ask the user whether to replace it, update it, or create a new plan alongside it
   • do not silently overwrite an existing plan