teamshare-bridge 0.2.4 → 0.2.5
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
|
@@ -57,17 +57,24 @@ Rules that are not optional:
|
|
|
57
57
|
6. Check off subtasks (`update_subtask done: true`) and update
|
|
58
58
|
`progress.md`/`plan.md` via `update_document_note` as you go — the human
|
|
59
59
|
watches the app.
|
|
60
|
-
7.
|
|
60
|
+
7. **Checklist items — ALWAYS list first.** Before creating checklist items,
|
|
61
|
+
call `list_checklist_items` (pass `taskId` or `subtaskId`) to see what
|
|
62
|
+
already exists. Use `update_checklist_item` with the existing ID to toggle
|
|
63
|
+
done/rename — do NOT create duplicates. Only call `create_checklist_item`
|
|
64
|
+
for genuinely new items. The `get_task` response also includes
|
|
65
|
+
`checklistItems` for task-level items, and `list_subtasks` includes them
|
|
66
|
+
per subtask.
|
|
67
|
+
8. When you make an architecture decision worth keeping, add it to `docs/adr`
|
|
61
68
|
as `ADR-<n>-<title>.md` (short: context → decision → consequences).
|
|
62
|
-
|
|
69
|
+
9. Blocked? Use `ask_human` and include a pointer to the relevant note.
|
|
63
70
|
|
|
64
71
|
### DONE (before closing)
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
72
|
+
10. **Move the task to `in_review`** via `update_task` — signals the human
|
|
73
|
+
to review your work.
|
|
74
|
+
11. Write `summary.md`: what you built, why, how it maps to the plan, links to
|
|
68
75
|
related docs, follow-ups.
|
|
69
|
-
|
|
70
|
-
|
|
76
|
+
12. Post the closing comment referencing the summary doc.
|
|
77
|
+
13. Never leave a task without `plan.md` + `summary.md` notes.
|
|
71
78
|
|
|
72
79
|
## Task status progression (guidance)
|
|
73
80
|
|