kwork

Execute repository implementation plans with code changes, tests, and reviews.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/kkestell/skills --skill kwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kwork
Source: https://github.com/kkestell/skills/tree/main/plugins/k/skills/kwork
Command: npx skills add https://github.com/kkestell/skills --skill kwork

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It automates the full lifecycle of implementing a repository plan—handling pre‑flight checks, task‑by‑task code changes, testing, dual review passes, and a final clean commit—so developers no longer need to manually coordinate each step.

Core Features & Use Cases

  • Pre‑flight validation: Ensures a clean Git state and baseline test success before any changes.
  • Task‑driven execution: Reads a plan file, creates a todo list, and implements each task with appropriate tests and comments.
  • Automated reviews: Runs completeness and test‑quality review prompts (via assets) to catch omissions and weak tests.
  • Single‑commit delivery: After passing all checks, commits the entire work in one well‑structured commit.

Quick Start

Invoke kwork with the path to your plan file to automatically implement, review, and commit the changes.

Frequently Asked Questions about kwork

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commit, testing, and code review for a repository implementation plan?

You can automate plan execution by using a tool that reads your implementation plan, applies code changes task by task, runs tests, executes dual review passes, and commits the final code in a single commit.

What is automated task-driven plan execution in software engineering?

Automated plan execution is the process of reading a specification file, generating a todo list, and implementing code changes task by task while running tests, linters, and review prompts before committing.

Do I need a clean git repository before running automated plan execution?

Yes, automated plan execution requires a clean git repository and baseline test success. Pre-flight validation checks your git state and runs tests before applying any new code changes.

How does automated dual code review work during plan execution?

Automated dual review runs completeness and test-quality review prompts after code changes are applied, catching omissions and weak tests before the final commit to ensure implementation quality.

Can I use this automated plan execution with specifications generated by other planning tools?

Yes, it applies to plans generated by kplan or similar specifications, handling code changes, tests, and reviews as long as the plan file format is compatible.

What happens if my baseline tests fail before automated plan execution starts?

If baseline tests fail during pre-flight validation, the execution stops before any changes are made, ensuring you start from a stable state with a clean git repository.