work

Execute development plans into tasks, code changes, tests, and commits.

1|Updated Mar 5, 2026

Search Tags:#testing #commit #branching #plan #todo #task-management #execute

Ready to run

npx skills add https://github.com/beratcelik1/compound-claude --skill work-beratcelik1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work
Source: https://github.com/beratcelik1/compound-claude/tree/main/skills/work
Command: npx skills add https://github.com/beratcelik1/compound-claude --skill work-beratcelik1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns written development plans into a repeatable, enforced workflow so work is implemented, tested, and shipped instead of languishing as unchecked notes.

Core Features & Use Cases

Breaks a plan into actionable tasks and maintains progress by marking items in progress and completed.
Manages branch state and feature branch creation, encourages incremental commits, and prepares conventional commit messages and PRs.
Enforces quality by requiring tests, running linters, and verifying all plan checkboxes before shipping; useful for feature development, bug fixes, and task-driven sprints.

Quick Start

Use the work skill to execute the specified plan file and follow tasks until tests pass, changes are committed, and the plan checkboxes are complete.

Frequently Asked Questions about work

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

FAQPage Schema

How do I execute a development plan step-by-step and track task progress?▼

To execute a development plan step-by-step, the Skill breaks plan files into actionable tasks and tracks progress by marking items as in progress or completed. It maintains task state by updating plan checkboxes as each code change is implemented.

How do I manage feature branches and prepare conventional commits during feature development?▼

Managing feature branches and preparing conventional commits is handled by validating the current branch state, creating a feature branch, and generating commit messages and PRs. This enforces incremental commits alongside completed task items.

Can I enforce testing and linting before shipping code changes from a task-driven workflow?▼

Yes, you can enforce testing and linting before shipping code changes. The Skill requires tests to pass and runs linters to verify quality, ensuring all plan checkboxes are checked before preparing commits and PRs for feature development or bug fixes.

What's the best way to turn written development plans into a repeatable workflow for bug fixes?▼

The best way to turn written development plans into a repeatable workflow for bug fixes is to follow a plan file step-by-step. The Skill validates branch state, creates a feature branch, runs tests, and updates plan checkboxes until the task-driven sprint is complete.

Do I need a plan file to use this task-management workflow for shipping features?▼

You need a plan file or a recent plan to use this task-management workflow for shipping features. The Skill executes the specified plan file by breaking it into tasks, running tests and linters, and preparing commits and PRs until all checkboxes are complete.

Why does plan execution stop before shipping if tests fail or checkboxes remain unchecked?▼

Plan execution stops before shipping if tests fail or checkboxes remain unchecked because the workflow enforces quality by requiring tests and linters to pass. It verifies all plan checkboxes are completed before preparing commits and PRs to ensure reliable feature delivery.