workflow-execute

Run /workflow-execute with the task name and commit number, such as /workflow-execute REFACTORING 1. It reads the checklist for that commit in docs/work/{task-name}/plan.md, implements the items, runs tests, and writes a summary document.

Pass only the commit number, for example /workflow-execute 1. The command searches docs/work/*/ for the most recently modified plan.md and uses it. If none exists, it errors and asks for the task name.

Execution stops with an error telling you to run /workflow-plan first for that task. The plan file is a required prerequisite because it contains the checklist and test requirements for each commit.

Yes. It follows the Test Requirement declared in plan.md: TDD writes a failing test first then implements, TEST-AFTER implements then writes tests, and NO-TEST skips tests. Tests and implementation must land in the same atomic commit.

All generated summary-commit-N.md documents must be written in Korean. This is a strict rule in the skill, covering achievement goals, changed files, verification results, and follow-up tasks.

Yes. If summary-commit-N.md already exists, the skill treats it as a revision cycle, reads the existing file for context, and overwrites it so only the final state is kept.