dev-docs-execute

Documentation execution in continuous delivery workflows is automated by coordinating specific phases, running Implementation Units, and checking system-wide tests to reduce manual effort. This ensures stability and correctness before finalizing each phase.

Running implementation units for a software workflow phase is best handled by an automated coordinator that executes each unit, manages error handling, and provides status updates throughout the process. System-wide tests are checked before completion.

Yes, documentation automation runs system-wide tests before finalizing a phase to ensure all checks are passed for stability and correctness. This validation step prevents errors from progressing through the continuous delivery pipeline.

To execute a specific phase for a documentation task, you run the skill with the task path and phase number as parameters, such as specifying 'docs/active/auth-refaktor' and 'phase=1' to initiate the workflow execution.

Yes, dev-workflow is required as a dependency to automate implementation unit execution. The skill relies on dev-workflow, autopilot-agent, and code-review-agent to coordinate phases and validate system-wide tests.

Continuous delivery documentation execution fails system-wide tests when implementation units encounter errors or dependencies are missing. The automation coordinates error handling and status updates to identify the specific failing check before finalizing the phase.