Menu
Six-axis spec review methodology — Structure, Clarity, Testability, Minimality, Consistency, Completeness, and UX Pattern Consistency. Each axis is evaluated independently, then findings are consolidated into a review report.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Automates CI/CD pipeline setup, adapted for the Mezon Mentor Bot ("MeKnow") platform. Use when setting up or modifying build and deployment pipelines, the GitHub Actions workflow (.github/workflows/rag-engine.yml), quality gates, or the /solo:implement verify step. Use when configuring the polyglot test runner (Python/uv, Go, TS/pnpm) with a pgvector service container or debugging CI failures.
Conducts multi-axis code review (MeKnow-adapted, polyglot). Use before merging any change. Use when reviewing code written by yourself, another agent, or a human across Python/Go/TypeScript. Use when you need to assess code quality across correctness, readability, architecture, security, and performance before it enters main. Complements the built-in `/code-review` and `/security-review` slash commands and the `/solo:address-review` PR-comment loop.
Simplifies code for clarity (MeKnow-adapted, polyglot + OpenSpec). Use when refactoring code for clarity without changing behavior in this repo. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity. Every change keeps the resolver-selected gates (uv/go/pnpm) green and respects the repo's invariants.
Collaborative bug-fixing mode — agent + human work together to triage, diagnose, fix, and verify bugs directly in the project code. Works for both FE (UI component bugs) and BE (logic/data/test bugs). Core pattern: understand → confirm with a failing test (Red) → fix to pass (Green). The test is both proof of understanding and a permanent regression guard.
Guides systematic root-cause debugging (Mezon Mentor Bot "MeKnow" platform). Use when a toolchain gate fails (`uv ... pytest`, `pyright`, `go test -race`, `pnpm test`), a build breaks, retrieval/runtime behavior doesn't match expectations, a citation is missing or a tenant boundary leaks, or you hit any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Records decisions and documentation, adapted for the Mezon Mentor Bot ("MeKnow") platform. Use when making architectural decisions, changing the API contract (OpenAPI) or the BotPolicy/MCP boundary, shipping features, or recording context future engineers and agents need. Notes how OpenSpec design.md files serve as lightweight ADRs, that former RFCs live in docs/design/, and where docs/ lives.
| name | spec-review-and-quality |
| description | Six-axis spec review methodology — Structure, Clarity, Testability, Minimality, Consistency, Completeness, and UX Pattern Consistency. Each axis is evaluated independently, then findings are consolidated into a review report. |
| tags | [] |
Six-axis spec review methodology. Each axis is evaluated independently, then findings are consolidated into a review report.
solo-spec validate --strict passes; Purpose + Requirements sections;
SHALL/MUST in the body line; >=1 Scenario each; delta uses ADDED/MODIFIED/REMOVED/RENAMED
with the FULL requirement on MODIFYui.md must exist with loading/empty/error states documented, a "Design Language Reference" section citing project design docs (or noting their absence), and UX patterns referenced from the project's design conventionsui.md references the project's existing UX patterns (from DESIGN.md, design skills, .solo/spec/patterns/ux-patterns.md, or codebase exploration) or explicitly justifies divergence; the abstract business flow is coherent and maps entry → steps → completion → next; visual concepts (character, density, tone) align with the project's established design language; ui.md reads as a final design handoff, not a first draftsolo-spec validate "<change>" --strictSeverity: Blocker (invalid/untestable/contradicts invariant) > Required (fix before ship) > Nit (optional) > FYI.