Loading...
Loading...
Found 19 Skills
Use tracer-bullet vertical slices to break down plans, specs, or PRDs into independently assignable issues in the project's issue tracker. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Decompose technical design into agent-sized implementation issues → numbered markdown files. Triggers: 'plan this,' 'break into issues,' 'create tasks,' 'ready to implement,' post-architect. Not for: designs without file paths/phases (run architect first).
Use this skill when > Convert plans, specs, or requirements into independently-grabbable vertical slice issues. Each slice is a thin but complete end-to-end cut through all layers (schema, API, UI, tests). Classifies issues as HITL (human-in-the-loop) or AFK (automated, no human interaction needed).
Use this skill when > Test-Driven Development using red-green-refactor cycles with vertical slices. Tests verify behavior through public interfaces, not implementation details. Use when building new features or fixing bugs with a test-first discipline to produce well-designed, behavior-verified code.
CleanSlice architecture for NestJS + Nuxt full-stack apps. Use for vertical slice features, gateway pattern, Provider.vue, Pinia stores, DTOs, or any CleanSlice project work.
Architecture selection advisor for .NET applications. Asks structured questions about domain complexity, team size, system lifetime, compliance, and integration needs, then recommends the best-fit architecture: Vertical Slice, Clean Architecture, DDD + Clean Architecture, or Modular Monolith. Load this skill when the user asks "which architecture", "choose architecture", "set up project", "new project", "architecture decision", "restructure", or "how should I organize". Always load BEFORE any architecture-specific skill.
Break a spec, plan, or conversation into tracer-bullet tickets, each declaring its blocking edges, published as GitHub sub-issues.