Epic Sprints

Sprint breakdown is automated by parsing a `plan.md` file to generate sprint plans, analyze dependencies, and define execution layers. This process ensures efficient execution and dependency management for complex workflows by maximizing parallelization.

API contract locking is achieved by generating OpenAPI schemas to define strict boundaries for parallel work. This mechanism ensures that different sprint teams can execute tasks concurrently without causing integration conflicts during the complex workflow.

Yes, XML parsing is required because the Skill generates a `tasks.xml` file containing all tasks, dependencies, and sprint assignments. This format structures the dependency graph and execution layers needed for optimal sprint planning.

The best way to manage dependencies is by building a dependency graph between sprints to optimize execution layers. This approach maximizes parallelization while strictly respecting task dependencies, ensuring seamless integration across large-scale projects.

Yes, you can track the progress of sprints and layers through automated state updates. This feature monitors the advancement of parallel execution layers within the project management workflow, ensuring complex tasks stay aligned.

This approach is ideal for large-scale projects with multiple dependent tasks and sprints. Small projects without complex dependencies may not benefit from the overhead of dependency graph building and execution layer optimization.