CtrlK
BlogDocsLog inGet started
Tessl Logo

sdd-verify

Trigger: SDD verification phase, verify change. Execute tests and prove implementation matches specs, design, and tasks.

48

Quality

53%

Does it follow best practices?

Impact

—

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./internal/assets/skills/sdd-verify/SKILL.md
SKILL.md
Quality
Evals
Security

ORCHESTRATOR GATE: If you loaded this skill via the skill() tool, you are the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to the dedicated sdd-verify sub-agent using your platform's delegation primitive (e.g., task(...), sub-agent invocation, etc.). This skill is for EXECUTORS only.

Activation Contract

Run when the orchestrator launches verification for an SDD change. You are the quality gate: prove completion with source inspection plus real execution evidence.

Hard Rules

  • Read proposal, spec, design, and tasks before judging implementation.
  • Execute relevant tests; static analysis alone is never verification.
  • A spec scenario is compliant only when a covering test passed at runtime.
  • Compare specs first, design second, task completion third.
  • Do not fix issues; report them for the orchestrator/user.
  • Persist verify-report according to mode: Engram, openspec file, hybrid both, or inline-only for none.
  • If Strict TDD is active, load strict-tdd-verify.md from this skill directory; if inactive, never load it.
  • Return the Section D envelope from ../_shared/sdd-phase-common.md.

Decision Gates

ConditionAction
Orchestrator says STRICT TDD MODE IS ACTIVETreat as authoritative.
Cached/config strict_tdd: true and runner existsStrict TDD verify; load module.
Strict TDD false or no runnerStandard verify; skip TDD checks.
Task incompleteCRITICAL for core task, WARNING for cleanup task.
Test command exits non-zeroCRITICAL.
Spec scenario has no passing covering testCRITICAL UNTESTED or FAILING.
Design deviation existsWARNING unless it breaks a spec.

Execution Steps

  1. Load relevant skills via shared SDD Section A.
  2. Retrieve artifacts via shared Section B for the active persistence mode.
  3. Resolve testing/TDD mode from cached capabilities, config, or project files.
  4. Count completed and incomplete tasks.
  5. Map each spec requirement/scenario to implementation evidence and tests.
  6. Check design decisions against changed code.
  7. Run test, build/type-check, and coverage commands when available.
  8. Build the behavioral compliance matrix from actual test results.
  9. Persist and return the verification report.

Output Contract

Return ## Verification Report with change, mode, completeness table, build/tests/coverage evidence, spec compliance matrix, correctness table, design coherence table, issues grouped as CRITICAL/WARNING/SUGGESTION, and final verdict PASS, PASS WITH WARNINGS, or FAIL.

References

  • references/report-format.md — full report template, compliance statuses, and command evidence fields.
  • strict-tdd-verify.md — load only when Strict TDD is active.
  • ../_shared/sdd-phase-common.md — skill loading, retrieval, persistence, and return envelope.
Repository
sergiodvillegas-art/gentle-ai
Commit

3bfa934

Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill