@brucewaynedecoy/make-docs 1.0.0-rc.1 → 2.0.2

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.
Files changed (187) hide show
  1. package/LICENSE +21 -201
  2. package/README.md +36 -27
  3. package/dist/backup-73HQNKMC.js +20 -0
  4. package/dist/backup-73HQNKMC.js.map +1 -0
  5. package/dist/chunk-3BAJQXGH.js +1575 -0
  6. package/dist/chunk-3BAJQXGH.js.map +1 -0
  7. package/dist/chunk-64CTKJO7.js +4136 -0
  8. package/dist/chunk-64CTKJO7.js.map +1 -0
  9. package/dist/chunk-BENO4IH5.js +875 -0
  10. package/dist/chunk-BENO4IH5.js.map +1 -0
  11. package/dist/chunk-D4HDZEJT.js +37 -0
  12. package/dist/chunk-D4HDZEJT.js.map +1 -0
  13. package/dist/chunk-G5EF63GG.js +1291 -0
  14. package/dist/chunk-G5EF63GG.js.map +1 -0
  15. package/dist/chunk-GNP6HRVP.js +523 -0
  16. package/dist/chunk-GNP6HRVP.js.map +1 -0
  17. package/dist/chunk-HJYIQTMD.js +204 -0
  18. package/dist/chunk-HJYIQTMD.js.map +1 -0
  19. package/dist/chunk-LQ5NSWCJ.js +39 -0
  20. package/dist/chunk-LQ5NSWCJ.js.map +1 -0
  21. package/dist/chunk-LRVV7UDD.js +2340 -0
  22. package/dist/chunk-LRVV7UDD.js.map +1 -0
  23. package/dist/chunk-LVQSJF63.js +24674 -0
  24. package/dist/chunk-LVQSJF63.js.map +1 -0
  25. package/dist/chunk-MXBHCHSM.js +13995 -0
  26. package/dist/chunk-MXBHCHSM.js.map +1 -0
  27. package/dist/chunk-Z5K4FHYP.js +922 -0
  28. package/dist/chunk-Z5K4FHYP.js.map +1 -0
  29. package/dist/index.js +3798 -250
  30. package/dist/index.js.map +1 -1
  31. package/dist/self-YYXOLDKU.js +653 -0
  32. package/dist/self-YYXOLDKU.js.map +1 -0
  33. package/dist/server-O2ZELIMX.js +512 -0
  34. package/dist/server-O2ZELIMX.js.map +1 -0
  35. package/dist/setup-system-HZROFNMP.js +544 -0
  36. package/dist/setup-system-HZROFNMP.js.map +1 -0
  37. package/dist/{skills-command-3ESCZ75U.js → skills-command-MGGHY7HU.js} +190 -32
  38. package/dist/skills-command-MGGHY7HU.js.map +1 -0
  39. package/dist/uninstall-3UXXXNFO.js +223 -0
  40. package/dist/uninstall-3UXXXNFO.js.map +1 -0
  41. package/dist/virtual_make-docs-first-party-skills-ZII74YOB.js +11 -0
  42. package/dist/virtual_make-docs-first-party-skills-ZII74YOB.js.map +1 -0
  43. package/package.json +9 -6
  44. package/skill-registry.json +328 -125
  45. package/skill-registry.schema.json +221 -45
  46. package/template/.make-docs/AGENTS.md +18 -0
  47. package/template/.make-docs/CLAUDE.md +18 -0
  48. package/template/.make-docs/archive/AGENTS.md +11 -0
  49. package/template/.make-docs/archive/CLAUDE.md +11 -0
  50. package/template/.make-docs/system/AGENTS.md +12 -0
  51. package/template/.make-docs/system/CLAUDE.md +12 -0
  52. package/template/.make-docs/system/contracts/AGENTS.md +13 -0
  53. package/template/.make-docs/system/contracts/CLAUDE.md +13 -0
  54. package/template/{docs/assets/references → .make-docs/system/contracts}/commit-message-convention.md +4 -4
  55. package/template/.make-docs/system/contracts/coverage-pass-contract.md +198 -0
  56. package/template/.make-docs/system/contracts/deferred-obligation-contract.md +128 -0
  57. package/template/{docs/assets/references → .make-docs/system/contracts}/design-contract.md +7 -2
  58. package/template/{docs/assets/references → .make-docs/system/contracts}/guide-contract.md +21 -19
  59. package/template/{docs/assets/references → .make-docs/system/contracts}/history-record-contract.md +17 -11
  60. package/template/.make-docs/system/contracts/human-experience-contract.md +134 -0
  61. package/template/.make-docs/system/contracts/naive-uat-contract.md +231 -0
  62. package/template/.make-docs/system/contracts/output-contract.md +277 -0
  63. package/template/.make-docs/system/contracts/performance-evidence-governance.md +257 -0
  64. package/template/.make-docs/system/contracts/system-resource-contract.md +93 -0
  65. package/template/.make-docs/system/prompts/AGENTS.md +12 -0
  66. package/template/.make-docs/system/prompts/CLAUDE.md +12 -0
  67. package/template/.make-docs/system/prompts/coverage-pass-maintainer-guide.prompt.md +20 -0
  68. package/template/.make-docs/system/prompts/coverage-pass-prd-reconciliation.prompt.md +18 -0
  69. package/template/.make-docs/system/prompts/coverage-pass-testing-uat.prompt.md +46 -0
  70. package/template/.make-docs/system/prompts/coverage-pass-user-guide.prompt.md +20 -0
  71. package/template/.make-docs/system/prompts/designs-to-plan-change.prompt.md +18 -0
  72. package/template/.make-docs/system/prompts/designs-to-plan.prompt.md +14 -0
  73. package/template/.make-docs/system/prompts/docs-path-hygiene-cleanup.prompt.md +29 -0
  74. package/template/.make-docs/system/prompts/naive-uat-facilitator.prompt.md +28 -0
  75. package/template/.make-docs/system/prompts/naive-uat-tester.prompt.md +20 -0
  76. package/template/.make-docs/system/prompts/performance-coverage.prompt.md +63 -0
  77. package/template/.make-docs/system/prompts/plan-to-prd-change.prompt.md +12 -0
  78. package/template/.make-docs/system/prompts/plan-to-prd-green-field.prompt.md +10 -0
  79. package/template/.make-docs/system/prompts/prd-change-to-work.prompt.md +14 -0
  80. package/template/.make-docs/system/prompts/prd-to-work-full-prd.prompt.md +10 -0
  81. package/template/.make-docs/system/prompts/prd-to-work-prd-feature.prompt.md +10 -0
  82. package/template/.make-docs/system/prompts/request-to-design.prompt.md +20 -0
  83. package/template/.make-docs/system/prompts/session-to-history-record.prompt.md +23 -0
  84. package/template/{docs/assets → .make-docs/system}/prompts/work-to-commit-message.prompt.md +2 -2
  85. package/template/.make-docs/system/prompts/work-to-guides.prompt.md +22 -0
  86. package/template/.make-docs/system/references/AGENTS.md +14 -0
  87. package/template/.make-docs/system/references/CLAUDE.md +14 -0
  88. package/template/{docs/assets → .make-docs/system}/references/design-workflow.md +15 -2
  89. package/template/.make-docs/system/references/execution-workflow.md +189 -0
  90. package/template/.make-docs/system/references/human-experience.md +138 -0
  91. package/template/.make-docs/system/references/lifecycle.md +153 -0
  92. package/template/.make-docs/system/references/naive-uat-validation.md +65 -0
  93. package/template/.make-docs/system/references/naive-uat-workflow.md +64 -0
  94. package/template/.make-docs/system/references/path-and-link-hygiene.md +101 -0
  95. package/template/.make-docs/system/references/performance-evidence.md +114 -0
  96. package/template/.make-docs/system/references/planning-workflow.md +209 -0
  97. package/template/.make-docs/system/references/prd-change-management.md +165 -0
  98. package/template/{docs/assets → .make-docs/system}/references/wave-model.md +10 -8
  99. package/template/.make-docs/system/templates/AGENTS.md +12 -0
  100. package/template/.make-docs/system/templates/CLAUDE.md +12 -0
  101. package/template/.make-docs/system/templates/design.md +79 -0
  102. package/template/{docs/assets/templates/guide-developer.md → .make-docs/system/templates/guide-maintainer.md} +7 -3
  103. package/template/{docs/assets → .make-docs/system}/templates/guide-user.md +6 -2
  104. package/template/{docs/assets → .make-docs/system}/templates/history-record.md +6 -3
  105. package/template/.make-docs/system/templates/naive-uat-scenario.md +91 -0
  106. package/template/.make-docs/system/templates/performance-evidence-profile.md +252 -0
  107. package/template/.make-docs/system/templates/plan-overview.md +76 -0
  108. package/template/.make-docs/system/templates/plan-prd-change.md +155 -0
  109. package/template/{docs/assets → .make-docs/system}/templates/plan-prd-decompose.md +10 -0
  110. package/template/{docs/assets → .make-docs/system}/templates/plan-prd.md +28 -2
  111. package/template/{docs/assets → .make-docs/system}/templates/prd-architecture.md +13 -0
  112. package/template/.make-docs/system/templates/prd-glossary.md +28 -0
  113. package/template/.make-docs/system/templates/prd-index.md +70 -0
  114. package/template/{docs/assets → .make-docs/system}/templates/prd-overview.md +13 -0
  115. package/template/.make-docs/system/templates/prd-reference.md +30 -0
  116. package/template/{docs/assets → .make-docs/system}/templates/prd-risk-register.md +16 -1
  117. package/template/{docs/assets → .make-docs/system}/templates/prd-subsystem.md +15 -0
  118. package/template/.make-docs/system/templates/work-index.md +58 -0
  119. package/template/.make-docs/system/templates/work-phase.md +107 -0
  120. package/template/.make-docs/system-resources.catalog.json +91 -0
  121. package/template/.make-docs/system-resources.schema.json +204 -0
  122. package/template/AGENTS.md +8 -1
  123. package/template/CLAUDE.md +8 -1
  124. package/template/docs/AGENTS.codex-only.md +22 -0
  125. package/template/docs/AGENTS.md +21 -13
  126. package/template/docs/CLAUDE.claude-only.md +22 -0
  127. package/template/docs/CLAUDE.md +21 -13
  128. package/template/docs/assets/AGENTS.md +11 -7
  129. package/template/docs/assets/CLAUDE.md +11 -7
  130. package/template/docs/designs/AGENTS.md +8 -3
  131. package/template/docs/designs/CLAUDE.md +8 -3
  132. package/template/docs/plans/AGENTS.md +10 -3
  133. package/template/docs/plans/CLAUDE.md +10 -3
  134. package/template/docs/prd/AGENTS.md +14 -4
  135. package/template/docs/prd/CLAUDE.md +14 -4
  136. package/template/docs/work/AGENTS.md +10 -3
  137. package/template/docs/work/CLAUDE.md +10 -3
  138. package/dist/chunk-HP3HBG7F.js +0 -626
  139. package/dist/chunk-HP3HBG7F.js.map +0 -1
  140. package/dist/chunk-QRFH4J6H.js +0 -1194
  141. package/dist/chunk-QRFH4J6H.js.map +0 -1
  142. package/dist/chunk-WM3OXYTW.js +0 -2630
  143. package/dist/chunk-WM3OXYTW.js.map +0 -1
  144. package/dist/skills-command-3ESCZ75U.js.map +0 -1
  145. package/dist/uninstall-GQE4SJF2.js +0 -150
  146. package/dist/uninstall-GQE4SJF2.js.map +0 -1
  147. package/template/.make-docs/scripts/check_path_hygiene.py +0 -435
  148. package/template/docs/assets/archive/AGENTS.md +0 -20
  149. package/template/docs/assets/archive/CLAUDE.md +0 -20
  150. package/template/docs/assets/history/AGENTS.md +0 -12
  151. package/template/docs/assets/history/CLAUDE.md +0 -12
  152. package/template/docs/assets/prompts/AGENTS.md +0 -8
  153. package/template/docs/assets/prompts/CLAUDE.md +0 -8
  154. package/template/docs/assets/prompts/designs-to-plan-change.prompt.md +0 -14
  155. package/template/docs/assets/prompts/designs-to-plan.prompt.md +0 -10
  156. package/template/docs/assets/prompts/docs-path-hygiene-cleanup.prompt.md +0 -27
  157. package/template/docs/assets/prompts/plan-to-prd-change.prompt.md +0 -8
  158. package/template/docs/assets/prompts/plan-to-prd-green-field.prompt.md +0 -6
  159. package/template/docs/assets/prompts/prd-change-to-work.prompt.md +0 -10
  160. package/template/docs/assets/prompts/prd-to-work-full-prd.prompt.md +0 -6
  161. package/template/docs/assets/prompts/prd-to-work-prd-feature.prompt.md +0 -6
  162. package/template/docs/assets/prompts/request-to-design.prompt.md +0 -16
  163. package/template/docs/assets/prompts/session-to-history-record.prompt.md +0 -19
  164. package/template/docs/assets/prompts/work-to-guides.prompt.md +0 -18
  165. package/template/docs/assets/references/AGENTS.md +0 -9
  166. package/template/docs/assets/references/CLAUDE.md +0 -9
  167. package/template/docs/assets/references/execution-workflow.md +0 -157
  168. package/template/docs/assets/references/output-contract.md +0 -221
  169. package/template/docs/assets/references/path-and-link-hygiene.md +0 -49
  170. package/template/docs/assets/references/planning-workflow.md +0 -160
  171. package/template/docs/assets/references/prd-change-management.md +0 -129
  172. package/template/docs/assets/templates/AGENTS.md +0 -8
  173. package/template/docs/assets/templates/CLAUDE.md +0 -8
  174. package/template/docs/assets/templates/design.md +0 -30
  175. package/template/docs/assets/templates/plan-overview.md +0 -32
  176. package/template/docs/assets/templates/plan-prd-change.md +0 -99
  177. package/template/docs/assets/templates/prd-change-addition.md +0 -45
  178. package/template/docs/assets/templates/prd-change-revision.md +0 -45
  179. package/template/docs/assets/templates/prd-glossary.md +0 -15
  180. package/template/docs/assets/templates/prd-index.md +0 -45
  181. package/template/docs/assets/templates/prd-reference.md +0 -17
  182. package/template/docs/assets/templates/work-index.md +0 -21
  183. package/template/docs/assets/templates/work-phase.md +0 -34
  184. package/template/docs/guides/AGENTS.md +0 -15
  185. package/template/docs/guides/CLAUDE.md +0 -15
  186. /package/template/{docs/assets → .make-docs/system}/prompts/update-readme-green-field.prompt.md +0 -0
  187. /package/template/{docs/assets → .make-docs/system}/references/harness-capability-matrix.md +0 -0
@@ -0,0 +1,63 @@
1
+ ___
2
+ name: Performance Coverage
3
+ description: Inventories current performance candidates and records bounded governance decisions.
4
+ ___
5
+
6
+ Inventory performance evidence needs for the current accepted work. Do not run a benchmark or change runtime state.
7
+
8
+ Before writing, read:
9
+
10
+ - `make-docs://system/contract/performance-evidence-governance.md`;
11
+ - `make-docs://system/reference/performance-evidence.md`;
12
+ - `make-docs://system/template/performance-evidence-profile.md`;
13
+ - the accepted PRD, plan, and work records for the changed surface; and
14
+ - the router for the target output directory.
15
+
16
+ Use the contract as the only reusable policy source.
17
+
18
+ ## Bounded Inventory
19
+
20
+ Inventory only current candidates that can affect the accepted work or a current product decision. Include active numeric targets, relative regression claims, resource budgets, absolute performance words, current benchmark assets, and current evidence. Do not expand the inventory to unrelated history or future ideas.
21
+
22
+ For every candidate, record both axes:
23
+
24
+ 1. Base maintenance action: `create`, `update-existing`, `link-only`, or `none`.
25
+ 2. Performance applicability: `required-now`, `characterize-now`, `defer-required`, `not-needed`, or `reject-unsupported`.
26
+
27
+ Also record the qualification fields required by the contract. Give each decision a short reason that names the evidence or authority used. Do not skip a candidate silently.
28
+
29
+ For an applicable candidate, record one target class and its one canonical owner. Do not treat a plan or work guardrail as product authority. Do not turn a baseline into a threshold.
30
+
31
+ ## Decision Questions
32
+
33
+ Ask a question only when the answer can change applicability, target class, canonical owner, supported scope, or execution authority.
34
+
35
+ Ask at most one grouped clarification round. Keep it to the unresolved decision fields. Do not ask for a preferred framework, sample count, environment, statistic, or target until accepted authority makes an executable profile necessary.
36
+
37
+ If authority remains missing after that round, record the missing authority and stop that candidate. Do not invent a target, owner, approval, `O-###`, `PERF-###`, environment, method, budget, or result.
38
+
39
+ ## Progressive Output
40
+
41
+ Use the profile template for each recorded candidate.
42
+
43
+ - For `not-needed` or `reject-unsupported`, finish the applicability record and stop.
44
+ - For `defer-required`, link the accepted `O-###` and stop.
45
+ - For `required-now` or `characterize-now`, create or update a `PERF-###` profile only in its canonical owning record.
46
+
47
+ An executable profile must state its finite evidence budget and stop rules before any run. Reuse a current result when its fingerprint is unchanged. After a material change, route only affected checks. Stop at budget exhaustion or diminishing return.
48
+
49
+ ## Closeout
50
+
51
+ Return a short table with each candidate, both decisions, target class or `none`, canonical owner, reason, and next record link.
52
+
53
+ Then state:
54
+
55
+ - files changed or `none`;
56
+ - profiles created or updated, with exact IDs;
57
+ - deferred obligations linked, with exact IDs;
58
+ - reused evidence;
59
+ - unresolved authority gaps;
60
+ - focused validation run; and
61
+ - the stop reason for the inventory.
62
+
63
+ Do not claim a performance result, product support, release readiness, or another proof mode from this coverage inventory.
@@ -0,0 +1,12 @@
1
+ ___
2
+ name: Plan to PRD Authority Maintenance
3
+ description: Instructs the agent to execute an approved maintenance plan by surgically updating the active product authority.
4
+ ___
5
+
6
+ When generating or materially rewriting make-docs documents, include PRD 23 YAML frontmatter: common `title`, `kind`, and `status`; add `coordinate`, `persona`, `source`, `lifecycle`, and `follow_on` only when their conditions apply; omit unknown coordinate levels rather than inserting placeholders.
7
+
8
+ Please review the approved PRD authority-maintenance plan {{CHANGE PLAN DOC}} and then execute it against the active PRD namespace in `docs/prd/`.
9
+
10
+ Read `make-docs://system/contract/human-experience-contract.md`, `make-docs://system/reference/human-experience.md`, and `make-docs://system/reference/lifecycle.md` through valid local bodies or `make-docs resource read`. Reconcile the plan's local human outcome with current product authority. Put each observable outcome or preserved boundary in the PRD that owns the affected surface. Preserve links to the source design, plan, and W/R coordinate. Keep the planned proof or current testing decision, its selected executor, and any accepted obligation route traceable for downstream work. Do not copy the full design intent or Human Experience Standard into the PRD set. Do not add Human Experience frontmatter.
11
+
12
+ Follow the instructions, references, and templates in the `docs` directory, especially `.make-docs/system/references/prd-change-management.md`. Update current normative requirements inline in their existing owners. Create a new numbered PRD only for a coherent, wholesale new capability, subsystem, or product boundary with no suitable owner. Add standardized, non-normative `## Requirement History` entries for material prior contracts, update the risk register and index where needed, and record `none` decisions outside the active PRD tree. Do not create addition, enhancement, revision, removal, migration, or reconciliation PRDs. Do not renumber existing PRDs. PRD document identity is the product subject, not W/R; carry the plan coordinate only in source links and requirement-history entries.
@@ -0,0 +1,10 @@
1
+ ___
2
+ name: Plan to PRD (Green Field)
3
+ description: Instructs the agent to generate a comprehensive set of PRD documents based from a specific plan document. Agent will automatically determine if parallel agents are needed, based on scope and complexity. If there are already requirements documents in `docs/prd`, they will be archived in a dated sub-folder (per agent instructions in `AGENTS.md` and `CLAUDE.md`).
4
+ ___
5
+
6
+ When generating or materially rewriting make-docs documents, include PRD 23 YAML frontmatter: common `title`, `kind`, and `status`; add `coordinate`, `persona`, `source`, `lifecycle`, and `follow_on` only when their conditions apply; omit unknown coordinate levels rather than inserting placeholders.
7
+
8
+ Read `make-docs://system/contract/human-experience-contract.md`, `make-docs://system/reference/human-experience.md`, and `make-docs://system/reference/lifecycle.md` through valid local bodies or `make-docs resource read`. Reconcile the plan's local human outcome with current product authority. Put each observable outcome or preserved boundary in the PRD that owns the affected surface. Preserve links to the source design, plan, and W/R coordinate. Keep the planned proof or current testing decision, its selected executor, and any accepted obligation route traceable for downstream work. Do not copy the full design intent or Human Experience Standard into the PRD set. Do not add Human Experience frontmatter.
9
+
10
+ I think we're ready to create the PRD documents in `docs/prd`. Please be as detailed as possible. Follow the instructions, references, and templates provided to you in the `docs` directory (and appropriate child directories) on how to do this. The resulting PRD set should be a comprehensive design based on the details you captured in the {{PLAN DOC}} plan doc.
@@ -0,0 +1,14 @@
1
+ ___
2
+ name: PRD Authority Maintenance to Work Backlog
3
+ description: Instructs the agent to generate a dated delta backlog from the updated authoritative PRDs and their governing maintenance plan.
4
+ ___
5
+
6
+ When generating or materially rewriting make-docs documents, include PRD 23 YAML frontmatter: common `title`, `kind`, and `status`; add `coordinate`, `persona`, `source`, `lifecycle`, and `follow_on` only when their conditions apply; omit unknown coordinate levels rather than inserting placeholders.
7
+
8
+ Please review the approved PRD authority-maintenance plan: {{CHANGE PLAN DOC}}.
9
+
10
+ Then review the updated or genuinely new authoritative PRDs that own the resulting requirements: {{AUTHORITATIVE PRD DOCS}}.
11
+
12
+ Read `make-docs://system/contract/human-experience-contract.md`, `make-docs://system/reference/human-experience.md`, and `make-docs://system/reference/lifecycle.md` through valid local bodies or `make-docs resource read`. For each applicable current PRD outcome or preserved boundary, create work tasks and observable acceptance criteria that retain the intended human outcome, owning requirement, affected surface, source design and plan lineage, and W/R coordinate. Name the evidence source or current testing decision and its selected executor when current authority has selected one. Route accepted deferral through the current obligation contract. Do not copy the full design intent or Human Experience Standard into the backlog. Do not add Human Experience frontmatter.
13
+
14
+ Generate a dated delta backlog in `docs/work/`. Follow the instructions, references, and templates in the `docs` directory, especially `.make-docs/system/references/prd-change-management.md`. The backlog should stay scoped to the requested maintenance, remain dependency-ordered, and cite the updated authoritative PRDs in each phase's source-traceability section. Use the maintenance plan for sequencing and scope provenance only. Treat current normative PRD sections as product authority; do not treat requirement-history entries or retired change records as effective requirements.
@@ -0,0 +1,10 @@
1
+ ___
2
+ name: PRD to Work Backlog (Full PRD Set)
3
+ description: Instructs the agent to generate a work backlog document or set of documents from the full PRD.
4
+ ___
5
+
6
+ When generating or materially rewriting make-docs documents, include PRD 23 YAML frontmatter: common `title`, `kind`, and `status`; add `coordinate`, `persona`, `source`, `lifecycle`, and `follow_on` only when their conditions apply; omit unknown coordinate levels rather than inserting placeholders.
7
+
8
+ Read `make-docs://system/contract/human-experience-contract.md`, `make-docs://system/reference/human-experience.md`, and `make-docs://system/reference/lifecycle.md` through valid local bodies or `make-docs resource read`. For each applicable current PRD outcome or preserved boundary, create work tasks and observable acceptance criteria that retain the intended human outcome, owning requirement, affected surface, source design and plan lineage, and W/R coordinate. Name the evidence source or current testing decision and its selected executor when current authority has selected one. Route accepted deferral through the current obligation contract. Do not copy the full design intent or Human Experience Standard into the backlog. Do not add Human Experience frontmatter.
9
+
10
+ Please generate a work backlog based on what's in the PRD set (in `docs/prd/`). We will need a work backlog document or documents (in `docs/work/`) for a full implementation of all of the features. Follow the instructions, references, and templates provided to you in the `docs` directory (and appropriate child directories) on how to do this.
@@ -0,0 +1,10 @@
1
+ ___
2
+ name: PRD to Work (for Single PRD Feature)
3
+ description: Instructs the agent to generate a work backlog document or set of documents for a single requirement document from the PRD set. Generally, a requirement document encapsulates a single feature or epic.
4
+ ___
5
+
6
+ When generating or materially rewriting make-docs documents, include PRD 23 YAML frontmatter: common `title`, `kind`, and `status`; add `coordinate`, `persona`, `source`, `lifecycle`, and `follow_on` only when their conditions apply; omit unknown coordinate levels rather than inserting placeholders.
7
+
8
+ Read `make-docs://system/contract/human-experience-contract.md`, `make-docs://system/reference/human-experience.md`, and `make-docs://system/reference/lifecycle.md` through valid local bodies or `make-docs resource read`. For each applicable current PRD outcome or preserved boundary, create work tasks and observable acceptance criteria that retain the intended human outcome, owning requirement, affected surface, source design and plan lineage, and W/R coordinate. Name the evidence source or current testing decision and its selected executor when current authority has selected one. Route accepted deferral through the current obligation contract. Do not copy the full design intent or Human Experience Standard into the backlog. Do not add Human Experience frontmatter.
9
+
10
+ Please review the requirement document {{REQUIREMENT DOC}} to understand the requirements for the specific epic or feature captured in that document. Then generate a document (or possibly documents) for our work backlog in `docs/work/`. Follow the instructions, references, and templates provided to you in the `docs` directory (and appropriate child directories) on how to do this.
@@ -0,0 +1,20 @@
1
+ ___
2
+ name: Request to Design
3
+ description: Instructs the agent to turn a user request into a design doc by updating an existing related design or creating a new dated design doc.
4
+ ___
5
+
6
+ When generating or materially rewriting make-docs documents, include PRD 23 YAML frontmatter: common `title`, `kind`, and `status`; add `coordinate`, `persona`, `source`, `lifecycle`, and `follow_on` only when their conditions apply; omit unknown coordinate levels rather than inserting placeholders.
7
+
8
+ Please review the request below and then either generate or update a design doc for the request.
9
+
10
+ Before writing anything, inspect `docs/designs/` for related design docs. If a related design clearly covers the same decision area, update it. Otherwise create a new dated design doc in `docs/designs/`.
11
+
12
+ Follow the instructions, references, and templates in the `docs` directory, especially `.make-docs/system/references/design-workflow.md`, `.make-docs/system/contracts/design-contract.md`, and `.make-docs/system/templates/design.md`.
13
+
14
+ Read `make-docs://system/contract/human-experience-contract.md` and `make-docs://system/reference/human-experience.md` through a valid local body or `make-docs resource read`. Use their conditional intent form once, after Context and before Decision. Classify the change's effect, resolve human roles or configured Personas, and state the goal and observable promises before internal detail. Name evidence as planned work. If current authority cannot support a coherent human path, stop for the missing product choice. Follow the design workflow's required-validation route for new and substantial design work; do not force older or minor-edited designs into a rewrite.
15
+
16
+ The resulting design doc should include an explicit `## Intended Follow-On` section with either `baseline-plan` or `change-plan` and the matching prompt link. Do not create a plan as part of this workflow.
17
+
18
+ Here is the request:
19
+
20
+ {{REQUEST}}
@@ -0,0 +1,23 @@
1
+ ___
2
+ name: Session to History Record
3
+ description: Instructs the agent to summarize the current session into a new dated history record under `.make-docs/archive/history/`.
4
+ ___
5
+
6
+ When generating or materially rewriting make-docs documents, include PRD 23 YAML frontmatter: common `title`, `kind`, and `status`; add `coordinate`, `persona`, `source`, `lifecycle`, and `follow_on` only when their conditions apply; omit unknown coordinate levels rather than inserting placeholders.
7
+
8
+ Please summarize this session into a new history record.
9
+
10
+ Before writing anything, read `.make-docs/system/contracts/history-record-contract.md`, `.make-docs/system/contracts/coverage-pass-contract.md`, `.make-docs/system/templates/history-record.md`, and the router at `.make-docs/archive/AGENTS.md` (or `CLAUDE.md`). Do not restate their rules — follow them.
11
+
12
+ If this history record is part of a coverage pass, apply the history idempotency rule in `coverage-pass-contract.md` before deciding whether to create a new file or update the current session's record.
13
+
14
+ Use today's date for `YYYY-MM-DD` and never backdate. If the active plan or work context gives a known position, record it in one `coordinate` frontmatter field such as `W9 R0 P1` or `W9 R0 P1 S2 T4`; omit unknown coordinate levels.
15
+
16
+ Create a new file under `.make-docs/archive/history/` (default slug `summary`). If W/R/P is known, name it `YYYY-MM-DD-w{W}-r{R}-p{P}-<slug>.md`. If only W/R is known, name it `YYYY-MM-DD-w{W}-r{R}-<slug>.md`. If no coordinate is known, name it `YYYY-MM-DD-<slug>.md`. Fill only known frontmatter fields; do not invent unknown `client`, `model`, or `provider` values. Follow the required headings exactly: `## Changes`, then `## Documentation` containing `### Project`, `### Maintainer`, and `### User` tables. State `None this session.` for any empty sub-section.
17
+
18
+ Keep the summary concise — breadcrumbs for a future auditor, not a verbose narrative. Use relative Markdown links to any touched files, plans, designs, or backlog phases. When deferred obligations or Unassisted Goal Testing changed materially, summarize the durable delta once in `## Changes`. Name an affected `O-###` or `NUAT-###` when one exists. Record `not-needed-now` without inventing an ID. Include the orphan-audit outcome when relevant and the resulting scenario or finding disposition. Do not copy raw run logs or evidence transcripts.
19
+
20
+ Optional hints (leave blank to accept defaults):
21
+
22
+ - Focus: {{FOCUS}}
23
+ - Slug: {{SLUG}}
@@ -5,14 +5,14 @@ ___
5
5
 
6
6
  Please prepare a commit message for the current work using the make-docs commit message convention.
7
7
 
8
- Before drafting or committing, read `docs/assets/references/commit-message-convention.md`. Use it as the authority for subject shape, body source, and commit execution rules.
8
+ Before drafting or committing, read `.make-docs/system/contracts/commit-message-convention.md`. Use it as the authority for subject shape, body source, and commit execution rules.
9
9
 
10
10
  Inspect the local context first:
11
11
 
12
12
  - `git status --short`
13
13
  - recent commit subjects with `git log --format='%h %s' -n 30`
14
14
  - the relevant design, plan, work, and history records for the requested coordinate
15
- - `docs/assets/history/` for current history records, falling back to legacy records only when needed
15
+ - `.make-docs/archive/history/` for current breadcrumb records
16
16
 
17
17
  If the user explicitly asks you to commit, stage only the requested change set, create the commit with the drafted subject/body, and verify it with `git log -1 --format=%B`. Do not stage unrelated edits, do not rewrite user work, and do not create a commit when the request is only to draft a message.
18
18
 
@@ -0,0 +1,22 @@
1
+ ___
2
+ name: Work to Guides
3
+ description: Instructs the agent to create or update maintainer and user guides from completed work backlog phases.
4
+ ___
5
+
6
+ When generating or materially rewriting make-docs documents, include PRD 23 YAML frontmatter: common `title`, `kind`, and `status`; add `coordinate`, `persona`, `source`, `lifecycle`, and `follow_on` only when their conditions apply; omit unknown coordinate levels rather than inserting placeholders.
7
+
8
+ Please review the completed work below and create or update the appropriate maintainer and/or user guides.
9
+
10
+ Before writing anything, read `.make-docs/system/contracts/coverage-pass-contract.md`, `.make-docs/system/contracts/guide-contract.md`, the matching guide template in `.make-docs/system/templates/`, and the router in `docs/assets/`. Treat those files as the authority for coverage-pass mechanics, audience intent, frontmatter, slug rules, guide coverage decisions, and future coverage handling.
11
+
12
+ Start by inspecting existing guides under each effective `docs/assets/<persona-slug>/`, including the built-in `maintainer` and `user` audiences. Decide whether each completed capability should result in `create`, `update-existing`, `link-only`, or `none`, with a separate target from the effective Persona set.
13
+
14
+ When this prompt is used as a coverage pass, apply the history idempotency rule and validation checklist in `coverage-pass-contract.md`, and record a verdict and reason for every candidate, including `none`.
15
+
16
+ Write guides as current-state documentation, not as phase summaries. Maintainer guides should help contributors and maintainers navigate the project, codebase, contracts, validation, extension points, and safe-change workflows so they can reach a useful first PR or maintenance action quickly. User guides should help users understand and use what the project ships, with novice-friendly orientation and clear paths into advanced capabilities.
17
+
18
+ If current confirmed behavior is useful now, document it now. If downstream capabilities are needed to complete or enrich the guide later, add a `## Future Coverage` section with `Blocked by`, `Update when`, and `Guide change` items. Do not create design docs, architecture decisions, or PRD risk-register items solely to remember future guide work.
19
+
20
+ Here is the completed work context:
21
+
22
+ {{WORK_CONTEXT}}
@@ -0,0 +1,14 @@
1
+ <!-- make-docs:begin -->
2
+ # System References Router
3
+
4
+ This always-local directory routes Make Docs references. A reference explains a workflow or gives context without replacing its governing contract. Reference bodies are optional local projections.
5
+
6
+ - Use a valid local reference body first. If it is absent, read `make-docs://system/reference/<posix-relative-path>` with `make-docs resource read`.
7
+ - Read only the specific reference needed for the task.
8
+ - Use these resources to resolve structure, lifecycle, and workflow questions instead of restating those rules in routers.
9
+ - Use `lifecycle.md` for the lifecycle arc and `naive-uat-workflow.md` to compose the governing contract, prompts, and scenario template.
10
+ - Use `.make-docs/system/contracts/coverage-pass-contract.md` for shared coverage-pass rules.
11
+ - Use `path-and-link-hygiene.md` for project-relative path rules, relative Markdown links, safe placeholders, and full-path exceptions.
12
+ - Do not treat this directory as an output target or modify a resource body unless the user asks.
13
+ - Do not infer optional Skills, plugins, Playbooks, Protocols, or unavailable policy from this router.
14
+ <!-- make-docs:end -->
@@ -0,0 +1,14 @@
1
+ <!-- make-docs:begin -->
2
+ # System References Router
3
+
4
+ This always-local directory routes Make Docs references. A reference explains a workflow or gives context without replacing its governing contract. Reference bodies are optional local projections.
5
+
6
+ - Use a valid local reference body first. If it is absent, read `make-docs://system/reference/<posix-relative-path>` with `make-docs resource read`.
7
+ - Read only the specific reference needed for the task.
8
+ - Use these resources to resolve structure, lifecycle, and workflow questions instead of restating those rules in routers.
9
+ - Use `lifecycle.md` for the lifecycle arc and `naive-uat-workflow.md` to compose the governing contract, prompts, and scenario template.
10
+ - Use `.make-docs/system/contracts/coverage-pass-contract.md` for shared coverage-pass rules.
11
+ - Use `path-and-link-hygiene.md` for project-relative path rules, relative Markdown links, safe placeholders, and full-path exceptions.
12
+ - Do not treat this directory as an output target or modify a resource body unless the user asks.
13
+ - Do not infer optional Skills, plugins, Playbooks, Protocols, or unavailable policy from this router.
14
+ <!-- make-docs:end -->
@@ -37,8 +37,9 @@ Before writing:
37
37
  - `baseline-plan`
38
38
  - `change-plan`
39
39
  - Required prompt links:
40
- - `baseline-plan` → `docs/assets/prompts/designs-to-plan.prompt.md`
41
- - `change-plan` → `docs/assets/prompts/designs-to-plan-change.prompt.md`
40
+ - `baseline-plan` → `make-docs://system/prompt/designs-to-plan.prompt.md`
41
+ - `change-plan` → `make-docs://system/prompt/designs-to-plan-change.prompt.md`
42
+ - Resolve the selected prompt with `make-docs resource read <uri>`. Do not require a local projection.
42
43
  - Downstream planners should treat the explicit route in `## Intended Follow-On` as authoritative unless the user explicitly overrides it.
43
44
  - Route guidance:
44
45
  - use `baseline-plan` when the design should feed a fresh baseline planning flow
@@ -58,3 +59,15 @@ Before closing the task, confirm:
58
59
  3. The create-vs-update choice is justified by the current design tree.
59
60
  4. `## Design Lineage` is present when the design materially updates prior intent.
60
61
  5. `## Intended Follow-On` includes both the route and the matching prompt link.
62
+
63
+ ## Human Experience Intent and Validation
64
+
65
+ Use the [Human Experience Contract](../contracts/human-experience-contract.md) and [reference](human-experience.md) before drafting the intent. Classify the proposed change, not the act of reading a design. Resolve configured human Personas or clear human roles. State the goal before internal detail. Use observable promises and planned evidence. Stop for a missing product choice when no coherent human path follows from accepted authority.
66
+
67
+ The contract applies to new generated designs and substantial agent-authored updates. The authoring context selects this rule. Do not infer activation from dates, names, Git status, or diff size. An older design with a minor edit does not need a new section. If a section exists, check its form.
68
+
69
+ For maintainers and internal callers, the existing `validateGeneratedDocumentMetadata(markdown, { sourcePath, humanExperienceMode: "required" })` call checks the required section as well as existing metadata. Select this mode explicitly for new or substantial design work. The default `if-present` mode preserves historical documents without a section. The dedicated `validateDesignBody(markdown, "required")` helper checks only the design body. These are internal TypeScript APIs, not new CLI or MCP commands. Consumer agents apply the same contract by review; do not tell them to import maintainer source from their project.
70
+
71
+ The internal closeout helpers accept `humanExperienceRequiredPaths`, a list of project-relative changed design paths selected by the authoring context. They inspect other changed designs in `if-present` mode. This list does not expand the selected Git scope or certify unchanged, missing, or deleted files. Call the document validator directly for work outside that scope. Do not treat an empty closeout findings list as proof that the author selected required mode or that the result is good for people.
72
+
73
+ Review misleading headless and `none` claims against their human effect. Structural checks cannot judge their meaning. Reuse suitable evidence for per-promise Human Experience Review. The agent prepares and records the review and its limits. Human feedback is optional unless accepted authority explicitly defines a human acceptance gate.
@@ -0,0 +1,189 @@
1
+ # Execution Workflow
2
+
3
+ See `.make-docs/system/references/wave-model.md` for W/R semantics; archive rules are authoritative in `.make-docs/archive/AGENTS.md`.
4
+
5
+ ## Purpose
6
+
7
+ Use this workflow to generate or maintain the active PRD namespace and the related backlog in a consistent way. Execution mode is allowed only after the user explicitly authorizes execution, either after plan approval or as direct execution from the start.
8
+
9
+ ## Preconditions
10
+
11
+ Execution mode requires one of:
12
+
13
+ - an approved plan plus an explicit instruction to execute it
14
+ - a direct user instruction that explicitly authorizes immediate execution
15
+
16
+ If neither exists, switch back to planning mode.
17
+
18
+ ## Execution Modes
19
+
20
+ Classify the task before writing:
21
+
22
+ 1. `full-set generation` — create or replace the active PRD namespace from a plan, design, or decomposition workflow
23
+ 2. `authoritative PRD maintenance` — update current product authorities in place and create a new PRD only for a coherent product subject with no current owner
24
+
25
+ Use `authoritative PRD maintenance` when a decision, design, implementation, or finding may change an existing requirement, establish a genuinely new capability, or deprecate or remove behavior already represented in the active PRD namespace.
26
+
27
+ In every mode, `docs/prd/` describes the current authoritative shape of the product and never the editorial operation used to change that authority.
28
+
29
+ ## Preflight
30
+
31
+ 1. Determine the highest usable delegation tier for the current session: parallel agents, then subagents, then single-agent fallback.
32
+ 2. Re-check existing docs so you avoid duplicating or clobbering useful material.
33
+ 3. Inspect `docs/prd/` and determine whether active root entries already exist outside the archive.
34
+ 4. Classify the task as `full-set generation` or `authoritative PRD maintenance`.
35
+ 5. If the task is authoritative PRD maintenance, identify current owner PRDs and genuinely ownerless product subjects before spawning authoring work.
36
+ 6. Read the source design and plan for each accepted Human Experience promise or preserved `none` boundary. Use the [Human Experience Contract](../contracts/human-experience-contract.md) and [Human Experience Reference](human-experience.md) as the shared authority.
37
+ 7. When a performance candidate exists, read the [Performance Evidence Governance Contract](../contracts/performance-evidence-governance.md), record both candidate decisions, and identify the one canonical owner before writing.
38
+
39
+ ## Delegation Ladder
40
+
41
+ - PRD work is delegation-first by default because this workflow is highly context-intensive.
42
+ - Use this priority order:
43
+ 1. parallel agents
44
+ 2. subagents
45
+ 3. single-agent fallback
46
+ - If the harness likely supports delegation, decide the workstream split and spawn workers before broad repo analysis or document drafting by the coordinator.
47
+ - If delegation is available, the coordinator write scope is `none`.
48
+ - The coordinating agent must not draft PRD docs, create backlog files, fill shared docs, run assembly sweeps, or perform fix-up edits when those tasks can be delegated.
49
+ - Any task that creates or edits output files must be assigned to a worker whenever delegation is available.
50
+ - Single-agent execution is the fallback only when the harness or session policy does not permit delegation.
51
+
52
+ ## Coordinator Role
53
+
54
+ If delegation is available, the coordinator is limited to:
55
+
56
+ - capability and preflight checks
57
+ - approval handling
58
+ - workstream definition and task routing
59
+ - worker spawning and monitoring
60
+ - blocker resolution and reassignment
61
+ - final user-facing status reporting
62
+
63
+ If delegation is available, the coordinator must not:
64
+
65
+ - author PRD docs
66
+ - author backlog docs
67
+ - own shared-doc assembly
68
+ - merge glossary or risk-register content itself
69
+ - run validator-driven document fixes itself
70
+ - perform broad deep-dive reads that belong to a worker's authoring scope
71
+
72
+ ## Full-Set Replacement Gate
73
+
74
+ Apply this gate only in `full-set generation` mode:
75
+
76
+ - Treat `docs/prd/` as a single active PRD namespace.
77
+ - If root entries already exist in `docs/prd/`, summarize them and ask for approval before moving them.
78
+ - On approval, archive every root entry into `.make-docs/archive/prds/YYYY-MM-DD/` or `.make-docs/archive/prds/YYYY-MM-DD-XX/`.
79
+ - Include stray or hidden root entries in the archive summary and move set when they are part of the active namespace.
80
+ - If archival is declined, stop before writing anything into `docs/prd/`.
81
+ - Treat archived PRD sets as historical records, not active output targets.
82
+
83
+ ## Authoritative PRD Maintenance Gate
84
+
85
+ Apply this gate only in `authoritative PRD maintenance` mode:
86
+
87
+ - Do not archive the active PRD namespace.
88
+ - Assign `update-existing`, `create`, `link-only`, or `none` with a reason to every candidate requirement.
89
+ - Update current normative requirements inline in their existing owners.
90
+ - Determine the next available `NN-` number only when a coherent, wholesale new capability, subsystem, or product boundary has no suitable owner.
91
+ - Add standardized, non-normative `## Requirement History` entries when a material prior contract needs to remain visible.
92
+ - Express removals and deprecations as current scope, non-goal, limitation, status, or boundary text before recording history.
93
+ - Update `docs/prd/00-index.md` so current product ownership, status, focus, and navigation are accurate.
94
+ - Do not create PRDs whose filename, title, kind, or subject describes an editorial operation.
95
+ - Put each current observable human outcome in the PRD that owns the affected capability. Link to the canonical Human Experience authority. Do not create a cross-cutting editorial PRD, copy the universal standard, or add Human Experience frontmatter.
96
+
97
+ ## Writing Order
98
+
99
+ ### Full-set generation
100
+
101
+ 1. Determine the delegation tier and spawn workstreams if supported.
102
+ 2. Resolve the active-PRD archive gate if one is required.
103
+ 3. Determine the final PRD catalog shape.
104
+ 4. Route domain and subsystem docs to delegated workers.
105
+ 5. Route shared-doc assembly for `00-index.md`, `03-open-questions-and-risk-register.md`, `04-glossary.md`, and the backlog to a dedicated worker.
106
+ 6. Route contract validation and fix-up work to a dedicated validation worker.
107
+ 7. Keep the coordinator focused on status, blockers, and final reporting.
108
+
109
+ ### Authoritative PRD maintenance
110
+
111
+ 1. Determine the delegation tier and spawn workstreams if supported.
112
+ 2. Confirm candidate decisions, existing owner PRDs, and any genuinely new product subjects.
113
+ 3. Route surgical current-requirement updates and requirement-history entries to existing-owner workers.
114
+ 4. Route genuinely new product PRDs and shared index/risk updates to disjoint authoring or assembly workers when possible.
115
+ 5. Route delta backlog generation to a dedicated worker.
116
+ 6. Route product-authority, status, link, and traceability validation to a dedicated validation worker.
117
+ 7. Keep the coordinator focused on status, blockers, and final reporting.
118
+
119
+ ## Parallelization Rules
120
+
121
+ If the harness supports delegated workers, do not postpone delegation until the coordinator has already consumed most of its context budget.
122
+
123
+ - Prefer multiple concurrent workers when the harness supports parallel agents.
124
+ - If the harness does not support concurrent workers but does support delegated workers, use subagents before falling back to single-agent execution.
125
+ - Split work by subsystem or document family.
126
+ - Keep write scopes disjoint.
127
+ - Reserve final assembly, cross-linking, and validation for delegated workers, not the coordinator.
128
+ - Tell each spawned agent to build its own MCP indexes in its own session before deep analysis.
129
+
130
+ For authoritative PRD maintenance, prefer these separate write scopes when possible:
131
+
132
+ - existing owner PRD updates and requirement history
133
+ - genuinely new product-authority PRDs
134
+ - PRD index, risk register, and shared-doc status updates
135
+ - delta backlog generation
136
+ - validation and fix-up
137
+
138
+ ## Existing Documentation Rule
139
+
140
+ - Supplement and cite useful existing docs.
141
+ - Do not silently overwrite docs that serve another audience or purpose.
142
+ - If existing docs drift from the code, record the drift in `03-open-questions-and-risk-register.md`.
143
+ - If the task is full-set generation and an older active PRD set already exists under `docs/prd/`, archive it to `.make-docs/archive/prds/YYYY-MM-DD/` before writing the replacement active PRD set.
144
+ - If the task is authoritative PRD maintenance, update the owning current requirement surgically and preserve material prior state only in non-normative requirement history.
145
+
146
+ ## Work Backlog Source Authority
147
+
148
+ When generating or revising `docs/work/**`, use this authority order:
149
+
150
+ 1. Explicit user direction plus the accepted design, plan, PRD, and existing work artifacts for the current coordinate.
151
+ 2. Live repository contracts: `docs/work/AGENTS.md`, this workflow, `output-contract.md`, `wave-model.md`, and the current work templates.
152
+ 3. Product/template source contracts when maintaining make-docs-owned shipped assets; dogfood copies validate those assets but do not replace their source.
153
+ 4. Archived backlogs as examples of style or lineage only.
154
+ 5. Bundled Skill references, native harness exposures, and installed Skill copies only when live repo contracts are unavailable or the task explicitly concerns those assets.
155
+
156
+ If a fallback source is used, record which fallback was used and why.
157
+
158
+ ## Backlog Rules
159
+
160
+ - Work is always a directory in v2. Full-set generation writes `docs/work/YYYY-MM-DD-w{W}-r{R}-<slug>/` containing `00-index.md` plus `0N-<phase>.md` phase files.
161
+ - Authoritative PRD maintenance writes `docs/work/YYYY-MM-DD-w{W}-r{R}-<slug>/` as a delta backlog directory containing `00-index.md` plus `0N-<phase>.md` phase files.
162
+ - Plans use the same form: `docs/plans/YYYY-MM-DD-w{W}-r{R}-<slug>/` containing `00-overview.md` plus `0N-<phase>.md` phase files.
163
+ - Keep backlog phases dependency-ordered across the `0N-<phase>.md` files.
164
+ - In every stage, write `### Tasks` as markdown task list items using phase-local task IDs (`- [ ] t1: ...`, `- [x] t1: ...`) and write `### Acceptance criteria` as plain unordered bullets only.
165
+ - Increment task IDs across the entire phase file without resetting in later stages. Do not renumber existing task IDs when inserting or completing work.
166
+ - Include phase-level PRD traceability via `Source PRD Docs`.
167
+ - Make the backlog index retain the source design, plan, owning PRDs, phase order, evidence decisions, and implementation gate for each accepted Human Experience promise or preserved boundary.
168
+ - In each applicable phase, state the intended human outcome, affected human-facing surface or indirect effect, implementation work, observable acceptance, evidence source or testing type selected under current authority, executor, and accepted obligation route when work remains owed.
169
+ - In each generated phase, record the current decision for Automated Implementation Testing, Performance Testing, Guided Progress Review, and Unassisted Goal Testing. Record `not-needed-now` when a type cannot change a current decision. Keep Human Experience Review separate as required agent review work for applicable promises, not a fifth testing type. Have the agent inspect the available real result and record conclusions and limits. For completed direct human-facing work, normally include a short optional experience handoff. Require a human response only when accepted authority explicitly defines a human acceptance gate.
170
+ - For each performance candidate, record the base maintenance action and performance applicability. Link one canonical `PERF-###` profile for each executable candidate. Render a finite execution packet from that profile. Do not copy or redefine a product target in the packet.
171
+ - Make performance phase gates reject missing, expired, invalid, non-comparable, adjacent-mode, or unrun required evidence. Record `pass`, `fail`, `revise`, `blocked`, or `waived` only. Treat a waiver as bounded risk acceptance, not success. Reuse unchanged evidence, rerun only affected checks after material change, and stop when the authorized budget or diminishing-return rule ends.
172
+ - Reject acceptance such as `UX is good`, `easy to use`, or `intuitive`. Replace it with a result that a reviewer can observe on the named surface or in evidence tied to the stated indirect effect.
173
+ - When deferred-obligation or Unassisted Goal Testing routing is active, include applicable `O-###`, `NUAT-###`, and finding traceability plus phase and capability closeout language. Do not invent an ID for `not-needed-now`.
174
+ - Delta backlogs cite the updated or genuinely new authoritative PRDs that constrain implementation. Maintenance plans provide sequencing and history provides provenance; neither replaces current PRD authority.
175
+
176
+ ## Final Validation
177
+
178
+ Before closing the task:
179
+
180
+ 1. Resolve broken links, missing core docs, missing required headings, or misplaced backlog files.
181
+ 2. Confirm the PRD index reflects the final catalog, status, and lineage.
182
+ 3. Confirm the backlog links to the relevant PRD docs.
183
+ 4. For authoritative PRD maintenance, confirm current requirements are inline, history is non-normative, every new PRD is a coherent product authority, and delta backlog traceability points to current PRDs rather than retired change records.
184
+ 5. When deferred-obligation or Unassisted Goal Testing routing is in scope, confirm closeout records separate testing decisions, any applicable `O-###` disposition, any activated `NUAT-###` scenario, evidence references, and explicit phase versus capability status. Record `not-needed-now` without creating a scenario or obligation.
185
+ 6. Confirm each accepted Human Experience promise reaches current PRD authority, work, and suitable evidence or an accepted obligation. For `none`, confirm the backlog records and proves the preserved human boundary.
186
+ 7. Confirm acceptance is observable. It must let a reviewer determine the subject, relationship, state, next action, recovery path, useful level of detail, or goal completion without relying on an unexplained internal identifier when one of those outcomes is promised.
187
+ 8. Confirm each generated phase records all four current testing decisions and keeps Human Experience Review separate as the agent-owned review lens. Confirm that the review records evidence, observations, conclusions, reviewer, and limits. Confirm that an optional experience handoff is not treated as a gate and that any human acceptance gate has explicit authority, scope, reviewer, surface, question, and gate effect.
188
+ 9. If the reply asks the user to act, confirm that the request is understandable without opening another document. State the action, reason, whether it is required, optional, or a separate authorization, the work it blocks, where supporting detail is available, and what happens after the action. Explain needed internal terms and identifiers.
189
+ 10. When performance evidence is in scope, confirm both candidate decisions, canonical profile identity/version/digest, finite packet, fingerprint and comparability, result/finding/waiver/expiry links, remaining budget, reuse or affected-only rerun, requalification state, gate disposition, and supported-scope limit. Confirm repository authority remains canonical and no adjacent proof mode or Store receipt substitutes for the required evidence.