@adamchanadam/agent-handoff-kit 0.3.41 → 0.3.43
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/LICENSE +21 -21
- package/README.en.md +81 -0
- package/README.md +38 -36
- package/bin/agent-handoff-kit.mjs +4664 -2544
- package/bin/installed-file-contract.mjs +74 -45
- package/bin/migration-baselines/official-origin-catalog.json +10039 -9828
- package/bin/official-origin-catalog.mjs +248 -192
- package/bin/prompt-mirror-core.mjs +84 -84
- package/bin/semantic-candidate.mjs +594 -0
- package/bin/upgrade-inventory.mjs +587 -0
- package/bin/user-rules-router.mjs +461 -0
- package/package.json +1 -13
- package/packs/agent-governance.md +103 -103
- package/packs/closeout.md +74 -72
- package/packs/coding.md +28 -28
- package/packs/communication.md +32 -30
- package/packs/integrations.md +251 -251
- package/packs/knowledge.md +5 -5
- package/packs/onboarding.md +214 -214
- package/packs/release.md +28 -28
- package/packs/research.md +30 -30
- package/packs/safety.md +29 -29
- package/packs/writing.md +36 -36
- package/runtime-core/AGENTS.core.md +115 -112
- package/runtime-core/CLAUDE.md +13 -13
- package/runtime-core/DOC_SYNC_REGISTRY.md +24 -24
- package/runtime-core/GEMINI.md +17 -17
- package/runtime-core/PROJECT_DECISIONS.md +43 -43
- package/runtime-core/PROJECT_INDEX.md +73 -73
- package/runtime-core/RULE_PACKS.md +14 -14
- package/runtime-core/SESSION_HANDOFF.md +42 -36
- package/runtime-core/SESSION_LOG.md +35 -35
- package/runtime-core/START_NEXT_SESSION_PROMPT.txt +5 -5
- package/runtime-core/USER_RULES.md +30 -0
- package/runtime-core/USER_RULES_ENTRY.md +7 -0
|
@@ -1,103 +1,103 @@
|
|
|
1
|
-
# Agent Governance Pack
|
|
2
|
-
|
|
3
|
-
## Scope
|
|
4
|
-
|
|
5
|
-
Use for governance rules, prompts, agent instructions, handoff systems, startup/closeout behavior, skills, and rule packs.
|
|
6
|
-
|
|
7
|
-
## Load When
|
|
8
|
-
|
|
9
|
-
- User asks to change AI behavior, project governance, prompts, handoff, startup, closeout, or tool-use rules.
|
|
10
|
-
- A change affects `AGENTS.md`, `dev/*`, rule packs, installer templates, or durable workflow docs.
|
|
11
|
-
- User asks to bridge governance, connect a document to governance, scan for unbridged governance documents, or uses equivalent Chinese phrases such as "治理打通", "把文件接入 Agent Handoff Kit", "接入 Agent Handoff Kit", or "掃描未接入 Agent Handoff Kit 的重要文件".
|
|
12
|
-
- User asks to make something long-term, cross-session, reusable, future sessions should remember an API / MCP / tool-use pattern, or uses equivalent Chinese phrases such as "寫入長期治理", "轉成長期機制", or "之後都要遵守".
|
|
13
|
-
- The task creates or materially changes Markdown documents, generated outputs, specifications, runbooks, checklists, guides, source-of-truth files, or research artifacts that future agents may need to discover.
|
|
14
|
-
|
|
15
|
-
## Rules
|
|
16
|
-
|
|
17
|
-
1. Locate the existing source of truth before adding a rule.
|
|
18
|
-
2. Prefer merge, replace, or registry rows over append-only rule growth.
|
|
19
|
-
3. Keep public runtime rules generic; project-specific incidents belong in logs, runbooks, or project index.
|
|
20
|
-
4. Do not let development-only workspace rules enter public runtime.
|
|
21
|
-
5. Check complexity budget before adding default-core behavior.
|
|
22
|
-
6. Before creating durable workflow, runbook, or instruction files, first classify the knowledge type and verify whether an existing home can carry it without a new file: current state belongs in `dev/SESSION_HANDOFF.md`; trace evidence belongs in `dev/SESSION_LOG.md`; file / command / reference maps belong in `dev/PROJECT_INDEX.md`; sync obligations belong in `dev/DOC_SYNC_REGISTRY.md`; reusable operating procedures belong in the relevant rule pack or registered reference. New runbooks are last resort only.
|
|
23
|
-
7. When a task uses external skills, subagents, demo workspaces, or another tool's closeout, treat those flows as subordinate to the active root's Agent Handoff Kit governance. The active root still needs the `runtime-core/AGENTS.core.md` persistence gate decision; do not duplicate the gate thresholds in this pack.
|
|
24
|
-
8. For long-running projects, maintain `dev/PROJECT_DECISIONS.md` per R-028 closeout discipline (see `runtime-core/AGENTS.core.md` closeout maintenance trigger check): capture major decisions when they happen, run the short trigger check at every closeout, and do full long-term maintenance only when a hard trigger, semantic trigger, or 10-closeout backstop applies. Short single-task projects keep this as a no-op default; users are not expected to edit this file manually.
|
|
25
|
-
9. Governance bridge is a triggered review, not a default startup scan. Use it when an important file, source-of-truth document, runbook, production guide, workflow, checklist, stock list, or similar durable document may need to be connected to project governance.
|
|
26
|
-
10. Content-based trigger: long-term governance routing is content-based, not trigger-only. Even if the user does not use explicit governance-routing phrases, treat a statement as durable governance when it says future sessions must follow it, when it corrects a recurring AI mistake, or when it defines a reusable API / MCP / tool-use pattern. Do not persist long-term governance knowledge only in `dev/SESSION_LOG.md`, `dev/SESSION_HANDOFF.md`, or `START_NEXT_SESSION_PROMPT.txt`; those surfaces may be compressed, archived, or regenerated.
|
|
27
|
-
11. Mid-task changes to product goals, requirements, development checklists, acceptance rules, exclusions, priorities, or scope are task contract changes. Before writing them, check whether the same contract already lives in a spec, backlog, issue list, README, runbook, project index entry, or handoff section. Merge into the existing authoritative home, then leave only a pointer or current-state summary elsewhere.
|
|
28
|
-
12. New Markdown or generated documents are not automatically harmless. After creating or materially changing them, classify each artifact before completion: source of truth, reference, runbook, workflow, checklist, public document, generated output, one-time evidence, draft, or temporary. Durable artifacts must be discoverable from `dev/PROJECT_INDEX.md` or intentionally tied to a registered sync / source-of-truth row. Temporary or one-time evidence must be labeled as such in the task record or closeout so future agents do not treat it as hidden current state.
|
|
29
|
-
13. Do not create a new document to hold a rule, requirement, checklist, or process if an existing authoritative document can carry it. Merge into the existing home or make the new document explicitly subordinate. If two files now carry the same durable instruction, resolve the duplicate by choosing one authoritative home and pointing the other to it.
|
|
30
|
-
|
|
31
|
-
## Governance Bridge Workflow
|
|
32
|
-
|
|
33
|
-
Use this workflow when the user asks for governance bridge, connect this document to governance, asks to scan for unbridged governance documents, or uses equivalent Chinese phrases such as "治理打通", "把文件接入 Agent Handoff Kit", "接入 Agent Handoff Kit", or "掃描未接入 Agent Handoff Kit 的重要文件".
|
|
34
|
-
|
|
35
|
-
1. Identify the target. If the user named a file, inspect that file and its surrounding directory. If no file is named, run a bounded repo scan for likely durable documents such as source-of-truth files, runbooks, workflows, guides, checklists, stock lists, production guides, and rules.
|
|
36
|
-
2. Check the target file itself: it should state its role, scope, update trigger, owner or responsible workflow when known, and what must not be inferred from it.
|
|
37
|
-
3. Check `dev/PROJECT_INDEX.md`: the file should be discoverable with its role and "read when" condition. Source-of-truth or reference files should appear in Fact Base, External Sources, Directory Map, Entry Points, or another existing indexed home that fits the project.
|
|
38
|
-
4. Check `dev/DOC_SYNC_REGISTRY.md`: future same-type changes should have a matching change type or an explicit reason no durable sync rule is needed.
|
|
39
|
-
5. Check related workflows, guides, runbooks, or rule packs: if a process creates or updates the file, that process should say when to update the file or its index row.
|
|
40
|
-
6. Check `dev/SESSION_HANDOFF.md`: only current state, recommended next action with reason, unresolved risk, blocker, or a startup-needed fact should be in handoff. Do not copy whole documents or old evidence into handoff.
|
|
41
|
-
7. Check `dev/SESSION_LOG.md`: this session's bridge review, validation, and evidence can be logged when it affects future action, but log entries must not become current state.
|
|
42
|
-
8. Search for duplicate source-of-truth risk. If another file has the same durable role, recommend merge, reference, or retire options; do not delete, rename, or move files without explicit approval.
|
|
43
|
-
|
|
44
|
-
For repo-wide scans, report candidates as candidates. Do not fail ordinary docs merely because they are not indexed; only durable files that future agents need to discover, update, or distinguish from drafts should be bridged.
|
|
45
|
-
|
|
46
|
-
Output format:
|
|
47
|
-
|
|
48
|
-
- Status: bridged / partially bridged / unbridged / blocked.
|
|
49
|
-
- Use bridged only when every applicable governance link is present. If only `dev/PROJECT_INDEX.md` or `dev/SESSION_LOG.md` was updated, report partially bridged.
|
|
50
|
-
- Already bridged: list the governance links that are present.
|
|
51
|
-
- Gaps: list missing links and why they matter for the next agent.
|
|
52
|
-
- Not applicable: list skipped layers with a reason.
|
|
53
|
-
- Suggested patches: list exact files and sections to update.
|
|
54
|
-
- Manual decisions: list duplicates, naming choices, deletion, renaming, external sync, or ownership questions requiring user confirmation.
|
|
55
|
-
- Acceptance: give one concrete check that proves the bridge is complete.
|
|
56
|
-
|
|
57
|
-
## Generated Artifact Governance Workflow
|
|
58
|
-
|
|
59
|
-
Use this workflow whenever the current task creates or materially changes Markdown documents or other durable artifacts, even if the user did not explicitly ask for governance bridge.
|
|
60
|
-
|
|
61
|
-
1. List the artifacts created or materially changed in this task.
|
|
62
|
-
2. Classify each artifact: source of truth, reference, runbook, workflow, checklist, public document, generated output, one-time evidence, draft, or temporary.
|
|
63
|
-
3. For source-of-truth, reference, runbook, workflow, checklist, public document, and reusable generated output, update `dev/PROJECT_INDEX.md` so the file is discoverable with a role and read condition.
|
|
64
|
-
4. For artifacts that require future mirror, external index, publication, or repeated sync, update `dev/DOC_SYNC_REGISTRY.md` or record why no durable sync rule applies.
|
|
65
|
-
5. For one-time evidence, draft, or temporary files, record that classification in `dev/SESSION_LOG.md` or the task summary, and do not promote it to current handoff unless it affects the next action.
|
|
66
|
-
6. Search for duplicate source-of-truth risk before keeping a new document. If another file already owns the same rule, requirement, checklist, or process, merge into that file or make the new document explicitly subordinate.
|
|
67
|
-
7. Before claiming completion, run the available project governance check or `agent-handoff-kit doctor`; if it reports orphan artifact candidates, register, consolidate, or explicitly classify them.
|
|
68
|
-
|
|
69
|
-
## Long-term Governance Routing
|
|
70
|
-
|
|
71
|
-
Use this workflow when the user asks to write something into long-term governance, turn an experience into a mechanism, make a rule apply across sessions, or when the content itself clearly has durable force.
|
|
72
|
-
|
|
73
|
-
1. Classify the knowledge before writing:
|
|
74
|
-
- Current task contract changes, including product goals, requirements, development checklists, acceptance rules, exclusions, priorities, or scope -> the existing authoritative spec / backlog / issue / runbook when one exists; otherwise `dev/SESSION_HANDOFF.md` current-state sections.
|
|
75
|
-
- Current task state, recommended next action with reason, unresolved risk, or startup-needed fact -> `dev/SESSION_HANDOFF.md`.
|
|
76
|
-
- Chronological evidence or validation trace -> `dev/SESSION_LOG.md`.
|
|
77
|
-
- File maps, command maps, API reference locations, tool capability maps, and external source coordinates -> `dev/PROJECT_INDEX.md`.
|
|
78
|
-
- Sync obligations or external mirror duties -> `dev/DOC_SYNC_REGISTRY.md`.
|
|
79
|
-
- Durable decisions, architecture trade-offs, research-derived rationale, and long-term lessons -> `dev/PROJECT_DECISIONS.md`.
|
|
80
|
-
- Reusable procedures, recurring mistake prevention, API / MCP / tool-use rules -> the relevant rule pack, registered reference, or QA check.
|
|
81
|
-
- API / MCP / tool-use patterns -> project index / registered reference / integrations pack, depending on scope.
|
|
82
|
-
2. If the knowledge is reusable but no existing home fits, propose the smallest new registered reference or rule-pack patch. New runbooks remain last resort.
|
|
83
|
-
3. If the knowledge was first captured in `SESSION_LOG` or handoff for short-term continuity, promote it to the correct durable home before claiming it is long-term.
|
|
84
|
-
4. Add or update a QA check when the same failure class could recur and can be tested.
|
|
85
|
-
5. Keep governance bridge wording reserved for document orphan prevention. Do not relabel non-file governance as "file connected to Agent Handoff Kit".
|
|
86
|
-
|
|
87
|
-
## Checks
|
|
88
|
-
|
|
89
|
-
- Verify affected files are indexed or intentionally installed templates.
|
|
90
|
-
- Check `dev/DOC_SYNC_REGISTRY.md` for governance, closeout/startup, and README sync rows.
|
|
91
|
-
- Confirm old overlapping wording was retired or marked legacy.
|
|
92
|
-
- Confirm any new durable file is reachable from `dev/PROJECT_INDEX.md` and does not rely only on a one-session handoff note.
|
|
93
|
-
- Confirm every Markdown document or generated artifact created in this task is indexed, synced, consolidated, or explicitly classified as draft / temporary / one-time evidence.
|
|
94
|
-
- Confirm no new file has become a parallel source for an existing rule, requirement, checklist, or process.
|
|
95
|
-
- Confirm reusable operating procedure knowledge is not stored only in `dev/SESSION_HANDOFF.md`, `dev/SESSION_LOG.md`, or a decision narrative when it belongs in a pack or registered reference.
|
|
96
|
-
- Confirm long-term governance knowledge is promoted out of `dev/SESSION_LOG.md`, `dev/SESSION_HANDOFF.md`, and `START_NEXT_SESSION_PROMPT.txt` when it should survive log archive or prompt regeneration.
|
|
97
|
-
- For governance bridge work, confirm the target file, project index, sync registry, related workflow, handoff/log role split, and duplicate-source risk were all checked or explicitly marked not applicable.
|
|
98
|
-
- Before claiming completion, apply the active root's core persistence gate and record the result only when that gate selects a checkpoint or full closeout; do not assume child or demo workspaces cover the parent/root workspace.
|
|
99
|
-
- For long-running projects, confirm `dev/PROJECT_DECISIONS.md` retains its four H2 sections in order (Evolution Timeline / Decisions Archive / Architecture Choices / Insights & Learnings) and that the closeout maintenance trigger check was recorded, with full maintenance applied where its trigger conditions were met.
|
|
100
|
-
|
|
101
|
-
## Closeout
|
|
102
|
-
|
|
103
|
-
Record the changed rule home, reason, complexity impact, retired wording, and follow-up checks.
|
|
1
|
+
# Agent Governance Pack
|
|
2
|
+
|
|
3
|
+
## Scope
|
|
4
|
+
|
|
5
|
+
Use for governance rules, prompts, agent instructions, handoff systems, startup/closeout behavior, skills, and rule packs.
|
|
6
|
+
|
|
7
|
+
## Load When
|
|
8
|
+
|
|
9
|
+
- User asks to change AI behavior, project governance, prompts, handoff, startup, closeout, or tool-use rules.
|
|
10
|
+
- A change affects `AGENTS.md`, `dev/*`, rule packs, installer templates, or durable workflow docs.
|
|
11
|
+
- User asks to bridge governance, connect a document to governance, scan for unbridged governance documents, or uses equivalent Chinese phrases such as "治理打通", "把文件接入 Agent Handoff Kit", "接入 Agent Handoff Kit", or "掃描未接入 Agent Handoff Kit 的重要文件".
|
|
12
|
+
- User asks to make something long-term, cross-session, reusable, future sessions should remember an API / MCP / tool-use pattern, or uses equivalent Chinese phrases such as "寫入長期治理", "轉成長期機制", or "之後都要遵守".
|
|
13
|
+
- The task creates or materially changes Markdown documents, generated outputs, specifications, runbooks, checklists, guides, source-of-truth files, or research artifacts that future agents may need to discover.
|
|
14
|
+
|
|
15
|
+
## Rules
|
|
16
|
+
|
|
17
|
+
1. Locate the existing source of truth before adding a rule.
|
|
18
|
+
2. Prefer merge, replace, or registry rows over append-only rule growth.
|
|
19
|
+
3. Keep public runtime rules generic; project-specific incidents belong in logs, runbooks, or project index.
|
|
20
|
+
4. Do not let development-only workspace rules enter public runtime.
|
|
21
|
+
5. Check complexity budget before adding default-core behavior.
|
|
22
|
+
6. Before creating durable workflow, runbook, or instruction files, first classify the knowledge type and verify whether an existing home can carry it without a new file: current state belongs in `dev/SESSION_HANDOFF.md`; trace evidence belongs in `dev/SESSION_LOG.md`; file / command / reference maps belong in `dev/PROJECT_INDEX.md`; sync obligations belong in `dev/DOC_SYNC_REGISTRY.md`; reusable operating procedures belong in the relevant rule pack or registered reference. New runbooks are last resort only.
|
|
23
|
+
7. When a task uses external skills, subagents, demo workspaces, or another tool's closeout, treat those flows as subordinate to the active root's Agent Handoff Kit governance. The active root still needs the `runtime-core/AGENTS.core.md` persistence gate decision; do not duplicate the gate thresholds in this pack.
|
|
24
|
+
8. For long-running projects, maintain `dev/PROJECT_DECISIONS.md` per R-028 closeout discipline (see `runtime-core/AGENTS.core.md` closeout maintenance trigger check): capture major decisions when they happen, run the short trigger check at every closeout, and do full long-term maintenance only when a hard trigger, semantic trigger, or 10-closeout backstop applies. Short single-task projects keep this as a no-op default; users are not expected to edit this file manually.
|
|
25
|
+
9. Governance bridge is a triggered review, not a default startup scan. Use it when an important file, source-of-truth document, runbook, production guide, workflow, checklist, stock list, or similar durable document may need to be connected to project governance.
|
|
26
|
+
10. Content-based trigger: long-term governance routing is content-based, not trigger-only. Even if the user does not use explicit governance-routing phrases, treat a statement as durable governance when it says future sessions must follow it, when it corrects a recurring AI mistake, or when it defines a reusable API / MCP / tool-use pattern. Do not persist long-term governance knowledge only in `dev/SESSION_LOG.md`, `dev/SESSION_HANDOFF.md`, or `START_NEXT_SESSION_PROMPT.txt`; those surfaces may be compressed, archived, or regenerated.
|
|
27
|
+
11. Mid-task changes to product goals, requirements, development checklists, acceptance rules, exclusions, priorities, or scope are task contract changes. Before writing them, check whether the same contract already lives in a spec, backlog, issue list, README, runbook, project index entry, or handoff section. Merge into the existing authoritative home, then leave only a pointer or current-state summary elsewhere.
|
|
28
|
+
12. New Markdown or generated documents are not automatically harmless. After creating or materially changing them, classify each artifact before completion: source of truth, reference, runbook, workflow, checklist, public document, generated output, one-time evidence, draft, or temporary. Durable artifacts must be discoverable from `dev/PROJECT_INDEX.md` or intentionally tied to a registered sync / source-of-truth row. Temporary or one-time evidence must be labeled as such in the task record or closeout so future agents do not treat it as hidden current state.
|
|
29
|
+
13. Do not create a new document to hold a rule, requirement, checklist, or process if an existing authoritative document can carry it. Merge into the existing home or make the new document explicitly subordinate. If two files now carry the same durable instruction, resolve the duplicate by choosing one authoritative home and pointing the other to it.
|
|
30
|
+
|
|
31
|
+
## Governance Bridge Workflow
|
|
32
|
+
|
|
33
|
+
Use this workflow when the user asks for governance bridge, connect this document to governance, asks to scan for unbridged governance documents, or uses equivalent Chinese phrases such as "治理打通", "把文件接入 Agent Handoff Kit", "接入 Agent Handoff Kit", or "掃描未接入 Agent Handoff Kit 的重要文件".
|
|
34
|
+
|
|
35
|
+
1. Identify the target. If the user named a file, inspect that file and its surrounding directory. If no file is named, run a bounded repo scan for likely durable documents such as source-of-truth files, runbooks, workflows, guides, checklists, stock lists, production guides, and rules.
|
|
36
|
+
2. Check the target file itself: it should state its role, scope, update trigger, owner or responsible workflow when known, and what must not be inferred from it.
|
|
37
|
+
3. Check `dev/PROJECT_INDEX.md`: the file should be discoverable with its role and "read when" condition. Source-of-truth or reference files should appear in Fact Base, External Sources, Directory Map, Entry Points, or another existing indexed home that fits the project.
|
|
38
|
+
4. Check `dev/DOC_SYNC_REGISTRY.md`: future same-type changes should have a matching change type or an explicit reason no durable sync rule is needed.
|
|
39
|
+
5. Check related workflows, guides, runbooks, or rule packs: if a process creates or updates the file, that process should say when to update the file or its index row.
|
|
40
|
+
6. Check `dev/SESSION_HANDOFF.md`: only current state, recommended next action with reason, unresolved risk, blocker, or a startup-needed fact should be in handoff. Do not copy whole documents or old evidence into handoff.
|
|
41
|
+
7. Check `dev/SESSION_LOG.md`: this session's bridge review, validation, and evidence can be logged when it affects future action, but log entries must not become current state.
|
|
42
|
+
8. Search for duplicate source-of-truth risk. If another file has the same durable role, recommend merge, reference, or retire options; do not delete, rename, or move files without explicit approval.
|
|
43
|
+
|
|
44
|
+
For repo-wide scans, report candidates as candidates. Do not fail ordinary docs merely because they are not indexed; only durable files that future agents need to discover, update, or distinguish from drafts should be bridged.
|
|
45
|
+
|
|
46
|
+
Output format:
|
|
47
|
+
|
|
48
|
+
- Status: bridged / partially bridged / unbridged / blocked.
|
|
49
|
+
- Use bridged only when every applicable governance link is present. If only `dev/PROJECT_INDEX.md` or `dev/SESSION_LOG.md` was updated, report partially bridged.
|
|
50
|
+
- Already bridged: list the governance links that are present.
|
|
51
|
+
- Gaps: list missing links and why they matter for the next agent.
|
|
52
|
+
- Not applicable: list skipped layers with a reason.
|
|
53
|
+
- Suggested patches: list exact files and sections to update.
|
|
54
|
+
- Manual decisions: list duplicates, naming choices, deletion, renaming, external sync, or ownership questions requiring user confirmation.
|
|
55
|
+
- Acceptance: give one concrete check that proves the bridge is complete.
|
|
56
|
+
|
|
57
|
+
## Generated Artifact Governance Workflow
|
|
58
|
+
|
|
59
|
+
Use this workflow whenever the current task creates or materially changes Markdown documents or other durable artifacts, even if the user did not explicitly ask for governance bridge.
|
|
60
|
+
|
|
61
|
+
1. List the artifacts created or materially changed in this task.
|
|
62
|
+
2. Classify each artifact: source of truth, reference, runbook, workflow, checklist, public document, generated output, one-time evidence, draft, or temporary.
|
|
63
|
+
3. For source-of-truth, reference, runbook, workflow, checklist, public document, and reusable generated output, update `dev/PROJECT_INDEX.md` so the file is discoverable with a role and read condition.
|
|
64
|
+
4. For artifacts that require future mirror, external index, publication, or repeated sync, update `dev/DOC_SYNC_REGISTRY.md` or record why no durable sync rule applies.
|
|
65
|
+
5. For one-time evidence, draft, or temporary files, record that classification in `dev/SESSION_LOG.md` or the task summary, and do not promote it to current handoff unless it affects the next action.
|
|
66
|
+
6. Search for duplicate source-of-truth risk before keeping a new document. If another file already owns the same rule, requirement, checklist, or process, merge into that file or make the new document explicitly subordinate.
|
|
67
|
+
7. Before claiming completion, run the available project governance check or `agent-handoff-kit doctor`; if it reports orphan artifact candidates, register, consolidate, or explicitly classify them.
|
|
68
|
+
|
|
69
|
+
## Long-term Governance Routing
|
|
70
|
+
|
|
71
|
+
Use this workflow when the user asks to write something into long-term governance, turn an experience into a mechanism, make a rule apply across sessions, or when the content itself clearly has durable force.
|
|
72
|
+
|
|
73
|
+
1. Classify the knowledge before writing:
|
|
74
|
+
- Current task contract changes, including product goals, requirements, development checklists, acceptance rules, exclusions, priorities, or scope -> the existing authoritative spec / backlog / issue / runbook when one exists; otherwise `dev/SESSION_HANDOFF.md` current-state sections.
|
|
75
|
+
- Current task state, recommended next action with reason, unresolved risk, or startup-needed fact -> `dev/SESSION_HANDOFF.md`.
|
|
76
|
+
- Chronological evidence or validation trace -> `dev/SESSION_LOG.md`.
|
|
77
|
+
- File maps, command maps, API reference locations, tool capability maps, and external source coordinates -> `dev/PROJECT_INDEX.md`.
|
|
78
|
+
- Sync obligations or external mirror duties -> `dev/DOC_SYNC_REGISTRY.md`.
|
|
79
|
+
- Durable decisions, architecture trade-offs, research-derived rationale, and long-term lessons -> `dev/PROJECT_DECISIONS.md`.
|
|
80
|
+
- Reusable procedures, recurring mistake prevention, API / MCP / tool-use rules -> the relevant rule pack, registered reference, or QA check.
|
|
81
|
+
- API / MCP / tool-use patterns -> project index / registered reference / integrations pack, depending on scope.
|
|
82
|
+
2. If the knowledge is reusable but no existing home fits, propose the smallest new registered reference or rule-pack patch. New runbooks remain last resort.
|
|
83
|
+
3. If the knowledge was first captured in `SESSION_LOG` or handoff for short-term continuity, promote it to the correct durable home before claiming it is long-term.
|
|
84
|
+
4. Add or update a QA check when the same failure class could recur and can be tested.
|
|
85
|
+
5. Keep governance bridge wording reserved for document orphan prevention. Do not relabel non-file governance as "file connected to Agent Handoff Kit".
|
|
86
|
+
|
|
87
|
+
## Checks
|
|
88
|
+
|
|
89
|
+
- Verify affected files are indexed or intentionally installed templates.
|
|
90
|
+
- Check `dev/DOC_SYNC_REGISTRY.md` for governance, closeout/startup, and README sync rows.
|
|
91
|
+
- Confirm old overlapping wording was retired or marked legacy.
|
|
92
|
+
- Confirm any new durable file is reachable from `dev/PROJECT_INDEX.md` and does not rely only on a one-session handoff note.
|
|
93
|
+
- Confirm every Markdown document or generated artifact created in this task is indexed, synced, consolidated, or explicitly classified as draft / temporary / one-time evidence.
|
|
94
|
+
- Confirm no new file has become a parallel source for an existing rule, requirement, checklist, or process.
|
|
95
|
+
- Confirm reusable operating procedure knowledge is not stored only in `dev/SESSION_HANDOFF.md`, `dev/SESSION_LOG.md`, or a decision narrative when it belongs in a pack or registered reference.
|
|
96
|
+
- Confirm long-term governance knowledge is promoted out of `dev/SESSION_LOG.md`, `dev/SESSION_HANDOFF.md`, and `START_NEXT_SESSION_PROMPT.txt` when it should survive log archive or prompt regeneration.
|
|
97
|
+
- For governance bridge work, confirm the target file, project index, sync registry, related workflow, handoff/log role split, and duplicate-source risk were all checked or explicitly marked not applicable.
|
|
98
|
+
- Before claiming completion, apply the active root's core persistence gate and record the result only when that gate selects a checkpoint or full closeout; do not assume child or demo workspaces cover the parent/root workspace.
|
|
99
|
+
- For long-running projects, confirm `dev/PROJECT_DECISIONS.md` retains its four H2 sections in order (Evolution Timeline / Decisions Archive / Architecture Choices / Insights & Learnings) and that the closeout maintenance trigger check was recorded, with full maintenance applied where its trigger conditions were met.
|
|
100
|
+
|
|
101
|
+
## Closeout
|
|
102
|
+
|
|
103
|
+
Record the changed rule home, reason, complexity impact, retired wording, and follow-up checks.
|
package/packs/closeout.md
CHANGED
|
@@ -1,72 +1,74 @@
|
|
|
1
|
-
# Closeout Pack
|
|
2
|
-
|
|
3
|
-
## Scope
|
|
4
|
-
|
|
5
|
-
This pack is the single detailed contract for full Agent Handoff Kit closeout. Load it only for clear end-of-session or handoff intent. It does not authorize Git, release, publish, deployment, deletion, permission, or cleanup actions.
|
|
6
|
-
|
|
7
|
-
## Required Reads
|
|
8
|
-
|
|
9
|
-
Read the current `dev/SESSION_HANDOFF.md`, `dev/SESSION_LOG.md`, `dev/PROJECT_INDEX.md`, and `dev/DOC_SYNC_REGISTRY.md`. Read `dev/PROJECT_DECISIONS.md`, integration rules, or another pack only when its closeout trigger or the session's actual work requires it.
|
|
10
|
-
|
|
11
|
-
## Write Contract
|
|
12
|
-
|
|
13
|
-
Use Kit markers as machine boundaries: `ack:section:*`, `ack:field:*`, `ack:log-entry:start/end`, and managed-core BEGIN/END. Human headings may be localized; markers may not be removed or translated.
|
|
14
|
-
|
|
15
|
-
- Current state, objective, recommended next action, active risk, blocker, required reading, workspace identity, and sync status belong in `dev/SESSION_HANDOFF.md`.
|
|
16
|
-
- Chronological work and evidence disposition belong in `dev/SESSION_LOG.md`.
|
|
17
|
-
- File / command / source / capability maps belong in `dev/PROJECT_INDEX.md`.
|
|
18
|
-
- Recurring sync obligations belong in `dev/DOC_SYNC_REGISTRY.md`.
|
|
19
|
-
- Long-term evolution, architectural rationale, and accumulated learning belong in `dev/PROJECT_DECISIONS.md` when triggered.
|
|
20
|
-
- Reusable procedures belong in the relevant pack, registered reference, or QA check.
|
|
21
|
-
- `START_NEXT_SESSION_PROMPT.txt` is generated only from the handoff opening-message block.
|
|
22
|
-
|
|
23
|
-
Do not copy the full opening message into `dev/SESSION_LOG.md` or any third current governance file. The log records that the mirror was regenerated and verified, plus an evidence reference when useful.
|
|
24
|
-
|
|
25
|
-
## Full Closeout
|
|
26
|
-
|
|
27
|
-
1. Reconcile `dev/SESSION_HANDOFF.md`; never append a new current-state snapshot beneath an old one. Verify durable anchors, then rewrite or explicitly confirm every closeout-reconciled section.
|
|
28
|
-
2. Reconcile lifecycle state across `Completed This Session`, `Validation / QC`, `Next Priorities`, `Risks / Blockers`, and `Next Session Opening Message`. Completed or verified work cannot remain unresolved unless explicitly reclassified as monitor-only, follow-up scope, blocked, or reopened with its missing evidence or trigger.
|
|
29
|
-
The bundled doctor is a mechanical floor for obvious overlap and unresolved fields; it cannot prove that renamed or paraphrased work is semantically consistent. Read all five sections as a whole before marking the lifecycle field resolved. For governance, release, or another project-defined high-risk completion, use the project's independent semantic review gate in addition to doctor.
|
|
30
|
-
3. Make `Next Priorities` name one recommended next action and a short reason unless blocked or a real user decision is required.
|
|
31
|
-
4. Complete the persistence-routing
|
|
32
|
-
5. Add one concise log entry for work actually performed. Record evidence disposition and the prompt-mirror verification result; omit the full opening message by design.
|
|
33
|
-
6. Update the project index and sync registry only when their owned maps or obligations changed. Record each applicable sync target as `confirmed`, `unverified`, `pending`, `blocked`, or `not_applicable`.
|
|
34
|
-
7. Record the actual root, Git root, branch, commit, worktrees / parallel workspaces, uncommitted changes, and unresolved drift. Do not clean or change them without separate authorization.
|
|
35
|
-
8. If the session used external tools or helper processes, apply the integrations and safety ownership rules. Close only task-owned resources. Retain shared, user-owned, other-agent-owned, system, or ambiguous resources unless separately authorized; state visibility limits.
|
|
36
|
-
9. Run the short maintenance trigger check below and record its result in the log.
|
|
37
|
-
10. Mark first-use guidance `consumed` after the first successfully completed task or first full closeout. Upgrade must never reset `consumed` or `not_applicable` to `eligible`.
|
|
38
|
-
11. Regenerate `START_NEXT_SESSION_PROMPT.txt` from the sole fenced handoff opening-message block. Run the project's fixed prompt-mirror checker or perform an equivalent anchored read-back that verifies marker, heading, fence, full-copy uniqueness, and normalized content equality.
|
|
39
|
-
12. Run available project closeout
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
-
|
|
47
|
-
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
1
|
+
# Closeout Pack
|
|
2
|
+
|
|
3
|
+
## Scope
|
|
4
|
+
|
|
5
|
+
This pack is the single detailed contract for full Agent Handoff Kit closeout. Load it only for clear end-of-session or handoff intent. It does not authorize Git, release, publish, deployment, deletion, permission, or cleanup actions.
|
|
6
|
+
|
|
7
|
+
## Required Reads
|
|
8
|
+
|
|
9
|
+
Read the current `dev/SESSION_HANDOFF.md`, `dev/SESSION_LOG.md`, `dev/PROJECT_INDEX.md`, and `dev/DOC_SYNC_REGISTRY.md`. Read `dev/PROJECT_DECISIONS.md`, integration rules, or another pack only when its closeout trigger or the session's actual work requires it.
|
|
10
|
+
|
|
11
|
+
## Write Contract
|
|
12
|
+
|
|
13
|
+
Use Kit markers as machine boundaries: `ack:section:*`, `ack:field:*`, `ack:log-entry:start/end`, and managed-core BEGIN/END. Human headings may be localized; markers may not be removed or translated.
|
|
14
|
+
|
|
15
|
+
- Current state, objective, recommended next action, active risk, blocker, required reading, workspace identity, and sync status belong in `dev/SESSION_HANDOFF.md`.
|
|
16
|
+
- Chronological work and evidence disposition belong in `dev/SESSION_LOG.md`.
|
|
17
|
+
- File / command / source / capability maps belong in `dev/PROJECT_INDEX.md`.
|
|
18
|
+
- Recurring sync obligations belong in `dev/DOC_SYNC_REGISTRY.md`.
|
|
19
|
+
- Long-term evolution, architectural rationale, and accumulated learning belong in `dev/PROJECT_DECISIONS.md` when triggered.
|
|
20
|
+
- Reusable procedures belong in the relevant pack, registered reference, or QA check.
|
|
21
|
+
- `START_NEXT_SESSION_PROMPT.txt` is generated only from the handoff opening-message block.
|
|
22
|
+
|
|
23
|
+
Do not copy the full opening message into `dev/SESSION_LOG.md` or any third current governance file. The log records that the mirror was regenerated and verified, plus an evidence reference when useful.
|
|
24
|
+
|
|
25
|
+
## Full Closeout
|
|
26
|
+
|
|
27
|
+
1. Reconcile `dev/SESSION_HANDOFF.md`; never append a new current-state snapshot beneath an old one. Verify durable anchors, then rewrite or explicitly confirm every closeout-reconciled section.
|
|
28
|
+
2. Reconcile lifecycle state across `Completed This Session`, `Validation / QC`, `Next Priorities`, `Risks / Blockers`, and `Next Session Opening Message`. Completed or verified work cannot remain unresolved unless explicitly reclassified as monitor-only, follow-up scope, blocked, or reopened with its missing evidence or trigger.
|
|
29
|
+
The bundled doctor is a mechanical floor for obvious overlap and unresolved fields; it cannot prove that renamed or paraphrased work is semantically consistent. Read all five sections as a whole before marking the lifecycle field resolved. For governance, release, or another project-defined high-risk completion, use the project's independent semantic review gate in addition to doctor.
|
|
30
|
+
3. Make `Next Priorities` name one recommended next action and a short reason unless blocked or a real user decision is required.
|
|
31
|
+
4. Complete the persistence-routing, handoff-sufficiency, `Closeout outcome`, and `Project-required persistence` fields. The next agent must be able to continue from `AGENTS.md`, the handoff, the project index when needed, and routed packs without searching old log history. `complete` is allowed only when all required writes/read-backs and any project-required persistence succeeded; use `not_required` only when that persistence is genuinely not required. If a required commit, push, release record, or equivalent persistence is blocked or not authorized, set both fields to `blocked` with the exact boundary.
|
|
32
|
+
5. Add one concise log entry for work actually performed. Record evidence disposition and the prompt-mirror verification result; omit the full opening message by design.
|
|
33
|
+
6. Update the project index and sync registry only when their owned maps or obligations changed. Record each applicable sync target as `confirmed`, `unverified`, `pending`, `blocked`, or `not_applicable`.
|
|
34
|
+
7. Record the actual root, Git root, branch, commit, worktrees / parallel workspaces, uncommitted changes, and unresolved drift. Do not clean or change them without separate authorization.
|
|
35
|
+
8. If the session used external tools or helper processes, apply the integrations and safety ownership rules. Close only task-owned resources. Retain shared, user-owned, other-agent-owned, system, or ambiguous resources unless separately authorized; state visibility limits.
|
|
36
|
+
9. Run the short maintenance trigger check below and record its result in the log.
|
|
37
|
+
10. Mark first-use guidance `consumed` after the first successfully completed task or first full closeout. Upgrade must never reset `consumed` or `not_applicable` to `eligible`.
|
|
38
|
+
11. Regenerate `START_NEXT_SESSION_PROMPT.txt` from the sole fenced handoff opening-message block. Run the project's fixed prompt-mirror checker or perform an equivalent anchored read-back that verifies marker, heading, fence, full-copy uniqueness, and normalized content equality.
|
|
39
|
+
12. Run available project-specific closeout checks. Do not run a separate bundled `doctor`: the `closeout-status` command below performs the one required fresh doctor read-back. Do not treat an external update-check failure as local closeout failure. Fix state or mirror failures before claiming handoff ready.
|
|
40
|
+
13. Run `agent-handoff-kit closeout-status --root <project root>` after the handoff and prompt read-back. It performs the one required fresh doctor read-back and its output is the only final card source: copy its status faithfully. A nonzero result means the closeout is blocked; do not replace it with a success summary.
|
|
41
|
+
|
|
42
|
+
## Maintenance Trigger Check
|
|
43
|
+
|
|
44
|
+
Every full closeout runs this short check; full maintenance runs only when triggered.
|
|
45
|
+
|
|
46
|
+
- SESSION_LOG: trigger when the main log reaches at least 11 entries, exceeds 1500 lines, or the 10-closeout backstop is due. Keep recent safety-buffer entries; collapse only content already absorbed by an authoritative home. Archive older raw entries to `dev/SESSION_LOG_archive/archive_<batch>_<low_date>_to_<high_date>.md` and maintain `INDEX.md`. Port unique narrative before collapsing it.
|
|
47
|
+
- PROJECT_DECISIONS: trigger when a decisions-like handoff section has at least 30 entries; retain the newest 8–22 in the hot tier and move older decisions into the decisions archive. Also write substantive task evolution, a multi-option architectural choice with rationale, or a cross-session learning when observed.
|
|
48
|
+
- Backstop: every 10 closeouts, run the full long-term maintenance pass even when no semantic trigger is obvious. If the count cannot be determined confidently at the boundary, treat the backstop as due.
|
|
49
|
+
|
|
50
|
+
If no trigger applies, record one no-op reason. Handoff carries continuity; log and project decisions carry trace and long-term narrative.
|
|
51
|
+
|
|
52
|
+
## Opening Message And Card
|
|
53
|
+
|
|
54
|
+
The handoff opening-message block is authoritative. It must name the absolute root, route the agent through `AGENTS.md` and the handoff, state the current objective and boundary, and avoid instructing the next agent to redo completed work. It must not require SESSION_LOG as an ordinary startup read.
|
|
55
|
+
|
|
56
|
+
Use `agent-handoff-kit closeout-status --root <project root>` after the required read-backs. It renders the verified version when available and otherwise `version unverified`; never print the literal placeholder `v<version>`, hand-compose a substitute card, or use `handoff saved` unless the command reports `status: complete`.
|
|
57
|
+
|
|
58
|
+
```text
|
|
59
|
+
/\_/\ Agent Handoff Kit v<version>
|
|
60
|
+
( -.- ) handoff saved
|
|
61
|
+
> ^ <
|
|
62
|
+
|
|
63
|
+
status: complete
|
|
64
|
+
✅ Done: <completed summary>
|
|
65
|
+
🔎 QC: <validation summary>
|
|
66
|
+
📌 Handoff: opening message ready
|
|
67
|
+
⚠️ Boundary: <important boundary or none>
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
For `status: blocked`, the command instead says `handoff blocked`; retain that status and reason, then give the short local-root entry `Start Agent Handoff` / `開工` and the path-bearing fallback for an agent not yet pointed at the root. Do not hand-compose a third stateful prompt in the final response.
|
|
71
|
+
|
|
72
|
+
## Stop Conditions
|
|
73
|
+
|
|
74
|
+
Do not claim closeout complete when any required write or read-back failed, lifecycle state conflicts remain, the mirror is stale or duplicated, the root is uncertain, mandatory sync is unclassified, `closeout-status` is nonzero, or required Git persistence was explicitly part of the project's closeout contract but did not succeed. State the exact blocker and leave the project in an honest resumable state.
|
package/packs/coding.md
CHANGED
|
@@ -1,28 +1,28 @@
|
|
|
1
|
-
# Coding Pack
|
|
2
|
-
|
|
3
|
-
## Scope
|
|
4
|
-
|
|
5
|
-
Use for code changes, tests, builds, package managers, SDKs, CLIs, APIs, or developer tooling.
|
|
6
|
-
|
|
7
|
-
## Load When
|
|
8
|
-
|
|
9
|
-
- User asks to write, edit, debug, refactor, test, build, package, or integrate code.
|
|
10
|
-
- The task depends on framework, runtime, dependency, or API behavior.
|
|
11
|
-
|
|
12
|
-
## Rules
|
|
13
|
-
|
|
14
|
-
1. Read `dev/PROJECT_INDEX.md` for stack, commands, entry points, and directory roles before editing.
|
|
15
|
-
2. Inspect relevant source, tests, configs, and docs before changing code.
|
|
16
|
-
3. Prefer project-local patterns and helpers over new abstractions.
|
|
17
|
-
4. Do not guess current SDK, CLI, package, API, or deployment behavior when docs or project files can verify it.
|
|
18
|
-
5. Preserve unrelated user changes.
|
|
19
|
-
|
|
20
|
-
## Checks
|
|
21
|
-
|
|
22
|
-
- Run the narrowest relevant test, build, lint, or typecheck available.
|
|
23
|
-
- If a check cannot run, record why and what remains unverified.
|
|
24
|
-
- Check `dev/DOC_SYNC_REGISTRY.md` if behavior, commands, public docs, or runbooks changed.
|
|
25
|
-
|
|
26
|
-
## Closeout
|
|
27
|
-
|
|
28
|
-
Record files changed, commands run, results, remaining risks, and any project index or doc sync updates.
|
|
1
|
+
# Coding Pack
|
|
2
|
+
|
|
3
|
+
## Scope
|
|
4
|
+
|
|
5
|
+
Use for code changes, tests, builds, package managers, SDKs, CLIs, APIs, or developer tooling.
|
|
6
|
+
|
|
7
|
+
## Load When
|
|
8
|
+
|
|
9
|
+
- User asks to write, edit, debug, refactor, test, build, package, or integrate code.
|
|
10
|
+
- The task depends on framework, runtime, dependency, or API behavior.
|
|
11
|
+
|
|
12
|
+
## Rules
|
|
13
|
+
|
|
14
|
+
1. Read `dev/PROJECT_INDEX.md` for stack, commands, entry points, and directory roles before editing.
|
|
15
|
+
2. Inspect relevant source, tests, configs, and docs before changing code.
|
|
16
|
+
3. Prefer project-local patterns and helpers over new abstractions.
|
|
17
|
+
4. Do not guess current SDK, CLI, package, API, or deployment behavior when docs or project files can verify it.
|
|
18
|
+
5. Preserve unrelated user changes.
|
|
19
|
+
|
|
20
|
+
## Checks
|
|
21
|
+
|
|
22
|
+
- Run the narrowest relevant test, build, lint, or typecheck available.
|
|
23
|
+
- If a check cannot run, record why and what remains unverified.
|
|
24
|
+
- Check `dev/DOC_SYNC_REGISTRY.md` if behavior, commands, public docs, or runbooks changed.
|
|
25
|
+
|
|
26
|
+
## Closeout
|
|
27
|
+
|
|
28
|
+
Record files changed, commands run, results, remaining risks, and any project index or doc sync updates.
|
package/packs/communication.md
CHANGED
|
@@ -1,30 +1,32 @@
|
|
|
1
|
-
# Communication Pack
|
|
2
|
-
|
|
3
|
-
## Scope
|
|
4
|
-
|
|
5
|
-
Use for reply format, language behavior, output schema, user-facing explanation, and cross-agent handoff wording.
|
|
6
|
-
|
|
7
|
-
## Load When
|
|
8
|
-
|
|
9
|
-
- User requests a specific response format, language, style, report, review, or schema.
|
|
10
|
-
- The task changes public-facing instructions or AI-facing reply discipline.
|
|
11
|
-
|
|
12
|
-
## Rules
|
|
13
|
-
|
|
14
|
-
1. Match the user's language unless a project file requires another language.
|
|
15
|
-
2. Lead with decisions, findings, or results before background.
|
|
16
|
-
3.
|
|
17
|
-
4.
|
|
18
|
-
5.
|
|
19
|
-
6.
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
-
|
|
26
|
-
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
1
|
+
# Communication Pack
|
|
2
|
+
|
|
3
|
+
## Scope
|
|
4
|
+
|
|
5
|
+
Use for reply format, language behavior, output schema, user-facing explanation, and cross-agent handoff wording.
|
|
6
|
+
|
|
7
|
+
## Load When
|
|
8
|
+
|
|
9
|
+
- User requests a specific response format, language, style, report, review, or schema.
|
|
10
|
+
- The task changes public-facing instructions or AI-facing reply discipline.
|
|
11
|
+
|
|
12
|
+
## Rules
|
|
13
|
+
|
|
14
|
+
1. Match the user's language unless a project file requires another language.
|
|
15
|
+
2. Lead with decisions, findings, or results before background.
|
|
16
|
+
3. For an ordinary direct task, first state the result and practical effect in everyday language. Add a next step only when the user needs one; do not attach a repeated summary merely because the answer is short.
|
|
17
|
+
4. For a complex technical result, first give a short, clear conclusion and practical effect. Put exact commands, errors, hashes, source paths, and supporting evidence after the conclusion; when the user asks for technical depth, provide it without losing the clear takeaway.
|
|
18
|
+
5. Mark assumptions and unverified facts. Clear language never permits hiding uncertainty, safety risk, data loss, permission boundaries, or a blocked condition.
|
|
19
|
+
6. Keep operational instructions copy-paste-ready when they are meant for future sessions.
|
|
20
|
+
7. Avoid exposing internal process unless it helps the user act.
|
|
21
|
+
8. Give a clear recommended next step whenever the user needs to continue. If there is one best path, state it directly with a short reason. Offer two or three choices only when the user truly must decide; mark the recommended choice and do not turn an already-made technical judgment into an open question.
|
|
22
|
+
|
|
23
|
+
## Checks
|
|
24
|
+
|
|
25
|
+
- Verify required headings, schema fields, or language split.
|
|
26
|
+
- Check public README or docs if user-facing behavior changed.
|
|
27
|
+
- Confirm handoff/opening messages are complete and root-specific when needed.
|
|
28
|
+
- Confirm user-facing next-step wording names the recommended action and reason when a continuation is needed.
|
|
29
|
+
|
|
30
|
+
## Closeout
|
|
31
|
+
|
|
32
|
+
Record any durable response-format decisions and where they were persisted.
|