@wipcomputer/wip-repo-init 1.9.39 → 1.9.41
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
|
@@ -1,63 +0,0 @@
|
|
|
1
|
-
# todos/
|
|
2
|
-
|
|
3
|
-
One todo file per person or agent. Three sections per file: To Do, Done, Deprecated.
|
|
4
|
-
|
|
5
|
-
## What This Folder Is
|
|
6
|
-
|
|
7
|
-
Todos that are specific to this repo. Each person or agent who works on this repo gets one file. The file tracks what they need to do, what they've done, and what got dropped.
|
|
8
|
-
|
|
9
|
-
For cross-repo work or bigger items, use GitHub Issues. Todos here are for repo-scoped tasks that don't need the overhead of an issue.
|
|
10
|
-
|
|
11
|
-
## Files
|
|
12
|
-
|
|
13
|
-
One file per person/agent. Name it `[Name]-todo.md`.
|
|
14
|
-
|
|
15
|
-
Example:
|
|
16
|
-
|
|
17
|
-
| File | Who |
|
|
18
|
-
|------|-----|
|
|
19
|
-
| `Parker-todo.md` | Parker (human tasks: reviews, credentials, approvals) |
|
|
20
|
-
| `CC-Mini-todo.md` | Claude Code on Mac Mini (code, builds, deploys) |
|
|
21
|
-
|
|
22
|
-
Create the file when that person/agent first has work to do. No empty placeholder files.
|
|
23
|
-
|
|
24
|
-
## File Format
|
|
25
|
-
|
|
26
|
-
```markdown
|
|
27
|
-
# [Name] Todos
|
|
28
|
-
|
|
29
|
-
**Last updated:** YYYY-MM-DD
|
|
30
|
-
|
|
31
|
-
## To Do
|
|
32
|
-
|
|
33
|
-
- [ ] Task description
|
|
34
|
-
- [ ] Task description (blocked by: reason)
|
|
35
|
-
|
|
36
|
-
## Done
|
|
37
|
-
|
|
38
|
-
- [x] Task description (YYYY-MM-DD)
|
|
39
|
-
- [x] Task description (YYYY-MM-DD)
|
|
40
|
-
|
|
41
|
-
## Deprecated
|
|
42
|
-
|
|
43
|
-
- ~~Task description~~ ... reason. (YYYY-MM-DD)
|
|
44
|
-
```
|
|
45
|
-
|
|
46
|
-
## Rules
|
|
47
|
-
|
|
48
|
-
- **Never delete anything.** Items move between sections, never off the page.
|
|
49
|
-
- **To Do** ... work that needs to happen.
|
|
50
|
-
- **Done** ... completed work. Check the box, add the date.
|
|
51
|
-
- **Deprecated** ... planned but no longer needed. Strikethrough, add the reason and date. Not the same as Done. Done means it shipped. Deprecated means the requirement changed.
|
|
52
|
-
- **Update the date** at the top of the file every time you edit it.
|
|
53
|
-
- **One file per person/agent.** No dated files, no subfolders, no inboxes.
|
|
54
|
-
- **Blocked items** stay in To Do with a `(blocked by: reason)` note. Don't move them to a separate section.
|
|
55
|
-
|
|
56
|
-
## When to Use Todos vs GitHub Issues
|
|
57
|
-
|
|
58
|
-
| Use | When |
|
|
59
|
-
|-----|------|
|
|
60
|
-
| **Todo file** | Quick tasks, repo-scoped work, things you'll do this session or this week |
|
|
61
|
-
| **GitHub Issue** | Bugs, feature requests, cross-repo work, things that need tracking or discussion |
|
|
62
|
-
|
|
63
|
-
Both is fine. File an issue AND add a todo that references it. The todo is your personal checklist. The issue is the team's record.
|