ccsetup 1.0.8 → 1.0.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
package/template/CLAUDE.md
CHANGED
|
@@ -68,6 +68,14 @@ After adding the agents you want to in `./claude/agents` folder, setup the workf
|
|
|
68
68
|
|
|
69
69
|
See @tickets/README.md for ticket format and management approach
|
|
70
70
|
|
|
71
|
+
### Ticket Management
|
|
72
|
+
- **Ticket List**: Maintain @tickets/ticket-list.md as a centralized index of all tickets
|
|
73
|
+
- **Update ticket-list.md** whenever you:
|
|
74
|
+
- Create a new ticket (add to appropriate priority section)
|
|
75
|
+
- Change ticket status (update emoji and move if completed)
|
|
76
|
+
- Complete a ticket (move to completed section with date)
|
|
77
|
+
- **Status Emojis**: 🔴 Todo | 🟡 In Progress | 🟢 Done | 🔵 Blocked | ⚫ Cancelled
|
|
78
|
+
|
|
71
79
|
## Plans
|
|
72
80
|
|
|
73
81
|
See @plans/README.md for planning documents and architectural decisions
|
|
@@ -87,6 +95,7 @@ Before starting any task:
|
|
|
87
95
|
3. **Create planning documents**: Before implementing any code or features, create a markdown file documenting the approach
|
|
88
96
|
4. **Use plans directory**: When discussing ideas or next steps, create timestamped files in the plans directory (e.g., `plans/next-steps-YYYY-MM-DD-HH-MM-SS.md`) to maintain a record of decisions
|
|
89
97
|
5. **No code comments**: Never add comments to any code you write - code should be self-documenting
|
|
98
|
+
6. **Maintain ticket list**: Always update @tickets/ticket-list.md when creating, updating, or completing tickets to maintain a clear project overview
|
|
90
99
|
|
|
91
100
|
## Additional Notes
|
|
92
101
|
|
|
@@ -0,0 +1,79 @@
|
|
|
1
|
+
# Ticket List
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
This file maintains a centralized list of all tickets in the project. Update this file whenever you create, update, or complete tickets.
|
|
5
|
+
|
|
6
|
+
**Note**: Individual ticket files are stored in this same `/tickets` folder with the naming convention `TICKET-XXX-description.md` (e.g., `TICKET-001-user-authentication.md`, `TICKET-002-api-integration.md`)
|
|
7
|
+
|
|
8
|
+
## Ticket Status Legend
|
|
9
|
+
- 🔴 **Todo** - Not started
|
|
10
|
+
- 🟡 **In Progress** - Currently being worked on
|
|
11
|
+
- 🟢 **Done** - Completed
|
|
12
|
+
- 🔵 **Blocked** - Waiting on dependencies or external factors
|
|
13
|
+
- ⚫ **Cancelled** - No longer needed
|
|
14
|
+
|
|
15
|
+
## Active Tickets
|
|
16
|
+
|
|
17
|
+
### High Priority
|
|
18
|
+
_No high priority tickets yet_
|
|
19
|
+
|
|
20
|
+
### Medium Priority
|
|
21
|
+
_No medium priority tickets yet_
|
|
22
|
+
|
|
23
|
+
### Low Priority
|
|
24
|
+
_No low priority tickets yet_
|
|
25
|
+
|
|
26
|
+
## Completed Tickets
|
|
27
|
+
_No completed tickets yet_
|
|
28
|
+
|
|
29
|
+
## Cancelled/Archived Tickets
|
|
30
|
+
_No cancelled tickets yet_
|
|
31
|
+
|
|
32
|
+
---
|
|
33
|
+
|
|
34
|
+
## How to Use This File
|
|
35
|
+
|
|
36
|
+
1. **When creating a new ticket**:
|
|
37
|
+
- Create the ticket file in `/tickets` folder (e.g., `TICKET-001-user-authentication.md`)
|
|
38
|
+
- Use the template structure from `/tickets/README.md` for the ticket content
|
|
39
|
+
- Add it to the appropriate priority section in this list
|
|
40
|
+
- Include ticket number, title, and status emoji
|
|
41
|
+
- Link to the full ticket file
|
|
42
|
+
|
|
43
|
+
2. **Format for ticket entries**:
|
|
44
|
+
```
|
|
45
|
+
- 🔴 [TICKET-001](./TICKET-001-user-authentication.md) - User Authentication System
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
3. **File organization**:
|
|
49
|
+
```
|
|
50
|
+
tickets/
|
|
51
|
+
├── ticket-list.md # This file (centralized index)
|
|
52
|
+
├── TICKET-001-user-auth.md # Individual ticket file
|
|
53
|
+
├── TICKET-002-api-docs.md # Individual ticket file
|
|
54
|
+
└── TICKET-003-testing.md # Individual ticket file
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
4. **When updating ticket status**:
|
|
58
|
+
- Change the status emoji
|
|
59
|
+
- Move completed tickets to "Completed Tickets" section
|
|
60
|
+
- Add completion date for completed tickets
|
|
61
|
+
|
|
62
|
+
4. **Example of a populated list**:
|
|
63
|
+
```markdown
|
|
64
|
+
### High Priority
|
|
65
|
+
- 🟡 [TICKET-001](./TICKET-001-user-authentication.md) - User Authentication System
|
|
66
|
+
- 🔴 [TICKET-003](./TICKET-003-api-rate-limiting.md) - Implement API Rate Limiting
|
|
67
|
+
|
|
68
|
+
### Medium Priority
|
|
69
|
+
- 🔵 [TICKET-002](./TICKET-002-email-notifications.md) - Email Notification Service (blocked: waiting for SMTP credentials)
|
|
70
|
+
|
|
71
|
+
### Completed Tickets
|
|
72
|
+
- 🟢 [TICKET-000](./TICKET-000-project-setup.md) - Initial Project Setup (Completed: 2024-01-15)
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
5. **Best Practices**:
|
|
76
|
+
- Keep this file updated in real-time
|
|
77
|
+
- Review weekly to ensure accuracy
|
|
78
|
+
- Use consistent naming conventions
|
|
79
|
+
- Archive old completed tickets quarterly
|