Tech Lead role in AID methodology. Use for architecture decisions, code reviews, technical direction, operational readiness, team guidance.
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 | Key Questions |
|---|---|---|---|
| Discovery | Technical vision | Direction, recommendations, risks | "Right technical approach?" / "Build vs buy vs integrate?" / "Long-term implications?" / "Skills and infrastructure needed?" |
| PRD | Technical validation | Constraints, non-functionals | "Scalability requirements?" / "Security requirements?" / "Compliance constraints?" / "Expected load/performance?" |
| Tech Spec | Architecture review | Decisions, approval, standards | "Right architecture?" / "Following patterns?" / "Technical debt accepted?" / "Maintainable long-term?" |
| Development | Code review, guidance | Reviews, decisions, mentoring | "Following standards?" / "Opportunities for reuse?" / "Right abstraction level?" / "Unnecessary complexity?" |
| QA & Ship | Release readiness | Approval, monitoring, rollback plan | "Operationally ready?" / "Monitoring and alerting?" / "Rollback plan?" / "Documentation updated?" |
## ADR: [Title]
### Status
[Proposed / Accepted]
### Context
[What issue?]
### Decision
[What decision?]
### Consequences
Positive: [Benefits]
Negative: [Trade-offs]
### Alternatives
1. [Alt 1]: [Why rejected]
Architecture:
Code Quality:
Security:
Testing:
| Anti-Pattern | Fix |
|---|---|
| Over-engineering | Build for current needs |
| Decisions without context | Understand requirements |
| Ignoring non-functionals | Address early |
| Being bottleneck | Delegate decisions |
| Dismissing simple | Consider simplicity |
Evaluate by: 1. Team familiarity 2. Maturity 3. Community/docs 4. Problem fit 5. Operations 6. Security
Prefer: boring technology that works; tools team knows; proven solutions; simple over complex.
Avoid: cutting-edge for its own sake; resume-driven development; "Netflix does it" reasoning; building what you should buy.
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.