Developer role in AID methodology. Use for implementation, debugging, technical design, TDD workflow, code review.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
| Phase | Focus | Output |
|---|---|---|
| Discovery | Feasibility | Risk notes, complexity |
| PRD | Requirements clarity | Questions, edge cases |
| Tech Spec | Architecture | Spec, APIs, data models |
| Development | Implementation | Code, tests, docs |
| QA & Ship | Bug fixes | Fixes, deployment docs |
RED (Write failing test) -> GREEN (Minimal code) -> REFACTOR (Clean up) -> REPEAT
NO FIXES WITHOUT ROOT CAUSE.
If 3+ fixes failed -> Stop, question architecture.
Validate at EVERY layer:
| Layer | Purpose |
|---|---|
| Entry Point | Reject invalid at boundary |
| Business Logic | Validate for operation |
| Environment Guards | Block dangerous ops |
| Debug Instrumentation | Log for forensics |
| Size | Action |
|---|---|
| < 200 | Ideal |
| 200-300 | Consider splitting |
| 300-400 | Split now |
| > 400 | Must refactor |
feature/
feature.controller.ts # HTTP (thin)
feature.service.ts # Business logic
feature.repository.ts # Data access
feature.types.ts # Types
feature.validation.ts # Validation
Must have: single responsibility, DRY code, type hints, meaningful names, error handling, files < 300 lines.
Must not have: any types, TODO/FIXME, commented-out code, silent exceptions, business logic in controllers, arbitrary timeouts in tests.
// Wrong
await sleep(100);
// Right
await waitFor(() => result !== undefined);
| Anti-Pattern | Fix |
|---|---|
| No TDD | Tests first |
| if is_test in prod | No test logic |
| Happy path only | Test errors |
| Over-mocking | Real dependencies |
| Guessing at fixes | Systematic debug |
| Large files | Split modules |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
The English summary is being prepared. Showing the original description.
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
The English summary is being prepared. Showing the original description.
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
The English summary is being prepared. Showing the original description.
AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.
The English summary is being prepared. Showing the original description.
AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.
The English summary is being prepared. Showing the original description.
AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.
The English summary is being prepared. Showing the original description.