worker-base

Define reusable governance patterns for worker skills with YAML frontmatter.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dylan-conlin/orch-go --skill worker-base
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker-base
Source: https://github.com/dylan-conlin/orch-go/tree/main/skills/src/shared/worker-base
Command: npx skills add https://github.com/dylan-conlin/orch-go --skill worker-base

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This is the foundation of consistent, safe, and observable worker skills. It provides a standard set of patterns for authority delegation, constitutional constraints, progress tracking, and phase signaling, so every skill can inherit reliable governance without reimplementing infrastructure.

Core Features & Use Cases

  • Authority delegation: clearly define what a worker may decide vs what must be escalated.
  • Hard limits and constitutional objection protocol: safety guards embedded in every workflow.
  • Beads progress tracking and phase reporting: uniform status updates during a task lifecycle.
  • Phase signaling and friction capture: structured communication of intent and blockers.
  • Probe-to-model merge: ensure evidence from probes feeds the central model.
  • Exit/completion protocol: clean session termination and artifact capture.
  • References and guidance for constructing new skills: ready-made patterns to follow.

Quick Start

Extend your worker skill by depending on this foundation to automatically apply governance, progress tracking, and phase reporting patterns.

Frequently Asked Questions about worker-base

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

FAQPage Schema
How do I enforce consistent governance and safety constraints across multiple worker skills?

Worker governance patterns enforce consistent safety constraints by providing reusable rules for authority delegation, constitutional objection protocols, and hard limits across all worker skills.

What is the best way to implement progress tracking and phase reporting for task orchestration?

Progress tracking and phase reporting are implemented using beads for uniform status updates and structured phase signaling, ensuring clear communication of intent and blockers throughout the task lifecycle.

How do I set up authority delegation to define what a worker can decide versus escalate?

Authority delegation is configured through a YAML frontmatter schema that explicitly defines what a worker may decide independently and what specific actions must be escalated for approval.

Can I use a single governance backbone for both simple task orchestration and complex multi-skill workflows?

Yes, this governance backbone applies across the entire lifecycle of skills and deployments, supporting use cases ranging from simple task orchestration to complex multi-skill workflows.

How does probe-to-model merge ensure evidence feeds into the central model?

Probe-to-model merge ensures evidence gathered from probes automatically feeds the central model, maintaining data integrity and preventing information loss during workflow execution.

Do I need to build my own exit and completion protocol for clean session termination?

No, an exit and completion protocol is provided for clean session termination and artifact capture, standardizing how worker skills conclude operations across the deployment lifecycle.