@caddis/cli 0.4.2 → 0.4.3
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.
|
@@ -70,6 +70,7 @@
|
|
|
70
70
|
| Skill | Path | When to Use |
|
|
71
71
|
|-------|------|-------------|
|
|
72
72
|
| Add Rules | `add-rules/` | Create canonical rules for ANY folder — write <folder>/AGENTS.md (from the folder template) + a <folder>/CLAUDE.md @import shim. For folders the stack-map generator doesn't cover. |
|
|
73
|
+
| Catchup | `catchup/` | Where were we? A quick list of what this session was doing and what is still open |
|
|
73
74
|
| Digress | `digress/` | Park the current workstream on the stack and switch to a new task — without losing the original |
|
|
74
75
|
| Excalidraw Db | `excalidraw-db/` | Turn a SQL artifact into an Excalidraw diagram for a design review / ARB pack / slide — higher-level, drag-the-boxes format |
|
|
75
76
|
| Feature Plan | `feature-plan/` | Create a phased, TDD-structured implementation plan that acts as the durable spine for multi-session work |
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: catchup
|
|
3
|
+
description: Where were we? A quick list of what this session was doing and what is still open
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# /catchup — where are we?
|
|
7
|
+
|
|
8
|
+
Answer one question: **what were we doing, and what is still open?**
|
|
9
|
+
|
|
10
|
+
Not named `/recap` on purpose — Claude Code has a built-in `/recap` that produces a one-line
|
|
11
|
+
session summary. This is the list version, and two commands whose names differ by nothing would
|
|
12
|
+
be a coin toss every time.
|
|
13
|
+
|
|
14
|
+
## Read these, in this order, and stop as soon as you can answer
|
|
15
|
+
|
|
16
|
+
1. **`.caddis/session-state.md`** — the primary source. The `Stop` hook rewrites it at the end of
|
|
17
|
+
every turn, so it is current even when the session ended abruptly and nobody ran `/handoff`.
|
|
18
|
+
It holds the last real request, the task list with statuses, and the files touched.
|
|
19
|
+
2. **`.caddis/relay.md`** — only refreshed by `/handoff`, so it may be days behind, but it carries
|
|
20
|
+
what the state file cannot: the agreed **next step** and the open blockers.
|
|
21
|
+
3. **The current turn's own context**, if this session has already done work. What you have done
|
|
22
|
+
since the last Stop is newer than both files, and neither knows about it.
|
|
23
|
+
|
|
24
|
+
Compare the timestamps rather than assuming. If `relay.md` is newer, a handoff ran and its "Next
|
|
25
|
+
step" is the authority. If `session-state.md` is newer, work happened after the last handoff and
|
|
26
|
+
the relay's next step may already be done.
|
|
27
|
+
|
|
28
|
+
**A missing file is not an error.** A repo with neither has simply not run a caddis session yet —
|
|
29
|
+
say that in one line and stop.
|
|
30
|
+
|
|
31
|
+
## What to report
|
|
32
|
+
|
|
33
|
+
Keep it short enough to read at a glance. Roughly:
|
|
34
|
+
|
|
35
|
+
- **One line on where we are** — the workstream, and whether it is mid-flight or at a clean stop.
|
|
36
|
+
- **In-progress and pending items**, as a short list. Mark anything blocked, and on what.
|
|
37
|
+
- **The next step**, if one is recorded. Say which file it came from.
|
|
38
|
+
- **Uncommitted work**, if `git status` is dirty — this is the thing most likely to be lost, and
|
|
39
|
+
the state file does not track it. Check it; do not assume clean.
|
|
40
|
+
|
|
41
|
+
Leave out anything already done unless the user asks. "What is finished" is a different question
|
|
42
|
+
from "where are we", and the completed list is usually the longest part of both files.
|
|
43
|
+
|
|
44
|
+
## Say plainly when the answer is thin
|
|
45
|
+
|
|
46
|
+
If the state file has no tasks and no last request, the honest answer is "the last session did not
|
|
47
|
+
record anything specific" — not a paragraph assembled from file names. A recap the user cannot act
|
|
48
|
+
on is worse than one sentence admitting there is nothing to recap.
|
|
49
|
+
|
|
50
|
+
## When the user wants more than a list
|
|
51
|
+
|
|
52
|
+
- To **reopen** the actual conversation rather than read about it: `claude --continue` in this
|
|
53
|
+
folder, or `claude --resume` to pick an older session. Mention this only if the recap is thin,
|
|
54
|
+
or if they ask for detail the files do not hold.
|
|
55
|
+
- To **write** a durable resume doc rather than read one: `/caddis:handoff`.
|
|
56
|
+
- To **pop a parked workstream** off the digress stack: `/caddis:resume`. That is a different
|
|
57
|
+
mechanism — it restores work deliberately set aside, not the last session's state.
|
package/bundles/manifest.json
CHANGED
package/package.json
CHANGED