dev

Step 4: API integration tests - requires GATE 3 passed

Step 3: Backend unit tests - requires GATE 2 passed

Step 2: Backend implementation - requires GATE 1 passed

Step 8: E2E Integration with real API - FINAL VALIDATION

Step 7: E2E tests with mocked API - requires GATE 6 passed

Deep verification that feature/module works end-to-end according to spec

Step 6: Frontend unit tests - requires GATE 5 passed

Step 5: Frontend implementation - requires GATE 4 passed

Project health dashboard - overall status, coverage, issues

Initialize project, analyze existing code, identify gaps in 8-step workflow

Capture learnings from mistakes, issues, or discoveries

Pre-implementation checklist - verify everything is ready before coding

Resume work from checkpoint after context compaction or new session

Step 1: Write specification with strict template - GATE 1 validation required

Smart project status - identifies next step with minimal token usage

Post-implementation review. Checks alignment with concepts, finds improvements, asks for decisions. Always runs after implementation is complete. <example> User: Review the user registration implementation Agent: I'll check fail-fast, reusability, clean code, and spec alignment. Then present improvements for your decision. </example>

Validates exit criteria for each development step. Uses step-specific gate skill. Scans for code quality issues. BLOCKS progress if any criterion fails. <example> User: Validate Gate 3 for user-registration Agent: I'll load gate-3-backend-unit skill, check all criteria, and scan for quality issues. </example>

Implements code following project patterns. Searches existing code first, never duplicates. For frontend, follows ux-patterns skill. <example> User: Implement backend for user registration Agent: I'll search existing code first, then implement following project.md patterns. </example>

QA validation against spec requirements. Traces flows, verifies steps, finds gaps. Ensures login → expected result has no missing steps. <example> User: QA validate user registration Agent: I'll trace the registration flow step by step, verify each against spec, and identify any missing steps or gaps. </example>

Writes complete specifications using PLAN MODE. Never writes spec in one pass. Discovers → Clarifies → Designs → Confirms → Compiles. <example> User: Write a spec for user registration Agent: I'll first discover existing patterns, then ask clarifying questions, design the API and UI with your confirmation, and finally compile the full spec. </example>

Writes tests following type-specific test-patterns skills. Traces tests to spec requirements. Uses strong assertions, fixtures, and proper mocking. <example> User: Write backend unit tests for user-registration Agent: I'll load the spec, create test checklist, then write tests following test-patterns-unit skill. </example>