work

Execute planned steps sequentially with integrated safety gates for failure halts.

28|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/AndrewDryga/coop --skill work-andrewdryga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/AndrewDryga/coop/tree/main/internal/scaffold/templates/skills/work
Command: npx skills add https://github.com/AndrewDryga/coop --skill work-andrewdryga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps maintain focus and control during implementation, ensuring every step of a plan is executed safely, with clear gates and no scope creep.

Core Features & Use Cases

  • Step-by-Step Execution: Follows each step of a plan meticulously, without deviation.
  • Safety Gates: Integrates with repository gates to stop at any failure.
  • Use Case: Ideal for implementing complex changes, like updating a critical function, where maintaining control and verifying at each stage is crucial.

Quick Start

Use the work skill to implement the following plan: work "Add new feature X" --plan "spec, develop, test, deploy".

Frequently Asked Questions about work

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

FAQPage Schema
How do I execute implementation plans step-by-step without scope creep?

To execute implementation plans step-by-step without scope creep, you need a structured execution process with safety gates. This ensures every step is followed meticulously, halting progress immediately upon any failure to require intervention or re-planning.

What are safety gates in change management and how do they work?

Safety gates in change management are checkpoints that halt progress upon failure. They integrate with repository-specific gates to ensure step-by-step implementation stops immediately when a validation fails, requiring explicit intervention or re-planning before proceeding.

How do I safely implement complex code changes while maintaining control?

Safely implementing complex code changes requires following a plan meticulously with clear gates. This maintains control by verifying progress at each stage and halting execution automatically at any failure, preventing uncontrolled modifications to critical functions.

Can I use repository gates to stop plan execution when tests fail?

Yes, you can use repository gates to stop plan execution when tests fail. The execution process integrates directly with repository-specific gates to ensure progress is halted at any failure, requiring intervention or re-planning before moving forward.

What is the best way to manage feature implementation across multiple stages?

The best way to manage feature implementation across multiple stages is step-by-step execution with clear safety gates. This approach applies to code changes and system updates, ensuring progress is verified at each stage and halted upon any failure.

Why does plan execution halt and require intervention during system updates?

Plan execution halts and requires intervention during system updates because safety gates detect failures. This mechanism stops progress at any failure point to prevent scope creep and ensure every step is executed safely before proceeding.