feature-a-bead

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

Updated May 3, 2026
One-click install
npx skills add https://github.com/fkberthold/loom --skill feature-a-bead
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-a-bead
Source: https://github.com/fkberthold/loom/tree/main/skills/feature-a-bead
Command: npx skills add https://github.com/fkberthold/loom --skill feature-a-bead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Activity recipe for working a feature-shaped beads issue. Owns the feature-specific middle of the bead lifecycle. The shared lifecycle scaffolding — MemPalace search, claim + worktree, verification, commit, finish-branch, close + capture — lives in the bead-lifecycle-shell skill. This recipe cites those phases by letter and supplies the variable middle that runs between phase A (pre-middle) and phase B (verification).

Core Features & Use Cases

  • Defines the feature-specific middle and coordinates with bead-lifecycle-shell for claim, verify, and close, enabling contract-driven progress across feature beads.
  • Supports both single-bead work and multi-bead plans by guiding design, RED/GREEN verification, planning, and integration within a consistent lifecycle.
  • Enforces phase boundaries (designing, planning, red, green, integration) and records stage markers for cold-start continuity.

Quick Start

Start the feature-bead workflow by claiming a feature bead and running the variable middle process through the bead-lifecycle-shell pipeline, which will guide you through design, red-test, green-implementation, and final verification.

Frequently Asked Questions about feature-a-bead

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

FAQPage Schema
How do I coordinate contract testing across multiple feature lifecycle stages?

Contract testing across feature lifecycle stages is coordinated by defining an explicit contract middle that governs design, RED/GREEN verification, and integration before dispatching work.

What is the best way to structure RED and GREEN commits for contract-driven feature work?

Structuring RED and GREEN commits for contract-driven work requires using a dispatch-middle pipeline to produce auditable commits that trace the feature's lifecycle through explicit stage markers.

How does contract-driven development work with single and multi-bead feature tasks?

Contract-driven development for single and multi-bead tasks works by applying explicit contracts authored before dispatch, guiding design, planning, and integration within a consistent lifecycle.

Do I need to author explicit contracts before dispatching feature work?

Authoring explicit contracts before dispatching feature work is required, as the workflow relies on contract-driven variables to govern lifecycle scaffolding and produce traceable verification commits.

Can I use bead-lifecycle-shell scaffolding for feature-focused work?

Bead-lifecycle-shell scaffolding supports feature-focused work by handling claim, verify, and close phases while the feature recipe supplies the variable middle running between pre-middle and verification.

Why does feature bead work require explicit phase boundaries for design and integration?

Feature bead work requires explicit phase boundaries to enforce separation between designing, planning, RED, GREEN, and integration, recording stage markers that enable cold-start continuity.