Open REEL Kanban board in a new terminal tab
Decomposes a product specification into ordered features with dependencies, tracks progress, and drives sequential execution through the go-hexagonal pipeline.
You MUST use this before starting any feature with go-pm. Explores user intent, alternative approaches, and domain design through Socratic questioning before locking a spec.
Writes zero-downtime, reversible, batched data migrations tested with testcontainers. Use for backfills, data transforms, column splits, and schema-level data moves.
Bootstraps a new Go project from scratch with hexagonal architecture, testcontainers, CI pipeline, and the full skill/agent suite installed.
Safe refactoring agent. First documents all inbound surfaces (HTTP, gRPC, message queues, etc.), creates exhaustive e2e tests with testcontainers to lock behavior, then plans and…
Creates all scaffolding files for a feature - stubs, interfaces, typed IDs, mocks, skipped tests - ensuring the project compiles and all tests pass or skip.
Thin task runner that executes .plan/<feature-slug>/TASKS.md by dispatching subagents for each task. Validates green phases by running tests.
Use whenever you need clarifications, decisions, or preferences from the user before proceeding on a task.
Red phase TDD - writes failing unit tests, contract tests, and e2e API tests. Covers all test levels in a single pass. Never touches implementation code.
Designs HTTP API endpoints - routes, request/response types, validation rules, error codes. Called by go-architect when the feature includes an API surface.
Fresh-perspective agent invoked by circuit breakers when another skill is stuck. Reads the error context and attempts to fix the problem without the bias of previous failed…
Use when a feature pipeline is fully complete — all tasks green, all reviews passed, acceptance criteria met.
Use when encountering any bug, test failure, or unexpected behavior in Go code — before proposing fixes. Enforces root cause investigation through the hexagonal layers.
Strict product manager that interrogates the user about feature specifications, detects maturity gaps, delegates to go-architect once the spec is solid, and arbitrates spec…
Designs implementation architecture following hexagonal patterns, produces TASKS.md and individual task-N.md files for the orchestrator to execute using red-green TDD.
Use this skill whenever the user wants to scaffold, bootstrap, or generate architectural components in a Go project that has `go-surgeon` installed with scaffolding templates…
ALWAYS load when browsing or editing go project. Use this skill whenever you need to read, navigate, explore, or modify Go source code in a project that has `go-surgeon` installed…
Use this skill when classifying a feature's complexity (mechanical, standard, architectural), when deciding which pipeline shape applies to a given feature, when escalating a task…
Use this skill whenever you create, write, modify, or statue an entry under `.decisions/` or `.adrs/`, or when you need to know the difference between a tactical DECISION and a…
Reference guide for mct (claude-mercato), a Git-based package manager for Claude agent and skill definitions.
Use this skill whenever you are working on a Go project following the agile-team-v2 workflow — features in .features/, sprints in .sprints/, strategic ADRs in .adrs/,…
Use this skill whenever you need the exact format, lifecycle, or strict rules for the agile-team-v2 code markers — `// AC: <criterion>` + `// TODO(impl-<feature-slug>, ac-<NNN>)`…
Use this skill whenever you are running as the `red` or `green` agent on an agile-team-v2 task. Covers the discipline-based spec isolation between red and green (no private…
Analyzes .feedback/ data across features to detect recurring pipeline