skills.rest
fkberthold
fkbertholdCOMMUNITY
Explore all skills by this author →
GitHub

bugfix-a-bead

Coordinate M1 through M6 stages for bug-shaped bead fixes.

Updated May 3, 2026
Search Tags:#workflow#tdd#beads#bugfix#red-green#bead-lifecycle#dispatch-middle
One-click install
npx skills add https://github.com/fkberthold/loom --skill bugfix-a-bead
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix-a-bead
Source: https://github.com/fkberthold/loom/tree/main/skills/bugfix-a-bead
Command: npx skills add https://github.com/fkberthold/loom --skill bugfix-a-bead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides the structured middle for bug-shaped bead fixes, pairing RED-test creation with GREEN implementation while delegating lifecycle orchestration to bead-lifecycle-shell.

Core Features & Use Cases

  • Establishes a disciplined bug-fix workflow that separates test authoring (RED) from implementation (GREEN) and tracks bug-class coverage and enshrined-test sweeps.
  • Coordinates the M1–M6 variable-middle stages and integrates with the bead-lifecycle-shell to handle claim, isolate, verify, close, and capture.
  • Typical use cases include starting a bug bead after session startup or via the /working-a-bead router, then executing the end-to-end bug-fix sequence.

Quick Start

Start a bug-shaped bead session and run bugfix-a-bead to coordinate RED test then GREEN fix.

Frequently Asked Questions about bugfix-a-bead

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

FAQPage Schema
How do I structure a bug fix workflow using TDD red-green phases?▼

bugfix-a-bead structures bug-shaped bead fixes by pairing RED-test creation with GREEN implementation across M1–M6 variable-middle stages. It coordinates diagnosis, testing, and fix implementation while delegating lifecycle orchestration to bead-lifecycle-shell.

What is the bead-lifecycle-shell coordination process for bug fixes?▼

Bead-lifecycle-shell coordination handles claim, isolate, verify, close, and capture phases for bug-shaped beads. The bugfix workflow delegates lifecycle orchestration to this shell while enforcing the variable middle stages M1 through M6.

How do I start a bug bead session after claiming a bug?▼

Start a bug-shaped bead session after claim or via the /working-a-bead router, then execute the end-to-end bug-fix sequence. The workflow coordinates diagnosis, testing, and implementation across variable middle stages M1 through M6.

Does the bugfix bead workflow separate test authoring from implementation?▼

Yes, the workflow pairs RED-test creation with GREEN implementation, enforcing separation between test authoring and fix implementation. It tracks bug-class coverage and enshrined-test sweeps while coordinating M1–M6 variable-middle stages.

What are the M1 through M6 variable middle stages in a bug fix workflow?▼

M1 through M6 are variable-middle stages enforced during bug-shaped bead fixes, structuring diagnosis, testing, and implementation. They integrate with bead-lifecycle-shell coordination for claim, isolate, verify, close, and capture operations.

Related Skills

Explore More Software Engineering Skills→
fkbertholdfkberthold

refactor-a-bead

Coordinate a refactor-shaped bead through the M1–M4 stage workflow.

Community
Intermediate
fkbertholdfkberthold

research-a-bead

Orchestrate research beads into decision drawers and KG triples.

Community
Advanced
fkbertholdfkberthold

bead-lifecycle-shell

Coordinate bead lifecycles from claim to merge across activity recipes.

Community
Advanced
fkbertholdfkberthold

feature-a-bead

Coordinate feature-bead work with contract-driven variable middle and lifecycle scaffolding.

Community
Advanced