CI / changes (push) Successful in 8s
CI / commitlint (push) Has been skipped
CI / openapi (push) Has been skipped
CI / web (push) Successful in 31s
CI / go (push) Successful in 51s
CI / bird2 (push) Successful in 15s
CI / release (push) Successful in 3m48s
Enhanced the MaintenancePoliciesTab by integrating a schedule editor for maintenance policies. Users can now select schedule modes, input custom cron expressions, and dynamically update the schedule preview. This update improves the user interface and experience for managing maintenance schedules.
181 lines
4.8 KiB
Plaintext
181 lines
4.8 KiB
Plaintext
---
|
|
description: Basic archiving approach for Level 2 Simple Enhancement tasks
|
|
globs: "**/level2/**", "**/archive/**", "**/completion/**"
|
|
alwaysApply: false
|
|
---
|
|
|
|
# BASIC ARCHIVING FOR LEVEL 2 TASKS
|
|
|
|
> **TL;DR:** This document outlines a basic archiving approach for Level 2 (Simple Enhancement) tasks, ensuring that completed work is properly documented and knowledge is preserved with minimal overhead.
|
|
|
|
## 🔍 ARCHIVING OVERVIEW
|
|
|
|
Even for Level 2 tasks, proper archiving ensures that completed work is documented and knowledge is preserved. This basic archiving approach provides sufficient structure while maintaining efficiency.
|
|
|
|
## 📋 ARCHIVING PRINCIPLES
|
|
|
|
1. **Completion**: Clearly document what was completed
|
|
2. **Context**: Preserve the context of the enhancement
|
|
3. **Knowledge**: Capture key insights and lessons
|
|
4. **Findability**: Make archived information easy to find
|
|
5. **References**: Create cross-references to related work
|
|
|
|
## 📋 BASIC ARCHIVE STRUCTURE
|
|
|
|
```markdown
|
|
# Enhancement Archive: [Feature Name]
|
|
|
|
## Summary
|
|
[Brief summary of the enhancement]
|
|
|
|
## Date Completed
|
|
YYYY-MM-DD
|
|
|
|
## Key Files Modified
|
|
- [File path 1]
|
|
- [File path 2]
|
|
- [File path 3]
|
|
|
|
## Requirements Addressed
|
|
- [Requirement 1]
|
|
- [Requirement 2]
|
|
- [Requirement 3]
|
|
|
|
## Implementation Details
|
|
[Brief description of how the enhancement was implemented]
|
|
|
|
## Testing Performed
|
|
- [Test 1]
|
|
- [Test 2]
|
|
- [Test 3]
|
|
|
|
## Lessons Learned
|
|
- [Lesson 1]
|
|
- [Lesson 2]
|
|
- [Lesson 3]
|
|
|
|
## Related Work
|
|
- [Link to related task/enhancement 1]
|
|
- [Link to related task/enhancement 2]
|
|
|
|
## Notes
|
|
[Any additional information or context]
|
|
```
|
|
|
|
## 📋 ARCHIVE LOCATION
|
|
|
|
Store archives in an organized structure:
|
|
|
|
```
|
|
docs/
|
|
└── archive/
|
|
└── enhancements/
|
|
└── YYYY-MM/
|
|
├── feature-name-1.md
|
|
└── feature-name-2.md
|
|
```
|
|
|
|
## 📋 ARCHIVING PROCESS
|
|
|
|
Follow these steps to archive a Level 2 task:
|
|
|
|
1. **Prepare Archive Content**:
|
|
- Gather all relevant information
|
|
- Fill in the archive template
|
|
- Include all key implementation details
|
|
|
|
2. **Cross-Reference Creation**:
|
|
- Update tasks.md with link to archive
|
|
- Add reference in progress.md
|
|
- Update activeContext.md with next focus
|
|
|
|
3. **File Creation and Storage**:
|
|
- Create appropriate directory if needed
|
|
- Save archive file with descriptive name
|
|
- Ensure file follows naming convention
|
|
|
|
4. **Final Verification**:
|
|
- Check archive for completeness
|
|
- Verify all cross-references
|
|
- Ensure all links are working
|
|
|
|
## 📋 CROSS-REFERENCE FORMAT
|
|
|
|
When creating cross-references:
|
|
|
|
1. **In tasks.md**:
|
|
```markdown
|
|
## Completed Enhancements
|
|
- [X] [Feature Name] (YYYY-MM-DD) - [Archive Link](../docs/archive/enhancements/YYYY-MM/feature-name.md)
|
|
```
|
|
|
|
2. **In progress.md**:
|
|
```markdown
|
|
## Completed Milestones
|
|
- [Feature Name] enhancement completed on YYYY-MM-DD. See [archive entry](../docs/archive/enhancements/YYYY-MM/feature-name.md).
|
|
```
|
|
|
|
3. **In activeContext.md**:
|
|
```markdown
|
|
## Recently Completed
|
|
- [Feature Name] enhancement is now complete. Archive: [link](../docs/archive/enhancements/YYYY-MM/feature-name.md)
|
|
|
|
## Current Focus
|
|
- Moving to [Next Task Name]
|
|
```
|
|
|
|
## 📋 ARCHIVING VERIFICATION CHECKLIST
|
|
|
|
```
|
|
✓ ARCHIVE VERIFICATION
|
|
- Archive content complete? [YES/NO]
|
|
- Archive properly stored? [YES/NO]
|
|
- Cross-references created? [YES/NO]
|
|
- tasks.md updated? [YES/NO]
|
|
- progress.md updated? [YES/NO]
|
|
- activeContext.md updated? [YES/NO]
|
|
|
|
→ If all YES: Archiving complete
|
|
→ If any NO: Complete archiving process
|
|
```
|
|
|
|
## 📋 MINIMAL MODE ARCHIVING
|
|
|
|
For minimal mode, use this format:
|
|
|
|
```
|
|
✓ ARCHIVE: [Feature Name]
|
|
✓ DATE: YYYY-MM-DD
|
|
✓ FILES: [Key files changed]
|
|
✓ SUMMARY: [One-sentence summary]
|
|
✓ LESSONS: [Key takeaway]
|
|
✓ REFS: [tasks.md, progress.md, activeContext.md]
|
|
```
|
|
|
|
## 🔄 INTEGRATION WITH MEMORY BANK
|
|
|
|
Archiving integrates with Memory Bank:
|
|
|
|
```mermaid
|
|
graph TD
|
|
Archive["Enhancement<br>Archive"] --> TasksUpdate["Update<br>tasks.md"]
|
|
Archive --> ProgressUpdate["Update<br>progress.md"]
|
|
Archive --> ContextUpdate["Update<br>activeContext.md"]
|
|
|
|
TasksUpdate & ProgressUpdate & ContextUpdate --> CrossLinks["Create<br>Cross-Links"]
|
|
CrossLinks --> Verify["Verify<br>References"]
|
|
```
|
|
|
|
## 🚨 KNOWLEDGE PRESERVATION PRINCIPLE
|
|
|
|
Remember:
|
|
|
|
```
|
|
┌─────────────────────────────────────────────────────┐
|
|
│ Archive files are a VALUABLE KNOWLEDGE RESOURCE. │
|
|
│ Take care to preserve insights and lessons that │
|
|
│ will benefit future work. │
|
|
└─────────────────────────────────────────────────────┘
|
|
```
|
|
|
|
This ensures that knowledge is preserved and can be referenced in the future. |