Granular implementation plan with ordered tasks and typed architectural anchors. Acts as Software Architect to define HOW, WHERE, and in what ORDER. Reads spec from docs/specs/ or accepts inline description. Produces tasks of 2-5 min each with exact file paths, typed signatures (interfaces, function contracts)…
Feature specification before coding. Captures WHAT, WHY, and key design decisions. Produces specs with problem statement, requirements, acceptance criteria, design decisions, schema/API/UI changes, risks, and deploy checklist. Detail scales to complexity — simple features get short specs, complex features get…
Designs operational functional tests for Medium+ features before production. Use after /test-plan (Full tier) or DIRECTLY after /feature-plan (Standard tier — its upstream is then the plan itself) when a feature changes a real business capability, workflow, automation, user journey, pipeline, agent behavior…
Adversarial security review of a change before it ships. Answers one question with evidence: what can an untrusted caller reach that they should not? Covers privilege reachability across trust boundaries, authorization vs authentication, caller-supplied identity and values, secret handling, data isolation…
Test-Driven Development enforcement. Use when implementing tasks from a feature plan, fixing bugs, or adding new functionality. Follows the classic RED-GREEN-REFACTOR cycle: write a failing test first, implement the minimum code to pass it, then refactor. Integrates with /feature-plan tasks that have Tests: Yes. Use…
Full test plan for Medium+ complexity features. Reads the approved plan (which already has a Test Matrix section), and expands it into a comprehensive standalone test suite — detailed cases, fixtures, factories, E2E flows, parallelization groups, and adversarial review. Use for features with cross-layer interactions…