arc-implementing

To break down large software project epics into executable tasks, you can orchestrate implementation by automatically expanding epics into features and decomposing features into detailed tasks with quality gates. This ensures a disciplined engineering workflow.

Task execution orchestration manages dependencies by checking and synchronizing with base branches while handling blocking dependencies. It calls other skills for implementation and review, managing sequential task execution until the entire feature lifecycle completes.

Yes, you can automate feature to task generation for workflow automation projects. The orchestration process decomposes each feature into detailed, executable tasks and assigns them to an agent for coding, managing the entire implementation lifecycle automatically.

The best way to handle epic failure reporting and quality gates during implementation is using an orchestration workflow that manages sequential execution, enforces quality gates at the task level, and generates failure reports for epics and tasks when blocking dependencies occur.

Yes, you need to define an epic in a file like epic.md before starting project implementation orchestration. The orchestration process reads the epic definition to automatically expand it into features and execute those features through the engineering workflow.

You should not use automated task breakdown for software engineering projects when working on small, isolated changes that do not require dependency synchronization, quality gates, or multi-step feature decomposition into executable tasks and sequential execution orchestration.