tranhieutt

Reviews a product, technical, API, UI, or implementation spec for completeness, testability, architectural fit, and readiness before planning or implementation.

Locks the codebase to prevent unintended writes during a freeze period such as before a release or during an incident. Use when the user mentions freezing, code lock, or release lockdown.

Creates a visual and textual map of the project systems, services, data flows, and integration boundaries. Use when documenting system architecture or when the user mentions system map, architecture diagram, or service boundaries.

Requires fresh verification evidence before claiming work is complete, fixed, passing, safe, ready, merged, or clean. Use before completion claims, commits, PRs, merge readiness, or moving to the next task.

Routes every software-development request through the right SDD workflow before action. Use at session start, before clarifying questions, before edits, and whenever deciding which SDD skill should govern a task.

Records unexpected API behaviors, undocumented caveats, version bugs, or non-obvious workarounds into .claude/memory/annotations.md. Use immediately when an undocumented behavior or surprising caveat is discovered during development.

Runs multiple specialist subagents in parallel then merges their outputs into a unified result. Use when a task can be split into independent parallel workstreams that need to be recombined.

Revisa textos em Markdown conforme as regras fixadas do estilo de agente v0.3.5 e, opcionalmente, escreve uma cópia aprimorada ao lado da fonte. Use para especificações, ADRs, corpos de PR, notas de lançamento e documentos técnicos quando a qualidade da prosa ou a disciplina de evidências forem importantes.

Executa um plano de implementação aprovado, tarefa por tarefa, utilizando um novo subagente implementador para cada etapa e com duas revisões. Ideal para planos aprovados com tarefas sequenciais e onde portões de qualidade são necessários, sem a sobrecarga de orquestração completa.

Creates a well-formed git commit following conventional commit format with type, scope, and descriptive message. Use when the user is ready to commit changes or mentions conventional commits.

Designs relational and NoSQL database schemas, indexing strategies, migration plans, and data modeling patterns. Use when designing a database or when the user mentions database architecture, schema design, or data modeling.

Reviews UI/UX designs, wireframes, and design systems for usability, accessibility, consistency, and implementation feasibility. Use when reviewing design specs or when the user mentions design review, UX review, or design feedback.