implement-task

You can automate task implementation from an approved technical plan to generate implementation.md or implementation-rN.md reports. The process enforces preconditions on workspace and task state, applying guidance from reference documents for branch management and reporting.

Plan-driven task management requires a plan.md or plan-rN.md file to initiate implementation. It updates task.md after each round and creates new implementation artifacts without overwriting previous ones, ensuring strict milestone tracking and traceability.

To generate implementation reports without automatic git commits, the workflow performs no automated git add or commit actions. It outputs implementation.md or implementation-rN.md as the primary artifact and updates task.md after each execution round.

Yes, an approved plan.md or plan-rN.md file is required to start task implementation. The skill applies only when a task has an approved plan, enforcing preconditions on the workspace and task state before generating the implementation report.

Milestone-driven implementation does not perform automatic git add or commit, requiring manual branch management. It references reference/branch-management.md to manage branches but limits automation to creating implementation artifacts and updating task.md per round.