Completion Report
A completion report is automatically generated when closing an increment with /specweave:done, documenting what was accomplished.
When Generated
Created automatically when:
- /specweave:done is called
- All quality gates pass
- PM Agent validates completion
Report Contents
Summary Section
## Completion Report: 0007-user-authentication
**Status**: Completed
**Duration**: 2.1 weeks (Nov 1 - Nov 15, 2025)
**Type**: Feature
Tasks Summary
## Task Summary
- **Total Tasks**: 42
- **Completed**: 42 (100%)
- **User Stories Completed**: 3/3
Test Coverage
## Test Coverage
| Type | Coverage | Target |
|------|----------|--------|
| Unit | 92% | 90% |
| Integration | 88% | 85% |
| E2E | 100% | 100% critical |
ADRs Created
## Architecture Decisions
- **ADR-0032**: JWT for authentication (Accepted)
- **ADR-0035**: bcrypt for password hashing (Accepted)
- **ADR-0036**: Token rotation strategy (Accepted)
Deliverables
## Deliverables
- `src/services/AuthService.ts` - Core authentication
- `src/middleware/jwt.ts` - Token validation
- `src/routes/auth.ts` - Auth endpoints
- `tests/auth.test.ts` - 45 test cases
Storage Location
.specweave/increments/0007-user-authentication/
├── spec.md
├── plan.md
├── tasks.md
├── metadata.json
└── reports/
└── completion-report.md ← Generated here
Living Docs Sync
The completion report is also synced to living documentation:
.specweave/docs/internal/increments/
└── 0007-user-authentication/
└── completion-report.md
Related
- /specweave:done - Close command
- Quality Gate - Validation checks
- Living Docs - Documentation system
- Increments - Work units