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.
See how to installReview the instructions the agent will receive before you install.
Purpose: design the technical solution - a blueprint developers follow without ambiguity.
Entry: PRD approved, requirements clear, dependencies identified. Exit: tech spec complete, architecture documented, API contracts defined, data models specified.
| Pitfall | Fix |
|---|---|
| Over-engineering | Design for current needs |
| Missing error handling | Define errors upfront |
| Tight coupling | Design for testability |
| Ignoring non-functionals | Address performance, security |
| Unclear contracts | APIs unambiguous with examples |
Emit these 8 sections, in this order, with these exact headings:
# [Feature] Technical Specification
## 1. Overview
### Problem Summary
### Proposed Solution
### Key Decisions
| Decision | Choice | Rationale |
## 2. Architecture
### System Diagram
[Mermaid or image]
### Component Breakdown
| Component | Responsibility | Dependencies |
### Data Flow
## 3. API Design
### POST /api/[resource]
**Request:**
```json
{ "field": "type" }
```
**Response (200):**
```json
{ "id": "string" }
```
**Errors:**
| Code | Error | Description |
## 4. Data Model
### Entity: [Name]
| Field | Type | Constraints | Description |
## 5. Security
### Authentication
### Authorization
### Data Protection
## 6. Error Handling
| Scenario | Response | Recovery |
## 7. Non-Functional Requirements
| Requirement | Target | Measurement |
## 8. Risks & Mitigations
| Risk | Impact | Mitigation |
| Role | Focus |
|---|---|
| PM | Validate approach addresses requirements |
| Dev | Own spec, design for testability |
| QA | Review testability, integration points |
| Tech Lead | Review architecture, approve direction |
Save to: docs/tech-spec/YYYY-MM-DD-[feature].md
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.
Build an Atomic Design system from Figma style guides - extract tokens, create atoms/molecules/organisms/templates/pages as reusable component libraries. Use when building or extending a design system or component library.
The English summary is being prepared. Showing the original description.