workflow-kit-implement

Task execution from tasks.md is managed by loading workspace artifacts, selecting the target [Txxx] task, enforcing scope.md editing rules, and updating verification.md with check results to prevent scope creep.

A managed change workspace keeps code aligned with the spec by forcing implementation strictly against tasks.md, plan.md, and scope.md, ensuring the agent only modifies files marked as freely editable.

To implement the next eligible task, run the implement command with your change name and optional task ID, which selects the first unfinished task while honoring dependencies and required confirmations.

Yes, you can prevent AI agents from modifying forbidden files by enforcing scope.md edit boundaries, which stops the agent before touching high-risk surfaces and restricts changes to approved files.

A markdown workflow task is marked complete only when verification.md is updated with concrete check results that pass, or clearly explains why the checks cannot be run.

Yes, you need to prepare tasks.md before task execution because the agent requires loaded workspace artifacts to select the appropriate next eligible unfinished task and update verification status accordingly.