Loading...
Loading...
Found 184 Skills
Use when breaking down a Beat change spec into tasks — not for spec creation or implementation
Evidence-grounded to-be design (ADRs + design doc) and an implementation orchestration plan (a machine-readable task ledger). Activates when the user asks to design a target state, plan the work, or produce a task plan for a goal.
Use when a Beat change is implemented and ready to archive — not for verifying implementation
Choose system boundaries, architectural patterns, and tradeoffs. USE when deciding overall software shape, domain boundaries, or major technical direction.