27 lines
587 B
Markdown
27 lines
587 B
Markdown
# [Title]
|
|
|
|
<purpose>
|
|
Brief description of what needs to be accomplished and why.
|
|
</purpose>
|
|
|
|
<requirements>
|
|
- Requirement 1
|
|
- Requirement 2
|
|
- Requirement 3
|
|
</requirements>
|
|
|
|
<implementation>
|
|
High-level technical approach and key decisions. Avoid specific code details.
|
|
|
|
Keep this concise - focus on architecture, patterns, and important constraints rather than detailed implementation.
|
|
|
|
If code examples are necessary, keep them minimal and illustrative only.
|
|
</implementation>
|
|
|
|
<testing>
|
|
How to verify the implementation:
|
|
- Test scenario 1
|
|
- Test scenario 2
|
|
- Test scenario 3
|
|
</testing>
|