worker

Plans a vertical slice from CLI entry to service wiring using Layer Cake and Beads.

2|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/dayvidpham/aura-plugins --skill worker-dayvidpham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/dayvidpham/aura-plugins/tree/main/skills/worker
Command: npx skills add https://github.com/dayvidpham/aura-plugins --skill worker-dayvidpham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define and own a complete vertical slice that delivers a full production code path from the CLI entry point to the service, ensuring the end-to-end workflow is maintainable and observable.

Core Features & Use Cases

  • Owns a full vertical slice (types, tests, service, and wiring) for a production-ready feature.
  • Guides end-to-end development using the Layer Cake approach and Beads workflow to coordinate tasks.
  • Enables safe, testable delivery with real dependencies wired and minimal scaffolding.

Quick Start

Begin by defining your slice, then implement the full production code path (types, tests, service, and wiring) end-to-end.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I implement a complete vertical slice from CLI entry to service wiring?

To implement a vertical slice, define your production code path, then coordinate types, tests, service logic, and wiring end-to-end using the Layer Cake approach and Beads workflow to ensure full production readiness.

What is the Layer Cake approach for end-to-end production code paths?

The Layer Cake approach is a workflow method that coordinates types, tests, implementation, and CLI wiring within a single vertical slice to deliver maintainable and observable production code paths.

How do I validate production readiness when wiring real dependencies?

You validate production readiness by wiring real dependencies, ensuring your tests import production code directly, and removing all TODOs from the implemented slice.

When do I need to use a Beads workflow for vertical slice development?

You need a Beads workflow when you must coordinate tasks across a full vertical slice, ensuring safe and testable delivery with real dependencies wired and minimal scaffolding.

Can I deliver a testable feature slice without heavy scaffolding?

Yes, you can deliver testable features with minimal scaffolding by coordinating the slice end-to-end and wiring real dependencies, ensuring tests import production code directly.

What's the best way to own end-to-end production code paths for a new feature?

The best way to own end-to-end paths is to plan a complete vertical slice, coordinating types, tests, service implementation, and wiring together to validate production readiness and remove TODOs.