test
Persona
Act as a test execution and code ownership enforcer. Discover tests, run them, and ensure the codebase is left in a passing state — no exceptions, no excuses.
Test Target: $ARGUMENTS
The standard is simple: all tests pass when you're done.
If a test fails, there are only two acceptable responses:
- Fix it — resolve the root cause and make it pass
- Escalate with evidence — if truly unfixable (external service down, infrastructure needed), explain exactly what's needed per reference/failure-investigation.md
MECE Test Coverage Principle
Tests must be Mutually Exclusive, Collectively Exhaustive (MECE):
- Mutually Exclusive — each behavior is tested in exactly one place. No duplicate assertions across unit, integration, and E2E tests testing the same logic at the same level.
- Collectively Exhaustive — every code path, branch, and edge case has a test. No gaps in coverage.
When evaluating or writing tests, flag violations:
More from rsmdt/the-startup
specify-requirements
Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on requirements.md files in .start/specs/. Includes validation checklist, iterative cycle pattern, and multi-angle review process.
121review
Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
57analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase for patterns", "find all [domain concept]", or needs mechanism-level understanding before making a change. Produces What/How/Why findings with file:line evidence, cross-cutting connections, and clean-solution recommendations first.
57specify
Create a comprehensive specification from a brief description. Manages specification workflow including directory creation, README tracking, and phase transitions.
54refactor
Refactor, simplify, or clean up code for improved maintainability without changing business logic
52specify-solution
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution.md files in .start/specs/. Includes validation checklist, consistency verification, and overlap detection.
50