aid-development
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
When & Why to Use This Skill
This Claude skill streamlines the software development lifecycle by managing the implementation phase through a rigorous Test-Driven Development (TDD) framework. It ensures the delivery of high-quality, production-ready code by enforcing strict coding standards, generating comprehensive test suites, and facilitating seamless transitions from architectural planning to quality assurance.
Use Cases
- Feature Implementation: Executing the Red-Green-Refactor workflow to build robust software features that align strictly with technical specifications.
- Automated Testing: Generating unit, integration, and E2E test suites to ensure >80% code coverage and eliminate 'happy path' only testing.
- Code Quality Enforcement: Applying automated checks for DRY principles, type safety, and single-responsibility functions to maintain a clean codebase.
- Technical Documentation: Automatically generating file-level and function-level documentation (TSDoc/JSDoc) to improve codebase maintainability.
- Development Handoff: Utilizing phase-gate checklists to ensure code is reviewed, tested, and ready for QA deployment.
| name | aid-development |
|---|---|
| description | AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA. |
Development Phase Skill
Phase Overview
Purpose: Implement solution with quality built-in through TDD.
Entry: Tech spec completed, architecture defined, data models specified Exit: All features implemented, tests passing, code reviewed
Deliverables
- Production Code - Clean, documented, follows standards
- Test Suite - Unit, integration, E2E, >80% coverage
- Documentation - Code docs, API docs, README updates
TDD Workflow
RED (Write failing test) -> GREEN (Make pass) -> REFACTOR (Clean up) -> REPEAT
| Phase | Rule |
|---|---|
| RED | Test MUST fail first |
| GREEN | Minimal code to pass |
| REFACTOR | Tests still pass |
Common Pitfalls
| Pitfall | Fix |
|---|---|
| Skipping TDD | Write tests first |
| Test-specific code | No if is_test: in prod |
| Over-mocking | <20% mocking |
| Happy path only | Test errors & edge cases |
| Weak assertions | Assert exact values |
Code Quality
Required
- Single responsibility functions
- DRY - no copy-paste
- Type hints on public functions
- Meaningful names
- Error handling
Forbidden
- No
anytypes - No TODO/FIXME
- No commented-out code
- No test-specific branching
Documentation Standards
Every file must have:
File-Level
/**
* @file UserService.ts
* @description Purpose of file
* @related ./UserRepository.ts, ./UserController.ts
* @created 2025-12-15 by AID
*/
Function
/**
* Creates user account.
* @param data - User input
* @returns Created user
* @throws {ValidationError} If email invalid
* @related ../validators/emailValidator.ts
*/
Phase Gate Checklist
- All features per spec
- All tests passing
- Realistic test data
- Edge cases tested
- Code reviewed
- No test-specific logic in prod
- Documentation updated
Role Guidance
| Role | Focus |
|---|---|
| PM | Clarifications, validate intent |
| Dev | TDD, implement to pass tests |
| QA | Review coverage, test scenarios |
| Tech Lead | Code review, standards |
Handoff to QA
- Complete, tested code
- Test results + coverage
- Known issues (if any)
- Deployment instructions