execution-skill

To execute ready tasks without breaking dependency safety, you need a mechanism that verifies dependency state before starting work. This Skill checks dependency state and only starts tasks when prerequisites are resolved, keeping implementation work visible and bounded.

Handling blockers during task execution requires surfacing them with explicit ownership and check-back timing. This Skill records progress updates and flags blockers with assigned ownership, allowing the agent to stop cleanly when blocked and ensuring accountability.

Keeping project progress updates visible during active delivery requires logging status changes and execution evidence. This Skill moves tasks into progress, records updates in the project update log, and produces delivery artifacts like notes or commits to maintain visibility.

Yes, you can automate task status changes from planning into implementation by applying controlled handoff logic. This Skill requires task identifiers and dependency state to transition tasks into active delivery while maintaining stream boundaries and required update logging.

To show execution progress, you need delivery artifacts such as notes, commits, or PR-related outputs. This Skill produces these artifacts during task execution to provide concrete evidence of implementation work and maintain a visible record of delivery.

You should not use an automated task execution approach when tasks lack defined identifiers or when dependency state is unclear. This Skill requires explicit task identifiers and dependency verification to ensure safe execution, meaning unstructured work without bounded context is not suitable.