quick-work

To execute a quick plan, provide a plan from chat or a TASK-*.md backlog file. The skill runs each step in order, verifies acceptance criteria, and ends by offering a commit or commit-and-push option.

Deterministic diffs maintain plan fidelity by generating code changes that map exactly to the steps defined in your quick plan, ensuring the execution does not deviate or re-plan from the original task scope.

Yes, you can use backlog TASK-*.md files to run focused coding sessions. The skill reads the saved task file, executes the specified steps sequentially, and verifies acceptance criteria before offering a final commit choice.

The best way to verify acceptance criteria during plan execution is to run a focused session that applies deterministic diffs. This enforces plan fidelity by checking the code changes against the criteria before offering to commit.

To commit code changes after executing a task plan, use the end-of-session commit flow. Once steps are complete and acceptance criteria are verified, the skill prompts you to choose option A to commit or option B to commit and push.