ce:work-beta

Triage plan documents and drive developers through structured planning, testing, and review phases.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-work-beta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:work-beta
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/ce-work-beta
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-work-beta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow keeps complex engineering work from stalling in ambiguity by triaging incoming plans or prompts, breaking them into executable tasks, and driving every change through disciplined execution, testing, and review stages.

Core Features & Use Cases

  • Phased Execution: Automatically shifts from input triage through planning, setup, task tracking, task execution, and quality validation so nothing important slips through the cracks.
  • Branch and Environment Guidance: Evaluates current Git branches, recommends meaningful names or branch creation strategies, and reminds you when to use worktrees or stay on default branches with explicit permission.
  • Quality, Testing, and Delegation: Enforces task-level testing, system-wide verification, reviews, and operational validation, while optionally delegating deterministic code work to the experimental Codex channel for token-efficient implementation.

Quick Start

Run ce:work-beta with a plan document path or work description to orchestrate the phased triage, planning, execution, testing, and review workflow.

Frequently Asked Questions about ce:work-beta

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

FAQPage Schema
How do I structure engineering plans for executable task tracking?

Engineering plans are triaged and broken down into executable tasks, driving changes through structured execution, testing, and review stages to prevent complex work from stalling in ambiguity.

What's the best way to manage Git branching for complex feature shipping?

Feature shipping workflows evaluate current Git branches, recommend meaningful names, and advise on branch creation strategies, including when to use worktrees or stay on default branches.

Can I automate code implementation tasks through Codex delegation?

Deterministic code work can be optionally delegated to the experimental Codex channel, enabling token-efficient implementation while maintaining structured execution and task-level testing.

How do I enforce quality gates before shipping features?

Quality gates enforce task-level testing, system-wide verification, reviews, and operational validation, ensuring comprehensive testing is completed before any features are shipped.

Does this workflow support post-deploy monitoring guidance?

Post-deploy monitoring guidance is documented as part of the workflow, satisfying requirements for review rituals and operational validation after features are shipped.

When should I use Git worktrees for task execution?

Git worktrees are recommended during task execution when branching strategies require isolated environments, with explicit reminders on when to use worktrees versus staying on default branches.