mission-planning

Planning a software development mission requires a structured process covering requirements gathering, codebase investigation, milestone definition, and artifact generation to ensure comprehensive pre-development preparation. This skill guides you through each step to establish scope and acceptance criteria.

Feature decomposition breaks down large features into manageable tasks during project kickoff. It fits into the planning phase after requirements gathering and milestone definition, ensuring development tasks are properly scoped with clear validation contracts before coding starts.

Validation contracts are created by defining clear acceptance criteria and feature specifications during the mission planning process. This skill facilitates the creation of these contracts to ensure comprehensive pre-development validation frameworks are established.

Milestones need to be defined during the pre-development planning phase, after requirements gathering and codebase investigation. This skill helps you systematically establish milestones to break down tasks and create clear validation boundaries for new or re-planned missions.

Re-planning an existing software development mission follows the same structured process as new missions. This skill guides you through requirements gathering, codebase investigation, and milestone definition to comprehensively re-establish scope and validation contracts for ongoing projects.

Requirements gathering should be structured as a step-by-step process that captures scope, investigates the existing codebase, and defines validation contracts. This skill streamlines this kickoff phase to ensure all critical aspects are covered before development begins.