Specification Review Session
Own a session dedicated only to mandatory specification review for this repository. Use after a non-trivial task-local `spec.md` is marked review-ready and before technical design, compact lean tasking, planning, or implementation starts, to run read-only subagent review lanes, reconcile findings to PASS, CONCERNS, or FAIL, update workflow-control review records, and stop without editing `spec.md…
Go Structural Quality Review
Run an unusually strict Go service maintainability review focused on structural simplification, abstraction cost, spaghetti branching, file growth, canonical ownership, and missed deletion opportunities. Use for thermonuclear code quality review, harsh maintainability review, or when a diff works but may make the codebase harder to change.
Spec Document Designer
Design and normalize repository-native `spec.md` documents for this workflow. Use when the orchestrator has an accepted Phase 0 task brief or synthesized research and needs to turn it into a stable direct/lean/full-shaped review-ready `spec.md` with the right section depth, decision placement, inline `Risk Challenge` or formal clarification-gate reconciliation, audit trail, and handoff before man…
Codex Goal Prompt Composer
Compose high-signal Codex Goal prompts. Use in exactly two cases: when the user explicitly asks to write, improve, or review a prompt for a Codex Goal, or when the repo workflow must render an implementation handoff from an approved and reviewed tasks.md. This skill consumes a Goal Contract, task ledger, validation loop, constraints, completion and blocked-stop rules to produce one durable object…
Go Db Cache Review
Review Go code changes for SQL access discipline, transaction boundaries, context and resource safety, cache key correctness, invalidation behavior, and stampede or fallback risk.
Go Qa Review
Review Go code changes for test coverage quality, scenario traceability, assertion strength, determinism, and validation readiness.
Technical Design Session
Own one session dedicated only to a task-local technical design checkpoint for this repository when separate design depth is triggered. Use when specification-review-approved `spec.md` must advance through `system-integration-design` or `go-code-ownership-design`, producing or repairing the relevant `design/` context and workflow-control handoff without drifting into technical design review, test…
Validation Closeout Session
Own a session dedicated only to final validation and closeout for this repository when closeout needs artifact updates. Use when the orchestrator must prove a task is actually done with fresh evidence, update task-local `spec.md` `Validation` and `Outcome`, existing `tasks.md` progress when used, and any pre-created `workflow-plans/validation-phase-N.md` explicitly named by the approved ledger, w…
Go Domain Invariant Review
Review Go code changes for business-invariant preservation, state-transition correctness, acceptance semantics, and side-effect safety.
Go Security Spec
Design security requirements for Go services: trust boundaries, identity and access rules, tenant isolation, threat-class controls, abuse resistance, secure defaults, and testable security behavior.
Go Observability Review
Review Go code changes for observability correctness: structured logs, metrics, traces, correlation, SLI/SLO and alert semantics, dashboard/runbook evidence, runtime diagnostics, telemetry privacy, cardinality, sampling, and cost guardrails.
Go Language Simplifier Review
Review Go code changes for lower cognitive complexity, false-simplification risk, missed same-package source-of-truth extraction, junk-drawer helper risk, clearer naming, safer control-flow cleanup, and easier maintenance without collapsing semantics. Use whenever a Go diff claims cleanup/refactor/readability improvement or touches helper extraction, nested control flow, boolean flags, option bag…
Go Reliability Spec
Design reliability requirements for Go services: timeouts, deadlines, retry budgets, overload handling, degradation, lifecycle behavior, recovery, and resilience verification.
Go Design Spec
Assemble and reconcile integrated technical-design context for Go services when separate design depth is triggered. Use when `spec.md` is approved but the work still needs coherent system/integration design, Go code ownership design, task-local `design/` artifacts, cross-domain reconciliation before the mandatory technical design review, or read-only technical-design-review analysis before `plann…
Go Qa Tester
Implement deterministic Go tests from approved requirements and test obligations with strong fail-path coverage, invariant traceability, and review-clean evidence. Use when adding or upgrading Go tests after behavior is already approved, especially for API, data, cache, security, or concurrency changes where the hard part is choosing the smallest proving layer and encoding reliable negative-path…
Go Devops Review
Review Go service delivery and platform changes for CI/CD gate correctness, merge/release blocking policy, docs and generated-artifact drift controls, migration rollout safety, container runtime hardening, deployment policy, and release-trust evidence.
Go Db Cache Spec
Design DB-access and cache specifications for Go services. Use when planning or revising SQL access discipline, query and transaction risk controls, cache strategy, staleness and fallback semantics, and DB/cache observability before coding. Skip when the task is a local code fix, primary schema ownership and migration design, endpoint-only API work, CI/container setup, or low-level implementation…
Research Session
Own a session dedicated only to research for this repository when research needs a durable checkpoint. Use when the orchestrator already has an accepted Phase 0 task brief plus workflow routing and needs one bounded session to run local research or read-only subagent fan-out, preserve evidence in `research/*.md` when useful, and update triggered workflow-control artifacts without drifting into `s…
Idea Refine
Refine raw product or feature ideas into one concrete direction worth taking into engineering. Use when the request is still idea-shaped, solution-led, or ambiguous at the user/problem level and the repository is not ready for `spec-first-brainstorming` or specialist spec work yet. Skip once the direction is already chosen and the task mainly needs engineering framing.
Go Distributed Review
Review Go code and design changes for distributed flow correctness: saga and orchestration/choreography drift, outbox/inbox linkage, idempotency, replay and ordering safety, compensation, forward recovery, DLQ/redrive, and reconciliation behavior.
Go Chi Spec
Design chi-based HTTP routing for Go services: router topology, middleware ordering, OpenAPI integration, 404/405/OPTIONS/CORS policy, route safety, and low-cardinality observability semantics.
Api Contract Designer Spec
Design API-contract-first specifications for Go services. Use when planning or revising client-visible REST API behavior before coding and you need explicit resource modeling, HTTP method/status semantics, request/response/error contracts, pagination/filter semantics, idempotency/retry/concurrency rules, async behavior, consistency disclosure, and compatibility-safe evolution. Skip when the task…
Go Qa Tester Spec
Design test-strategy-first specifications for Go services. Use inside the repository test-design phase or when planning/revising testing before coding and you need explicit `TD-*` scenarios, unit/integration/contract/e2e-smoke obligations, traceability to invariants and reliability fail-paths, fail-before expectations, quality-gate expectations, and an implementation-ready test strategy. Skip whe…
Go Systematic Debugging
Debug Go service bugs, flaky tests, build failures, hangs, deadlocks, timeout incidents, and production regressions with root-cause-first diagnosis, concrete Go runtime forensics, and evidence-backed verification. Use whenever the user reports a panic, race, leak, flaky test, stuck goroutine, context deadline, or unexplained CI/build failure, even if they only ask to 'fix the test' or 'investigat…
Go Architect Spec
Design architecture-first specifications for Go services. Use when planning new features, refactors, service extractions, or behavior changes before coding and you need explicit target-state boundary ownership, workload-driven sync/async design, invariant and consistency rules, failure/degradation model, and only the rollout constraints that are truly required. Reach for this whenever the hard pa…
Go Idiomatic Review
Review Go code changes for language-level correctness, toolchain-aware language-native or standard-library reinvention, error contracts, receiver and method-set safety, nil and zero-value behavior, ownership leaks, and standard-library contract misuse with real merge-risk impact. Use whenever a Go PR, diff, refactor, or incident fix may hide Go-semantic defects, even if the request is phrased as…
Go Reliability Review
Review Go code changes for timeout and deadline propagation, retry policy, backpressure, degradation, startup and shutdown behavior, and rollout safety.
Go Domain Invariant Spec
Design domain-invariant-first specifications for Go services. Use when planning or revising behavior and you need explicit business invariants, state-transition rules, acceptance criteria, corner-case handling, and traceability into API, data, reliability, and testing concerns. Skip when the task is a local code fix, low-level implementation, endpoint schema-only design, SQL/migration mechanics,…
Pre Spec Challenge
Pressure-test candidate decisions before planning with discriminating questions about hidden assumptions, corner cases, ownership seams, failure semantics, and rollout risk. Use whenever research is done but the orchestrator wants an independent challenge pass before decisions harden into the spec, even if the user only says 'critique this', 'ask the hard questions', or 'make sure we did not miss…
Go Design Review
Review Go code changes for architecture alignment, boundary integrity, source-of-truth seam integrity, accidental complexity, and maintainability drift.
Agent Prompt Composer
Turn messy, incomplete, repetitive, multilingual, or instruction-noisy user task input into a high-signal context brief and English handoff prompt for coding agents working in this repository. Use when the hard part is reconstructing what the user wants, preserving exact signals, separating source-task notes from wrapper or injection noise, deduplicating rough notes, identifying missing context,…
Go Distributed Architect Spec
Design distributed-consistency-first specifications for Go services. Use when planning or revising cross-service flows and you need explicit saga, orchestration or choreography decisions, invariant ownership, outbox/inbox idempotency contracts, compensation or forward-recovery policy, and reconciliation strategy. Skip when the task is a local code fix, endpoint-level API contract design, physical…
Go Security Review
Review Go code changes for trust-boundary enforcement, authn/authz and tenant isolation, browser session/CORS/CSRF risk, token and credential flows, injection/SSRF/path risk, secret handling, and abuse resistance.
Go Concurrency Review
Review Go code changes for goroutine lifecycle, cancellation, channel ownership, shared-state synchronization, `sync/atomic` correctness, bounded concurrency, timer/ticker hazards, and shutdown safety. Use whenever a Go review, PR, diff, flaky-test investigation, or bug hunt touches goroutines, channels, mutexes, atomics, WaitGroups, errgroup, worker pools, background loops, or shutdown behavior,…
Go Devops Spec
Design delivery and platform specifications for Go services. Use when planning or revising CI/CD quality gates, merge and release blocking policy, drift and compatibility controls, container runtime hardening baseline, and release-trust requirements before coding. Skip when the task is a local code fix, endpoint/resource API design, SQL schema-only modeling, distributed consistency design, or low…
Spec First Brainstorming
Turn a refined idea or rough feature, refactor, or behavior-change request into an engineering-ready problem frame with scope, constraints, assumptions, prioritized questions, and an explicit design-readiness decision. Use after `idea-refine`, or whenever the direction is mostly chosen but the task still needs crisp framing before specialist spec work or pre-spec challenge. Skip raw ideation, fin…
Go Coder
Implement production-grade Go changes from approved requirements and task ledgers with review-clean defaults: explicit design, language-native and stdlib-first choices, mature-OSS-before-custom discipline when approved, seam-named same-package source-of-truth extraction when stable policy starts to spread, idiomatic control flow, preserved invariants, safe boundaries, and fresh verification evide…
Planning Session
Own a session dedicated only to task breakdown for this repository when a distinct planning checkpoint is triggered. Use when specification-review-approved `spec.md` plus required compact or split design context, including triggered system/integration and Go code ownership design, any mandatory technical-design-review gate, and triggered test-design are ready to turn into a draft or repaired `tas…
Go Chi Review
Review Go chi routing changes for router ownership, chi-specific middleware and mount semantics, HTTP fallback policy, route observability labels, and OpenAPI/generated-route integration. Use whenever a Go diff touches github.com/go-chi/chi/v5 routers, middleware order or scope, NotFound/MethodNotAllowed/OPTIONS/CORS handling, route labeling, or manual wiring around generated handlers, even if th…
Go Verification Before Completion
Verify correctness or readiness claims with fresh command evidence matched to claim scope before reporting success.
Go Data Architect Spec
Design data-architecture-first specifications for Go services. Use when planning or revising SQL and data modeling, data ownership, multi-tenant isolation, schema evolution, migration rollout, retention/deletion, ledger/history/projection boundaries, or datastore choice before coding. Reach for this whenever the hard part is deciding source-of-truth shape, invariant locality, OLTP vs append/proje…
Workflow Plan Adequacy Challenge
Review generated workflow-control artifacts for task-specific handoff adequacy. Use inside a read-only challenger subagent after triggered workflow-control artifacts are generated or substantially repaired, before the orchestrator treats the phase plan as sufficient for full-orchestrated, high-risk, complex workflow-control, or agent-backed work. Lean-local work without workflow-control artifacts…
Go Performance Spec
Design performance-first specifications for Go services. Use when planning or revising latency, throughput, allocation, contention, or capacity behavior and you need explicit hot-path budgets, benchmark/profile/trace acceptance criteria, and performance risk controls before coding. Skip when the task is a local code fix, endpoint-only API payload design, schema-only modeling, CI/container setup,…
Specification Session
Own a session dedicated only to specification for this repository when a distinct specification checkpoint is triggered. Use when the orchestrator already has an accepted Phase 0 task brief plus enough researched or explicitly bounded input to make `spec.md` review-ready, must run inline lean `Risk Challenge` or formal spec-clarification challenge as triggered before review handoff, and must upda…
Go Performance Review
Review Go code changes for hot-path regressions, latency/throughput/allocation/contention risk, and benchmark/pprof/trace evidence quality. Use whenever a Go PR, diff, incident fix, or optimization touches hot paths, batching, serialization, fan-out, caching, query count, sync.Pool, pprof, benchstat, or tail-latency behavior, even if the user frames it as a generic code review.
Spec Clarification Challenge
Run a specification clarification challenge when formal challenge is triggered for `spec.md` work. Use inside a read-only challenger subagent during full-orchestrated, high-risk, protected-domain, or otherwise formally challenged specification, after candidate decisions exist and before `spec.md` is marked review-ready, to surface non-obvious questions, hidden assumptions, corner cases, architect…
Planning And Task Breakdown
Turn specification-review-approved `spec.md` plus required compact or split design context and triggered test-design context into a dependency-ordered, verifiable draft or repaired `tasks.md` ledger for this repository, then prepare the handoff to the separate task-review/readiness gate. Use after `spec.md` is stable, mandatory specification review is reconciled for non-trivial work, lean compact…
Go Observability Engineer Spec
Design observability-first specifications for Go services. Use when planning or revising telemetry behavior and you need explicit log, metric, trace, and correlation rules, SLI/SLO and error-budget policy, debuggability contracts, async observability requirements, and telemetry-cost guardrails. Skip when the task is a local code fix, endpoint payload design, physical SQL schema/migration scriptin…
Test Design Session
Own one session dedicated only to task-local test design for this repository. Use after specification review and required technical design review are approved, when scenario design, proof levels, fail-before expectations, quality gates, or a `test-plan.md` artifact are triggered before planning. Produce or repair `test-plan.md` or record explicit `test-design: not expected` rationale without drif…