quality-driven-dev_skill

Overview

This skill implements a quality-driven development workflow that automatically chooses between TDD and DDD and enforces the TRUST 5 quality framework. It guides you through project analysis, SPEC creation, test-driven or characterization-driven changes, structured logging, and a final quality gate. Use it to deliver tested, readable, secure, unified, and trackable code with clear progress reporting.

How this skill works

The skill inspects the repository to detect language, test framework, existing coverage, and logging infrastructure. Based on coverage (>=10% → TDD, <10% → DDD) it generates a SPEC, orchestrates test creation and implementation phases, injects or improves logs at key points, and runs the TRUST 5 checklist before completion. It reports phase results and produces a completion summary with test and log details.

When to use it

• Building a new feature where tests should be written first
• Refactoring or changing legacy code that lacks test coverage
• Fixing bugs while preserving existing behavior
• Adding or standardizing logging across a codebase
• Enforcing a formal quality gate before merges or releases

Best practices

• Run project analysis before writing any code or tests
• Create a concise SPEC with testable acceptance criteria for every change
• Follow RED→GREEN→REFACTOR in TDD and ANALYZE→PRESERVE→IMPROVE in DDD
• Add meaningful logs at API entry, external calls, errors, state changes, and batch boundaries
• Avoid logging sensitive data and keep INFO logs sufficient for production tracing
• Verify all five TRUST checks (Tested, Readable, Unified, Secured, Trackable) before completion

Example use cases

• New microservice: initialize tests, choose TDD, and produce a SPEC-driven implementation
• Legacy endpoint with <10% coverage: create characterization tests, preserve behavior, then incrementally refactor
• Bug fix: write failing test that reproduces the issue, implement minimal fix, and add contextual logs
• Logging standardization: detect missing logger, add consistent log format and messages across modules
• Release readiness: run full TRUST 5 gate to ensure tests, security review, and documentation are in place