Loading...
Loading...
Found 16 Skills
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.
Use when the user wants a design, plan, or approach stress-tested against the project's own domain model and documented decisions - terminology challenged, contradictions with the real code surfaced, CONTEXT.md and ADRs kept current as decisions land - and does NOT need an implementation plan produced afterward. Use grill-then-plan instead when a written plan is the required outcome.
Trim a spec, ADR set, or design doc down to what a builder needs, without losing a fact. TRIGGER when: user says a spec is 'too long' or 'bloated'; user asks what to remove from it, or wants it cut to 'just what we need to build'.
Use when breaking down a Beat change spec into tasks — not for spec creation or implementation