Use for a 60-second quality check across all documents. Triggers on 'quick check', 'quality check', 'are the docs ready', 'sanity check', 'check rapido', 'check rápido', or 'are we ready'.
From pmnpx claudepluginhub etusdigital/etus-plugins --plugin pmThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides implementation of event-driven hooks in Claude Code plugins using prompt-based validation and bash commands for PreToolUse, Stop, and session events.
Run a rapid 8-question diagnostic across all documents in docs/ets/projects/{project-slug}/. This is NOT a deep validation — it is a fast sanity check that flags obvious gaps before a full gate review. Think of it as a smoke test for documentation quality.
docs/ets/projects/{project-slug}/ recursively — read all .md and .yaml filesFor each question, answer YES or NO. If NO, specify which document needs work and what is missing.
product-vision.md or project-context.md — Does it clearly state the target user and the value proposition?baseline.md or project-context.md — Are there quantified metrics with data sources?project-context.md, product-vision.md — Are decisions backed by evidence (data, research, user quotes) rather than just opinions?product-vision.md (BO-# objectives), ost.md if it exists — Are opportunities tied to measurable business outcomes?prd.md (MoSCoW), user-stories.md — Is the prioritization rationale documented?prd.md — Can a developer understand what to build and how to test it from the PRD alone?user-stories.md — Does every US-# have Given/When/Then acceptance criteria?implementation-plan.md, quality-checklist.md, release-plan.md — Is there a launch plan with monitoring and rollback?================================================
QUICK CHECK — Documentation Quality (60s)
================================================
1. Visao (para quem / qual valor) [PASS | FAIL]
2. Baseline (numeros e fonte) [PASS | FAIL | N/A]
3. Discovery (evidencia) [PASS | FAIL]
4. OST (outcomes com evidencia) [PASS | FAIL | N/A]
5. Priorizacao (rationale) [PASS | FAIL | N/A]
6. PRD (implementavel e testavel) [PASS | FAIL | N/A]
7. Backlog (aceite verificavel) [PASS | FAIL | N/A]
8. Release (lancar, monitorar, reverter) [PASS | FAIL | N/A]
Result: X/8 PASS | Y FAIL | Z N/A
--- Failures ---
[#]: [Document] — [What is missing]
...
--- Recommendation ---
[Next action to address highest-priority failure]
================================================
N/A means the document does not exist yet (expected if the project hasn't reached that phase). N/A is NOT a failure — it means that phase hasn't been started.
FAIL means the document exists but is missing critical content.
/validate instead.