What problem does it solve? Teams often declare implementation tasks complete without a consistent quality check, letting reliability, security, or observability issues slip into production. This Skill enforces a mandatory five-pillar verification gate (Reliability, Scalability, Security, Observability, Maintainability) on every code change before sign-off. ## Core Features & Use Cases - Automated Gate Script: Run npm run harness:gate to evaluate the git diff against the five pillars, producing a JSON report with exit codes 0 (pass), 1 (fail), or 2 (concerns). - Canonical Pillar Checklist: A single source of truth in references/harness-pillars.md defines PASS / CONCERN / FAIL criteria shared with code-review and process-verification-gate workflows. - Sprint Contract Awareness: Cross-checks diffs against active sprint contracts, tagging findings with criterion IDs like REL-01 or SEC-02. - Use Case: After finishing a feature branch, an engineer runs the gate, fixes all blocking findings, documents concerns in the turn summary, and includes the harnessVerdict map in the agent turn summary before routing to QA. ## Quick Start Ask the agent to run the harness completion gate on the current changes and report the five-pillar verdict before marking the task done.
