unavlab
31 lines
796 B
Markdown
31 lines
796 B
Markdown
# Research: [task name]
|
|
**Date:** YYYY-MM-DD
|
|
**Task size:** S | M | L
|
|
|
|
## Current Architecture
|
|
How it works now (key modules, data flow)
|
|
|
|
## Affected Areas
|
|
Which files/modules will change and why
|
|
|
|
| # | File/Module | Why affected |
|
|
|---|-------------|-------------|
|
|
| 1 | ... | ... |
|
|
|
|
## Codebase Patterns
|
|
Conventions in use (style, state management, API patterns, testing approach)
|
|
|
|
## Risks and Constraints
|
|
What could break, edge cases, performance concerns
|
|
|
|
## Open Questions
|
|
What needs clarification from user or further research
|
|
|
|
## Best Practices Found
|
|
(if WebSearch was used — key findings and links)
|
|
|
|
## Conclusion & Recommendation
|
|
**Recommended approach:** [which solution is best and why]
|
|
**Key reasons:** [2-3 concrete justifications]
|
|
**Risks of this approach:** [what to watch for]
|