From devflow
Use during PREVC Validation phase — comprehensive verification including tests, security audit, and spec compliance check
npx claudepluginhub nexuz-sys/devflow --plugin devflowThis 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.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Comprehensive verification that the implementation matches the spec, tests pass, and no security or quality issues exist.
Announce at start: "I'm using the devflow:prevc-validation skill for the Validation phase."
REQUIRED SUB-SKILL: Invoke superpowers:verification-before-completion
Run the full test suite, not just new tests. Verify:
Compare the implementation against the design spec point by point:
agent({ action: "orchestrate", phase: "V", task: "spec-compliance" })
The code-reviewer agent performs structured spec compliance.
Read .context/agents/code-reviewer.md and apply its checklist against the spec.
Check if the implementation complies with active ADR guardrails.
Only if .context/docs/adrs/README.md exists and has active ADRs.
.context/docs/adrs/README.md — get list of active ADRsAprovado:
a. Read the Guardrails section
b. For each guardrail rule (SEMPRE/NUNCA/QUANDO):
### ADR Compliance: PASS/FAIL
| ADR | Guardrails | Violations | Status |
|-----|-----------|------------|--------|
| 001 - SOLID Python | 8 | 0 | PASS |
| 002 - TDD Python | 5 | 1 | FAIL |
| 003 - AWS Data Lake | 8 | 0 | PASS |
**Violations:**
- ADR 002, rule "NUNCA usar mocks para banco": found mock in `tests/test_user.py:45`
agent({ action: "orchestrate", agents: ["code-reviewer"], task: "adr-compliance" })
The code-reviewer agent performs ADR compliance checking against the guardrails.
agent({ action: "orchestrate", agents: ["test-writer"], task: "coverage-review" })
| Implementation area | Required test types | Gate blocks if missing |
|---|---|---|
| Pure functions, utilities | Unit tests | Yes |
| API endpoints, DB queries | Unit + Integration | Yes |
| Auth, payments, registration | Unit + Integration + E2E | Yes |
| CLI tools, shell scripts | Unit + E2E (real execution) | Yes |
| UI components | Unit + Snapshot | Yes |
E2E is mandatory when the task touches:
What counts as an E2E test:
If E2E tests are required but missing, return to Execution phase to add them before proceeding. </HARD-GATE>
Verify:
Skip for QUICK scale or tasks that don't touch security surfaces.
agent({ action: "orchestrate", agents: ["security-auditor"], task: "security-validation" })
Skip unless the task involves:
agent({ action: "orchestrate", agents: ["performance-optimizer"], task: "perf-check" })
The Validation phase gate requires:
Present validation summary:
## Validation Summary
### Tests: PASS (X passed, 0 failed)
### Test Types: Unit ✓ | Integration ✓/N/A | E2E ✓/N/A
### TDD Ordering: VERIFIED / VIOLATION (list files without test-first)
### Spec Compliance: PASS/FAIL
### ADR Compliance: PASS/N/A (X guardrails checked, Y violations)
### Security: PASS/N/A
### Performance: PASS/N/A
### Result: VALIDATED / ISSUES FOUND
If ISSUES FOUND: return to Execution phase to fix, then re-validate.
When gate is met:
Full mode:
plan({ action: "commitPhase", phase: "V" })
workflow-advance() # Moves to C phase
| Thought | Reality |
|---|---|
| "Tests pass, we're done" | Tests are step 1 of 5. Spec compliance and security remain. |
| "Security is someone else's job" | Every developer validates security at implementation time. |
| "Performance testing is overkill" | Only skip if the task literally can't affect performance. |
| "The code reviewer already checked this" | R phase reviewed the plan. V phase validates the implementation. |