| doc-type | refactor-plan | ||||||
|---|---|---|---|---|---|---|---|
| status | draft | ||||||
| related-issue | |||||||
| spec-path | docs/refactor-plans/drafts/{short-description}.md | ||||||
| last-updated-utc | YYYY-MM-DD HH:MM | ||||||
| semantic-links |
|
State in one or two sentences what the refactor achieves and why it is worthwhile. Focus on the quality property improved (readability, testability, maintainability, etc.).
Related artifact: {path/to/related/file-or-issue-spec.md}
Problem: Describe the current state and why it is a problem. Be specific — name files, line numbers, or function names where relevant.
Files:
{path/to/file.rs}
Change: Describe exactly what needs to change. Prefer concrete before/after examples over abstract descriptions.
Problem: ...
Files:
{path/to/file.rs}
Change: ...
| Order | Status | Item | Impact | Effort |
|---|---|---|---|---|
| 1 | [ ] | {Short title of item} | High | Trivial |
| 2 | [ ] | {Short title of item} | Medium | Low |