Coordinate bead lifecycles from claim to merge across activity recipes.
npx skills add https://github.com/fkberthold/loom --skill bead-lifecycle-shell
Please help me install this Agent Skill. Skill: bead-lifecycle-shell Source: https://github.com/fkberthold/loom/tree/main/skills/bead-lifecycle-shell Command: npx skills add https://github.com/fkberthold/loom --skill bead-lifecycle-shell
Bead work across multiple activity recipes often suffers from fragmented lifecycle handling. This skill centralizes the cross-activity phases (search, claim, isolate, verify, commit, close, and memory capture) and coordinates the MemPalace drawers, KG triples, and diary entries, ensuring a consistent flow from start to finish.
Trigger bead-lifecycle-shell via an activity recipe reference and follow its phases from MemPalace search (A1) through to diary wrap-up (D3).
High-intent search queries and answers about installing and using this skill.
Coordinate development branch lifecycles from claim to merge by applying a dispatch-middle architecture with per-phase ownership. This centralizes cross-activity phases like search, isolate, verify, and commit to ensure consistent stage management across parallel work.
A dispatch-middle architecture for workflow automation runs the variable middle processing in isolated workers while the central handle manages conversation and integration. This enables safe parallel work and reliable integration across distinct activity recipes.
Manage memory capture across multiple development activities by centralizing stage transitions into MemPalace drawers, KG triples, and diary entries. This ensures phase-accurate artifact capture and consistent flow from start to finish.
Yes, you can run parallel work safely during bugfix or feature workflows. The system uses crash-resilient drawers and mandatory workflow-state updates to enable safe parallel work and reliable integration across isolated workers.
Unify bugfix and feature workflows by applying cross-activity lifecycle scaffolding. This coordinates phases like search, claim, isolate, verify, commit, and close across activity recipes to ensure consistent stage management and memory capture.
Manual bead lifecycle handling suffers from fragmented lifecycle tracking across multiple activity recipes. Without centralized phase coordination, crash-resilient drawers, and mandatory workflow-state updates, stage management and memory capture become inconsistent and prone to failure.
mwargerInject a feature-specific question bank into Bead 1's study instructions.
faizkhairiSave session context, reminders, and diary entries to GitHub.
fkbertholdDispatch a bead's middle to isolated subagents with content-bridge artifact relay.
intelligentcode-aiAutomate the development workflow and PR lifecycle with staged gates.
