codeassembly-guidance 0.3.0 → 0.4.0
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/.meta/changelog.json +64 -0
- package/CHANGELOG.md +23 -0
- package/README.md +17 -34
- package/content/_partials/guidance-change-since-capture.md +9 -0
- package/content/codeassembly-content.yaml +2 -0
- package/content/scripts/check-prose.mjs +1 -1
- package/content/scripts/select-lede-exemplars.mjs +53 -53
- package/content/skills/_data/artifact-conventions.md +8 -3
- package/content/skills/_partials/cluster-feedback-events.md +21 -0
- package/content/skills/capture-event/capture-event.mjs +32 -32
- package/content/skills/curate-feedback/SKILL.md +102 -0
- package/content/skills/curate-feedback/curate-feedback.mjs +211 -0
- package/content/skills/kb-add/kb-add.mjs +53 -53
- package/content/skills/kb-curate/kb-curate.mjs +64 -64
- package/content/skills/kb-edit/kb-edit.mjs +61 -61
- package/content/skills/kb-update-events/kb-update-events.mjs +19 -19
- package/content/skills/lesson-clusters/lesson-clusters.mjs +47 -47
- package/content/skills/migrate-feedback-memories/feedback-memories.mjs +75 -75
- package/content/skills/revise-prose/revise-prose.mjs +66 -66
- package/content/skills/save-artifact/SKILL.md +1 -1
- package/content/skills/streamline-guidance/streamline-guidance.mjs +30 -30
- package/content/skills/triage-feedback/SKILL.md +7 -22
- package/content/skills/triage-feedback/triage-feedback.mjs +7 -7
- package/content/skills/triage-spike-findings/SKILL.md +1 -1
- package/content/subagents/feedback-coverage-judge.md +95 -0
- package/content/subagents/feedback-triage-challenger.md +9 -4
- package/package.json +3 -3
- package/schemas/preferences.v1.json +1 -1
- package/schemas/work-types.v1.json +1 -1
|
@@ -54,6 +54,9 @@ All artifacts are stored under a configurable base directory (`base_dir`, defaul
|
|
|
54
54
|
│ └── {timestamp}_{slug}_deferred-findings.md ← project-scoped fallback when a ticket is not in session
|
|
55
55
|
├── devlogs/
|
|
56
56
|
│ └── {timestamp}_{concise-title}.md ← project-scoped fallback when a ticket is not in session
|
|
57
|
+
├── feedback-curation/
|
|
58
|
+
│ ├── {timestamp}_{slug}_feedback-curation.md ← project-scoped fallback when a ticket is not in session
|
|
59
|
+
│ └── {timestamp}_work/ ← the run's working files
|
|
57
60
|
├── feedback-triage/
|
|
58
61
|
│ ├── {timestamp}_{slug}_feedback-triage.md ← project-scoped fallback when a ticket is not in session
|
|
59
62
|
│ └── {timestamp}_work/ ← the run's working files
|
|
@@ -146,12 +149,13 @@ Ticket-level artifacts and run directories are both stored here. Invoke the bund
|
|
|
146
149
|
| chats | `chats` | `{base_dir}/projects/{project-slug}/chats/` |
|
|
147
150
|
| deferred-findings | `deferred-findings` | `{base_dir}/projects/{project-slug}/deferred-findings/` |
|
|
148
151
|
| devlogs | `devlogs` | `{base_dir}/projects/{project-slug}/devlogs/` |
|
|
152
|
+
| feedback-curation | `feedback-curation` | `{base_dir}/projects/{project-slug}/feedback-curation/` |
|
|
149
153
|
| feedback-triage | `feedback-triage` | `{base_dir}/projects/{project-slug}/feedback-triage/` |
|
|
150
154
|
| plans | `plans` | `{base_dir}/projects/{project-slug}/plans/` |
|
|
151
155
|
|
|
152
|
-
Non-ticket paths are relative to the project directory. Category names remain configurable via `artifacts.paths.{category}` in preferences.yaml, with
|
|
156
|
+
Non-ticket paths are relative to the project directory. Category names remain configurable via `artifacts.paths.{category}` in preferences.yaml, with three exceptions: `deferred-findings`, `feedback-curation`, and `feedback-triage` are hardcoded and cannot be overridden.
|
|
153
157
|
|
|
154
|
-
Devlogs, deferred-findings, and feedback-triage artifacts are dual-homed: When a ticket is in session context they are written as ticket-level artifacts under `tickets/{ticket-id}/`; otherwise they fall back to the project-scoped paths above (`devlogs/`, `deferred-findings/`, and `feedback-triage/`). All filenames in these types use the standard `YYYYMMDD-HHMMSSZ` ticket-level timestamp shape regardless of which directory they are written to.
|
|
158
|
+
Devlogs, deferred-findings, feedback-curation, and feedback-triage artifacts are dual-homed: When a ticket is in session context they are written as ticket-level artifacts under `tickets/{ticket-id}/`; otherwise they fall back to the project-scoped paths above (`devlogs/`, `deferred-findings/`, `feedback-curation/`, and `feedback-triage/`). All filenames in these types use the standard `YYYYMMDD-HHMMSSZ` ticket-level timestamp shape regardless of which directory they are written to.
|
|
155
159
|
|
|
156
160
|
## Naming conventions
|
|
157
161
|
|
|
@@ -726,7 +730,7 @@ Full run state (phases, artifacts, review rounds, criticalities) is reconstructe
|
|
|
726
730
|
|
|
727
731
|
### Backward compatibility
|
|
728
732
|
|
|
729
|
-
|
|
733
|
+
The run-core parser, `parseRunData`, still reads the v2 `run-index.json` format and the v1 `status.json` format.
|
|
730
734
|
|
|
731
735
|
## Artifact types
|
|
732
736
|
|
|
@@ -753,6 +757,7 @@ The first `coder_change-summary` in a run does not have dispositions (nothing to
|
|
|
753
757
|
- `deferred-findings`: Record of findings deferred during a `wrap-up` session, with cross-references to created tickets (falls back to non-ticket path when a ticket is not in session)
|
|
754
758
|
- `dispositions`: The rendered dispositions of a triage of findings, the text that `triage-spike-findings` posts on the triage ticket: every item with its disposition, its confidence and value, where it went, and its reason, with the challenge's summary; the JSON record from which it is rendered stays in `triage/`
|
|
755
759
|
- `devlog`: Development log entry (falls back to non-ticket path when a ticket is not in session)
|
|
760
|
+
- `feedback-curation`: The record of a `curate-feedback` run: the count of events in each bin, the guidance commits against which the judges read, each mark with its result, and every event with its bin, reference, and reason; the run's working files stay in `{timestamp}_work/` beside it (falls back to non-ticket path when a ticket is not in session)
|
|
756
761
|
- `feedback-triage`: The record of a `triage-feedback` run: each surfaced cluster of feedback events with its signals, priority, challenge, disposition, and result, and the remainder left in the pool. A deferred event's `addressed-by` names the artifact, whose filename timestamp dates the deferral; the run's working files stay in `{timestamp}_work/` beside it (falls back to non-ticket path when a ticket is not in session)
|
|
757
762
|
- `idea-decisions`: The idea table of a round of prototypes with the decision on each idea filled; `prepare-prototype-brief` saves it after the developer decides each idea, and the end vision cites it
|
|
758
763
|
- `merge`: Record of a merged pull request; `capture-lede-decision` reads its `## Body` as the merged side of a lede episode
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
An inventory is clustered in batches, because one clusterer cannot place every event of a large store. Each batch is clustered on its own, and when there is more than one, a merge pass groups the batch clusters that teach the same lesson.
|
|
2
|
+
|
|
3
|
+
1. Run `lesson-clusters inventory --store <store> --out {work}/inventory.json`. Report each `skipped` file, and stop when `pool` and `deferred` are both zero: Nothing awaits attention.
|
|
4
|
+
2. Run `lesson-clusters batch --inventory {work}/inventory.json --out {work}/batches`. Its `batches` list gives each batch's `path` and the `map` path to which its clusterer writes.
|
|
5
|
+
3. Send one {tool:Task} call per batch, all in one message, `subagent_type: lesson-clusterer`, each with this block and nothing else composed into it:
|
|
6
|
+
|
|
7
|
+
```dispatch
|
|
8
|
+
inventory: {batch path}
|
|
9
|
+
output: {batch map path}
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
4. When there is one batch, its map is the event map: Copy `{work}/batches/map-01.json` to `{work}/map.json`, and skip sub-steps 5 to 7.
|
|
13
|
+
5. Run `lesson-clusters lessons --batches {work}/batches --out {work}/lessons.json`. On `invalid-map`, resume the clusterer of each batch that the `violations` name once, sending it that batch's violations and asking it to correct its map; on Claude Code, send it a message with `SendMessage`, addressed by the agent ID that its dispatch returned. Run `lessons` again, and on a second failure, stop and report the violations.
|
|
14
|
+
6. Send one more {tool:Task} call, `subagent_type: lesson-clusterer`, for the merge pass:
|
|
15
|
+
|
|
16
|
+
```dispatch
|
|
17
|
+
inventory: {work}/lessons.json
|
|
18
|
+
output: {work}/merge.json
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
7. Run `lesson-clusters combine --batches {work}/batches --lessons {work}/lessons.json --map {work}/merge.json --out {work}/map.json`. On `invalid-map`, resume the merge clusterer once with the violations, run `combine` again, and on a second failure, stop and report them.
|