beadmeister

Convert architecture beads into per-leg execution-ready task beads with dependencies.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/kyletabor/claude_plugins --skill beadmeister
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beadmeister
Source: https://github.com/kyletabor/claude_plugins/tree/main/gastown/skills/beadmeister
Command: npx skills add https://github.com/kyletabor/claude_plugins --skill beadmeister

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Beadmeister solves the challenge of turning architecture-level output into actionable, execution-ready task beads. It generates step-by-step instructions from implementation legs so polecats can execute tasks without further design work.

Core Features & Use Cases

  • Convert architecture beads into execution-ready beads: reads architecture beads and produces per-leg task beads with clear steps.
  • Dependency-aware task creation: sets up dependencies only for real blockers and reports results.
  • Isolated-context execution: runs as a subagent to keep the main conversation clean and focused.

Quick Start

Provide an architecture bead gt-xyz.arch and ask Beadmeister to generate the corresponding task beads.

Frequently Asked Questions about beadmeister

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

FAQPage Schema
How do I convert architecture output into executable task steps?

To turn architecture output into executable task steps, provide an architecture bead and the system generates per-leg, execution-ready task beads with complete steps and explicit dependencies for automated workflows.

What are task beads in automated software workflows?

Task beads are execution-ready, step-by-step instruction sets generated from implementation legs. They allow automated agents to execute architecture tasks without requiring further manual design work.

How do I set up dependencies for automated architecture tasks?

Dependency setup for automated architecture tasks is handled automatically during bead generation, configuring dependencies only for real blockers and reporting results to ensure correct execution order.

Can I generate task beads without cluttering my main conversation context?

Yes, you can generate task beads without cluttering the main conversation context because the process runs as an isolated subagent, keeping the primary workflow clean and focused on orchestration.

What do I need to start generating execution-ready beads from architecture?

To start generating execution-ready beads from architecture, you need an existing architecture bead file, which serves as the input to produce per-leg beads with complete steps and explicit dependencies.