codeassembly-guidance 0.0.0 β 0.1.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 +563 -0
- package/CHANGELOG.md +134 -0
- package/LICENSE +7 -0
- package/README.md +165 -1
- package/content/_partials/README.md +192 -0
- package/content/_partials/code-descriptions.md +4 -0
- package/content/_partials/code-style.md +7 -0
- package/content/_partials/comment-discipline.md +89 -0
- package/content/_partials/concision.md +3 -0
- package/content/_partials/diff-audit-checklist.md +9 -0
- package/content/_partials/file-access.md +4 -0
- package/content/_partials/live-repo-writes.md +13 -0
- package/content/_partials/plain-speech-calibration.md +66 -0
- package/content/_partials/plain-speech.md +13 -0
- package/content/_partials/prose-line-breaks.md +3 -0
- package/content/_partials/record-marker.md +1 -0
- package/content/_partials/reduced-object-relative.md +28 -0
- package/content/_partials/shell-commands.md +3 -0
- package/content/_partials/target-file-set-resolution.md +22 -0
- package/content/_partials/technical-recommendations.md +5 -0
- package/content/_partials/test-structure-audit-checklist.md +7 -0
- package/content/_partials/ticket-assessment-baseline.md +12 -0
- package/content/_partials/ticket-assessment.md +202 -0
- package/content/_partials/work-type-choice.md +13 -0
- package/content/codeassembly-content.yaml +49 -0
- package/content/collections/all.md +11 -0
- package/content/collections/atlassian.md +16 -0
- package/content/collections/recommended.md +34 -0
- package/content/collections/triage.md +77 -0
- package/content/collections/williamthorsen.md +25 -0
- package/content/guidance/README.md +22 -0
- package/content/guidance/_harnesses/claude/CLAUDE.md +6 -0
- package/content/guidance/_harnesses/rovo/AGENTS.md +5 -0
- package/content/guidance/_harnesses/rovo/codeassembly-guidance.md +4 -0
- package/content/guidance/rulebooks/accessibility-conventions.md +20 -0
- package/content/guidance/rulebooks/codeassembly-content-specification.md +161 -0
- package/content/guidance/rulebooks/command-output-conventions.md +14 -0
- package/content/guidance/rulebooks/commit-conventions.md +72 -0
- package/content/guidance/rulebooks/generated-content-policy.md +10 -0
- package/content/guidance/rulebooks/live-worktree-policy.md +18 -0
- package/content/guidance/rulebooks/readme-conventions.md +74 -0
- package/content/guidance/rulebooks/shared-data-conventions.md +14 -0
- package/content/guidance/rulebooks/shell-conventions.md +279 -0
- package/content/guidance/rulebooks/williamthorsen-code-layout-preferences.md +102 -0
- package/content/guidance/rulebooks/williamthorsen-collaboration-preferences.md +58 -0
- package/content/guidance/rulebooks/williamthorsen-comment-preferences.md +30 -0
- package/content/guidance/rulebooks/williamthorsen-subagent-model-preferences.md +15 -0
- package/content/guidance/rulebooks/williamthorsen-ticketing-preferences.md +22 -0
- package/content/guidance/rulebooks/williamthorsen-tooling-preferences.md +36 -0
- package/content/guidance/rulebooks/williamthorsen-typescript-preferences.md +90 -0
- package/content/guidance/rulebooks/williamthorsen-workflow-preferences.md +58 -0
- package/content/guidance/rulebooks/williamthorsen-writing-preferences.md +80 -0
- package/content/guidance/shared/AGENTS.md +43 -0
- package/content/scripts/README.md +41 -0
- package/content/scripts/describe-change.mjs +165 -0
- package/content/scripts/get-ticket-id.sh +131 -0
- package/content/scripts/manage-jira-ticket.mjs +209 -0
- package/content/scripts/resolve-frontmatter.sh +540 -0
- package/content/scripts/resolve-review-run.mjs +12 -0
- package/content/scripts/select-lede-exemplars.mjs +208 -0
- package/content/skills/_data/action-items.md +83 -0
- package/content/skills/_data/artifact-conventions.md +969 -0
- package/content/skills/_data/bitbucket-pr-access.md +89 -0
- package/content/skills/_data/branch-format.md +34 -0
- package/content/skills/_data/change-record.md +163 -0
- package/content/skills/_data/complexity-classification.md +58 -0
- package/content/skills/_data/concision.md +23 -0
- package/content/skills/_data/deployed-file-provenance.md +46 -0
- package/content/skills/_data/design-priorities.md +76 -0
- package/content/skills/_data/gh-body-file.md +30 -0
- package/content/skills/_data/git-commands.md +39 -0
- package/content/skills/_data/naming-conventions.md +50 -0
- package/content/skills/_data/pr-resolution.md +25 -0
- package/content/skills/_data/pr-source-resolution.md +36 -0
- package/content/skills/_data/recommendation-gradient.md +90 -0
- package/content/skills/_data/scope-and-deferral.md +83 -0
- package/content/skills/_data/spike-conventions.md +89 -0
- package/content/skills/_data/ticket-evaluation.md +13 -0
- package/content/skills/_data/ticket-id-extraction.md +43 -0
- package/content/skills/_data/ticket-source-resolution.md +147 -0
- package/content/skills/_data/title-templates.md +624 -0
- package/content/skills/_data/title-voice.md +17 -0
- package/content/skills/_data/work-types.json +168 -0
- package/content/skills/_partials/acceptance-criteria-scaffold.md +15 -0
- package/content/skills/_partials/action-items.md +22 -0
- package/content/skills/_partials/bitbucket-delete-both-refusal.md +3 -0
- package/content/skills/_partials/commit-title-rendering.md +14 -0
- package/content/skills/_partials/gh-body-file.md +22 -0
- package/content/skills/_partials/nested-list-indent.md +9 -0
- package/content/skills/_partials/next-steps-after-plan.md +99 -0
- package/content/skills/_partials/next-steps-after-review.md +350 -0
- package/content/skills/_partials/option-format.md +84 -0
- package/content/skills/_partials/plan-template.md +97 -0
- package/content/skills/_partials/split-launch-prompts.md +5 -0
- package/content/skills/_partials/split-ticket-compose.md +5 -0
- package/content/skills/_partials/split-ticket-create.md +3 -0
- package/content/skills/_partials/ticket-and-plan-completeness.md +33 -0
- package/content/skills/_partials/ticket-concision.md +18 -0
- package/content/skills/_partials/ticket-criteria-conventions.md +7 -0
- package/content/skills/_partials/ticket-placement.md +14 -0
- package/content/skills/_partials/ticket-skeleton-tiers.md +6 -0
- package/content/skills/_partials/ticket-skeleton.md +13 -0
- package/content/skills/add-change-record/SKILL.md +136 -0
- package/content/skills/add-test-ids/SKILL.md +51 -0
- package/content/skills/align-ticket-with-implementation/SKILL.md +115 -0
- package/content/skills/anti-patterns/SKILL.md +57 -0
- package/content/skills/assess-ticket/SKILL.md +46 -0
- package/content/skills/assess-ticket/next-steps-after-assessment.md +98 -0
- package/content/skills/brainstorming/SKILL.md +107 -0
- package/content/skills/capture-event/SKILL.md +108 -0
- package/content/skills/capture-event/capture-event.mjs +216 -0
- package/content/skills/capture-feedback/SKILL.md +71 -0
- package/content/skills/capture-lede-decision/SKILL.md +163 -0
- package/content/skills/capture-lede-decision/capture-lede-decision.mjs +231 -0
- package/content/skills/classify-complexity/SKILL.md +92 -0
- package/content/skills/collaborate/SKILL.md +86 -0
- package/content/skills/condense-branch/SKILL.md +83 -0
- package/content/skills/create-bitbucket-pr/SKILL.md +87 -0
- package/content/skills/create-commit/SKILL.md +65 -0
- package/content/skills/create-devlog/SKILL.md +108 -0
- package/content/skills/create-gh-pr/SKILL.md +106 -0
- package/content/skills/create-pr/SKILL.md +150 -0
- package/content/skills/create-ticket/SKILL.md +350 -0
- package/content/skills/derive-session-context/derive-session-context.mjs +148 -0
- package/content/skills/design-and-plan/SKILL.md +194 -0
- package/content/skills/development-workflows/SKILL.md +41 -0
- package/content/skills/get-ticket-id/SKILL.md +67 -0
- package/content/skills/groom-backlog/SKILL.md +245 -0
- package/content/skills/groom-backlog/groom-backlog.mjs +106 -0
- package/content/skills/implement-plan/SKILL.md +164 -0
- package/content/skills/index-prototypes/SKILL.md +145 -0
- package/content/skills/index-prototypes/index-prototypes.mjs +328 -0
- package/content/skills/kb-add/SKILL.md +156 -0
- package/content/skills/kb-add/kb-add.mjs +216 -0
- package/content/skills/kb-curate/SKILL.md +117 -0
- package/content/skills/kb-curate/kb-curate.mjs +213 -0
- package/content/skills/kb-edit/SKILL.md +128 -0
- package/content/skills/kb-edit/kb-edit.mjs +219 -0
- package/content/skills/kb-retrieve/SKILL.md +100 -0
- package/content/skills/kb-retrieve/kb-retrieve.mjs +206 -0
- package/content/skills/kb-retrieve-events/SKILL.md +98 -0
- package/content/skills/kb-retrieve-events/kb-retrieve-events.mjs +206 -0
- package/content/skills/kb-update-events/SKILL.md +77 -0
- package/content/skills/kb-update-events/kb-update-events.mjs +215 -0
- package/content/skills/merge-bb-pr/SKILL.md +136 -0
- package/content/skills/merge-gh-pr/SKILL.md +167 -0
- package/content/skills/merge-gh-pr/merge-gh-pr.mjs +10 -0
- package/content/skills/merge-pr/SKILL.md +368 -0
- package/content/skills/migrate-feedback-memories/SKILL.md +136 -0
- package/content/skills/migrate-feedback-memories/feedback-memories.mjs +161 -0
- package/content/skills/people-report/SKILL.md +208 -0
- package/content/skills/plan/SKILL.md +87 -0
- package/content/skills/prepare-prototype-brief/SKILL.md +126 -0
- package/content/skills/pull-from-backlog/SKILL.md +83 -0
- package/content/skills/pull-from-backlog/pull-from-backlog.mjs +208 -0
- package/content/skills/refine-plan/SKILL.md +259 -0
- package/content/skills/respond-to-review/SKILL.md +292 -0
- package/content/skills/review-bb-pr/SKILL.md +161 -0
- package/content/skills/review-branch/SKILL.md +301 -0
- package/content/skills/review-criteria/SKILL.md +108 -0
- package/content/skills/review-gh-pr/SKILL.md +155 -0
- package/content/skills/review-gh-pr/select-pr-ticket.mjs +8 -0
- package/content/skills/review-permissions/SKILL.md +39 -0
- package/content/skills/review-pr/SKILL.md +123 -0
- package/content/skills/revise-comments/SKILL.md +115 -0
- package/content/skills/revise-prose/SKILL.md +197 -0
- package/content/skills/revise-prose/revise-prose.mjs +229 -0
- package/content/skills/save-artifact/SKILL.md +69 -0
- package/content/skills/save-plan/SKILL.md +55 -0
- package/content/skills/software-engineering/SKILL.md +74 -0
- package/content/skills/streamline-guidance/SKILL.md +174 -0
- package/content/skills/streamline-guidance/streamline-guidance.mjs +211 -0
- package/content/skills/summarize-change/SKILL.md +308 -0
- package/content/skills/summarize-chat/SKILL.md +100 -0
- package/content/skills/systematic-debugging/SKILL.md +308 -0
- package/content/skills/systematic-debugging/condition-based-waiting-example.ts +160 -0
- package/content/skills/systematic-debugging/condition-based-waiting.md +122 -0
- package/content/skills/systematic-debugging/defense-in-depth.md +130 -0
- package/content/skills/systematic-debugging/find-polluter.sh +68 -0
- package/content/skills/systematic-debugging/root-cause-tracing.md +185 -0
- package/content/skills/systematic-debugging/test-academic.md +16 -0
- package/content/skills/systematic-debugging/test-pressure-1.md +67 -0
- package/content/skills/systematic-debugging/test-pressure-2.md +77 -0
- package/content/skills/systematic-debugging/test-pressure-3.md +77 -0
- package/content/skills/testing-conventions/SKILL.md +168 -0
- package/content/skills/testing-conventions/mistakes.md +1 -0
- package/content/skills/typescript-testing-conventions/SKILL.md +129 -0
- package/content/skills/update-jira-ticket/SKILL.md +245 -0
- package/content/skills/update-jira-ticket/update-jira-ticket.mjs +9 -0
- package/content/skills/update-project-guidance/SKILL.md +300 -0
- package/content/skills/upgrade-dependencies/SKILL.md +139 -0
- package/content/skills/wrap-up/SKILL.md +431 -0
- package/content/subagents/_data/claude.yaml +19 -0
- package/content/subagents/_data/rovo.yaml +31 -0
- package/content/subagents/canary.md +11 -0
- package/content/subagents/entry-drafter.md +187 -0
- package/content/subagents/handoff-reviewer.md +75 -0
- package/content/subagents/plan-reviewer.md +184 -0
- package/content/subagents/plan-reviser.md +88 -0
- package/content/subagents/prose-reviser.md +130 -0
- package/content/subagents/ticket-assessor.md +139 -0
- package/package.json +70 -2
- package/schemas/preferences.v1.json +294 -0
- package/schemas/work-types.v1.json +142 -0
|
@@ -0,0 +1,431 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: wrap-up
|
|
3
|
+
description: 'Post-session housekeeping: Create tickets for deferred items, post insights, and generate devlogs'
|
|
4
|
+
user-invocable: true
|
|
5
|
+
dependencies:
|
|
6
|
+
skills:
|
|
7
|
+
- save-artifact
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Wrap up
|
|
11
|
+
|
|
12
|
+
Post-session housekeeping. Assess what happened during the session, present an inventory of addressable items with a numbered action menu, and delegate to existing skills after user confirmation.
|
|
13
|
+
|
|
14
|
+
This skill is context-adaptive: It detects the session type and adjusts its recommendations, but the user always confirms before anything executes.
|
|
15
|
+
|
|
16
|
+
## Item vocabulary
|
|
17
|
+
|
|
18
|
+
Items in the wrap-up output use spelled-out prefixes followed by a short ID. The prefix tells the developer the nature of the work at a glance. The ID provides a handle for referencing the item in instructions. Each item also renders with an icon drawn from the canonical [finding scheme](../_data/artifact-conventions.md#finding-scheme-fwtrs--legacy-suffix) and [knowledge items](../_data/artifact-conventions.md#knowledge-items) tables. Render the icon before the prefix so that the reader gets an at-a-glance severity cue.
|
|
19
|
+
|
|
20
|
+
| Prefix | ID pattern | Icon | Meaning |
|
|
21
|
+
| ---------------- | ------------------ | ---- | --------------------------------------------- |
|
|
22
|
+
| `fixme` | `F{n}` | π¨ | Must fix: Bugs, security issues, breakage |
|
|
23
|
+
| `warning` | `W{n}` | β οΈ | Questionable: May need action, needs judgment |
|
|
24
|
+
| `todo` | `T{n}` | π | Should do: Not urgent, can wait |
|
|
25
|
+
| `recommendation` | `R{n}` | π§ | Advisable: Discretionary improvement |
|
|
26
|
+
| `suggestion` | `S{n}` | βοΈ | Optional: Nice-to-have |
|
|
27
|
+
| `legacy` | `{F,W,T,R,S}{n}-L` | π | Pre-existing: Noticed in old code |
|
|
28
|
+
| `insight` | `I{n}` | π‘ | Knowledge: Pattern, gotcha, or learning |
|
|
29
|
+
|
|
30
|
+
This vocabulary is consistent with the F/W/T/R/S classification (with `-L` suffix for legacy) used by review agents. The `insight` prefix extends it for knowledge items that aren't defects.
|
|
31
|
+
|
|
32
|
+
### Numbering rules
|
|
33
|
+
|
|
34
|
+
- **Fresh numbering per wrap-up.** IDs are assigned sequentially within each prefix, regardless of what IDs existed in source artifacts. `F1` in the wrap-up may correspond to `F3` in a review; the wrap-up is its own namespace.
|
|
35
|
+
- Items may originate from conversation, review artifacts, or casual observation. Fresh numbering unifies all sources.
|
|
36
|
+
|
|
37
|
+
## Process
|
|
38
|
+
|
|
39
|
+
### Phase 1: Session assessment
|
|
40
|
+
|
|
41
|
+
Gather signals to classify the session and identify actionable items.
|
|
42
|
+
|
|
43
|
+
#### 1a. Detect session type
|
|
44
|
+
|
|
45
|
+
Check these signals in order to classify the session:
|
|
46
|
+
|
|
47
|
+
| Signal | How to check | Session type |
|
|
48
|
+
| -------------------------------- | ----------------------------------------------------------------------------- | ------------------------ |
|
|
49
|
+
| Code changes on branch | `git diff --name-only {default_branch}...HEAD` produces output | **Interactive dev** |
|
|
50
|
+
| Review artifacts in conversation | Conversation contains review findings or `review-branch` / `review-pr` output | **Review** |
|
|
51
|
+
| None of the above | No code changes, no run artifacts, no review artifacts | **Research/exploration** |
|
|
52
|
+
|
|
53
|
+
Check from top to bottom. Use the first match.
|
|
54
|
+
|
|
55
|
+
#### 1b. Scan for deferred items
|
|
56
|
+
|
|
57
|
+
Deferred items are things that were identified during the session but intentionally not addressed.
|
|
58
|
+
|
|
59
|
+
**Structured sources** (high confidence):
|
|
60
|
+
|
|
61
|
+
- **Review artifacts**: Extract unresolved T (TODO) and R (Recommendation) findings from review artifacts that were not addressed in subsequent coder responses.
|
|
62
|
+
|
|
63
|
+
**Conversation scanning** (heuristic: may produce false positives):
|
|
64
|
+
|
|
65
|
+
Structured sources take precedence. When scanning conversation, skip items already captured from structured sources (review artifacts) to avoid duplicates.
|
|
66
|
+
|
|
67
|
+
Scan the conversation for items that were explicitly deferred. Look for phrases indicating deferral:
|
|
68
|
+
|
|
69
|
+
- "out of scope", "not in scope", "beyond scope"
|
|
70
|
+
- "deferred", "defer this", "defer that"
|
|
71
|
+
- "TODO", "to-do" (when referring to future work, not task lists)
|
|
72
|
+
- "follow-up", "follow up on"
|
|
73
|
+
- "separate ticket", "separate issue", "separate PR"
|
|
74
|
+
- "not now", "later", "next time", "future work"
|
|
75
|
+
- "punting", "parking", "tabling"
|
|
76
|
+
- "not part of this PR", "left for a future PR", "tracked separately"
|
|
77
|
+
|
|
78
|
+
For each match, extract a short description of what was deferred and why (if stated). Discard matches that are clearly not actionable (e.g., general discussion about priorities).
|
|
79
|
+
|
|
80
|
+
#### 1b-ii. Classify deferred items
|
|
81
|
+
|
|
82
|
+
For each deferred item found, assign a prefix from the item vocabulary based on the nature of the work:
|
|
83
|
+
|
|
84
|
+
- Items from **review artifacts** retain their original classification (F/W/T/R/S). If the source used severity-tagged legacy IDs (e.g., `F3-L`), map to the corresponding prefix but assign a fresh number.
|
|
85
|
+
- Items from **conversation scanning**: Classify based on the context in which they were deferred. "We should fix X" β `fixme` or `todo`. "It would be nice to Y" β `suggestion`. "Consider Z approach" β `recommendation`.
|
|
86
|
+
- **Legacy items** (pre-existing issues not authored in this branch) get the `legacy` prefix and are collected into a separate section. These come from review artifacts with `-L` suffix IDs, or from conversation observations about old code.
|
|
87
|
+
|
|
88
|
+
Record the source attribution for each item (e.g., "review artifact", "conversation").
|
|
89
|
+
|
|
90
|
+
#### 1b-iii. Assess complexity
|
|
91
|
+
|
|
92
|
+
For each finding (not legacy items or insights), assess its complexity using the [complexity classification](../_data/complexity-classification.md) rubric. Assign a level (1β4) based on the characteristics described in the rubric.
|
|
93
|
+
|
|
94
|
+
Items at levels 1β2 (trivial or mechanical) are **drive-by candidates**: simple enough for the agent to apply immediately on the current branch without review. Tag these items for the drive-by pass in Phase 2a, in which branch-state and code-overlap guardrails determine whether they are actually applied as drive-bys.
|
|
95
|
+
|
|
96
|
+
Items at levels 3β4 remain in the standard findings pool for the housekeeping menu in Phase 2b.
|
|
97
|
+
|
|
98
|
+
The complexity assessment is an input to the cost-aware disposition flow described in [`_data/scope-and-deferral.md`](../_data/scope-and-deferral.md): **Do now** (Phase 2a drive-bys) is preferred for trivial items; **batch later** (Phase 2b batch action) for items that cannot be applied as drive-bys but share scope or source; and substantive items get a **separate ticket** (Phase 2b per-item ticketing).
|
|
99
|
+
|
|
100
|
+
#### 1c. Collect insights
|
|
101
|
+
|
|
102
|
+
Insights are notable observations worth preserving: patterns learned, surprising findings, or knowledge that would benefit future work.
|
|
103
|
+
|
|
104
|
+
**Structured source** (high confidence): Read the `## Insights` section of the review artifact (`*_reviewer_review.md`).
|
|
105
|
+
|
|
106
|
+
These are vetted knowledge, not heuristic guesses: Reviewers emit them under the insight gate.
|
|
107
|
+
|
|
108
|
+
**Conversation scanning** (heuristic: may produce false positives):
|
|
109
|
+
|
|
110
|
+
Structured sources take precedence. When scanning conversation, skip any insight already captured from a structured source (the same observation) to avoid duplicates: A review-emitted insight and its conversation echo are one item, and the structured one is kept.
|
|
111
|
+
|
|
112
|
+
Scan the conversation for:
|
|
113
|
+
|
|
114
|
+
- Architectural patterns discovered or validated
|
|
115
|
+
- Surprising behavior or bugs encountered
|
|
116
|
+
- Conventions or project-specific patterns learned
|
|
117
|
+
- Technical debt or risks identified
|
|
118
|
+
- Difficult bugs and their root causes
|
|
119
|
+
|
|
120
|
+
Look for language like: "interesting", "discovered", "realized", "turns out", "surprisingly", "TIL", "worth noting", "insight", "lesson", "gotcha", "caveat".
|
|
121
|
+
|
|
122
|
+
For each insight (structured or conversation-scanned), assign an `I{n}` ID (sequentially: I1, I2, ...) and resolve a destination:
|
|
123
|
+
|
|
124
|
+
- Honor a destination already stated by the source insight: A reviewer may suggest `ticket comment` or `devlog`.
|
|
125
|
+
- Otherwise: `ticket comment` if the insight relates to the current ticket's work; `devlog` if it is general knowledge not specific to one ticket.
|
|
126
|
+
|
|
127
|
+
If a ticket is not available (from the session-context manifest), default all destinations to `devlog`.
|
|
128
|
+
|
|
129
|
+
#### 1d. Check code state
|
|
130
|
+
|
|
131
|
+
Run `git status` and `git log --oneline {default_branch}..HEAD` to understand:
|
|
132
|
+
|
|
133
|
+
- Are there uncommitted changes?
|
|
134
|
+
- How many commits are on the branch?
|
|
135
|
+
- Has a change summary already been generated? (Check for `*_change-summary.md` artifacts.)
|
|
136
|
+
|
|
137
|
+
### Phase 2a: Drive-by fixes
|
|
138
|
+
|
|
139
|
+
If any findings were tagged as drive-by candidates (complexity levels 1β2) in step 1b-iii, present them for immediate action before the housekeeping menu. This is the **do now** lane from the cost-aware disposition model; see [`_data/scope-and-deferral.md`](../_data/scope-and-deferral.md) for the principle. Skip this phase entirely if step 1b-iii did not tag any items; do not show an empty section.
|
|
140
|
+
|
|
141
|
+
#### Suitability check
|
|
142
|
+
|
|
143
|
+
Before presenting candidates, evaluate the branch state. The drive-by lane is preferred when the branch can absorb a small additional change without obscuring its main work; it is not preferred when the branch is already large or when the candidate touches the same code as the branch's main work.
|
|
144
|
+
|
|
145
|
+
Consult these signals (starting points, not rigid gates):
|
|
146
|
+
|
|
147
|
+
- **Branch size**: `git diff --stat {default_branch}..HEAD`. Above ~10 files or ~500 lines of diff, treat the branch as already large; new drive-bys clear a higher bar. When the threshold is exceeded, prefer demoting candidates to Phase 2b's batch action rather than offering them as drive-bys.
|
|
148
|
+
- **Code overlap** For each candidate, check whether its target file appears in `git diff --name-only {default_branch}..HEAD`.
|
|
149
|
+
- **Same-file overlap**: Exercise caution. The reviewer must disentangle concerns within one diff. Prefer demoting unless the change is genuinely related to the branch's main work.
|
|
150
|
+
- **Different-file**: This is fine. Changes in unrelated files are good drive-by candidates because the reviewer can skim past them.
|
|
151
|
+
|
|
152
|
+
When the agent's judgment disagrees with a signal (e.g., the "large" branch is just a generated-file refresh), make the call and note the reasoning briefly to the user when presenting candidates.
|
|
153
|
+
|
|
154
|
+
#### Output format
|
|
155
|
+
|
|
156
|
+
```
|
|
157
|
+
### Drive-by fixes
|
|
158
|
+
|
|
159
|
+
These findings are simple enough to apply now on the current branch:
|
|
160
|
+
|
|
161
|
+
{icon} {prefix} {ID} {description}
|
|
162
|
+
|
|
163
|
+
{icon} {prefix} {ID} {description}
|
|
164
|
+
|
|
165
|
+
Apply drive-by fixes? Reply "all", numbers, or "skip"
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
#### Response handling
|
|
169
|
+
|
|
170
|
+
- **Applied items**: Make the changes and commit them with a message summarizing the fixes. Stage only the drive-by changes; if uncommitted work from earlier in the session exists, keep it separate. Remove applied items from the findings pool. They do not appear in Phase 2b.
|
|
171
|
+
- **Skipped items**: Demote back into the Findings section. They become eligible for the batch-ticket and per-item ticket actions in Phase 2b.
|
|
172
|
+
- **Partial selection** (e.g., `"1, 3"`): Apply selected items, demote the rest.
|
|
173
|
+
|
|
174
|
+
**Wait for the user to respond before proceeding.**
|
|
175
|
+
|
|
176
|
+
### Phase 2b: Inventory and action menu
|
|
177
|
+
|
|
178
|
+
Present the user with an inventory of remaining addressable items and a numbered action menu. Only include sections that have at least one item. Items applied as drive-by fixes in Phase 2a do not appear here.
|
|
179
|
+
|
|
180
|
+
The action menu offers two distinct ticket-creation actions ("Batch tickets for findings" and "Create tickets for findings"); their conditions and recommendation rules (drawn from the cost-aware disposition model in [`_data/scope-and-deferral.md`](../_data/scope-and-deferral.md)) are documented under [standard actions](#standard-actions) below.
|
|
181
|
+
|
|
182
|
+
#### Output format
|
|
183
|
+
|
|
184
|
+
```
|
|
185
|
+
## Session wrap-up
|
|
186
|
+
|
|
187
|
+
{Summary of what was built or changed: the outcome, not the process.
|
|
188
|
+
|
|
189
|
+
Derive from session type:
|
|
190
|
+
- **Interactive dev**: Summarize the actual code changes (`git diff` against the default branch)
|
|
191
|
+
- **Review**: Summarize what was reviewed and the key outcomes (approved, changes requested, etc.)
|
|
192
|
+
- **Research/exploration**: Summarize what was explored and key findings
|
|
193
|
+
|
|
194
|
+
Do NOT narrate routine workflow mechanics as the summary (e.g., "Ran three review rounds before approval"). Lead with the code change itself. If a workflow event materially affected the outcome or offers a lesson for future work (e.g., a review caught a late-stage regression), mention it briefly after the outcome summary.}
|
|
195
|
+
|
|
196
|
+
### Findings
|
|
197
|
+
|
|
198
|
+
{icon} {prefix} {ID} {description}
|
|
199
|
+
*source: {origin}*
|
|
200
|
+
|
|
201
|
+
### Legacy
|
|
202
|
+
|
|
203
|
+
π legacy {ID} {description}
|
|
204
|
+
*source: {origin}*
|
|
205
|
+
|
|
206
|
+
### Insights
|
|
207
|
+
|
|
208
|
+
π‘ insight {ID} {description}
|
|
209
|
+
*destination: {target}*
|
|
210
|
+
|
|
211
|
+
### Actions
|
|
212
|
+
|
|
213
|
+
1. {action} ({item references})
|
|
214
|
+
2. {action} ({item references})
|
|
215
|
+
...
|
|
216
|
+
|
|
217
|
+
What would you like to do? Reply with numbers, or 'all'.
|
|
218
|
+
```
|
|
219
|
+
|
|
220
|
+
#### Formatting rules
|
|
221
|
+
|
|
222
|
+
- Each item's description may wrap across multiple lines, indented to align with the first line of the description (not the prefix).
|
|
223
|
+
- The `*source:*` and `*destination:*` lines are italicized; this visual separation makes items easier to parse.
|
|
224
|
+
- Items within a section are separated by a blank line for readability.
|
|
225
|
+
|
|
226
|
+
#### Standard actions
|
|
227
|
+
|
|
228
|
+
The actions menu is built dynamically based on which sections are populated:
|
|
229
|
+
|
|
230
|
+
| Action | Offered when | Skill/tool invoked |
|
|
231
|
+
| ------------------------------- | ------------------------------------------ | ----------------------- |
|
|
232
|
+
| Batch tickets for findings | Findings section has β₯2 items | `{skill:create-ticket}` |
|
|
233
|
+
| Create tickets for findings | Findings section non-empty | `{skill:create-ticket}` |
|
|
234
|
+
| Create tickets for legacy items | Legacy section non-empty | `{skill:create-ticket}` |
|
|
235
|
+
| Post insights to ticket #{n} | Insights with `ticket comment` destination | `gh issue comment` |
|
|
236
|
+
| Save session devlog | Always (unless trivial) | `{skill:create-devlog}` |
|
|
237
|
+
|
|
238
|
+
**Batching versus per-item ticketing.** The "Batch tickets for findings" action creates a single ticket whose body is a checklist with one entry per finding (description plus source attribution); per-item complexity levels are not repeated since they were already used to reach this phase. The "Create tickets for findings" action creates one ticket per item. These are alternatives: Only one is executed for the findings pool, based on the user's selection. Recommend the batch action by default when β₯2 trivial items remain or when items share a `scope:` label or source artifact; recommend per-item ticketing when items are thematically unrelated. The "Batch tickets for findings" action implements the **batch later** lane; "Create tickets for findings" implements the **separate ticket** lane from [`_data/scope-and-deferral.md`](../_data/scope-and-deferral.md).
|
|
239
|
+
|
|
240
|
+
**Dropping findings.** Findings not selected by the user for a ticket-creation action are implicitly dropped: Menu omission is the close-without-tracking signal. The agent does not prompt to confirm; the user's selection is taken at face value. Dropped findings are still recorded in the report's `### Dropped` section and the deferred-findings artifact's `## Dropped` section so that they remain discoverable.
|
|
241
|
+
|
|
242
|
+
**Insight routing.** Each insight's destination determines where it appears in the action menu. Insights destined for `ticket comment` become part of the "Post insights to ticket" action; this action is independent and posts directly via `gh issue comment`. Insights destined for `devlog` are folded into the "Save session devlog" action and included automatically in the devlog content. This means devlog-bound insights only appear if the devlog action is selected, which is the correct dependency.
|
|
243
|
+
|
|
244
|
+
**Rendering the action menu.** Actions are numbered sequentially starting from 1. Only include actions that apply. The numbered list rendered to the user must include every applicable row from the Standard actions table. When both "Batch tickets for findings" and "Create tickets for findings" appear, annotate them as mutually exclusive alternatives so that the user cannot accidentally select both. Use the convention `1a` / `1b` for the batch and per-item entries (sharing the same primary number) and continue numbering subsequent actions from `2`. Any other action keeps a plain integer.
|
|
245
|
+
|
|
246
|
+
#### Defaults by session type
|
|
247
|
+
|
|
248
|
+
| Session type | Findings | Legacy | Ticket insights | Devlog |
|
|
249
|
+
| -------------------- | ------------------------- | ------ | --------------- | -------- |
|
|
250
|
+
| Interactive dev | Yes (from conversation) | Yes | If applicable | Yes |
|
|
251
|
+
| Research/exploration | Rarely | Rarely | If applicable | Optional |
|
|
252
|
+
| Review | Yes (unresolved findings) | Yes | If applicable | No |
|
|
253
|
+
|
|
254
|
+
These are defaults. Always include any section for which items were actually found, regardless of session type.
|
|
255
|
+
|
|
256
|
+
**Wait for the user to respond before proceeding.** Do not execute any actions until the user confirms.
|
|
257
|
+
|
|
258
|
+
<!-- include: ../_partials/action-items.md / -->
|
|
259
|
+
|
|
260
|
+
### Phase 3: Execution
|
|
261
|
+
|
|
262
|
+
Parse the user's response to the Phase 2b action menu and execute confirmed actions.
|
|
263
|
+
|
|
264
|
+
#### Response parsing
|
|
265
|
+
|
|
266
|
+
The user may respond with:
|
|
267
|
+
|
|
268
|
+
- **Numbers only:** `"1, 3"` or `"all"`; execute the referenced actions as-is
|
|
269
|
+
- **Per-item adjustments:** `"1 but combine F1+F2"`; execute the action with modifications
|
|
270
|
+
- **Multiple action selections:** `"1a with F1+F2; 3"`; apply action 1a to F1 and F2, then execute action 3
|
|
271
|
+
- **Exclusions:** `"all except I2"`; execute everything, omitting specific items
|
|
272
|
+
- **Custom instructions:** Free-form text; interpret and confirm before executing
|
|
273
|
+
|
|
274
|
+
Any finding not selected for a ticket-creation action is implicitly dropped.
|
|
275
|
+
|
|
276
|
+
If the response is ambiguous, ask for clarification before executing.
|
|
277
|
+
|
|
278
|
+
#### Execution order
|
|
279
|
+
|
|
280
|
+
Process confirmed actions in this order:
|
|
281
|
+
|
|
282
|
+
1. **Batch tickets for findings**: Invoke `{skill:create-ticket}` once. The ticket title summarizes the bundle (e.g., "Address minor follow-ups from {session topic}"). The body is a markdown checklist with one entry per finding (description plus source attribution); per-item complexity levels are not repeated. Apply a label that fits the bundle (typically the shared `scope:` label or `task`). The batch and per-item actions are alternatives: Execute whichever the user selected, not both.
|
|
283
|
+
2. **Tickets for findings**: Invoke `{skill:create-ticket}` once per ticket (or once for combined items). Use the item description as the ticket body seed. Apply the label from the issue's context (feature, bug, refactoring, dependencies, ci, tests). Classify items using the prefix: `fixme` β bug, `todo` β task, `warning` β bug, `recommendation` β improvement, `suggestion` β improvement.
|
|
284
|
+
3. **Tickets for legacy items**: Invoke `{skill:create-ticket}` once per item. Label as technical debt or the appropriate category.
|
|
285
|
+
4. **Post insights to ticket**: For each `ticket comment` insight, write the insight body to a scratch file per [gh body file](#gh-body-file), naming it for the insight that it contains (`gh-body-insight{index}-{timestamp}.md`), then post it with the call below (ticket number from the session-context manifest). Do not inline insight content into the shell command. If a ticket is not available, re-route to devlog.
|
|
286
|
+
|
|
287
|
+
```bash
|
|
288
|
+
body_path="{absolute path from the write step}"
|
|
289
|
+
[ -s "$body_path" ] || { echo "Body file missing or empty: $body_path" >&2; exit 1; }
|
|
290
|
+
gh issue comment {number} --body-file "$body_path"
|
|
291
|
+
```
|
|
292
|
+
|
|
293
|
+
5. **Save session devlog**: Invoke `{skill:create-devlog}`. Insights with `devlog` destination are automatically included in the devlog content; they do not need a separate action.
|
|
294
|
+
|
|
295
|
+
After all actions complete, identify which findings were _not_ selected by any action (implicitly dropped) and pass that set forward to Phase 4 for inclusion in the report's `### Dropped` section and the artifact's `## Dropped` section.
|
|
296
|
+
|
|
297
|
+
**Between each action**, briefly report the result (ticket URL, artifact path) before proceeding to the next.
|
|
298
|
+
|
|
299
|
+
<!-- include: ../../_partials/prose-line-breaks.md / -->
|
|
300
|
+
|
|
301
|
+
#### Idempotent safety
|
|
302
|
+
|
|
303
|
+
Before creating a ticket, check if an issue with a similar title already exists: `gh issue list --search "{keywords}"`. If a match is found, report it and skip creation.
|
|
304
|
+
|
|
305
|
+
### Phase 4: Results
|
|
306
|
+
|
|
307
|
+
After all actions are processed, persist a record of deferred work and present a concise conversation report.
|
|
308
|
+
|
|
309
|
+
#### Step 1: Persist deferred record
|
|
310
|
+
|
|
311
|
+
Write a `deferred-findings` artifact capturing items that remain to be done. The artifact is the single record to which a developer can return for an answer to "what was deferred from this session?"
|
|
312
|
+
|
|
313
|
+
##### When to write
|
|
314
|
+
|
|
315
|
+
Write the artifact when at least one finding became a created ticket in Phase 3 **or** at least one finding was dropped (by being unselected for any ticket-creation action).
|
|
316
|
+
|
|
317
|
+
Drive-by fixes that were applied in Phase 2a do not count toward the trigger; they were completed in the ordinary course of coding. Insights that were posted or folded into the devlog do not count; they have already been recorded.
|
|
318
|
+
|
|
319
|
+
If Phase 3 did not create any tickets and did not drop any findings (e.g., a research session with only insights), skip writing entirely. Do not produce an empty artifact.
|
|
320
|
+
|
|
321
|
+
##### Where to write
|
|
322
|
+
|
|
323
|
+
Resolve the artifact path:
|
|
324
|
+
|
|
325
|
+
- **Ticket-scoped** (when `ticket_id` from session context is non-null):
|
|
326
|
+
|
|
327
|
+
```
|
|
328
|
+
{artifact_base_dir}/projects/{project_slug}/tickets/{ticket_id}/{filename}
|
|
329
|
+
```
|
|
330
|
+
|
|
331
|
+
- **Project-scoped fallback** (when `ticket_id` is null):
|
|
332
|
+
|
|
333
|
+
```
|
|
334
|
+
{artifact_base_dir}/projects/{project_slug}/deferred-findings/{filename}
|
|
335
|
+
```
|
|
336
|
+
|
|
337
|
+
The `deferred-findings/` directory name is hardcoded; do not consult `artifact_paths` for it.
|
|
338
|
+
|
|
339
|
+
Filename: `{YYYYMMDD-HHMMSSZ}_{slug}_deferred-findings.md` (standard ticket-level shape; see [save-artifact](../save-artifact/SKILL.md#filename-formats)). Derive the slug per [save-artifact's slug generation rules](../save-artifact/SKILL.md#slug-generation). For non-ticket sessions whose branch description is empty, use the literal `deferred-findings` as the slug.
|
|
340
|
+
|
|
341
|
+
`mkdir -p` the target directory before writing.
|
|
342
|
+
|
|
343
|
+
##### What to write
|
|
344
|
+
|
|
345
|
+
Prepend YAML frontmatter, then the markdown body.
|
|
346
|
+
|
|
347
|
+
**Frontmatter**: See [universal artifact frontmatter](../_data/artifact-conventions.md#universal-artifact-frontmatter) for the canonical schema and [Deferred-findings frontmatter](../_data/artifact-conventions.md#deferred-findings-frontmatter) for the artifact-specific extensions.
|
|
348
|
+
|
|
349
|
+
This site uses `--format json` because `tickets_created` is a list-of-objects extension that does not have a clean CLI expression; see [artifact-conventions.md](../_data/artifact-conventions.md#bespoke-frontmatter-composition).
|
|
350
|
+
|
|
351
|
+
Run `{harness_home_dir}/scripts/resolve-frontmatter.sh --format json` via Bash. It emits a JSON object with the universal artifact fields (`branch`, `commit`, `baseSha`, `pr`, `ticket_id`, `ticket_ref`, `scm`, `timestamp`, `run_id`). Use those values verbatim for the matching YAML keys. Optional fields that the script omits from its output (`baseSha`, `pr`, `ticket_id`, `ticket_ref`, `run_id`) must be omitted from the frontmatter too; do not emit `null` or empty strings.
|
|
352
|
+
|
|
353
|
+
Set these skill-specific values inline (not in the script's output):
|
|
354
|
+
|
|
355
|
+
- `provenance.skill`: Always `wrap-up`.
|
|
356
|
+
- `provenance.isInteractive`: Always `true`.
|
|
357
|
+
- `session_type` (deferred-findings extension): The classification produced by Phase 1a's session-type detection (`interactive-dev`, `review`, or `research`).
|
|
358
|
+
- `tickets_created` (deferred-findings extension): List of `{id, items}` entries cross-referencing each created ticket to the wrap-up item IDs that it addresses. `items` is always a list. Omit when empty.
|
|
359
|
+
|
|
360
|
+
**Body**: Emit the tickets-created cross-reference and the dropped-findings record:
|
|
361
|
+
|
|
362
|
+
```markdown
|
|
363
|
+
# Deferred findings: {Concise session description}
|
|
364
|
+
|
|
365
|
+
## Tickets created
|
|
366
|
+
|
|
367
|
+
- #{number}: Addresses {prefix} {item-ID} -- {ticket title}
|
|
368
|
+
- #{number}: Addresses {prefix} {item-ID} -- {ticket title}
|
|
369
|
+
|
|
370
|
+
## Dropped
|
|
371
|
+
|
|
372
|
+
- {prefix} {item-ID}: {description}
|
|
373
|
+
- {prefix} {item-ID}: {description}
|
|
374
|
+
```
|
|
375
|
+
|
|
376
|
+
Render both sections from the same in-memory inventory used by the conversation report (Step 2 below); do not re-derive from conversation, so that the artifact and the report cannot drift. Omit either section when it does not have any entries (e.g., omit `## Dropped` when every finding was ticketed).
|
|
377
|
+
|
|
378
|
+
Insights, applied drive-by fixes, and devlog references do not appear in the body.
|
|
379
|
+
|
|
380
|
+
#### Step 2: Present report
|
|
381
|
+
|
|
382
|
+
```
|
|
383
|
+
## Wrap-up complete
|
|
384
|
+
|
|
385
|
+
### Tickets created
|
|
386
|
+
- {ticket-id}: {prefix} {item-ID} "{title}" -- {URL or file path}
|
|
387
|
+
|
|
388
|
+
### Insights recorded
|
|
389
|
+
- {prefix} {item-ID}: Posted to #{number}
|
|
390
|
+
- {prefix} {item-ID}: Included in devlog
|
|
391
|
+
|
|
392
|
+
### Artifacts saved
|
|
393
|
+
- {devlog path}
|
|
394
|
+
- {deferred-findings path}
|
|
395
|
+
|
|
396
|
+
### Dropped
|
|
397
|
+
- {prefix} {item-ID}: {description}
|
|
398
|
+
```
|
|
399
|
+
|
|
400
|
+
Omit empty sections. The "Artifacts saved" section is omitted when the skill did not write any artifacts (Step 1 did not produce a deferred-findings artifact, and Phase 3 did not generate a devlog). Filename suffixes (`_devlog.md`, `_deferred-findings.md`) state the artifact type; the report does not need separate sub-headings. Use the item's original ID (F1, L1, I2) so that the developer can cross-reference with the inventory.
|
|
401
|
+
|
|
402
|
+
### Phase 5: PR prompt
|
|
403
|
+
|
|
404
|
+
After the results report, check whether the branch has commits ahead of the default branch (`git log --oneline {default_branch}..HEAD`). If there are commits (whether from the session's earlier work, drive-by fixes applied in Phase 2a, or both), prompt the user to create a PR:
|
|
405
|
+
|
|
406
|
+
```
|
|
407
|
+
---
|
|
408
|
+
|
|
409
|
+
**Action items**
|
|
410
|
+
|
|
411
|
+
Create a pull request for this branch? I'll open it with `{skill:create-pr}`. ππΌππΌ
|
|
412
|
+
```
|
|
413
|
+
|
|
414
|
+
Skip this prompt if the branch does not have any commits ahead of the default branch (e.g., a research/exploration session without code changes).
|
|
415
|
+
|
|
416
|
+
The prompt closes the turn that presents the results report, so it goes in an action-items block of its own. It is not an entry in the Phase 2b action menu, and it never auto-executes.
|
|
417
|
+
|
|
418
|
+
## Ticket title conventions
|
|
419
|
+
|
|
420
|
+
Compose the title of a deferred-item ticket per [`title-voice.md`](../_data/title-voice.md), which governs voice, length, content discipline, and the framing that gives a bug ticket the problem rather than the fix.
|
|
421
|
+
|
|
422
|
+
<!-- include: ../_partials/gh-body-file.md / -->
|
|
423
|
+
|
|
424
|
+
## Constraints
|
|
425
|
+
|
|
426
|
+
- **Never auto-execute**: Always present the inventory and action menu, wait for user confirmation
|
|
427
|
+
- **Delegate, don't duplicate**: Every action goes through an existing skill or a direct `gh` CLI call
|
|
428
|
+
- **Idempotent-safe**: Before creating a ticket, check if an issue with a similar title already exists
|
|
429
|
+
- **Conversation is primary source**: Deferred items and insights appear in the dialogue, not just in git state
|
|
430
|
+
- **Graceful when empty**: If the assessment finds nothing actionable, say so and end: "No wrap-up items identified for this session."
|
|
431
|
+
- **Fresh numbering**: Always assign new sequential IDs within the wrap-up; never reuse IDs from source artifacts
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# claude.yaml
|
|
2
|
+
|
|
3
|
+
# Frontmatter that this harness merges into each deployed subagent: _defaults for every agent, then per-agent
|
|
4
|
+
# overrides.
|
|
5
|
+
|
|
6
|
+
_defaults:
|
|
7
|
+
permissionMode: bypassPermissions
|
|
8
|
+
|
|
9
|
+
handoff-reviewer:
|
|
10
|
+
model: sonnet
|
|
11
|
+
|
|
12
|
+
plan-reviewer:
|
|
13
|
+
model: sonnet
|
|
14
|
+
|
|
15
|
+
plan-reviser:
|
|
16
|
+
model: inherit
|
|
17
|
+
|
|
18
|
+
prose-reviser:
|
|
19
|
+
model: inherit
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# rovo.yaml
|
|
2
|
+
|
|
3
|
+
# Frontmatter that this harness merges into each deployed subagent: _defaults for every agent, then per-agent
|
|
4
|
+
# overrides.
|
|
5
|
+
|
|
6
|
+
_defaults:
|
|
7
|
+
tools: [bash, create_file, expand_code_chunks, expand_folder, grep, open_files]
|
|
8
|
+
|
|
9
|
+
# Rovo does not read a denylist, so the read-only grant is named here.
|
|
10
|
+
# `create_file` is dropped: The drafter returns text.
|
|
11
|
+
entry-drafter:
|
|
12
|
+
tools: [bash, expand_code_chunks, expand_folder, grep, open_files]
|
|
13
|
+
|
|
14
|
+
# Rovo does not read a denylist, so the read-only grant is named here.
|
|
15
|
+
# `create_file` is dropped: The reviewer returns text.
|
|
16
|
+
handoff-reviewer:
|
|
17
|
+
tools: [bash, expand_code_chunks, expand_folder, grep, open_files]
|
|
18
|
+
|
|
19
|
+
plan-reviewer: {} # inherits _defaults
|
|
20
|
+
|
|
21
|
+
plan-reviser: {} # inherits _defaults
|
|
22
|
+
|
|
23
|
+
# Edits prose in place and creates nothing: `create_file` is dropped, and `bash` with it, the reviser
|
|
24
|
+
# not having any command to run.
|
|
25
|
+
prose-reviser:
|
|
26
|
+
tools: [expand_code_chunks, expand_folder, find_and_replace_code, grep, open_files]
|
|
27
|
+
|
|
28
|
+
# Rovo does not read a denylist, so the read-only grant is named here.
|
|
29
|
+
# `create_file` is dropped: The assessor returns text.
|
|
30
|
+
ticket-assessor:
|
|
31
|
+
tools: [bash, expand_code_chunks, expand_folder, grep, open_files]
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: canary
|
|
3
|
+
description: Deployment canary for the declared-subagent mechanism; not meant to be invoked.
|
|
4
|
+
tools: [Read]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Canary
|
|
8
|
+
|
|
9
|
+
This subagent exists to prove that declared subagents deploy end-to-end. It doesn't have any consumers in this library and is never dispatched. Its body deliberately exercises the harness transform so that the deployed file is a real specimen: A `{tool:Read}` placeholder rewrites to the harness-native tool name, and a `{harness_home_dir}` reference rewrites to the harness home path.
|
|
10
|
+
|
|
11
|
+
Read configuration from `{harness_home_dir}/skills/_data/` if you ever need it, using the {tool:Read} tool.
|