miko.split_proposal

Splitting large software development proposals into manageable phases requires automating the breakdown of complex documents into multiple sub-proposals. This Skill structures proposals based on specified phases and cross-capability business rules, ensuring organized project management for large-scale workflows.

You need to split a project proposal into sub-proposals when managing large-scale software development workflows that require structured proposal management. It is essential when breaking down complex features into smaller, testable, and deployable components across multiple capabilities or domains.

Automating proposal splitting for cross-capability coordination involves using a script that processes a specified proposal path. The automation identifies sub-proposals using proposal markers, aligning business rules across different domains and phases without manual organization.

Proposal splitting works with existing markdown structures but requires a clear proposal structure and proper use of proposal markers for sub-proposal identification. Without these specified markers, the automation cannot accurately identify and separate the phases and sub-proposals.

The limitation of automated proposal splitting for codebase organization is its strict dependency on a clear proposal structure and proper proposal markers. If the input proposal lacks these specified markers or structural clarity, the automated splitting process cannot accurately identify the sub-proposals.