Orchestrate Plan, Research, and Architect phases across L1-L3 substrates.
npx skills add https://github.com/fkberthold/loom --skill design-a-cycle
Please help me install this Agent Skill. Skill: design-a-cycle Source: https://github.com/fkberthold/loom/tree/main/skills/design-a-cycle Command: npx skills add https://github.com/fkberthold/loom --skill design-a-cycle
Above-bead campaign/arc orchestrator that drives a design cycle's Plan→Research→Architect cadence over the layered design substrate (L1 KG spine / L2 design-doc drawer / L3 optional executable specs), gates on two-tier soundness, then hands off to create-beads to spawn the implementation epic. NOT a bead-lifecycle activity recipe — it iterates, spawns research-a-beads + an epic, and is stateless beyond the substrate it maintains. Triggers on "/design-a-cycle <topic>", or when the user wants to open or advance a design cycle for a topic that will eventually become beads.
Open a topic design cycle with /design-a-cycle <topic> to start or advance a design cadence from Plan to Handoff.
High-intent search queries and answers about installing and using this skill.
You orchestrate a design cycle by triggering the /design-a-cycle command with a topic, which drives the Plan, Research, and Architect phases across a knowledge graph substrate and design-doc headers. It coordinates the entire cadence and hands off to create-beads for implementation.
A two-tier soundness gate validates design cycle progression by checking state consistency across the layered substrate before advancing phases. It ensures the knowledge graph spine, design-doc headers, and optional executable specs align before spawning research beads or implementation epics.
State is managed by reading and writing directly to the layered substrate, comprising the L1 knowledge graph, L2 design-doc headers, and L3 optional specs. This enables stateless orchestration, preserving cycle-state externally without storing internal bead instances.
Research beads are spawned to ground open clarification markers that arise during the Research phase of the design cycle. Once these markers are resolved and the cycle passes soundness gates, the orchestrator hands off to create an implementation epic.
No, design-a-cycle is not a bead-lifecycle activity recipe. It functions as an above-bead campaign orchestrator that iterates through the Plan, Research, and Architect cadence, spawning research beads and implementation epics rather than managing individual bead states.
Design-doc drawers are scaffolded from templates during the orchestration of the design cycle. The orchestrator reads the substrate state, applies templates to generate the L2 design-doc structure, and advances the cycle through the required architectural phases.
JaviMontanoImplement progressive L1/L2/L3 content loading and pruning for AI context.
dsifryCoordinate AI agents to manage BEADS epic and GitHub issue lifecycles.
DicklesworthstoneConvert markdown plans into dependency-aware beads using the Beads CLI.
porcupine-mdOrchestrate AI software development through a 16-phase pipeline with persistent state.
