plan-sdlc

An SDLC plan converts requirements into actionable tasks by scoping work from provided specs or conversation context. It establishes project-level boundaries and generates a plan header with metadata alongside a detailed Requirements section mapped to delta specs.

You generate an implementation plan from OpenSpec delta specs by scoping work through provided proposals and design constraints. The resulting plan aligns tasks with spec changes, mapping the detailed Requirements section directly to the delta specs for consistent execution.

Decomposing software development tasks with dependencies requires translating requirements into a structured implementation plan. This approach breaks down work into actionable tasks and explicitly maps their dependencies to ensure correct execution order.

Yes, you can scope a project-level implementation plan using conversation context. The planning process determines project-level boundaries by extracting requirements either from a provided OpenSpec document or directly from the ongoing conversation context.

No, a provided spec is not required to generate an SDLC plan. The process can scope work and determine project-level plan boundaries using either a provided OpenSpec spec or the existing conversation context as input.