@llipe.com/dev-tasks 0.10.0 → 0.16.1

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 (620) hide show
  1. package/.claude/agents/developer.md +108 -35
  2. package/.claude/agents/github-ops.md +48 -4
  3. package/.claude/agents/housekeeping.md +44 -7
  4. package/.claude/agents/qa-engineer.md +45 -3
  5. package/.claude/agents/researcher.md +116 -0
  6. package/.claude/agents/technical-writer.md +61 -6
  7. package/.claude/agents/ux-engineer.md +1 -0
  8. package/.claude/agents/verifier.md +48 -6
  9. package/.claude/commands/developer.md +2 -266
  10. package/.claude/commands/infra-engineer.md +92 -0
  11. package/.claude/commands/planner.md +64 -28
  12. package/.claude/commands/product-engineer.md +58 -19
  13. package/.claude/commands/researcher.md +27 -0
  14. package/.claude/commands/technical-writer.md +1 -1
  15. package/.claude/hooks/branch-guard.sh +30 -0
  16. package/.claude/hooks/git-guard.sh +483 -22
  17. package/.claude/skills/activity-codebase-research/SKILL.md +151 -0
  18. package/.claude/skills/activity-e2e-test-implementation/SKILL.md +156 -0
  19. package/.claude/skills/activity-generate-spec/SKILL.md +34 -10
  20. package/.claude/skills/activity-grill/SKILL.md +150 -0
  21. package/.claude/skills/activity-init/SKILL.md +121 -71
  22. package/.claude/skills/activity-integration-test-implementation/SKILL.md +156 -0
  23. package/.claude/skills/activity-refine/SKILL.md +75 -15
  24. package/.claude/skills/activity-test-standards/SKILL.md +66 -0
  25. package/.claude/skills/aws-ops/SKILL.md +155 -0
  26. package/.claude/skills/deploy-ops/SKILL.md +121 -0
  27. package/.claude/skills/fly-ops/SKILL.md +138 -0
  28. package/.claude/skills/git-ops/SKILL.md +27 -7
  29. package/.claude/skills/implement/SKILL.md +49 -4
  30. package/.claude/skills/memo-cli-usage/REFERENCE.md +230 -17
  31. package/.claude/skills/memo-cli-usage/SKILL.md +66 -13
  32. package/.claude/skills/plan/SKILL.md +43 -1
  33. package/.claude/skills/supabase-ops/SKILL.md +109 -0
  34. package/.github/agents/developer.agent.md +80 -18
  35. package/.github/agents/github-ops.agent.md +46 -4
  36. package/.github/agents/housekeeping.agent.md +43 -7
  37. package/.github/agents/infra-engineer.agent.md +139 -0
  38. package/.github/agents/planner.agent.md +45 -9
  39. package/.github/agents/product-engineer.agent.md +58 -19
  40. package/.github/agents/qa-engineer.agent.md +43 -4
  41. package/.github/agents/researcher.agent.md +115 -0
  42. package/.github/agents/technical-writer.agent.md +60 -6
  43. package/.github/agents/verifier.agent.md +46 -5
  44. package/.github/instructions/implement.instructions.md +49 -4
  45. package/.github/instructions/plan.instructions.md +43 -1
  46. package/.github/prompts/infra-engineer.prompt.md +12 -0
  47. package/.github/prompts/product-engineer-init.prompt.md +5 -6
  48. package/.github/prompts/researcher.prompt.md +28 -0
  49. package/.github/prompts/technical-writer.prompt.md +1 -1
  50. package/.github/skills/activity-codebase-research/SKILL.md +146 -0
  51. package/.github/skills/activity-e2e-test-implementation/SKILL.md +156 -0
  52. package/.github/skills/activity-generate-spec/SKILL.md +34 -10
  53. package/.github/skills/activity-grill/SKILL.md +145 -0
  54. package/.github/skills/activity-init/SKILL.md +120 -70
  55. package/.github/skills/activity-integration-test-implementation/SKILL.md +156 -0
  56. package/.github/skills/activity-refine/SKILL.md +75 -15
  57. package/.github/skills/activity-test-standards/SKILL.md +66 -0
  58. package/.github/skills/aws-ops/SKILL.md +150 -0
  59. package/.github/skills/deploy-ops/SKILL.md +116 -0
  60. package/.github/skills/fly-ops/SKILL.md +133 -0
  61. package/.github/skills/git-ops/SKILL.md +27 -7
  62. package/.github/skills/memo-cli-usage/REFERENCE.md +230 -17
  63. package/.github/skills/memo-cli-usage/SKILL.md +66 -13
  64. package/.github/skills/supabase-ops/SKILL.md +104 -0
  65. package/.kiro/agents/developer.md +81 -19
  66. package/.kiro/agents/github-ops.md +46 -4
  67. package/.kiro/agents/housekeeping.md +44 -8
  68. package/.kiro/agents/infra-engineer.md +102 -0
  69. package/.kiro/agents/planner.md +53 -20
  70. package/.kiro/agents/product-engineer.md +61 -22
  71. package/.kiro/agents/qa-engineer.md +44 -5
  72. package/.kiro/agents/researcher.md +118 -0
  73. package/.kiro/agents/technical-writer.md +63 -9
  74. package/.kiro/agents/verifier.md +48 -7
  75. package/.kiro/skills/activity-codebase-research/SKILL.md +151 -0
  76. package/.kiro/skills/activity-e2e-test-implementation/SKILL.md +156 -0
  77. package/.kiro/skills/activity-generate-spec/SKILL.md +34 -10
  78. package/.kiro/skills/activity-grill/SKILL.md +150 -0
  79. package/.kiro/skills/activity-init/SKILL.md +121 -71
  80. package/.kiro/skills/activity-integration-test-implementation/SKILL.md +156 -0
  81. package/.kiro/skills/activity-refine/SKILL.md +75 -15
  82. package/.kiro/skills/activity-test-standards/SKILL.md +66 -0
  83. package/.kiro/skills/aws-ops/SKILL.md +155 -0
  84. package/.kiro/skills/deploy-ops/SKILL.md +121 -0
  85. package/.kiro/skills/fly-ops/SKILL.md +138 -0
  86. package/.kiro/skills/git-ops/SKILL.md +27 -7
  87. package/.kiro/skills/memo-cli-usage/REFERENCE.md +230 -17
  88. package/.kiro/skills/memo-cli-usage/SKILL.md +66 -13
  89. package/.kiro/skills/supabase-ops/SKILL.md +109 -0
  90. package/.kiro/steering/implement.md +49 -4
  91. package/.kiro/steering/plan.md +43 -1
  92. package/AGENTS.md +88 -261
  93. package/AGENTS.md.template +124 -0
  94. package/CHANGELOG.md +196 -0
  95. package/CLAUDE.md +24 -18
  96. package/CLAUDE.md.template +103 -0
  97. package/README.md +168 -145
  98. package/TESTING.md +84 -140
  99. package/bundle-manifest.json +43 -2
  100. package/dist/bin/dev-tasks.js +65 -3
  101. package/dist/bin/dev-tasks.js.map +1 -1
  102. package/dist/{adapters/cli → bin}/parse-args.d.ts +2 -6
  103. package/dist/bin/parse-args.d.ts.map +1 -0
  104. package/dist/{adapters/cli → bin}/parse-args.js +2 -18
  105. package/dist/bin/parse-args.js.map +1 -0
  106. package/dist/core/checks/decision-log-format.d.ts +44 -0
  107. package/dist/core/checks/decision-log-format.d.ts.map +1 -0
  108. package/dist/core/checks/decision-log-format.js +171 -0
  109. package/dist/core/checks/decision-log-format.js.map +1 -0
  110. package/dist/core/checks/docs-structure.d.ts +82 -0
  111. package/dist/core/checks/docs-structure.d.ts.map +1 -0
  112. package/dist/core/checks/docs-structure.js +285 -0
  113. package/dist/core/checks/docs-structure.js.map +1 -0
  114. package/dist/core/checks/glossary.d.ts +178 -0
  115. package/dist/core/checks/glossary.d.ts.map +1 -0
  116. package/dist/core/checks/glossary.js +651 -0
  117. package/dist/core/checks/glossary.js.map +1 -0
  118. package/dist/core/checks/index.d.ts +19 -0
  119. package/dist/core/checks/index.d.ts.map +1 -0
  120. package/dist/core/checks/index.js +16 -0
  121. package/dist/core/checks/index.js.map +1 -0
  122. package/dist/core/checks/run.d.ts +22 -0
  123. package/dist/core/checks/run.d.ts.map +1 -0
  124. package/dist/core/checks/run.js +51 -0
  125. package/dist/core/checks/run.js.map +1 -0
  126. package/dist/core/distribution/doctor.d.ts +46 -1
  127. package/dist/core/distribution/doctor.d.ts.map +1 -1
  128. package/dist/core/distribution/doctor.js +161 -2
  129. package/dist/core/distribution/doctor.js.map +1 -1
  130. package/dist/core/distribution/index.d.ts +9 -3
  131. package/dist/core/distribution/index.d.ts.map +1 -1
  132. package/dist/core/distribution/index.js +5 -2
  133. package/dist/core/distribution/index.js.map +1 -1
  134. package/dist/core/distribution/install-if-absent.d.ts +46 -0
  135. package/dist/core/distribution/install-if-absent.d.ts.map +1 -0
  136. package/dist/core/distribution/install-if-absent.js +81 -0
  137. package/dist/core/distribution/install-if-absent.js.map +1 -0
  138. package/dist/core/distribution/install.d.ts.map +1 -1
  139. package/dist/core/distribution/install.js +5 -0
  140. package/dist/core/distribution/install.js.map +1 -1
  141. package/dist/core/distribution/migrate-docs.d.ts +64 -0
  142. package/dist/core/distribution/migrate-docs.d.ts.map +1 -0
  143. package/dist/core/distribution/migrate-docs.js +139 -0
  144. package/dist/core/distribution/migrate-docs.js.map +1 -0
  145. package/dist/core/distribution/profiles.d.ts +49 -0
  146. package/dist/core/distribution/profiles.d.ts.map +1 -1
  147. package/dist/core/distribution/profiles.js +45 -0
  148. package/dist/core/distribution/profiles.js.map +1 -1
  149. package/dist/core/distribution/update.d.ts +14 -0
  150. package/dist/core/distribution/update.d.ts.map +1 -1
  151. package/dist/core/distribution/update.js +77 -3
  152. package/dist/core/distribution/update.js.map +1 -1
  153. package/dist/core/distribution/workspace.d.ts +84 -0
  154. package/dist/core/distribution/workspace.d.ts.map +1 -0
  155. package/dist/core/distribution/workspace.js +276 -0
  156. package/dist/core/distribution/workspace.js.map +1 -0
  157. package/dist/core/exit-codes.d.ts +15 -35
  158. package/dist/core/exit-codes.d.ts.map +1 -1
  159. package/dist/core/exit-codes.js +15 -36
  160. package/dist/core/exit-codes.js.map +1 -1
  161. package/dist/core/index.d.ts +1 -6
  162. package/dist/core/index.d.ts.map +1 -1
  163. package/dist/core/index.js +1 -7
  164. package/dist/core/index.js.map +1 -1
  165. package/package.json +17 -32
  166. package/templates/claude/settings.json +48 -0
  167. package/templates/domain/ubiquitous-language.md +28 -0
  168. package/templates/infra/environments.yaml +16 -0
  169. package/templates/infra/redaction-patterns.txt +47 -0
  170. package/templates/runbooks/README.md +14 -0
  171. package/templates/runbooks/runbook-template.md +40 -0
  172. package/templates/scripts/deploy-status.sh +89 -0
  173. package/templates/scripts/deploy-verify.sh +85 -0
  174. package/templates/scripts/deploy.sh +284 -0
  175. package/templates/scripts/release.sh +170 -0
  176. package/templates/scripts/rollback.sh +109 -0
  177. package/templates/workflows/deploy-dev.yml +66 -0
  178. package/templates/workflows/deploy-prod.yml +66 -0
  179. package/templates/workflows/rollback.yml +77 -0
  180. package/dist/adapters/cli/catalog-build.d.ts +0 -30
  181. package/dist/adapters/cli/catalog-build.d.ts.map +0 -1
  182. package/dist/adapters/cli/catalog-build.js +0 -73
  183. package/dist/adapters/cli/catalog-build.js.map +0 -1
  184. package/dist/adapters/cli/catalog-query.d.ts +0 -13
  185. package/dist/adapters/cli/catalog-query.d.ts.map +0 -1
  186. package/dist/adapters/cli/catalog-query.js +0 -329
  187. package/dist/adapters/cli/catalog-query.js.map +0 -1
  188. package/dist/adapters/cli/catalog-scaffold.d.ts +0 -24
  189. package/dist/adapters/cli/catalog-scaffold.d.ts.map +0 -1
  190. package/dist/adapters/cli/catalog-scaffold.js +0 -46
  191. package/dist/adapters/cli/catalog-scaffold.js.map +0 -1
  192. package/dist/adapters/cli/catalog-validate.d.ts +0 -35
  193. package/dist/adapters/cli/catalog-validate.d.ts.map +0 -1
  194. package/dist/adapters/cli/catalog-validate.js +0 -122
  195. package/dist/adapters/cli/catalog-validate.js.map +0 -1
  196. package/dist/adapters/cli/ctx-assemble.d.ts +0 -19
  197. package/dist/adapters/cli/ctx-assemble.d.ts.map +0 -1
  198. package/dist/adapters/cli/ctx-assemble.js +0 -293
  199. package/dist/adapters/cli/ctx-assemble.js.map +0 -1
  200. package/dist/adapters/cli/ctx-fetch.d.ts +0 -49
  201. package/dist/adapters/cli/ctx-fetch.d.ts.map +0 -1
  202. package/dist/adapters/cli/ctx-fetch.js +0 -267
  203. package/dist/adapters/cli/ctx-fetch.js.map +0 -1
  204. package/dist/adapters/cli/extract-all.d.ts +0 -31
  205. package/dist/adapters/cli/extract-all.d.ts.map +0 -1
  206. package/dist/adapters/cli/extract-all.js +0 -374
  207. package/dist/adapters/cli/extract-all.js.map +0 -1
  208. package/dist/adapters/cli/extract-asyncapi.d.ts +0 -26
  209. package/dist/adapters/cli/extract-asyncapi.d.ts.map +0 -1
  210. package/dist/adapters/cli/extract-asyncapi.js +0 -142
  211. package/dist/adapters/cli/extract-asyncapi.js.map +0 -1
  212. package/dist/adapters/cli/extract-component.d.ts +0 -24
  213. package/dist/adapters/cli/extract-component.d.ts.map +0 -1
  214. package/dist/adapters/cli/extract-component.js +0 -198
  215. package/dist/adapters/cli/extract-component.js.map +0 -1
  216. package/dist/adapters/cli/extract-detect.d.ts +0 -19
  217. package/dist/adapters/cli/extract-detect.d.ts.map +0 -1
  218. package/dist/adapters/cli/extract-detect.js +0 -98
  219. package/dist/adapters/cli/extract-detect.js.map +0 -1
  220. package/dist/adapters/cli/extract-openapi.d.ts +0 -29
  221. package/dist/adapters/cli/extract-openapi.d.ts.map +0 -1
  222. package/dist/adapters/cli/extract-openapi.js +0 -111
  223. package/dist/adapters/cli/extract-openapi.js.map +0 -1
  224. package/dist/adapters/cli/extract-schema.d.ts +0 -15
  225. package/dist/adapters/cli/extract-schema.d.ts.map +0 -1
  226. package/dist/adapters/cli/extract-schema.js +0 -39
  227. package/dist/adapters/cli/extract-schema.js.map +0 -1
  228. package/dist/adapters/cli/index.d.ts +0 -6
  229. package/dist/adapters/cli/index.d.ts.map +0 -1
  230. package/dist/adapters/cli/index.js +0 -5
  231. package/dist/adapters/cli/index.js.map +0 -1
  232. package/dist/adapters/cli/init.d.ts +0 -37
  233. package/dist/adapters/cli/init.d.ts.map +0 -1
  234. package/dist/adapters/cli/init.js +0 -336
  235. package/dist/adapters/cli/init.js.map +0 -1
  236. package/dist/adapters/cli/parse-args.d.ts.map +0 -1
  237. package/dist/adapters/cli/parse-args.js.map +0 -1
  238. package/dist/adapters/cli/scope-gate.d.ts +0 -25
  239. package/dist/adapters/cli/scope-gate.d.ts.map +0 -1
  240. package/dist/adapters/cli/scope-gate.js +0 -157
  241. package/dist/adapters/cli/scope-gate.js.map +0 -1
  242. package/dist/adapters/cli/scope.d.ts +0 -26
  243. package/dist/adapters/cli/scope.d.ts.map +0 -1
  244. package/dist/adapters/cli/scope.js +0 -172
  245. package/dist/adapters/cli/scope.js.map +0 -1
  246. package/dist/adapters/cli/validate-component.d.ts +0 -24
  247. package/dist/adapters/cli/validate-component.d.ts.map +0 -1
  248. package/dist/adapters/cli/validate-component.js +0 -62
  249. package/dist/adapters/cli/validate-component.js.map +0 -1
  250. package/dist/adapters/cli/verify-contract-diff.d.ts +0 -21
  251. package/dist/adapters/cli/verify-contract-diff.d.ts.map +0 -1
  252. package/dist/adapters/cli/verify-contract-diff.js +0 -69
  253. package/dist/adapters/cli/verify-contract-diff.js.map +0 -1
  254. package/dist/adapters/cli/verify-drift.d.ts +0 -24
  255. package/dist/adapters/cli/verify-drift.d.ts.map +0 -1
  256. package/dist/adapters/cli/verify-drift.js +0 -103
  257. package/dist/adapters/cli/verify-drift.js.map +0 -1
  258. package/dist/adapters/cli/verify-impact.d.ts +0 -23
  259. package/dist/adapters/cli/verify-impact.d.ts.map +0 -1
  260. package/dist/adapters/cli/verify-impact.js +0 -119
  261. package/dist/adapters/cli/verify-impact.js.map +0 -1
  262. package/dist/adapters/mcp/index.d.ts +0 -5
  263. package/dist/adapters/mcp/index.d.ts.map +0 -1
  264. package/dist/adapters/mcp/index.js +0 -2
  265. package/dist/adapters/mcp/index.js.map +0 -1
  266. package/dist/bin/dt.d.ts +0 -7
  267. package/dist/bin/dt.d.ts.map +0 -1
  268. package/dist/bin/dt.js +0 -647
  269. package/dist/bin/dt.js.map +0 -1
  270. package/dist/core/catalog/build.d.ts +0 -143
  271. package/dist/core/catalog/build.d.ts.map +0 -1
  272. package/dist/core/catalog/build.js +0 -475
  273. package/dist/core/catalog/build.js.map +0 -1
  274. package/dist/core/catalog/checks/index.d.ts +0 -18
  275. package/dist/core/catalog/checks/index.d.ts.map +0 -1
  276. package/dist/core/catalog/checks/index.js +0 -18
  277. package/dist/core/catalog/checks/index.js.map +0 -1
  278. package/dist/core/catalog/checks/v01-schema.d.ts +0 -17
  279. package/dist/core/catalog/checks/v01-schema.d.ts.map +0 -1
  280. package/dist/core/catalog/checks/v01-schema.js +0 -57
  281. package/dist/core/catalog/checks/v01-schema.js.map +0 -1
  282. package/dist/core/catalog/checks/v02-v03-identity.d.ts +0 -14
  283. package/dist/core/catalog/checks/v02-v03-identity.d.ts.map +0 -1
  284. package/dist/core/catalog/checks/v02-v03-identity.js +0 -60
  285. package/dist/core/catalog/checks/v02-v03-identity.js.map +0 -1
  286. package/dist/core/catalog/checks/v04-referential-integrity.d.ts +0 -7
  287. package/dist/core/catalog/checks/v04-referential-integrity.d.ts.map +0 -1
  288. package/dist/core/catalog/checks/v04-referential-integrity.js +0 -32
  289. package/dist/core/catalog/checks/v04-referential-integrity.js.map +0 -1
  290. package/dist/core/catalog/checks/v05-domain-existence.d.ts +0 -6
  291. package/dist/core/catalog/checks/v05-domain-existence.d.ts.map +0 -1
  292. package/dist/core/catalog/checks/v05-domain-existence.js +0 -23
  293. package/dist/core/catalog/checks/v05-domain-existence.js.map +0 -1
  294. package/dist/core/catalog/checks/v06-v07-paths.d.ts +0 -29
  295. package/dist/core/catalog/checks/v06-v07-paths.d.ts.map +0 -1
  296. package/dist/core/catalog/checks/v06-v07-paths.js +0 -107
  297. package/dist/core/catalog/checks/v06-v07-paths.js.map +0 -1
  298. package/dist/core/catalog/checks/v08-v10-contracts.d.ts +0 -13
  299. package/dist/core/catalog/checks/v08-v10-contracts.d.ts.map +0 -1
  300. package/dist/core/catalog/checks/v08-v10-contracts.js +0 -70
  301. package/dist/core/catalog/checks/v08-v10-contracts.js.map +0 -1
  302. package/dist/core/catalog/checks/v11-manual-fields.d.ts +0 -16
  303. package/dist/core/catalog/checks/v11-manual-fields.d.ts.map +0 -1
  304. package/dist/core/catalog/checks/v11-manual-fields.js +0 -60
  305. package/dist/core/catalog/checks/v11-manual-fields.js.map +0 -1
  306. package/dist/core/catalog/checks/v12-cycles.d.ts +0 -8
  307. package/dist/core/catalog/checks/v12-cycles.d.ts.map +0 -1
  308. package/dist/core/catalog/checks/v12-cycles.js +0 -28
  309. package/dist/core/catalog/checks/v12-cycles.js.map +0 -1
  310. package/dist/core/catalog/checks/v13-orphan-contracts.d.ts +0 -7
  311. package/dist/core/catalog/checks/v13-orphan-contracts.d.ts.map +0 -1
  312. package/dist/core/catalog/checks/v13-orphan-contracts.js +0 -33
  313. package/dist/core/catalog/checks/v13-orphan-contracts.js.map +0 -1
  314. package/dist/core/catalog/checks/v14-v15-lifecycle.d.ts +0 -8
  315. package/dist/core/catalog/checks/v14-v15-lifecycle.d.ts.map +0 -1
  316. package/dist/core/catalog/checks/v14-v15-lifecycle.js +0 -42
  317. package/dist/core/catalog/checks/v14-v15-lifecycle.js.map +0 -1
  318. package/dist/core/catalog/checks/v16-deprecated-consumers.d.ts +0 -7
  319. package/dist/core/catalog/checks/v16-deprecated-consumers.d.ts.map +0 -1
  320. package/dist/core/catalog/checks/v16-deprecated-consumers.js +0 -47
  321. package/dist/core/catalog/checks/v16-deprecated-consumers.js.map +0 -1
  322. package/dist/core/catalog/checks/v17-low-confidence.d.ts +0 -7
  323. package/dist/core/catalog/checks/v17-low-confidence.d.ts.map +0 -1
  324. package/dist/core/catalog/checks/v17-low-confidence.js +0 -32
  325. package/dist/core/catalog/checks/v17-low-confidence.js.map +0 -1
  326. package/dist/core/catalog/checks/v18-low-payload.d.ts +0 -7
  327. package/dist/core/catalog/checks/v18-low-payload.d.ts.map +0 -1
  328. package/dist/core/catalog/checks/v18-low-payload.js +0 -33
  329. package/dist/core/catalog/checks/v18-low-payload.js.map +0 -1
  330. package/dist/core/catalog/checks/v19-domain-membership.d.ts +0 -8
  331. package/dist/core/catalog/checks/v19-domain-membership.d.ts.map +0 -1
  332. package/dist/core/catalog/checks/v19-domain-membership.js +0 -55
  333. package/dist/core/catalog/checks/v19-domain-membership.js.map +0 -1
  334. package/dist/core/catalog/coverage.d.ts +0 -39
  335. package/dist/core/catalog/coverage.d.ts.map +0 -1
  336. package/dist/core/catalog/coverage.js +0 -62
  337. package/dist/core/catalog/coverage.js.map +0 -1
  338. package/dist/core/catalog/graph.d.ts +0 -49
  339. package/dist/core/catalog/graph.d.ts.map +0 -1
  340. package/dist/core/catalog/graph.js +0 -114
  341. package/dist/core/catalog/graph.js.map +0 -1
  342. package/dist/core/catalog/index-model.d.ts +0 -96
  343. package/dist/core/catalog/index-model.d.ts.map +0 -1
  344. package/dist/core/catalog/index-model.js +0 -8
  345. package/dist/core/catalog/index-model.js.map +0 -1
  346. package/dist/core/catalog/index.d.ts +0 -5
  347. package/dist/core/catalog/index.d.ts.map +0 -1
  348. package/dist/core/catalog/index.js +0 -2
  349. package/dist/core/catalog/index.js.map +0 -1
  350. package/dist/core/catalog/queries.d.ts +0 -69
  351. package/dist/core/catalog/queries.d.ts.map +0 -1
  352. package/dist/core/catalog/queries.js +0 -165
  353. package/dist/core/catalog/queries.js.map +0 -1
  354. package/dist/core/catalog/resolve.d.ts +0 -47
  355. package/dist/core/catalog/resolve.d.ts.map +0 -1
  356. package/dist/core/catalog/resolve.js +0 -318
  357. package/dist/core/catalog/resolve.js.map +0 -1
  358. package/dist/core/catalog/scaffold.d.ts +0 -31
  359. package/dist/core/catalog/scaffold.d.ts.map +0 -1
  360. package/dist/core/catalog/scaffold.js +0 -141
  361. package/dist/core/catalog/scaffold.js.map +0 -1
  362. package/dist/core/catalog/validate-component.d.ts +0 -50
  363. package/dist/core/catalog/validate-component.d.ts.map +0 -1
  364. package/dist/core/catalog/validate-component.js +0 -105
  365. package/dist/core/catalog/validate-component.js.map +0 -1
  366. package/dist/core/catalog/validate.d.ts +0 -71
  367. package/dist/core/catalog/validate.d.ts.map +0 -1
  368. package/dist/core/catalog/validate.js +0 -103
  369. package/dist/core/catalog/validate.js.map +0 -1
  370. package/dist/core/context/assemble.d.ts +0 -126
  371. package/dist/core/context/assemble.d.ts.map +0 -1
  372. package/dist/core/context/assemble.js +0 -197
  373. package/dist/core/context/assemble.js.map +0 -1
  374. package/dist/core/context/cache.d.ts +0 -60
  375. package/dist/core/context/cache.d.ts.map +0 -1
  376. package/dist/core/context/cache.js +0 -236
  377. package/dist/core/context/cache.js.map +0 -1
  378. package/dist/core/context/exit-codes.d.ts +0 -28
  379. package/dist/core/context/exit-codes.d.ts.map +0 -1
  380. package/dist/core/context/exit-codes.js +0 -28
  381. package/dist/core/context/exit-codes.js.map +0 -1
  382. package/dist/core/context/fetch.d.ts +0 -55
  383. package/dist/core/context/fetch.d.ts.map +0 -1
  384. package/dist/core/context/fetch.js +0 -112
  385. package/dist/core/context/fetch.js.map +0 -1
  386. package/dist/core/context/index.d.ts +0 -11
  387. package/dist/core/context/index.d.ts.map +0 -1
  388. package/dist/core/context/index.js +0 -8
  389. package/dist/core/context/index.js.map +0 -1
  390. package/dist/core/context/init.d.ts +0 -179
  391. package/dist/core/context/init.d.ts.map +0 -1
  392. package/dist/core/context/init.js +0 -532
  393. package/dist/core/context/init.js.map +0 -1
  394. package/dist/core/context/layers/architecture-layer.d.ts +0 -13
  395. package/dist/core/context/layers/architecture-layer.d.ts.map +0 -1
  396. package/dist/core/context/layers/architecture-layer.js +0 -24
  397. package/dist/core/context/layers/architecture-layer.js.map +0 -1
  398. package/dist/core/context/layers/contracts-layer.d.ts +0 -13
  399. package/dist/core/context/layers/contracts-layer.d.ts.map +0 -1
  400. package/dist/core/context/layers/contracts-layer.js +0 -83
  401. package/dist/core/context/layers/contracts-layer.js.map +0 -1
  402. package/dist/core/context/layers/conventions-delta-layer.d.ts +0 -13
  403. package/dist/core/context/layers/conventions-delta-layer.d.ts.map +0 -1
  404. package/dist/core/context/layers/conventions-delta-layer.js +0 -37
  405. package/dist/core/context/layers/conventions-delta-layer.js.map +0 -1
  406. package/dist/core/context/layers/flow-layer.d.ts +0 -14
  407. package/dist/core/context/layers/flow-layer.d.ts.map +0 -1
  408. package/dist/core/context/layers/flow-layer.js +0 -61
  409. package/dist/core/context/layers/flow-layer.js.map +0 -1
  410. package/dist/core/context/layers/index-layer.d.ts +0 -13
  411. package/dist/core/context/layers/index-layer.d.ts.map +0 -1
  412. package/dist/core/context/layers/index-layer.js +0 -77
  413. package/dist/core/context/layers/index-layer.js.map +0 -1
  414. package/dist/core/context/layers/primary-layer.d.ts +0 -16
  415. package/dist/core/context/layers/primary-layer.d.ts.map +0 -1
  416. package/dist/core/context/layers/primary-layer.js +0 -61
  417. package/dist/core/context/layers/primary-layer.js.map +0 -1
  418. package/dist/core/context/layers/secondary-layer.d.ts +0 -19
  419. package/dist/core/context/layers/secondary-layer.d.ts.map +0 -1
  420. package/dist/core/context/layers/secondary-layer.js +0 -52
  421. package/dist/core/context/layers/secondary-layer.js.map +0 -1
  422. package/dist/core/context/session-lock.d.ts +0 -114
  423. package/dist/core/context/session-lock.d.ts.map +0 -1
  424. package/dist/core/context/session-lock.js +0 -90
  425. package/dist/core/context/session-lock.js.map +0 -1
  426. package/dist/core/context/tokens.d.ts +0 -35
  427. package/dist/core/context/tokens.d.ts.map +0 -1
  428. package/dist/core/context/tokens.js +0 -88
  429. package/dist/core/context/tokens.js.map +0 -1
  430. package/dist/core/extract/asyncapi/declared.d.ts +0 -19
  431. package/dist/core/extract/asyncapi/declared.d.ts.map +0 -1
  432. package/dist/core/extract/asyncapi/declared.js +0 -168
  433. package/dist/core/extract/asyncapi/declared.js.map +0 -1
  434. package/dist/core/extract/asyncapi/index.d.ts +0 -12
  435. package/dist/core/extract/asyncapi/index.d.ts.map +0 -1
  436. package/dist/core/extract/asyncapi/index.js +0 -8
  437. package/dist/core/extract/asyncapi/index.js.map +0 -1
  438. package/dist/core/extract/asyncapi/payloads.d.ts +0 -20
  439. package/dist/core/extract/asyncapi/payloads.d.ts.map +0 -1
  440. package/dist/core/extract/asyncapi/payloads.js +0 -421
  441. package/dist/core/extract/asyncapi/payloads.js.map +0 -1
  442. package/dist/core/extract/asyncapi/topics.d.ts +0 -27
  443. package/dist/core/extract/asyncapi/topics.d.ts.map +0 -1
  444. package/dist/core/extract/asyncapi/topics.js +0 -368
  445. package/dist/core/extract/asyncapi/topics.js.map +0 -1
  446. package/dist/core/extract/asyncapi/types.d.ts +0 -129
  447. package/dist/core/extract/asyncapi/types.d.ts.map +0 -1
  448. package/dist/core/extract/asyncapi/types.js +0 -5
  449. package/dist/core/extract/asyncapi/types.js.map +0 -1
  450. package/dist/core/extract/asyncapi/validate.d.ts +0 -29
  451. package/dist/core/extract/asyncapi/validate.d.ts.map +0 -1
  452. package/dist/core/extract/asyncapi/validate.js +0 -156
  453. package/dist/core/extract/asyncapi/validate.js.map +0 -1
  454. package/dist/core/extract/component.d.ts +0 -204
  455. package/dist/core/extract/component.d.ts.map +0 -1
  456. package/dist/core/extract/component.js +0 -258
  457. package/dist/core/extract/component.js.map +0 -1
  458. package/dist/core/extract/detect.d.ts +0 -35
  459. package/dist/core/extract/detect.d.ts.map +0 -1
  460. package/dist/core/extract/detect.js +0 -89
  461. package/dist/core/extract/detect.js.map +0 -1
  462. package/dist/core/extract/index.d.ts +0 -12
  463. package/dist/core/extract/index.d.ts.map +0 -1
  464. package/dist/core/extract/index.js +0 -6
  465. package/dist/core/extract/index.js.map +0 -1
  466. package/dist/core/extract/ladder.d.ts +0 -79
  467. package/dist/core/extract/ladder.d.ts.map +0 -1
  468. package/dist/core/extract/ladder.js +0 -70
  469. package/dist/core/extract/ladder.js.map +0 -1
  470. package/dist/core/extract/openapi/index.d.ts +0 -43
  471. package/dist/core/extract/openapi/index.d.ts.map +0 -1
  472. package/dist/core/extract/openapi/index.js +0 -142
  473. package/dist/core/extract/openapi/index.js.map +0 -1
  474. package/dist/core/extract/openapi/route1.d.ts +0 -36
  475. package/dist/core/extract/openapi/route1.d.ts.map +0 -1
  476. package/dist/core/extract/openapi/route1.js +0 -333
  477. package/dist/core/extract/openapi/route1.js.map +0 -1
  478. package/dist/core/extract/openapi/route2-introspect.d.ts +0 -18
  479. package/dist/core/extract/openapi/route2-introspect.d.ts.map +0 -1
  480. package/dist/core/extract/openapi/route2-introspect.js +0 -249
  481. package/dist/core/extract/openapi/route2-introspect.js.map +0 -1
  482. package/dist/core/extract/openapi/route2.d.ts +0 -69
  483. package/dist/core/extract/openapi/route2.d.ts.map +0 -1
  484. package/dist/core/extract/openapi/route2.js +0 -211
  485. package/dist/core/extract/openapi/route2.js.map +0 -1
  486. package/dist/core/extract/openapi/route3.d.ts +0 -26
  487. package/dist/core/extract/openapi/route3.d.ts.map +0 -1
  488. package/dist/core/extract/openapi/route3.js +0 -737
  489. package/dist/core/extract/openapi/route3.js.map +0 -1
  490. package/dist/core/extract/openapi/types.d.ts +0 -125
  491. package/dist/core/extract/openapi/types.d.ts.map +0 -1
  492. package/dist/core/extract/openapi/types.js +0 -5
  493. package/dist/core/extract/openapi/types.js.map +0 -1
  494. package/dist/core/extract/openapi/validate.d.ts +0 -29
  495. package/dist/core/extract/openapi/validate.d.ts.map +0 -1
  496. package/dist/core/extract/openapi/validate.js +0 -200
  497. package/dist/core/extract/openapi/validate.js.map +0 -1
  498. package/dist/core/extract/orm/drizzle.d.ts +0 -20
  499. package/dist/core/extract/orm/drizzle.d.ts.map +0 -1
  500. package/dist/core/extract/orm/drizzle.js +0 -283
  501. package/dist/core/extract/orm/drizzle.js.map +0 -1
  502. package/dist/core/extract/orm/information-schema.d.ts +0 -26
  503. package/dist/core/extract/orm/information-schema.d.ts.map +0 -1
  504. package/dist/core/extract/orm/information-schema.js +0 -142
  505. package/dist/core/extract/orm/information-schema.js.map +0 -1
  506. package/dist/core/extract/orm/prisma.d.ts +0 -23
  507. package/dist/core/extract/orm/prisma.d.ts.map +0 -1
  508. package/dist/core/extract/orm/prisma.js +0 -234
  509. package/dist/core/extract/orm/prisma.js.map +0 -1
  510. package/dist/core/extract/orm/typeorm.d.ts +0 -22
  511. package/dist/core/extract/orm/typeorm.d.ts.map +0 -1
  512. package/dist/core/extract/orm/typeorm.js +0 -269
  513. package/dist/core/extract/orm/typeorm.js.map +0 -1
  514. package/dist/core/extract/orm/types.d.ts +0 -97
  515. package/dist/core/extract/orm/types.d.ts.map +0 -1
  516. package/dist/core/extract/orm/types.js +0 -6
  517. package/dist/core/extract/orm/types.js.map +0 -1
  518. package/dist/core/extract/prompt.d.ts +0 -21
  519. package/dist/core/extract/prompt.d.ts.map +0 -1
  520. package/dist/core/extract/prompt.js +0 -79
  521. package/dist/core/extract/prompt.js.map +0 -1
  522. package/dist/core/extract/provider.d.ts +0 -121
  523. package/dist/core/extract/provider.d.ts.map +0 -1
  524. package/dist/core/extract/provider.js +0 -6
  525. package/dist/core/extract/provider.js.map +0 -1
  526. package/dist/core/extract/providers/node-ts.d.ts +0 -69
  527. package/dist/core/extract/providers/node-ts.d.ts.map +0 -1
  528. package/dist/core/extract/providers/node-ts.js +0 -320
  529. package/dist/core/extract/providers/node-ts.js.map +0 -1
  530. package/dist/core/extract/render/schema-md.d.ts +0 -16
  531. package/dist/core/extract/render/schema-md.d.ts.map +0 -1
  532. package/dist/core/extract/render/schema-md.js +0 -140
  533. package/dist/core/extract/render/schema-md.js.map +0 -1
  534. package/dist/core/extract/report.d.ts +0 -125
  535. package/dist/core/extract/report.d.ts.map +0 -1
  536. package/dist/core/extract/report.js +0 -52
  537. package/dist/core/extract/report.js.map +0 -1
  538. package/dist/core/extract/schema.d.ts +0 -34
  539. package/dist/core/extract/schema.d.ts.map +0 -1
  540. package/dist/core/extract/schema.js +0 -146
  541. package/dist/core/extract/schema.js.map +0 -1
  542. package/dist/core/extract/workspaces.d.ts +0 -33
  543. package/dist/core/extract/workspaces.d.ts.map +0 -1
  544. package/dist/core/extract/workspaces.js +0 -193
  545. package/dist/core/extract/workspaces.js.map +0 -1
  546. package/dist/core/providers/index.d.ts +0 -6
  547. package/dist/core/providers/index.d.ts.map +0 -1
  548. package/dist/core/providers/index.js +0 -2
  549. package/dist/core/providers/index.js.map +0 -1
  550. package/dist/core/providers/tracker.d.ts +0 -74
  551. package/dist/core/providers/tracker.d.ts.map +0 -1
  552. package/dist/core/providers/tracker.js +0 -38
  553. package/dist/core/providers/tracker.js.map +0 -1
  554. package/dist/core/scope/calibration.d.ts +0 -25
  555. package/dist/core/scope/calibration.d.ts.map +0 -1
  556. package/dist/core/scope/calibration.js +0 -52
  557. package/dist/core/scope/calibration.js.map +0 -1
  558. package/dist/core/scope/closure.d.ts +0 -31
  559. package/dist/core/scope/closure.d.ts.map +0 -1
  560. package/dist/core/scope/closure.js +0 -68
  561. package/dist/core/scope/closure.js.map +0 -1
  562. package/dist/core/scope/gate.d.ts +0 -41
  563. package/dist/core/scope/gate.d.ts.map +0 -1
  564. package/dist/core/scope/gate.js +0 -165
  565. package/dist/core/scope/gate.js.map +0 -1
  566. package/dist/core/scope/index.d.ts +0 -18
  567. package/dist/core/scope/index.d.ts.map +0 -1
  568. package/dist/core/scope/index.js +0 -12
  569. package/dist/core/scope/index.js.map +0 -1
  570. package/dist/core/scope/partition.d.ts +0 -36
  571. package/dist/core/scope/partition.d.ts.map +0 -1
  572. package/dist/core/scope/partition.js +0 -78
  573. package/dist/core/scope/partition.js.map +0 -1
  574. package/dist/core/scope/prompt.d.ts +0 -39
  575. package/dist/core/scope/prompt.d.ts.map +0 -1
  576. package/dist/core/scope/prompt.js +0 -123
  577. package/dist/core/scope/prompt.js.map +0 -1
  578. package/dist/core/scope/scoping.d.ts +0 -52
  579. package/dist/core/scope/scoping.d.ts.map +0 -1
  580. package/dist/core/scope/scoping.js +0 -99
  581. package/dist/core/scope/scoping.js.map +0 -1
  582. package/dist/core/scope/types.d.ts +0 -77
  583. package/dist/core/scope/types.d.ts.map +0 -1
  584. package/dist/core/scope/types.js +0 -5
  585. package/dist/core/scope/types.js.map +0 -1
  586. package/dist/core/scope/validate.d.ts +0 -47
  587. package/dist/core/scope/validate.d.ts.map +0 -1
  588. package/dist/core/scope/validate.js +0 -90
  589. package/dist/core/scope/validate.js.map +0 -1
  590. package/dist/core/verify/asyncapi-diff.d.ts +0 -34
  591. package/dist/core/verify/asyncapi-diff.d.ts.map +0 -1
  592. package/dist/core/verify/asyncapi-diff.js +0 -209
  593. package/dist/core/verify/asyncapi-diff.js.map +0 -1
  594. package/dist/core/verify/contract-diff.d.ts +0 -39
  595. package/dist/core/verify/contract-diff.d.ts.map +0 -1
  596. package/dist/core/verify/contract-diff.js +0 -63
  597. package/dist/core/verify/contract-diff.js.map +0 -1
  598. package/dist/core/verify/drift.d.ts +0 -47
  599. package/dist/core/verify/drift.d.ts.map +0 -1
  600. package/dist/core/verify/drift.js +0 -122
  601. package/dist/core/verify/drift.js.map +0 -1
  602. package/dist/core/verify/impact.d.ts +0 -22
  603. package/dist/core/verify/impact.d.ts.map +0 -1
  604. package/dist/core/verify/impact.js +0 -93
  605. package/dist/core/verify/impact.js.map +0 -1
  606. package/dist/core/verify/index.d.ts +0 -10
  607. package/dist/core/verify/index.d.ts.map +0 -1
  608. package/dist/core/verify/index.js +0 -9
  609. package/dist/core/verify/index.js.map +0 -1
  610. package/dist/core/verify/openapi-diff.d.ts +0 -29
  611. package/dist/core/verify/openapi-diff.d.ts.map +0 -1
  612. package/dist/core/verify/openapi-diff.js +0 -291
  613. package/dist/core/verify/openapi-diff.js.map +0 -1
  614. package/dist/core/verify/types.d.ts +0 -138
  615. package/dist/core/verify/types.d.ts.map +0 -1
  616. package/dist/core/verify/types.js +0 -5
  617. package/dist/core/verify/types.js.map +0 -1
  618. package/schemas/component.schema.json +0 -203
  619. package/schemas/flow.schema.json +0 -75
  620. package/schemas/scope-output.schema.json +0 -62
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: activity-init
3
- description: "Establish product-context.md and technical-guidelines.md foundation docs. Use in product-engineer Init Mode."
3
+ description: "Establish product.md and tech.md foundation docs. Use in product-engineer Init Mode."
4
4
  ---
5
5
 
6
6
  # Activity: Initialize Project Foundation
@@ -17,6 +17,27 @@ Guide an AI assistant in establishing the foundational documents for a project:
17
17
 
18
18
  Run this activity **once per project** (or when a major strategic or technical pivot occurs).
19
19
 
20
+ ## Foundation Document Names
21
+
22
+ The canonical names are **`docs/product.md`** and **`docs/tech.md`**. Create and reference those names only.
23
+
24
+ **Fallback, one release cycle (FR-45, `shared-understanding#D-42`).** These documents were renamed from `docs/product-context.md` and `docs/technical-guidelines.md`. A consumer repository installed before the rename still carries the old names, and `dev-tasks update` never renames a consumer-owned file on its own. So when reading a foundation document: resolve `docs/product.md` first and fall back to `docs/product-context.md` only if the new name is absent; likewise `docs/tech.md`, then `docs/technical-guidelines.md`. When writing, always write the new name.
25
+
26
+ On encountering the old names, propose `dev-tasks migrate docs`, which performs the rename with content unchanged. Do not rename a consumer's files without being asked. The fallback is removed one release cycle after the rename ships (tracked in issue #201); after that the proposal is the only path.
27
+
28
+ ## Repository Setup — Branch Protection (Required)
29
+
30
+ Before or alongside establishing the foundation documents, verify the repository's default branch has GitHub branch protection configured. This is not optional hardening — it is the actual gate for "no agent merges into the default branch." Every hook shipped with dev-tasks (`git-guard.sh`, `branch-guard.sh`, and their Kiro equivalents) is a best-effort, advisory, local check that can be evaded by a sufficiently creative command or tool-input shape, and Copilot has no hook system at all; only a server-side branch protection rule is unbypassable by any tool surface.
31
+
32
+ Check with `gh api repos/<owner>/<repo>/branches/<default-branch>/protection` (a 404 means it is not configured). If missing, tell the user and offer to configure it:
33
+
34
+ - Require a pull request before merging
35
+ - Require at least 1 approving review
36
+ - Require status checks to pass before merging
37
+ - Disable force-pushes and branch deletion on the default branch
38
+
39
+ See the README "Configure branch protection" step for the exact `gh api` invocation. You **MUST NOT** proceed to treat the project as fully initialized while branch protection remains unconfigured without the user's explicit acknowledgment.
40
+
20
41
  ## Document Changelog Convention
21
42
 
22
43
  Every document produced by this activity **MUST** include a **Changelog** table as the **first section** after the document title. The changelog tracks the version history of the document.
@@ -36,90 +57,119 @@ Every document produced by this activity **MUST** include a **Changelog** table
36
57
 
37
58
  ---
38
59
 
39
- ## Mode Detection (RF-60)
60
+ ## Mode Detection
40
61
 
41
62
  Before starting the interview, the skill **MUST** detect the repository mode and route accordingly. The detection logic is:
42
63
 
43
- 1. **Multi-repo mode:** `component.json` exists at the repository root → the repository is a component in a multi-repo product. Context resolution passes exclusively through `dt`.
44
- 2. **Mono-repo mode:** no `component.json` at root, but `/docs` directory exists → current single-repo flow (interview + direct docs generation).
45
- 3. **Undocumented / greenfield mode:** neither `component.json` nor `/docs` → extraction-first flow to bootstrap documentation from code, then interview.
46
-
47
- > **Precedence:** If both `component.json` AND `/docs` exist, multi-repo mode wins — `component.json` is the authoritative signal.
64
+ 1. **Documented-repository mode:** `/docs` directory exists → interview + direct docs generation.
65
+ This mode is about whether documentation exists, not about how many packages the repository has. Repository _shape_ (single-package or monorepo) is detected separately — see Repository Shape Detection below. The mode was called "Mono-Repo" until `shared-understanding#D-44` renamed it to free the term.
66
+ 2. **Undocumented / greenfield mode:** no `/docs` → investigation-first flow to bootstrap documentation from the codebase, then interview.
48
67
 
49
68
  ---
50
69
 
51
- ## Mode A — Multi-Repo (RF-61)
70
+ ## Mode A — Documented Repository (Current Flow)
52
71
 
53
- When `component.json` is present at the repo root, the skill **MUST** delegate all context resolution to `dt` and **MUST NOT** read `/docs` or walk the repository directly.
72
+ When `/docs` exists, the skill follows the **existing single-repo flow** unchanged.
54
73
 
55
74
  ### Process
56
75
 
57
- 1. **Invoke `dt init --task "<user's task/product description>" --json`**.
58
- 2. **Handle exit codes:**
76
+ 1. **Receive Initial Brief:** The user describes the product, project, or technology stack.
77
+ 2. **Ask Clarifying Questions:** Gather information for both product context and technical guidelines in a single interview. Group questions by domain.
78
+ 3. **Generate Product Document:** Create `docs/product.md` using the structure below.
79
+ 4. **Generate Technical Document:** Create `docs/tech.md` using the structure below.
80
+ 5. **Save Output:** Save both documents in `/docs/` and present them for user review.
81
+
82
+ ---
83
+
84
+ ## Mode B — Undocumented / Greenfield
59
85
 
60
- | Exit Code | Meaning | Action |
61
- | --------- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
62
- | `0` | Success — bundle emitted | Load bundle files in numeric order. Present `review_flags` (if any) to the user before proceeding to planning. Continue to the interview for product context and technical guidelines using the bundle as input. |
63
- | `7` | Gate abort — partition proposal | Present the partition proposal to the user. Explain that the scope is too broad and needs to be split. **Stop** — do not proceed to planning. |
64
- | `9` | Stale catalog index | Inform the user that the catalog index is stale and needs to be rebuilt (e.g., `dt catalog build`). **Stop** — do not proceed. |
65
- | `10` | Invalid scope after LLM retry | Inform the user that automatic scoping failed. Suggest running with `--components` for manual scope. **Stop.** |
66
- | `11` | No candidates found | Inform the user that no components matched the task description. Suggest refining the task text or using `--components`. **Stop.** |
67
- | `6` | Budget overflow | Inform the user that the scoped context exceeds the token budget. Suggest narrowing scope with `--max-components` or `--budget`. **Stop.** |
86
+ When `/docs` does not exist, the repository has no established documentation. The skill investigates the codebase directly before conducting the interview.
68
87
 
69
- 3. **On success (exit 0):**
70
- - Load the assembled bundle files in numeric order (they form the context).
71
- - If `review_flags` are present in the JSON output, present them as warnings to the user (e.g., "scope spans >2 domains", "low-payload boundary contract") and ask whether to proceed.
72
- - Use the bundle content as the basis for the product-context and technical-guidelines interview — the bundle replaces direct `/docs` reading.
88
+ ### Process
89
+
90
+ 1. **Investigate the codebase:** Read manifest files (`package.json`, `pyproject.toml`, `go.mod`, or equivalent), the directory structure, the README, and any existing configuration to identify the technology stack, frameworks, and conventions in use.
91
+ 2. **Present a findings summary:** Show the user what was found — stack, frameworks, notable directories, confidence per finding — before the interview.
92
+ 3. **Conduct the interview:** Proceed with the standard clarifying questions for product and technical context (same as documented-repository mode).
93
+ 4. **Generate documents:** Create `docs/product.md` and `docs/tech.md` using the investigation findings as pre-filled context combined with interview answers.
94
+ 5. **Save Output:** Save both documents in `/docs/` and present them for user review.
73
95
 
74
96
  ### Constraints
75
97
 
76
- - The skill **MUST NOT** read `/docs`, walk the repository tree, or inspect source files directly in multi-repo mode.
77
- - All context comes from the `dt init` bundle output.
78
- - The skill **MAY** ask follow-up questions to fill gaps not covered by the bundle (e.g., strategic goals, success metrics).
98
+ - The investigation findings inform but do not replace the interview — the user confirms and supplements.
99
+ - If the repository has no identifiable stack (an empty project), skip investigation and proceed directly to the interview (pure greenfield).
79
100
 
80
101
  ---
81
102
 
82
- ## Mode B — Mono-Repo (Current Flow)
103
+ ---
83
104
 
84
- When no `component.json` is present but `/docs` exists, the skill follows the **existing single-repo flow** unchanged.
105
+ ## Repository Shape Detection
85
106
 
86
- ### Process
107
+ Before the interview, detect the repository's **shape**. This is independent of the mode above: a documented repository can be either shape, and so can a greenfield one.
87
108
 
88
- 1. **Receive Initial Brief:** The user describes the product, project, or technology stack.
89
- 2. **Ask Clarifying Questions:** Gather information for both product context and technical guidelines in a single interview. Group questions by domain.
90
- 3. **Generate Product Context Document:** Create `product-context.md` using the structure below.
91
- 4. **Generate Technical Guidelines Document:** Create `technical-guidelines.md` using the structure below.
92
- 5. **Save Output:** Save both documents in `/docs/` and present them for user review.
109
+ Detect from these signals (FR-59):
93
110
 
94
- ---
111
+ | Signal | Read for |
112
+ | ----------------------------------------- | ------------------------------ |
113
+ | `pnpm-workspace.yaml` | Shape **and** the package list |
114
+ | `workspaces` in `package.json` | Shape **and** the package list |
115
+ | `turbo.json` | Shape only |
116
+ | `nx.json` | Shape only |
117
+ | `lerna.json` | Shape only |
118
+ | `[tool.uv.workspace]` in `pyproject.toml` | Shape only |
95
119
 
96
- ## Mode C — Undocumented / Greenfield
120
+ Any signal present → **monorepo**. No signal → **single-package**.
97
121
 
98
- When neither `component.json` nor `/docs` exists, the repository has no established documentation. The skill bootstraps documentation from code extraction before conducting the interview.
122
+ Only the first two are parsed for a package list. When a repository signals monorepo through one of the other four, ask the user which packages exist rather than guessing.
99
123
 
100
- ### Process
124
+ `core/distribution/workspace.ts` exports `detectWorkspace(repoRoot)`, which returns the shape, the signals found, and the packages. Use it rather than re-deriving the answer.
101
125
 
102
- 1. **Run detection:** Invoke `dt extract detect` to identify the repository's technology stack, frameworks, and extractable artifacts.
103
- 2. **Run extraction:** Invoke `dt extract all --interactive` to extract schema, OpenAPI, AsyncAPI, and component manifest from the codebase.
104
- - The `--interactive` flag allows the user to confirm or skip ambiguous extractions.
105
- - If interrupted, the skill **SHOULD** inform the user how to resume (`dt extract all --interactive` picks up where it left off).
106
- 3. **Present extraction report:** Show the user the results of extraction — what was found, confidence levels, any `unresolved` items.
107
- 4. **Conduct the interview:** Proceed with the standard clarifying questions for product context and technical guidelines (same as Mono-Repo mode).
108
- 5. **Generate documents:** Create `product-context.md` and `technical-guidelines.md` using the extraction results as pre-filled context combined with interview answers.
109
- 6. **Save Output:** Save both documents in `/docs/` and present them for user review.
126
+ ### Package Map
110
127
 
111
- ### Constraints
128
+ Record the result in `docs/tech.md` as a **Package Map** section, one row per package:
129
+
130
+ ```markdown
131
+ ## Package Map
132
+
133
+ | Package | Path | Purpose | Owner | Canonical scripts | Bounded context |
134
+ | ---------- | ------------- | ------------------- | -------- | --------------------- | --------------- |
135
+ | @acme/core | packages/core | Shared domain logic | platform | lint, typecheck, test | Ordering |
136
+ ```
112
137
 
113
- - The extraction results inform but do not replace the interview — the user confirms and supplements.
114
- - If `dt extract detect` reports that no extractable content was found (empty project), skip extraction and proceed directly to the interview (pure greenfield).
138
+ Rules:
139
+
140
+ - A **single-package repository records exactly one row**, for the root, with path `.`. The table has the same shape in both cases, so a reader never has to work out which kind of repository they are looking at.
141
+ - **Purpose** and **Owner** come from the interview. Do not invent an owner; ask.
142
+ - **Canonical scripts** lists the scripts the package actually defines, in the order `lint`, `format:check`, `typecheck`, `test`, `test:unit`, `test:integration`, `test:e2e`, `audit`, `validate`. Absent scripts are omitted, not marked missing.
143
+ - **Bounded context** is filled **freeform at interview time** (`shared-understanding#D-45`). Ask: _"In one phrase, what part of the business or domain does this package own?"_ A freeform guess beats an empty column. Once `docs/domain/ubiquitous-language.md` defines a bounded context, that file is canonical: copy the name from its `## Bounded Context:` heading character for character, because `lint`'s glossary check matches the two exactly (`shared-understanding#D-69`, closing `#D-45`).
144
+ - A package whose `package.json` has no `name` is listed by its path. Do not invent a name — nothing would match it.
145
+
146
+ `dev-tasks doctor` warns when the map and the workspace disagree in either direction: a package on disk with no row, or a row for a package that no longer exists. It warns and never fails; structural failures belong to `lint`.
115
147
 
116
148
  ---
117
149
 
150
+ ### Runbooks
151
+
152
+ Initialization also establishes `docs/runbooks/` (PRD AC-26, S-005 AC-7). Create:
153
+
154
+ - `docs/runbooks/README.md` — the index, with Runbook / Trigger / Owner / Last verified columns.
155
+ - `docs/runbooks/runbook-template.md` — the form to copy for a new procedure.
156
+
157
+ `dev-tasks install` delivers both install-if-absent, so in an installed repository they are already present and **MUST NOT** be overwritten. Create them only when absent, and confirm with the user which procedures are worth a runbook now rather than writing placeholder files.
158
+
159
+ ## SIMPLICITY.md Confirmation
160
+
161
+ `SIMPLICITY.md` ships at the repository root and states the code-simplicity contract, including section D's tool-enforced thresholds. During initialization you **MUST** confirm two things with the user rather than assuming them:
162
+
163
+ 1. **Owner** — who is accountable for the contract. The shipped default is `housekeeping`.
164
+ 2. **Thresholds** — section D's defaults (function length ≤ 40 lines, cyclomatic complexity ≤ 10, cognitive complexity ≤ 15, nesting depth ≤ 3, parameters ≤ 4, file length ≤ 400 lines). A repository **MAY** tighten a default; it **MUST NOT** loosen one.
165
+
166
+ Ask: _"SIMPLICITY.md's owner is `housekeeping` and its thresholds are the shipped defaults. Keep both, or tighten anything?"_ Record the answer in the file's frontmatter and in the section D table. Wiring the thresholds into a linter is a separate procedure — see `docs/runbooks/runbook-setup-simplicity-tooling.md`.
167
+
118
168
  ## Part 1 — Product Context
119
169
 
120
170
  ### Clarifying Questions
121
171
 
122
- Adapt questions based on context provided (and based on mode — in multi-repo mode, the bundle already provides some answers):
172
+ Adapt questions based on context already gathered (e.g., from codebase investigation in greenfield mode):
123
173
 
124
174
  - **Product Definition:** "What is this product/project, and what does it do?"
125
175
  - **Problem Statement:** "What core problem does this product solve?"
@@ -132,7 +182,7 @@ Adapt questions based on context provided (and based on mode — in multi-repo m
132
182
  - **Key Constraints:** "Budget, timeline, technology, or regulatory constraints?"
133
183
  - **Stakeholders:** "Who are the key decision-makers?"
134
184
 
135
- ### Output Structure: `product-context.md`
185
+ ### Output Structure: `docs/product.md`
136
186
 
137
187
  0. **Changelog** — Version history table (see Document Changelog Convention above)
138
188
  1. **Executive Summary** — 2-3 sentence overview
@@ -171,27 +221,28 @@ Adapt questions based on context provided (and based on mode — in multi-repo m
171
221
  - **Package Manager Standard:** "Can we standardize on `pnpm` for JS/TS projects?"
172
222
  - **Script Naming Standard:** "Should canonical `package.json` scripts (`lint`, `format:check`, `typecheck`, `test`, `audit`, `validate`) be enforced?"
173
223
 
174
- ### Output Structure: `technical-guidelines.md`
224
+ ### Output Structure: `docs/tech.md`
175
225
 
176
226
  0. **Changelog** — Version history table (see Document Changelog Convention above)
177
227
  1. **Overview** — Technical vision and guiding principles
178
- 2. **Technology Stack** — Backend/frontend languages, frameworks, databases, key dependencies
179
- 3. **Architecture Patterns** — System architecture, key decisions and rationale, component organization
180
- 4. **API Design Standards** — Style, naming, request/response formats, error handling
181
- 5. **Authentication & Authorization** — Mechanism, model, permission levels, session management
182
- 6. **Security Requirements** — Encryption, OWASP compliance, API key management, PII handling
183
- 7. **Data & Database Guidelines** — Schema patterns, naming conventions, query optimization, backup
184
- 8. **Integration Methods** — External integrations, patterns, retry/failure handling
185
- 9. **Code Organization & Structure** — Folder/file conventions, module boundaries, naming
186
- 10. **Design Patterns & Principles** — Preferred patterns, SOLID, DRY/KISS/YAGNI
187
- 11. **Testing Strategy** — Frameworks, testing pyramid, coverage, mock strategies
188
- 12. **Code Quality & Standards** — Linting, static analysis, reviews, documentation
189
- 13. **Deployment & DevOps** — Environments, CI/CD, infrastructure-as-code, containers
190
- 14. **Monitoring, Logging & Observability** — Levels, frameworks, alerting, error tracking
191
- 15. **Performance & Scalability** — Response targets, throughput, caching, optimization
192
- 16. **Dependency Management** — Management approach, version pinning, vulnerability scanning
193
- 17. **Development Workflow** — Branching strategy, commit conventions, PR process
194
- 18. **Known Constraints & Trade-offs** — Limitations and rationale
228
+ 2. **Package Map** — Repository shape and one row per package (see Repository Shape Detection above)
229
+ 3. **Technology Stack** — Backend/frontend languages, frameworks, databases, key dependencies
230
+ 4. **Architecture Patterns** — System architecture, key decisions and rationale, component organization
231
+ 5. **API Design Standards** — Style, naming, request/response formats, error handling
232
+ 6. **Authentication & Authorization** — Mechanism, model, permission levels, session management
233
+ 7. **Security Requirements** — Encryption, OWASP compliance, API key management, PII handling
234
+ 8. **Data & Database Guidelines** — Schema patterns, naming conventions, query optimization, backup
235
+ 9. **Integration Methods** — External integrations, patterns, retry/failure handling
236
+ 10. **Code Organization & Structure** — Folder/file conventions, module boundaries, naming
237
+ 11. **Design Patterns & Principles** — Preferred patterns, SOLID, DRY/KISS/YAGNI
238
+ 12. **Testing Strategy** — Frameworks, testing pyramid, coverage, mock strategies
239
+ 13. **Code Quality & Standards** — Linting, static analysis, reviews, documentation
240
+ 14. **Deployment & DevOps** — Environments, CI/CD, infrastructure-as-code, containers
241
+ 15. **Monitoring, Logging & Observability** — Levels, frameworks, alerting, error tracking
242
+ 16. **Performance & Scalability** — Response targets, throughput, caching, optimization
243
+ 17. **Dependency Management** — Management approach, version pinning, vulnerability scanning
244
+ 18. **Development Workflow** — Branching strategy, commit conventions, PR process
245
+ 19. **Known Constraints & Trade-offs** — Limitations and rationale
195
246
 
196
247
  ### JS/TS Package Manager and Script Defaults
197
248
 
@@ -213,7 +264,7 @@ When the project includes JavaScript/TypeScript:
213
264
 
214
265
  - **Format:** Markdown (`.md`)
215
266
  - **Location:** `/docs/`
216
- - **Filenames:** `product-context.md`, `technical-guidelines.md`
267
+ - **Filenames:** `product.md`, `tech.md`
217
268
 
218
269
  ## AGENTS.md Sizing
219
270
 
@@ -232,4 +283,3 @@ When generating or updating `AGENTS.md` during project initialization, you **MUS
232
283
  5. You **MUST** save both files and present them for user review.
233
284
  6. You **SHOULD** iterate based on user feedback before finalizing.
234
285
  7. When updating an existing document, you **MUST** add a new row to the Changelog table with an incremented version, the current date, a summary of changes, and the responsible author/agent.
235
- 8. In multi-repo mode, you **MUST NOT** read `/docs` or walk the repository directly — all context passes through `dt init`.
@@ -0,0 +1,156 @@
1
+ ---
2
+ name: activity-integration-test-implementation
3
+ description: "Author integration tests (Layer 2.5) against real databases — local via testcontainers/docker-compose/Supabase CLI, remote via testing environments. Covers migrations, RLS, pgTAP, fixtures, and fallback paths. Use when writing or backfilling integration tests."
4
+ ---
5
+
6
+ # Activity: Integration Test Implementation (Layer 2.5)
7
+
8
+ Author integration tests that exercise code against a real database. Layer 2.5 exists because mocking the data layer makes SQL errors, type mismatches, NULL handling, malformed joins, and RLS policies structurally invisible.
9
+
10
+ ---
11
+
12
+ > **RFC 2119 Notice:** The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHALL**, **SHALL NOT**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY**, and **OPTIONAL** in this document are to be interpreted as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119).
13
+
14
+ ## Goal
15
+
16
+ Produce integration tests that fail when the data layer is wrong. If the database is mocked, the test belongs at Layer 2, not here.
17
+
18
+ Consult `/TESTING.md` first. Its Layer 2.5 boundary governs; this skill supplies the method.
19
+
20
+ ## Layer 2.5 Boundary
21
+
22
+ - **MUST** use a real database (Postgres, SQLite, etc.) — not a mock or in-memory fake.
23
+ - **MUST NOT** mock the data layer. If you mock `sql`, `prisma`, `drizzle`, or the ORM client, the test is Layer 2.
24
+ - **MUST NOT** assert on SQL text or internal query shape. Assert on persisted state or returned data.
25
+ - **MAY** mock third-party external services (payment gateways, email providers) at the HTTP boundary.
26
+
27
+ ## Part 1 — Local Integration Environment Detection
28
+
29
+ Detect the easiest applicable local option. Prefer in this order:
30
+
31
+ ### 1. Testcontainers (preferred for isolation)
32
+
33
+ - Look for `@testcontainers/postgresql` or equivalent in `package.json`/`pom.xml`/`Cargo.toml`.
34
+ - Requires Docker. Check: `docker info` succeeds.
35
+ - Each test suite gets an ephemeral container — full isolation, no cleanup conflicts.
36
+
37
+ ### 2. Docker Compose
38
+
39
+ - Look for `docker-compose.yml` or `compose.yml` with a database service.
40
+ - Requires Docker. Shared instance across tests — needs explicit state reset.
41
+
42
+ ### 3. Supabase Local CLI
43
+
44
+ - Look for `supabase/config.toml` or `.supabase/` directory.
45
+ - Check: `supabase status` succeeds.
46
+ - Provides real Postgres with auth, storage, and edge functions locally.
47
+
48
+ ### 4. Fallback — No Local Environment
49
+
50
+ - If Docker is unavailable and Supabase CLI is not installed, report the limitation.
51
+ - Emit: `SKIPPED(no local database environment — Docker unavailable, Supabase CLI not installed)`.
52
+ - Recommend environment setup as a follow-up. Do not silently omit.
53
+
54
+ ## Part 2 — Fixtures, Seeding, and Lifecycle
55
+
56
+ ### Test isolation
57
+
58
+ - Each test **SHOULD** run in a transaction that rolls back on completion (preferred).
59
+ - Alternative: truncate affected tables in `beforeEach`/`afterEach`.
60
+ - Alternative for testcontainers: fresh container per suite (slower but fully isolated).
61
+
62
+ ### Seeding
63
+
64
+ - Shared seed data lives in one location per package (e.g., `test/fixtures/seed.sql` or `test/helpers/seed.ts`).
65
+ - Seeds **MUST** be idempotent — running twice produces the same state.
66
+ - Seeds **MUST NOT** depend on auto-increment IDs. Use deterministic UUIDs or named references.
67
+
68
+ ### Deterministic teardown
69
+
70
+ - Every integration test file **MUST** clean up after itself or use rollback isolation.
71
+ - Tests **MUST NOT** depend on execution order.
72
+ - Tests **MUST NOT** leave residual data that affects other test files.
73
+
74
+ ## Part 3 — Migration Clean-Apply Tests
75
+
76
+ - **MUST** test that all migrations apply cleanly from an empty database.
77
+ - **MUST** verify apply order (no duplicate prefixes, no gaps).
78
+ - **MUST** verify idempotency: running migrations twice does not error.
79
+ - For large stacks (50+ migrations): run full clean-apply on CI/scheduled; run latest N on PR.
80
+ - Report duplicate migration prefixes as a finding.
81
+
82
+ ## Part 4 — Row-Level Security (RLS) Policy Tests
83
+
84
+ RLS tests **MUST** exercise the real database policy, not application-level tenant checks in JavaScript.
85
+
86
+ ### Multi-session setup
87
+
88
+ - Create at least two database roles or authenticated sessions (Tenant A, Tenant B).
89
+ - Use `SET ROLE` or separate connections per tenant.
90
+ - For Supabase: use `supabase.auth.admin.createUser()` for test users, then authenticate with their JWTs.
91
+
92
+ ### Required assertions
93
+
94
+ | Case | Assertion |
95
+ | ---------------------------- | ----------------------------------- |
96
+ | Tenant A reads own data | Returns expected rows |
97
+ | Tenant A reads Tenant B data | Returns empty set or error |
98
+ | Tenant A writes to Tenant B | Insert/update fails or is invisible |
99
+ | Unauthenticated access | Denied by policy |
100
+ | Service role bypasses RLS | Returns all rows (when expected) |
101
+
102
+ ### Record limitations
103
+
104
+ If isolation is asserted against application-level checks rather than the real RLS policy, you **MUST** record: "Production RLS policy unverified — tested against application-layer tenant filtering only."
105
+
106
+ ## Part 5 — pgTAP / Schema Contract Tests
107
+
108
+ Use pgTAP (or equivalent: `pg_prove`, raw SQL assertions) for:
109
+
110
+ - Table and column existence.
111
+ - Constraint verification (NOT NULL, UNIQUE, CHECK, FK).
112
+ - Function and trigger existence and signatures.
113
+ - Permission grants per role.
114
+ - Index existence for query-critical paths.
115
+
116
+ When pgTAP is unavailable, use raw `SELECT` assertions against `information_schema` or `pg_catalog`.
117
+
118
+ ## Part 6 — Remote Integration Testing
119
+
120
+ ### Default: read-only
121
+
122
+ - Inspect schema, permissions, RLS policies, and data shape without mutation.
123
+ - Use `EXPLAIN` for query plan verification without executing writes.
124
+ - No approval required for read-only operations.
125
+
126
+ ### Testing environment writes
127
+
128
+ - **REQUIRE** explicit user approval before any write or migration apply.
129
+ - Connect only to a dedicated testing environment — never to production for writes.
130
+ - After writes: verify applied state, then clean up test data.
131
+ - Record: environment name, operation performed, approval evidence.
132
+
133
+ ### No testing environment available
134
+
135
+ - Report: "Remote integration limited to read-only inspection. No testing environment configured."
136
+ - Recommend environment setup. Do not fabricate a pass.
137
+
138
+ ## Output
139
+
140
+ - Tests written or updated, by path and layer
141
+ - Local environment detection result (which option selected, or fallback triggered)
142
+ - Migration clean-apply result
143
+ - RLS policy test coverage per table with RLS enabled
144
+ - Schema contract coverage (tables, constraints, functions)
145
+ - Remote integration status (read-only / testing-env / unavailable)
146
+ - Stated limitations where real-policy testing was not possible
147
+
148
+ ## Final Instructions
149
+
150
+ 1. You **MUST** consult `/TESTING.md` and respect its Layer 2.5 boundary.
151
+ 2. You **MUST NOT** mock the data layer. If the database is mocked, the test is Layer 2.
152
+ 3. You **MUST** detect the local environment and recommend the easiest applicable option.
153
+ 4. You **MUST** report a limitation when no local or remote environment is available.
154
+ 5. You **MUST** test RLS against the real policy layer, not application-level checks.
155
+ 6. You **MUST** require explicit approval before any remote write operation.
156
+ 7. You **MUST NOT** install dependencies — detect and recommend only.
@@ -19,12 +19,14 @@ Clarify the scope, acceptance criteria, and constraints of a feature or issue be
19
19
 
20
20
  This step assumes foundation documents exist:
21
21
 
22
- - `product-context.md` — Understanding the overall product
23
- - `technical-guidelines.md` — Understanding technical constraints and patterns
22
+ - `product.md` — Understanding the overall product
23
+ - `tech.md` — Understanding technical constraints and patterns
24
24
 
25
25
  If the user provides a **GitHub Issue number**, you **MUST** produce a lightweight refinement.
26
26
  If the user provides a **feature description**, you **MUST** produce a full PRD.
27
27
 
28
+ Before drafting either output, this activity invokes the `activity-grill` sub-skill (WHAT phase for PRD Creation mode, Issue Mode for Issue Refinement mode) to walk the design tree to shared understanding, and writes every resolved question to `workstream/decisions-<feature>.md` — see Mode A and Mode B Process below.
29
+
28
30
  ---
29
31
 
30
32
  ## Document Changelog Convention
@@ -61,14 +63,14 @@ Every document produced by this activity **MUST** include a **Changelog** table
61
63
 
62
64
  1. **Receive Issue Reference:** User provides GitHub Issue number and repo.
63
65
  2. **Read Issue:** Delegate to `github-ops` to fetch issue body, comments, labels, and status whenever possible.
64
- 3. **Ask Clarifying Questions:** Focus on missing scope, acceptance criteria, and constraints.
65
- 4. **Refine Scope:** Summarize scope, non-goals, risks, and dependencies.
66
+ 3. **Invoke `activity-grill`:** Before asking any clarifying question, invoke `activity-grill(mode="issue", cap=cap.issue)` (`cap.issue` defaults to 8; read from `docs/tech.md` § Grilling if that subsection exists, else the hardcoded default) (FR-15, AC-09). The candidate questions below seed the interview's question pool — `activity-grill` owns the one-question-at-a-time, resolve-before-ask mechanics, including mandatory reuse of a matching answer from any prior `decisions-<other-feature>.md` (cited in qualified `<other-feature>#D-NN` form, not re-asked) and read-only glossary treatment (no new term proposals) for the duration of this invocation. You **MUST NOT** proceed to scope refinement until `activity-grill` returns the exit gate satisfied.
67
+ 4. **Refine Scope:** Summarize scope, non-goals, risks, and dependencies, citing inline (`… (D-NN)`) every statement a decision shaped.
66
68
  5. **Update GitHub Issue:** Delegate to `github-ops` to add or update a "Refined Scope" section in the issue body.
67
69
  6. **Save Output.**
68
70
 
69
71
  If `github-ops` delegation is unavailable in the current runtime, you **MUST** apply `github-ops` conventions directly and explicitly note that fallback in your status output.
70
72
 
71
- ### Clarifying Questions (ask only what is missing)
73
+ ### Candidate Clarifying Questions (seed the `activity-grill` interview; ask only what is missing)
72
74
 
73
75
  - "What is the exact user-visible behavior change?"
74
76
  - "What is explicitly out of scope?"
@@ -132,11 +134,19 @@ For each criterion, you **SHOULD** use a concise "Given / When / Then" style whe
132
134
  - Edge-case checks:
133
135
  - Acceptance-criteria-to-test mapping:
134
136
 
137
+ ## Decisions
138
+
139
+ | ID | Decision (short form) |
140
+ | ---- | --------------------- |
141
+ | D-NN | … |
142
+
135
143
  ## Open Questions
136
144
 
137
145
  - [Remaining unknowns]
138
146
  ```
139
147
 
148
+ The `## Decisions` table lists every decision ID `activity-grill` produced or reused that shaped this document (FR-14, AC-05) — the same shape this repository's own PRDs and specs already use. A refinement with zero decisions needed still runs the `activity-grill` interview and still requires the explicit exit-gate confirmation; the table may legitimately be empty in that case.
149
+
140
150
  ### Output
141
151
 
142
152
  - **Location:** `/workstream/`
@@ -149,12 +159,12 @@ For each criterion, you **SHOULD** use a concise "Given / When / Then" style whe
149
159
  ### Process
150
160
 
151
161
  1. **Receive Feature Scope:** User describes the features or feature set.
152
- 2. **Ask Clarifying Questions:** Gather detail about requirements, prioritization, and acceptance criteria.
162
+ 2. **Invoke `activity-grill`:** Before asking any clarifying question, invoke `activity-grill(phase="WHAT", cap=cap.what)` (`cap.what` defaults to 25; read from `docs/tech.md` § Grilling if that subsection exists, else the hardcoded default) (FR-12, AC-01). The candidate questions below seed the interview's question pool — `activity-grill` owns the one-question-at-a-time, resolve-before-ask mechanics and the decision-tree summary/cap cadence. You **MUST NOT** produce any PRD section, draft, or outline until `activity-grill` returns the exit gate satisfied.
153
163
  3. **Reference Existing Documents:** Consider product context and technical guidelines.
154
- 4. **Generate PRD.**
164
+ 4. **Generate PRD:** Cite inline (`… (D-NN)`) every requirement, goal, or scope statement a decision shaped.
155
165
  5. **Save Output.**
156
166
 
157
- ### Clarifying Questions
167
+ ### Candidate Clarifying Questions (seed the `activity-grill` interview)
158
168
 
159
169
  - **Feature Title & Scope:** "What is the main feature? What is included?"
160
170
  - **Affected Repositories:** "Which repositories will be affected by this feature? (e.g., `owner/repo-frontend`, `owner/repo-backend`)"
@@ -190,6 +200,53 @@ For each criterion, you **SHOULD** use a concise "Given / When / Then" style whe
190
200
  16. **Constraints & Dependencies** — Timeline, resource, external dependencies
191
201
  17. **Security & Compliance** — Security, privacy, auth requirements
192
202
  18. **Open Questions** — Ambiguities needing clarification
203
+ 19. **Decisions** — Table (`ID | Decision (short form)`) listing every `activity-grill` decision ID consumed by this PRD (FR-14, AC-05); may legitimately be empty for a trivial feature that needed no decisions, but the `activity-grill` interview and exit-gate confirmation still ran
204
+ 20. **Vocabulary** — `## Vocabulary` table listing every domain term the PRD uses and where each one stands against the glossary: `existing`, `proposed`, or settled by a decision (FR-20, AC-07). See "Vocabulary Section" below
205
+
206
+ ### Vocabulary Section (FR-20, AC-07)
207
+
208
+ Every PRD carries a `## Vocabulary` section immediately after `## Decisions`. It lists the domain terms the PRD uses and where each one stands against `docs/domain/ubiquitous-language.md`, the repository's canonical vocabulary:
209
+
210
+ ```markdown
211
+ ## Vocabulary
212
+
213
+ | Term | Status in glossary | Bounded context | Definition (proposals only) | Forbidden synonyms (proposals only) |
214
+ | ---- | --------------------------------------- | --------------- | --------------------------- | ----------------------------------- |
215
+ | … | existing \| proposed \| conflict → D-NN | … | … | … |
216
+ ```
217
+
218
+ A row is complete when one of these holds:
219
+
220
+ - `existing` — the glossary already defines the term (matched case-insensitively). The proposal columns stay empty.
221
+ - `proposed` — the row carries a bounded context, a definition, and forbidden synonyms. `none` is an answer for forbidden synonyms; an empty cell is not. A `proposed` row for a term the glossary already defines is **incomplete** — use `existing`.
222
+ - `conflict → D-NN` — a recorded decision settled a clash between this term and one already in the glossary. `->` and `→` are both accepted, and the ID may be qualified (`<feature>#D-NN`).
223
+
224
+ A PRD that genuinely introduces no domain concept carries the section with exactly one line, which is complete on its own:
225
+
226
+ ```markdown
227
+ ## Vocabulary
228
+
229
+ None — this PRD introduces no domain concepts.
230
+ ```
231
+
232
+ Terms are identified during grilling, from what the user actually said. You **MUST NOT** derive them by scanning the PRD's prose for likely-looking nouns (D-65) — a list assembled that way is a list nobody can act on.
233
+
234
+ ### Approval Append (FR-20, specification §8.4)
235
+
236
+ The glossary grows when the user approves the PRD — **never when the PRD is drafted**. A term recorded at draft time is a term nobody agreed to.
237
+
238
+ When the user approves a PRD, for each `proposed` row you **MUST**:
239
+
240
+ 1. Resolve the row's bounded context against the `docs/tech.md` package map (FR-63). If it matches no package name and no `Bounded context` value, you **MUST NOT** create the heading — refuse the append for that row and report the unresolved context to the user. An unresolvable heading fails `lint` for everyone who comes after.
241
+ 2. Append a `### <Term>` entry under the matching `## Bounded Context:` heading in `docs/domain/ubiquitous-language.md`, creating that heading only when the context resolved. The entry carries all five fields: `Definition` and `Forbidden synonyms` from the row, `Invariants` (`none` when there are none), `Origin` to the PRD's path, and `Status: active`.
242
+ 3. Add one changelog row naming every term this approval added, in `+term` form (`+decision log, +exit gate`), and bump the frontmatter `version`.
243
+ 4. On the first append, flip the frontmatter `status` from `unfilled` to `active`. `unfilled` means "no vocabulary established yet", never permission to invent one.
244
+
245
+ A `conflict → D-NN` row whose decision superseded a term already in the glossary rewrites that term's `Status` to `superseded by <New Term> (<feature#D-NN>)`. The old entry **MUST** stay — terms are superseded, never deleted (FR-19).
246
+
247
+ Running the append again over an already-approved PRD **MUST** be a no-op: its rows now read `existing`, and neither the entry nor the changelog row is duplicated.
248
+
249
+ This append is `activity-refine`'s write and nobody else's. `activity-grill` surfaces vocabulary conflicts as questions and writes only the decision log (D-61).
193
250
 
194
251
  ### Diagram Guidelines
195
252
 
@@ -228,10 +285,13 @@ Rules:
228
285
 
229
286
  1. You **MUST NOT** start implementing anything.
230
287
  2. You **MUST** detect the mode based on user input (issue number vs. feature description).
231
- 3. You **MUST** ask clarifying questions to fill gaps.
232
- 4. You **MUST** present the document for user review.
233
- 5. You **SHOULD** iterate based on feedback.
234
- 6. You **MUST** save the finalized document.
235
- 7. In Issue Refinement mode, you **MUST** update the GitHub Issue with a "Refined Scope" section by delegating to `github-ops` whenever possible.
236
- 8. When updating an existing document, you **MUST** add a new row to the Changelog table with an incremented version, the current date, a summary of changes, and the responsible author/agent.
237
- 9. After producing the document, if the feature includes UI/UX scope (detected by keywords: UI, screen, page, form, modal, dialog, navigation, layout, component, responsive, accessibility), you **SHOULD** add the following recommendation to the user: "This feature has UI scope. **Recommended:** use `ux-engineer` (lite mode) to generate screen sketches before proceeding to spec/stories."
288
+ 3. You **MUST** ask clarifying questions to fill gaps, conducted through `activity-grill` (WHAT phase for PRD Creation mode, Issue Mode for Issue Refinement mode) — you **MUST NOT** draft any part of the document until `activity-grill`'s exit gate returns satisfied (FR-12, FR-15).
289
+ 4. Before presenting the PRD for review, you **MUST** run `checkVocabularySection()` from `core/checks/glossary.ts` over the drafted document and the repository's glossary, and **MUST** report every finding to the user by its rule name: `vocabulary-missing` when the `## Vocabulary` section is absent, `vocabulary-incomplete` naming the row that accounts for no term (AC-07, D-65). The same check runs under `lint` over `docs/requirements/`, so a finding left unfixed here becomes a failing gate later.
290
+ 5. You **MUST** present the document for user review.
291
+ 6. You **SHOULD** iterate based on feedback.
292
+ 7. You **MUST** save the finalized document.
293
+ 8. In Issue Refinement mode, you **MUST** update the GitHub Issue with a "Refined Scope" section by delegating to `github-ops` whenever possible.
294
+ 9. When updating an existing document, you **MUST** add a new row to the Changelog table with an incremented version, the current date, a summary of changes, and the responsible author/agent.
295
+ 10. After producing the document, if the feature includes UI/UX scope (detected by keywords: UI, screen, page, form, modal, dialog, navigation, layout, component, responsive, accessibility), you **SHOULD** add the following recommendation to the user: "This feature has UI scope. **Recommended:** use `ux-engineer` (lite mode) to generate screen sketches before proceeding to spec/stories."
296
+ 11. You **MUST** cite every decision that shaped a requirement or scope statement inline (`… (D-NN)`), and **MUST** populate the document's `## Decisions` section with every ID consumed from the `activity-grill` session, in qualified `<feature>#D-NN` form when reusing a decision from another feature's log (FR-14, AC-05).
297
+ 12. On user approval of a PRD, you **MUST** perform the Approval Append into `docs/domain/ubiquitous-language.md` for every `proposed` Vocabulary row, exactly as "Approval Append" above describes — and **MUST NOT** perform it when the PRD is merely drafted or revised (FR-20, D-61).