{ID}:¶
ID: {ID} Status: Planned | In Progress | Complete Created: {YYYY-MM-DD} Updated: {YYYY-MM-DD} Priority: Critical | High | Medium | Low
URS References¶
| URS ID | Requirement | Impact |
|---|---|---|
| URS-{CTX}-001.{N} | {brief description} | New / Modified / Verified |
Implementation Progress¶
| Phase | Description | Status | Commit |
|---|---|---|---|
| 1 | {Phase 1 description} | Planned | — |
| 2 | {Phase 2 description} | Planned | — |
Summary¶
{1-3 paragraph description of what this requirement covers and why it matters.}
Phase 1:¶
Goal: {What this phase achieves} Status: Planned Estimated impact: {N new files, M modified}
1.1 {Layer} Changes¶
| File | Action | Description |
|---|---|---|
path/to/file |
Create / Modify / Delete | {what changes} |
1.2 Implementation Notes¶
{Captured during implementation: deviations from plan, lessons learned, actual impact.}
Phase 2:¶
{Same structure as Phase 1}
Dependency Graph¶
Risks and Considerations¶
- {Risk 1} — {mitigation}
- {Risk 2} — {mitigation}
Verification Plan¶
dotnet build— solution compiles without errorsdotnet test {relevant test project}— tests pass- {any other verification steps}
ID Pattern Reference¶
| Prefix | Use For | Example |
|---|---|---|
| SCHEMA-NNN | Database schema work | SCHEMA-001 |
| FEAT-NNN | New features | FEAT-001 |
| FIX-NNN | Bug fixes | FIX-001 |
| DEBT-NNN | Technical debt | DEBT-001 |
Gold Standard Reference¶
See SCHEMA-001 for a completed 7-phase requirement document.