design-a-cycle
CommunityOrchestrates design cycles from plan to handoff.
System Documentation
What problem does it solve?
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.
Core Features & Use Cases
- Orchestrates Plan → Research → Architect cadence across L1-L3 substrates, preserving cycle-state in the KG and design-docs.
- Spawns research beads for grounding open [CLARIFICATION] markers and then creates an implementation epic when green.
- Reads and writes substrate state to drive cadence without storing internal bead instances, enabling stateless orchestration.
Quick Start
Open a topic design cycle with /design-a-cycle <topic> to start or advance a design cadence from Plan to Handoff.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: design-a-cycle Download link: https://github.com/fkberthold/loom/archive/main.zip#design-a-cycle Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 510,000+ vetted skills library on demand.