Loading...
Loading...
Found 318 Skills
Manages cross-session knowledge persistence. Triggers on "remember", "recall", "what did we", "save this decision", "todo", or session handoff.
Design system architecture and high-level technical strategy
Use when breaking down a Beat change spec into tasks — not for spec creation or implementation
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, drill into their design, or says "drill this" or "drill me".
Choose system boundaries, architectural patterns, and tradeoffs. USE when deciding overall software shape, domain boundaries, or major technical direction.
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections are untouched.