@caddis/cli 0.4.113 → 0.4.115
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/bundles/antigravity-plugin/plugin.json +1 -1
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_exit.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_file_lock.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_frontmatter.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_redact.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_roadmap.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_rows.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_status.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_tidy.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_todo.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_workstreams.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_worktree_safety.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/caddis_coordinate.py +107 -1
- package/bundles/antigravity-plugin/scripts/caddis_guide.json +34 -7
- package/bundles/antigravity-plugin/scripts/caddis_stories.py +760 -0
- package/bundles/antigravity-plugin/skills/_registry.md +1 -0
- package/bundles/antigravity-plugin/skills/coordinate/SKILL.md +6 -2
- package/bundles/antigravity-plugin/skills/feature-plan/SKILL.md +15 -0
- package/bundles/antigravity-plugin/skills/implement/SKILL.md +5 -0
- package/bundles/antigravity-plugin/skills/stories/SKILL.md +50 -0
- package/bundles/manifest.json +2 -2
- package/dist/cli.js +207 -113
- package/dist/ui/assets/{Activity-B816JVqx.js → Activity-CITEjSUJ.js} +1 -1
- package/dist/ui/assets/Benchmarks-B2_1oerW.css +1 -0
- package/dist/ui/assets/Benchmarks-ChQoYa0P.js +1 -0
- package/dist/ui/assets/{Guide-CnL1DiTr.js → Guide-9Ob-m7gx.js} +1 -1
- package/dist/ui/assets/{Palette-BKM_A64G.js → Palette-CinCoveU.js} +1 -1
- package/dist/ui/assets/{RoadmapTab-DhC4-kqv.js → RoadmapTab-BeD4-8IU.js} +2 -2
- package/dist/ui/assets/{external-link-DagTFCsV.js → external-link-D_rks7KV.js} +1 -1
- package/dist/ui/assets/index-CFKn_GzG.js +231 -0
- package/dist/ui/index.html +1 -1
- package/package.json +1 -1
- package/dist/ui/assets/index-Bj5qA-fq.js +0 -226
|
@@ -109,6 +109,7 @@
|
|
|
109
109
|
| Ship Merge | `ship-merge/` | Merge an already-green, already-reviewed PR behind an explicit deploy-confirm, monitor the deploy, validate prod, then clean up the branch — only on green. |
|
|
110
110
|
| Ship Pr | `ship-pr/` | Open a reviewed PR for the current feature branch — rebase-safe push, PR create/update, monitor CI, STOP at green. Never merges, never deploys (that's /ship-merge). |
|
|
111
111
|
| Spawn Session | `spawn-session/` | Hand the WORK to a fresh session — generate the handover from the repo, then validate the successor by re-deriving its answers |
|
|
112
|
+
| Stories | `stories/` | Publish a plan's phases as development stories to the Jira Epic's Confluence page — one marked section per plan |
|
|
112
113
|
| Tdd | `tdd/` | Run a strict red-green-refactor TDD cycle for a unit of behavior |
|
|
113
114
|
| Ui Brief | `ui-brief/` | Design-first UI brief — lock the aesthetic before writing any code |
|
|
114
115
|
| Usage Review | `usage-review/` | Review local caddis usage over a window, surface prioritised recommendations, and apply config changes in one step |
|
|
@@ -231,8 +231,12 @@ and 7.3. While the queue is frozen (section 5 step 1), do steps 3.1 to 3.3 only.
|
|
|
231
231
|
9. Send `merge-warning <PR> <watched sha> in 2 min. Reply ack <PR> <sha> or hold.` to every live peer
|
|
232
232
|
that has a stake in this repo (design 7.3), and `queue set --repo <R> --pr <n> --state merging`. Send
|
|
233
233
|
`re-warn <PR> <sha>` after any coordinator restart and after any new head on a warned PR. Old acks do not count.
|
|
234
|
-
Stake test, run
|
|
235
|
-
|
|
234
|
+
Stake test, run at the warning (design 7.3a): run
|
|
235
|
+
`python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_coordinate.py" stake --repo <checkout>`. Warn every `STAKE`
|
|
236
|
+
peer and every peer the script does not list; warn no `NO-STAKE` peer unless the queue, the ledger or a
|
|
237
|
+
`ready`/`phase` message ties it to this repo. `STAKE-UNKNOWN` (exit 4): warn every live peer. The script
|
|
238
|
+
only decides by cwd; it never removes a stake that the queue, the ledger or a message gives. A peer has a
|
|
239
|
+
stake when ANY of these holds: its cwd is inside the checkout or one of its worktrees (for example under
|
|
236
240
|
`.worktrees/<repo>/`); the queue or the ledger lists a PR, branch or plan phase of that peer in this
|
|
237
241
|
repo; or it has sent `ready` or `phase` for this repo. Anything else is no stake. When the cwd is
|
|
238
242
|
unknown or you are unsure, the peer has a stake. A peer with no stake gets no warning and is not in
|
|
@@ -41,6 +41,8 @@ Absolute rules in this mode (they override everything below):
|
|
|
41
41
|
a bullet under `## Constraints & decisions` — never a question to the user.
|
|
42
42
|
- **Honor the caller's output path and slug** (falling back to `.caddis/plans/<feature-slug>.md`);
|
|
43
43
|
set `feature: <slug>` in the frontmatter to that slug.
|
|
44
|
+
- **Do not write `jira_epic` or `confluence_parent`** (Step 1b is interactive only). Add the assumption: no Jira
|
|
45
|
+
Epic or Confluence page was given (headless). Add both fields to publish the stories with `/caddis:stories`.
|
|
44
46
|
- **Always write the plan file, then end with exactly one fenced `json` highlights block** — nothing
|
|
45
47
|
after it:
|
|
46
48
|
```json
|
|
@@ -93,6 +95,15 @@ exactly what a phase's exit gate needs) and its `## Open questions` into `## Con
|
|
|
93
95
|
A headless pipeline that plans straight from a bare title while a complete PRD sits on disk is the
|
|
94
96
|
failure this closes.
|
|
95
97
|
|
|
98
|
+
## Step 1b — Jira Epic and Confluence page (interactive only)
|
|
99
|
+
Skip this step in headless mode. Ask the user one self-contained AskUserQuestion with these two questions:
|
|
100
|
+
- "Is there a Confluence HLA or HLSA page for this project? Give its URL."
|
|
101
|
+
- "Is there a Jira Epic for this work? Give its key, for example ABC-123."
|
|
102
|
+
|
|
103
|
+
Write `confluence_parent: <URL>` and `jira_epic: <KEY>` into the plan frontmatter only for the answers the user
|
|
104
|
+
gives. With both fields, `/caddis:stories` publishes each phase as a development story to the Confluence page
|
|
105
|
+
titled with the Epic key, and `/caddis:implement` syncs it after each Tracker update.
|
|
106
|
+
|
|
96
107
|
## Step 2 — Design phases
|
|
97
108
|
Break the work into **independently completable** phases (~30–60 min each, clear exit gate). Each phase
|
|
98
109
|
follows the harness loop: **RED → GREEN → REFACTOR → VERIFY → COMMIT**. Front-load risk.
|
|
@@ -263,6 +274,8 @@ Create `.caddis/plans/` if it doesn't exist.
|
|
|
263
274
|
type: plan
|
|
264
275
|
status: draft
|
|
265
276
|
feature: <feature-slug>
|
|
277
|
+
jira_epic: <KEY>
|
|
278
|
+
confluence_parent: <URL of the HLA or HLSA page>
|
|
266
279
|
creation-agent: caddis
|
|
267
280
|
Original Author: Claude Code
|
|
268
281
|
Creation Date: <YYYY-MM-DDTHH:MM:SSZ>
|
|
@@ -423,6 +436,8 @@ Three rules: one attempt, one review.
|
|
|
423
436
|
| 1 | M1 | mid | claude | not started | — | — | |
|
|
424
437
|
```
|
|
425
438
|
|
|
439
|
+
`jira_epic` and `confluence_parent`: Only when Step 1b gave them. Leave out a line that has no answer.
|
|
440
|
+
|
|
426
441
|
Status words (one vocabulary, `scripts/caddis_status.py`): done is `done`, `merged`, `✅`, `☑`, `✔` or `✓`;
|
|
427
442
|
`in progress`, `blocked` and `moved` name the other states; anything else (`not started`, `☐`) is to do. A cell
|
|
428
443
|
that says `pending` is never done.
|
|
@@ -369,6 +369,11 @@ report — do not redo completed work.
|
|
|
369
369
|
ACTUALLY ran on (not the planned one — see Step 1), and add a one-line note. This is what lets a
|
|
370
370
|
future session (or the runner) see progress. Commit the Tracker update with the phase (or as a tiny
|
|
371
371
|
follow-up commit) — it lives in the plan file, which is fine to commit on this branch.
|
|
372
|
+
- **SYNC THE STORIES** — only when the plan frontmatter has both `jira_epic` and `confluence_parent`. After
|
|
373
|
+
the Tracker commit, run `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_stories.py" sync --plan <plan path>`.
|
|
374
|
+
On exit 0, print nothing more. On any other exit, print one line
|
|
375
|
+
`WARN: stories sync exit <n> - <first output line>` and go on. The sync never stops, fails or blocks a
|
|
376
|
+
phase, and you do not retry it in that phase. Never print the Confluence token.
|
|
372
377
|
|
|
373
378
|
If a phase cannot be completed (a blocking gap the plan did not resolve, or a rule above would be
|
|
374
379
|
violated), **stop there**: leave later phases untouched, record the blocker in the review file, mark the
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: stories
|
|
3
|
+
description: Publish a plan's phases as development stories to the Jira Epic's Confluence page — one marked section per plan
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# /stories — plan phases as development stories on Confluence
|
|
7
|
+
|
|
8
|
+
One plan phase becomes one sprint-sized development story. The script writes a "Development stories" table to the
|
|
9
|
+
Confluence page whose title is the plan's Jira Epic key, under the page in `confluence_parent`. It writes only the
|
|
10
|
+
plan's own marked section. It never changes other page content and never deletes a page. Copying the stories into
|
|
11
|
+
Jira is the reader's job: caddis does not call Jira.
|
|
12
|
+
|
|
13
|
+
## Input
|
|
14
|
+
|
|
15
|
+
- Usage: `/caddis:stories <plan path>`. The plan path is `$ARGUMENTS`; with no argument, ask for it.
|
|
16
|
+
- When no argument is given, find the plan with
|
|
17
|
+
`python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_todo.py" active-plan`.
|
|
18
|
+
- The plan frontmatter must hold `jira_epic: <KEY>` and `confluence_parent: <URL of the HLA or HLSA page>`.
|
|
19
|
+
- The keys must be in the environment or in `~/.caddis/keys.env`: `CONFLUENCE_URL` (https only) and
|
|
20
|
+
`CONFLUENCE_TOKEN` (a personal access token). Never print, echo or show the token.
|
|
21
|
+
|
|
22
|
+
## Steps
|
|
23
|
+
|
|
24
|
+
1. Show the table. Run `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_stories.py" render --plan <plan path>` and
|
|
25
|
+
show its output to the user.
|
|
26
|
+
2. Check the login and the parent page. Run
|
|
27
|
+
`python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_stories.py" check --plan <plan path>`. It makes read-only calls and
|
|
28
|
+
prints `USER:` and `PARENT:` lines.
|
|
29
|
+
3. Do a dry run. Run `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_stories.py" sync --plan <plan path> --dry-run`.
|
|
30
|
+
Show the `ACTION:` and `PAGE:` lines. It writes nothing.
|
|
31
|
+
4. Write. Run `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_stories.py" sync --plan <plan path>`. Report the
|
|
32
|
+
`ACTION:` and `PAGE:` lines, and each `WARN:` line.
|
|
33
|
+
|
|
34
|
+
Stop at the first step that does not exit 0, and report its output.
|
|
35
|
+
|
|
36
|
+
## Exit codes
|
|
37
|
+
|
|
38
|
+
| Exit | Meaning | What to do |
|
|
39
|
+
|---|---|---|
|
|
40
|
+
| 0 | Synced, or the section is unchanged | Nothing |
|
|
41
|
+
| 1 | Confluence refused (HTTP error, a second version conflict) or the markers on the page are broken | Read the message. Broken markers: fix the page by hand |
|
|
42
|
+
| 3 | Not configured (no keys, or no `jira_epic` / `confluence_parent`), or the network failed | Add the keys or the fields, or try again later |
|
|
43
|
+
| 4 | Bad input: the plan cannot be read, a bad Epic key, or the parent page is on another host | Fix the plan |
|
|
44
|
+
|
|
45
|
+
## Rules
|
|
46
|
+
|
|
47
|
+
- The token goes only to the `CONFLUENCE_URL` host. A `confluence_parent` on another host stops the sync before any
|
|
48
|
+
call.
|
|
49
|
+
- A sync rewrites the plan's whole section. A phase removed from the plan leaves the table.
|
|
50
|
+
- When the stored section has the same hash, the sync writes nothing and makes no new page version.
|