work

Turn plans and prompts into tracked tasks with repo-grounded execution.

1|Updated Apr 18, 2026

Search Tags:#quality-gate #workflow-automation #code-review #task-tracking #repo-truth #execute-work #plan-to-work

Ready to run

npx skills add https://github.com/mopeyjellyfish/flywheel --skill work-mopeyjellyfish

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

## What problem does it solve? Coordinates the execution of planned work within a repository, turning plans, specs, and requests into tracked tasks that drive concrete changes with validation and governance.

## Core Features & Use Cases

Translates plan or bare prompts into actionable work units aligned with project goals.
Grounded repo truth validation, guided task execution, and gated handoffs to review and commit.
Supports host tooling integration, task tracking surfaces, and observability hooks as needed by the plan.

Quick Start

Start executing the first work unit from the current plan and follow the guided execution loop to completion.

Frequently Asked Questions about work

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

FAQPage Schema

How do I automate turning project plans into tracked repository tasks?▼

Plan-driven execution automation translates plans and bare prompts into actionable work units aligned with project goals, grounding actions in repo truth and validating changes through gated transitions before commit.

What is a quality gate in workflow automation for code review?▼

A quality gate in workflow automation enforces discipline around test posture, patterns, and documentation by validating repo-grounded execution signals before allowing gated transitions to code review and commit.

How do I execute plan-to-work cycles with repo truth validation?▼

Plan-to-work cycles execute by starting the first work unit from a current plan and following a guided execution loop that validates actions against repository truth, ensuring end-to-end work from plan to commit.

Can I use task tracking surfaces with host tooling integration for planned work?▼

Task tracking surfaces support host tooling integration and observability hooks as needed by the plan, coordinating the execution of planned work within a repository through guided task execution.

What is the best way to manage planning-to-implementation cycles with gated handoffs?▼

The best way to manage planning-to-implementation cycles is using guided task execution with gated handoffs, ensuring work units transition to review and commit only after passing defined governance signal validation.

When do I need gated transitions for task tracking in software engineering?▼

Gated transitions for task tracking are needed when executing end-to-end work from plan to commit, ensuring discipline around test posture and documentation by grounding actions in defined governance signals and repo truth.