Quality

Investigate is a systematic debugging skill that enforces the Iron Law: never fix without a confirmed root cause. It walks through 5 phases from evidence collection to verified fix, producing structured debug reports.

Review Code analyzes code across six dimensions—correctness, readability, performance, security, testing, and architecture—and generates structured review reports with actionable recommendations. Use it to review code changes for bugs, risks, and quality issues.

Review Cycle orchestrates multi-dimensional code review with automated fix workflows. It detects session, module, or fix modes from input and routes through the corresponding phase doc for code analysis and remediation.

Security Audit runs a four-phase security audit covering supply chain risks, OWASP Top 10 code review, STRIDE threat modeling, and trend-tracked JSON reporting.

Accessibility Audit examines an existing interface against WCAG criteria, identifies barriers, and provides severity-rated findings with remediation steps. Use it when you have a design or build to assess now, not for planning future assistive-technology testing sessions.

Design QA Checklist builds a systematic checklist for verifying that a build matches the design specification, used at implementation review.

Usability Test Plan designs a comprehensive usability study, including research questions, methodology, participant criteria, task metrics, and facilitation guide. Use when planning a usability test for designs or prototypes, especially before writing test scenarios.

37signals Way applies the 37signals philosophy from Getting Real, Rework, and Shape Up to shape work, bet on six-week cycles, and ship lean products. Use it when cutting scope, avoiding overbuilding, or running a small team with fixed time and flexible scope.

Clean Architecture structures software around the Dependency Rule so source code dependencies point inward from frameworks to use cases to entities. Use when reviewing architecture layers, module boundaries, or deciding where business logic belongs.

Clean Code applies disciplined naming, small functions, and clean error handling to make code more readable and maintainable. Use it when cleaning up messy code, reviewing pull requests for readability, or improving test quality.

Continuous Discovery helps product teams establish a weekly customer discovery cadence using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use it to set up regular customer feedback loops, prioritize experiments, and connect discovery insights to delivery work.

Design Sprint guides a team through a five-day structured process to map, sketch, decide, prototype, and test product ideas with real users. Use it to validate a high-stakes product decision or compress months of debate into one week.