narejeno
This commit is contained in:
125
.agent/workflows/auto-update-tasks.md
Normal file
125
.agent/workflows/auto-update-tasks.md
Normal file
@@ -0,0 +1,125 @@
|
||||
# 📋 Workflow: Automatic TASKS.md Updates
|
||||
|
||||
## 🎯 Purpose
|
||||
Automatically update TASKS.md whenever new features are implemented.
|
||||
|
||||
---
|
||||
|
||||
## ✅ Standard Workflow
|
||||
|
||||
### **When Implementing a New Feature:**
|
||||
|
||||
1. **Implement the feature** (write code)
|
||||
2. **Test the feature** (verify it works)
|
||||
3. **Update TASKS.md immediately:**
|
||||
- Mark the task as `[x]` (completed)
|
||||
- Add date: `✅ DD.MM.YYYY`
|
||||
- Add any relevant notes
|
||||
|
||||
### **Example:**
|
||||
|
||||
**Before:**
|
||||
```markdown
|
||||
- [ ] **Fishing System**
|
||||
- [ ] Fishing rod crafting
|
||||
- [ ] Fishing minigame
|
||||
```
|
||||
|
||||
**After:**
|
||||
```markdown
|
||||
- [x] **Fishing System** ✅ 12.12.2025
|
||||
- [x] Fishing rod crafting
|
||||
- [x] Fishing minigame
|
||||
- **File**: `src/systems/FishingSystem.js`
|
||||
- **Lines**: 450
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔄 Automatic Update Process
|
||||
|
||||
### **Step 1: Implement Feature**
|
||||
```javascript
|
||||
// Create new system file
|
||||
class NewSystem {
|
||||
constructor(scene) {
|
||||
// Implementation
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### **Step 2: Integrate**
|
||||
```javascript
|
||||
// Add to index.html
|
||||
<script src="src/systems/NewSystem.js"></script>
|
||||
|
||||
// Add to GameScene.js
|
||||
this.newSystem = new NewSystem(this);
|
||||
```
|
||||
|
||||
### **Step 3: Update TASKS.md**
|
||||
```markdown
|
||||
- [x] **New Feature** ✅ 12.12.2025
|
||||
- [x] Core functionality
|
||||
- [x] Integration complete
|
||||
- **Status**: Production ready
|
||||
```
|
||||
|
||||
### **Step 4: Document**
|
||||
Create summary in `docs/` if needed.
|
||||
|
||||
---
|
||||
|
||||
## 📝 Template for New Features
|
||||
|
||||
```markdown
|
||||
- [x] **[Feature Name]** ✅ [Date]
|
||||
- [x] [Sub-feature 1]
|
||||
- [x] [Sub-feature 2]
|
||||
- [x] [Sub-feature 3]
|
||||
- **File**: `src/systems/[FileName].js`
|
||||
- **Lines**: [Number]
|
||||
- **Status**: [Production Ready / In Progress / Testing]
|
||||
- **Notes**: [Any important notes]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Commitment
|
||||
|
||||
**From now on, I will:**
|
||||
1. ✅ Update TASKS.md immediately after implementing features
|
||||
2. ✅ Mark completed tasks with `[x]` and date
|
||||
3. ✅ Add file locations and line counts
|
||||
4. ✅ Include status and notes
|
||||
5. ✅ Keep documentation synchronized
|
||||
|
||||
---
|
||||
|
||||
## 📊 Benefits
|
||||
|
||||
- **Always up-to-date** task list
|
||||
- **Clear progress tracking**
|
||||
- **Easy to see what's done**
|
||||
- **Better project management**
|
||||
- **Transparent development**
|
||||
|
||||
---
|
||||
|
||||
## 🔍 Review Process
|
||||
|
||||
**At end of each session:**
|
||||
1. Review TASKS.md for accuracy
|
||||
2. Verify all completed tasks are marked
|
||||
3. Update statistics
|
||||
4. Create session summary
|
||||
|
||||
---
|
||||
|
||||
**Status**: ✅ **ACTIVE**
|
||||
**Effective From**: 2025-12-12 23:20
|
||||
**Applies To**: All future development
|
||||
|
||||
---
|
||||
|
||||
**This workflow ensures TASKS.md is always current and accurate!** 📋✨
|
||||
Reference in New Issue
Block a user