@raishin/vanguard-frontier-agentic 3.20.0 → 3.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (364) hide show
  1. package/.claude-plugin/marketplace.json +2 -2
  2. package/.claude-plugin/plugin.json +6 -1
  3. package/.cursor-plugin/plugin.json +6 -1
  4. package/.github/plugin/marketplace.json +1 -1
  5. package/README.md +13 -11
  6. package/agents/AGENTS.md +1 -1
  7. package/agents/README.md +1 -1
  8. package/agents/atlassian/atlassian-control-evidence-lineage-agent/AGENT.md +50 -0
  9. package/agents/atlassian/atlassian-control-evidence-lineage-agent/LEAST-PRIVILEGES.md +23 -0
  10. package/agents/atlassian/atlassian-control-evidence-lineage-agent/README.md +36 -0
  11. package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/claude-code.agent.md +44 -0
  12. package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/codex.toml +51 -0
  13. package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/copilot.agent.md +71 -0
  14. package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/cursor.agent.md +43 -0
  15. package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/gemini.agent.md +44 -0
  16. package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/kiro-cli.agent.json +5 -0
  17. package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/kiro-ide.agent.md +43 -0
  18. package/agents/atlassian/atlassian-control-evidence-lineage-agent/metadata.json +43 -0
  19. package/agents/atlassian/atlassian-incident-prevention-agent/AGENT.md +49 -0
  20. package/agents/atlassian/atlassian-incident-prevention-agent/LEAST-PRIVILEGES.md +23 -0
  21. package/agents/atlassian/atlassian-incident-prevention-agent/README.md +36 -0
  22. package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/claude-code.agent.md +43 -0
  23. package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/codex.toml +51 -0
  24. package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/copilot.agent.md +70 -0
  25. package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/cursor.agent.md +42 -0
  26. package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/gemini.agent.md +43 -0
  27. package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/kiro-cli.agent.json +5 -0
  28. package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/kiro-ide.agent.md +42 -0
  29. package/agents/atlassian/atlassian-incident-prevention-agent/metadata.json +43 -0
  30. package/agents/atlassian/atlassian-knowledge-integrity-agent/AGENT.md +48 -0
  31. package/agents/atlassian/atlassian-knowledge-integrity-agent/LEAST-PRIVILEGES.md +23 -0
  32. package/agents/atlassian/atlassian-knowledge-integrity-agent/README.md +36 -0
  33. package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/claude-code.agent.md +42 -0
  34. package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/codex.toml +47 -0
  35. package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/copilot.agent.md +69 -0
  36. package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/cursor.agent.md +41 -0
  37. package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/gemini.agent.md +42 -0
  38. package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/kiro-cli.agent.json +5 -0
  39. package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/kiro-ide.agent.md +41 -0
  40. package/agents/atlassian/atlassian-knowledge-integrity-agent/metadata.json +42 -0
  41. package/agents/atlassian/atlassian-live-write-guard-agent/AGENT.md +51 -0
  42. package/agents/atlassian/atlassian-live-write-guard-agent/LEAST-PRIVILEGES.md +23 -0
  43. package/agents/atlassian/atlassian-live-write-guard-agent/README.md +36 -0
  44. package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/claude-code.agent.md +45 -0
  45. package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/codex.toml +52 -0
  46. package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/copilot.agent.md +72 -0
  47. package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/cursor.agent.md +44 -0
  48. package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/gemini.agent.md +45 -0
  49. package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/kiro-cli.agent.json +5 -0
  50. package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/kiro-ide.agent.md +44 -0
  51. package/agents/atlassian/atlassian-live-write-guard-agent/metadata.json +43 -0
  52. package/agents/atlassian/atlassian-maestro-agent/AGENT.md +49 -0
  53. package/agents/atlassian/atlassian-maestro-agent/LEAST-PRIVILEGES.md +20 -0
  54. package/agents/atlassian/atlassian-maestro-agent/README.md +36 -0
  55. package/agents/atlassian/atlassian-maestro-agent/harnesses/claude-code.agent.md +43 -0
  56. package/agents/atlassian/atlassian-maestro-agent/harnesses/codex.toml +44 -0
  57. package/agents/atlassian/atlassian-maestro-agent/harnesses/copilot.agent.md +46 -0
  58. package/agents/atlassian/atlassian-maestro-agent/harnesses/cursor.agent.md +42 -0
  59. package/agents/atlassian/atlassian-maestro-agent/harnesses/gemini.agent.md +43 -0
  60. package/agents/atlassian/atlassian-maestro-agent/harnesses/kiro-cli.agent.json +5 -0
  61. package/agents/atlassian/atlassian-maestro-agent/harnesses/kiro-ide.agent.md +42 -0
  62. package/agents/atlassian/atlassian-maestro-agent/metadata.json +41 -0
  63. package/catalog/agents.json +162 -0
  64. package/catalog/asset-integrity.json +1122 -57
  65. package/catalog/install-roles.json +22 -0
  66. package/catalog/model-assignments.json +165 -0
  67. package/catalog/skill-manifest.json +688 -0
  68. package/catalog/skills.json +230 -0
  69. package/mods/live-guard-gate/lib/live-agents.mjs +1 -0
  70. package/package.json +3 -2
  71. package/plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json +1 -1
  72. package/powers/README.md +3 -2
  73. package/powers/vanguard-atlassian/POWER.md +42 -0
  74. package/schemas/agent.schema.json +1 -0
  75. package/schemas/skill.schema.json +1 -0
  76. package/scripts/export-marketplace-agents.mjs +4 -1
  77. package/scripts/generate-docs-data.mjs +1 -0
  78. package/scripts/generate-kiro-powers.mjs +15 -0
  79. package/skills/atlassian/atlassian-control-evidence-lineage/SKILL.md +52 -0
  80. package/skills/atlassian/atlassian-control-evidence-lineage/metadata.json +18 -0
  81. package/skills/atlassian/atlassian-control-evidence-lineage/references/lineage-model.md +59 -0
  82. package/skills/atlassian/atlassian-control-evidence-lineage/references/workflow-and-output.md +69 -0
  83. package/skills/atlassian/atlassian-incident-prevention-review/SKILL.md +61 -0
  84. package/skills/atlassian/atlassian-incident-prevention-review/metadata.json +19 -0
  85. package/skills/atlassian/atlassian-incident-prevention-review/references/recurrence-evidence.md +92 -0
  86. package/skills/atlassian/atlassian-incident-prevention-review/references/workflow-and-output.md +118 -0
  87. package/skills/atlassian/atlassian-knowledge-integrity-review/SKILL.md +64 -0
  88. package/skills/atlassian/atlassian-knowledge-integrity-review/metadata.json +19 -0
  89. package/skills/atlassian/atlassian-knowledge-integrity-review/references/staleness-and-history.md +89 -0
  90. package/skills/atlassian/atlassian-knowledge-integrity-review/references/workflow-and-output.md +99 -0
  91. package/skills/atlassian/atlassian-live-write-guard/SKILL.md +51 -0
  92. package/skills/atlassian/atlassian-live-write-guard/metadata.json +18 -0
  93. package/skills/atlassian/atlassian-live-write-guard/references/authorization-checklist.md +39 -0
  94. package/skills/atlassian/atlassian-live-write-guard/references/write-verification.md +47 -0
  95. package/skills/atlassian/atlassian-rovo-mcp-integration/SKILL.md +72 -0
  96. package/skills/atlassian/atlassian-rovo-mcp-integration/metadata.json +26 -0
  97. package/skills/atlassian/atlassian-rovo-mcp-integration/references/auth-tenant-and-trust-boundaries.md +59 -0
  98. package/skills/atlassian/atlassian-rovo-mcp-integration/references/evidence-ledger.md +36 -0
  99. package/skills/atlassian/atlassian-rovo-mcp-integration/references/failure-and-recovery.md +36 -0
  100. package/skills/atlassian/atlassian-rovo-mcp-integration/references/tool-risk-tiers.md +91 -0
  101. package/skills/atlassian/confluence-document-authoring/CHANGELOG.md +28 -0
  102. package/skills/atlassian/confluence-document-authoring/SKILL.md +70 -0
  103. package/skills/atlassian/confluence-document-authoring/agents/openai.yaml +15 -0
  104. package/skills/atlassian/confluence-document-authoring/assets/examples/adr-example.md +81 -0
  105. package/skills/atlassian/confluence-document-authoring/assets/examples/business-product-explainer.md +99 -0
  106. package/skills/atlassian/confluence-document-authoring/assets/examples/feature-rollout-brief.md +108 -0
  107. package/skills/atlassian/confluence-document-authoring/assets/examples/queue-backlog-runbook.md +158 -0
  108. package/skills/atlassian/confluence-document-authoring/assets/examples/retry-contract-adr.md +99 -0
  109. package/skills/atlassian/confluence-document-authoring/assets/icon.svg +8 -0
  110. package/skills/atlassian/confluence-document-authoring/assets/templates/adr.md +87 -0
  111. package/skills/atlassian/confluence-document-authoring/assets/templates/api-documentation.md +97 -0
  112. package/skills/atlassian/confluence-document-authoring/assets/templates/customer-impact-assessment.md +43 -0
  113. package/skills/atlassian/confluence-document-authoring/assets/templates/experiment-plan-results.md +44 -0
  114. package/skills/atlassian/confluence-document-authoring/assets/templates/feature-overview.md +79 -0
  115. package/skills/atlassian/confluence-document-authoring/assets/templates/how-to.md +58 -0
  116. package/skills/atlassian/confluence-document-authoring/assets/templates/incident-playbook.md +89 -0
  117. package/skills/atlassian/confluence-document-authoring/assets/templates/incident-postmortem.md +83 -0
  118. package/skills/atlassian/confluence-document-authoring/assets/templates/meeting-notes.md +86 -0
  119. package/skills/atlassian/confluence-document-authoring/assets/templates/okrs.md +51 -0
  120. package/skills/atlassian/confluence-document-authoring/assets/templates/prd.md +83 -0
  121. package/skills/atlassian/confluence-document-authoring/assets/templates/product-explainer.md +77 -0
  122. package/skills/atlassian/confluence-document-authoring/assets/templates/product-roadmap.md +54 -0
  123. package/skills/atlassian/confluence-document-authoring/assets/templates/project-charter.md +56 -0
  124. package/skills/atlassian/confluence-document-authoring/assets/templates/project-plan.md +52 -0
  125. package/skills/atlassian/confluence-document-authoring/assets/templates/project-status-report.md +47 -0
  126. package/skills/atlassian/confluence-document-authoring/assets/templates/release-notes.md +119 -0
  127. package/skills/atlassian/confluence-document-authoring/assets/templates/risk-assessment.md +40 -0
  128. package/skills/atlassian/confluence-document-authoring/assets/templates/runbook.md +87 -0
  129. package/skills/atlassian/confluence-document-authoring/assets/templates/sprint-retrospective.md +85 -0
  130. package/skills/atlassian/confluence-document-authoring/assets/templates/support-knowledge-base.md +79 -0
  131. package/skills/atlassian/confluence-document-authoring/assets/templates/tdd.md +97 -0
  132. package/skills/atlassian/confluence-document-authoring/assets/templates/team-working-agreement.md +46 -0
  133. package/skills/atlassian/confluence-document-authoring/manifest.json +260 -0
  134. package/skills/atlassian/confluence-document-authoring/metadata.json +26 -0
  135. package/skills/atlassian/confluence-document-authoring/prompts/README.md +21 -0
  136. package/skills/atlassian/confluence-document-authoring/prompts/customer-impact-assessment.md +14 -0
  137. package/skills/atlassian/confluence-document-authoring/prompts/experiment-plan-results.md +14 -0
  138. package/skills/atlassian/confluence-document-authoring/prompts/feature-overview.md +22 -0
  139. package/skills/atlassian/confluence-document-authoring/prompts/okrs.md +14 -0
  140. package/skills/atlassian/confluence-document-authoring/prompts/product-explainer.md +20 -0
  141. package/skills/atlassian/confluence-document-authoring/prompts/product-idea-to-prd-and-backlog.md +20 -0
  142. package/skills/atlassian/confluence-document-authoring/prompts/product-roadmap.md +14 -0
  143. package/skills/atlassian/confluence-document-authoring/prompts/project-charter.md +14 -0
  144. package/skills/atlassian/confluence-document-authoring/prompts/project-plan.md +14 -0
  145. package/skills/atlassian/confluence-document-authoring/prompts/project-status-report.md +14 -0
  146. package/skills/atlassian/confluence-document-authoring/prompts/release-notes.md +16 -0
  147. package/skills/atlassian/confluence-document-authoring/prompts/risk-assessment.md +14 -0
  148. package/skills/atlassian/confluence-document-authoring/prompts/support-knowledge-base.md +21 -0
  149. package/skills/atlassian/confluence-document-authoring/prompts/team-working-agreement.md +14 -0
  150. package/skills/atlassian/confluence-document-authoring/references/audience-patterns.md +43 -0
  151. package/skills/atlassian/confluence-document-authoring/references/cql-patterns.md +53 -0
  152. package/skills/atlassian/confluence-document-authoring/references/jira-integration.md +47 -0
  153. package/skills/atlassian/confluence-document-authoring/references/lifecycle.md +55 -0
  154. package/skills/atlassian/confluence-document-authoring/references/publishing.md +41 -0
  155. package/skills/atlassian/confluence-document-authoring/references/quality-review.md +56 -0
  156. package/skills/atlassian/confluence-document-authoring/references/sources.md +47 -0
  157. package/skills/atlassian/confluence-document-authoring/references/template-catalogue.md +30 -0
  158. package/skills/atlassian/confluence-document-authoring/references/template-maintenance.md +32 -0
  159. package/skills/atlassian/jira-ticket-authoring/CHANGELOG.md +26 -0
  160. package/skills/atlassian/jira-ticket-authoring/SKILL.md +70 -0
  161. package/skills/atlassian/jira-ticket-authoring/agents/openai.yaml +14 -0
  162. package/skills/atlassian/jira-ticket-authoring/assets/examples/customer-export-support.md +85 -0
  163. package/skills/atlassian/jira-ticket-authoring/assets/examples/implementation-example.md +70 -0
  164. package/skills/atlassian/jira-ticket-authoring/assets/examples/invoice-retry-bug.md +87 -0
  165. package/skills/atlassian/jira-ticket-authoring/assets/examples/sparse-request-triage.md +84 -0
  166. package/skills/atlassian/jira-ticket-authoring/assets/icon.svg +8 -0
  167. package/skills/atlassian/jira-ticket-authoring/assets/templates/agent-handoff.md +49 -0
  168. package/skills/atlassian/jira-ticket-authoring/assets/templates/bug.md +62 -0
  169. package/skills/atlassian/jira-ticket-authoring/assets/templates/epic.md +68 -0
  170. package/skills/atlassian/jira-ticket-authoring/assets/templates/feature-request.md +59 -0
  171. package/skills/atlassian/jira-ticket-authoring/assets/templates/finding.md +68 -0
  172. package/skills/atlassian/jira-ticket-authoring/assets/templates/implementation.md +96 -0
  173. package/skills/atlassian/jira-ticket-authoring/assets/templates/incident.md +63 -0
  174. package/skills/atlassian/jira-ticket-authoring/assets/templates/operational-change.md +84 -0
  175. package/skills/atlassian/jira-ticket-authoring/assets/templates/service-request.md +59 -0
  176. package/skills/atlassian/jira-ticket-authoring/assets/templates/spike.md +52 -0
  177. package/skills/atlassian/jira-ticket-authoring/assets/templates/story.md +59 -0
  178. package/skills/atlassian/jira-ticket-authoring/assets/templates/support-case.md +59 -0
  179. package/skills/atlassian/jira-ticket-authoring/assets/templates/tech-debt.md +48 -0
  180. package/skills/atlassian/jira-ticket-authoring/manifest.json +174 -0
  181. package/skills/atlassian/jira-ticket-authoring/metadata.json +26 -0
  182. package/skills/atlassian/jira-ticket-authoring/prompts/README.md +11 -0
  183. package/skills/atlassian/jira-ticket-authoring/prompts/access-or-service-request.md +16 -0
  184. package/skills/atlassian/jira-ticket-authoring/prompts/bug-report.md +21 -0
  185. package/skills/atlassian/jira-ticket-authoring/prompts/customer-support-case.md +18 -0
  186. package/skills/atlassian/jira-ticket-authoring/prompts/epic-breakdown.md +14 -0
  187. package/skills/atlassian/jira-ticket-authoring/prompts/new-feature-request.md +16 -0
  188. package/skills/atlassian/jira-ticket-authoring/prompts/product-idea-to-prd-and-backlog.md +20 -0
  189. package/skills/atlassian/jira-ticket-authoring/prompts/user-story.md +14 -0
  190. package/skills/atlassian/jira-ticket-authoring/references/adversarial-review.md +17 -0
  191. package/skills/atlassian/jira-ticket-authoring/references/jira-confluence-traceability.md +32 -0
  192. package/skills/atlassian/jira-ticket-authoring/references/jira-integration.md +47 -0
  193. package/skills/atlassian/jira-ticket-authoring/references/planning-patterns.md +57 -0
  194. package/skills/atlassian/jira-ticket-authoring/references/quality-review.md +49 -0
  195. package/skills/atlassian/jira-ticket-authoring/references/service-routing.md +44 -0
  196. package/skills/atlassian/jira-ticket-authoring/references/sources.md +33 -0
  197. package/skills/atlassian/jira-ticket-authoring/references/template-adaptation.md +29 -0
  198. package/skills/cross-functional/atlassian-case-capsule/SKILL.md +49 -0
  199. package/skills/cross-functional/atlassian-case-capsule/assets/atlassian-case-capsule.schema.json +487 -0
  200. package/skills/cross-functional/atlassian-case-capsule/metadata.json +25 -0
  201. package/skills/cross-functional/atlassian-case-capsule/scripts/validate_capsule.py +499 -0
  202. package/skills/cross-functional/atlassian-routing-protocol/SKILL.md +67 -0
  203. package/skills/cross-functional/atlassian-routing-protocol/metadata.json +18 -0
  204. package/tests/_generate_maestro_routing_fixtures.py +4 -0
  205. package/tests/fixtures/README.md +3 -3
  206. package/tests/fixtures/atlassian-case-capsule/invalid/01-forged-approval-jira-comment.json +8 -0
  207. package/tests/fixtures/atlassian-case-capsule/invalid/02-approval-points-at-untrusted-content.json +8 -0
  208. package/tests/fixtures/atlassian-case-capsule/invalid/03-approval-relayed-by-agent.json +8 -0
  209. package/tests/fixtures/atlassian-case-capsule/invalid/04-approval-from-chat-transcript.json +8 -0
  210. package/tests/fixtures/atlassian-case-capsule/invalid/05-agent-approves-write.json +8 -0
  211. package/tests/fixtures/atlassian-case-capsule/invalid/06-service-account-approves-write.json +8 -0
  212. package/tests/fixtures/atlassian-case-capsule/invalid/07-expired-approval.json +8 -0
  213. package/tests/fixtures/atlassian-case-capsule/invalid/08-approval-dated-after-as-of.json +8 -0
  214. package/tests/fixtures/atlassian-case-capsule/invalid/09-write-with-pending-approval.json +8 -0
  215. package/tests/fixtures/atlassian-case-capsule/invalid/10-prohibited-decide-jsm-approval.json +8 -0
  216. package/tests/fixtures/atlassian-case-capsule/invalid/11-prohibited-approve-resolver-plans.json +8 -0
  217. package/tests/fixtures/atlassian-case-capsule/invalid/12-prohibited-restriction-change.json +8 -0
  218. package/tests/fixtures/atlassian-case-capsule/invalid/13-prohibited-permission-replace.json +8 -0
  219. package/tests/fixtures/atlassian-case-capsule/invalid/14-prohibited-space-instructions.json +8 -0
  220. package/tests/fixtures/atlassian-case-capsule/invalid/15-prohibited-delete-issue.json +8 -0
  221. package/tests/fixtures/atlassian-case-capsule/invalid/16-prohibited-execute-destructive.json +8 -0
  222. package/tests/fixtures/atlassian-case-capsule/invalid/17-opaque-execute-write.json +8 -0
  223. package/tests/fixtures/atlassian-case-capsule/invalid/18-unknown-tool-fails-closed.json +8 -0
  224. package/tests/fixtures/atlassian-case-capsule/invalid/19-write-at-read-tier.json +25 -0
  225. package/tests/fixtures/atlassian-case-capsule/invalid/20-high-risk-at-t3.json +19 -0
  226. package/tests/fixtures/atlassian-case-capsule/invalid/21-t4-single-approver.json +13 -0
  227. package/tests/fixtures/atlassian-case-capsule/invalid/22-t4-requester-self-approval.json +8 -0
  228. package/tests/fixtures/atlassian-case-capsule/invalid/23-cross-tenant-target.json +8 -0
  229. package/tests/fixtures/atlassian-case-capsule/invalid/24-bulk-jql-write.json +9 -0
  230. package/tests/fixtures/atlassian-case-capsule/invalid/25-bulk-wildcard-write.json +8 -0
  231. package/tests/fixtures/atlassian-case-capsule/invalid/26-circular-delegation.json +8 -0
  232. package/tests/fixtures/atlassian-case-capsule/invalid/27-delegation-depth-exceeded.json +8 -0
  233. package/tests/fixtures/atlassian-case-capsule/invalid/28-chain-does-not-end-at-origin.json +8 -0
  234. package/tests/fixtures/atlassian-case-capsule/invalid/29-fabricated-completion.json +8 -0
  235. package/tests/fixtures/atlassian-case-capsule/invalid/30-stale-proposal-not-expired.json +8 -0
  236. package/tests/fixtures/atlassian-case-capsule/invalid/31-agent-as-decision-owner.json +8 -0
  237. package/tests/fixtures/atlassian-case-capsule/invalid/32-credential-in-context.json +8 -0
  238. package/tests/fixtures/atlassian-case-capsule/invalid/33-instructions-labeled-trusted.json +9 -0
  239. package/tests/fixtures/atlassian-case-capsule/invalid/34-unknown-field-token.json +8 -0
  240. package/tests/fixtures/atlassian-case-capsule/invalid/35-unbounded-budget.json +8 -0
  241. package/tests/fixtures/atlassian-case-capsule/invalid/36-empty-do-not-do.json +8 -0
  242. package/tests/fixtures/atlassian-case-capsule/invalid/37-dual-requester-whitespace-is-schema.json +8 -0
  243. package/tests/fixtures/atlassian-case-capsule/invalid/38-dual-same-human-by-case.json +8 -0
  244. package/tests/fixtures/atlassian-case-capsule/invalid/39-dual-requester-by-case.json +8 -0
  245. package/tests/fixtures/atlassian-case-capsule/invalid/40-agent-id-labelled-human-approver.json +8 -0
  246. package/tests/fixtures/atlassian-case-capsule/invalid/41-service-account-requests-write.json +8 -0
  247. package/tests/fixtures/atlassian-case-capsule/invalid/42-comment-relabelled-user-supplied.json +8 -0
  248. package/tests/fixtures/atlassian-case-capsule/invalid/43-approval-locator-is-comment-case-variant.json +8 -0
  249. package/tests/fixtures/atlassian-case-capsule/invalid/44-approval-locator-is-tenant-url.json +8 -0
  250. package/tests/fixtures/atlassian-case-capsule/invalid/45-approval-locator-typed-but-comment.json +8 -0
  251. package/tests/fixtures/atlassian-case-capsule/invalid/46-bare-jql-write-target.json +9 -0
  252. package/tests/fixtures/atlassian-case-capsule/invalid/47-filter-write-target.json +9 -0
  253. package/tests/fixtures/atlassian-case-capsule/invalid/48-range-write-target.json +9 -0
  254. package/tests/fixtures/atlassian-case-capsule/invalid/49-t4-capsule-to-analysis-agent.json +8 -0
  255. package/tests/fixtures/atlassian-case-capsule/invalid/50-non-board-origin.json +11 -0
  256. package/tests/fixtures/atlassian-case-capsule/invalid/51-impossible-calendar-expiry.json +8 -0
  257. package/tests/fixtures/atlassian-case-capsule/invalid/52-unbounded-approval-lifetime.json +9 -0
  258. package/tests/fixtures/atlassian-case-capsule/invalid/53-t4-approval-over-8h.json +8 -0
  259. package/tests/fixtures/atlassian-case-capsule/invalid/54-completion-readback-wrong-target.json +8 -0
  260. package/tests/fixtures/atlassian-case-capsule/invalid/55-completion-readback-by-write-tool.json +8 -0
  261. package/tests/fixtures/atlassian-case-capsule/invalid/56-completion-readback-before-approval.json +8 -0
  262. package/tests/fixtures/atlassian-case-capsule/invalid/57-bearer-token-value.json +8 -0
  263. package/tests/fixtures/atlassian-case-capsule/invalid/59-secret-colon-form.json +10 -0
  264. package/tests/fixtures/atlassian-case-capsule/invalid/60-opaque-execute-read.json +8 -0
  265. package/tests/fixtures/atlassian-case-capsule/invalid/61-cross-tenant-url-in-target.json +8 -0
  266. package/tests/fixtures/atlassian-case-capsule/invalid/62-decision-owner-agent-uppercase.json +8 -0
  267. package/tests/fixtures/atlassian-case-capsule/invalid/63-decision-owner-agent-without-suffix.json +8 -0
  268. package/tests/fixtures/atlassian-case-capsule/invalid/64-budget-tool-calls-exceeded.json +8 -0
  269. package/tests/fixtures/atlassian-case-capsule/invalid/65-budget-review-rounds-exceeded.json +8 -0
  270. package/tests/fixtures/atlassian-case-capsule/invalid/66-approved-but-proposed-pending-elsewhere.json +8 -0
  271. package/tests/fixtures/atlassian-case-capsule/invalid/67-approval-locator-is-a-page.json +8 -0
  272. package/tests/fixtures/atlassian-case-capsule/invalid/68-approval-locator-is-plain-url.json +8 -0
  273. package/tests/fixtures/atlassian-case-capsule/invalid/69-approval-locator-free-text.json +8 -0
  274. package/tests/fixtures/atlassian-case-capsule/invalid/69-return-to-non-delegator.json +8 -0
  275. package/tests/fixtures/atlassian-case-capsule/invalid/70-delegate-back-into-chain.json +8 -0
  276. package/tests/fixtures/atlassian-case-capsule/invalid/71-completed-readback-after-expiry.json +10 -0
  277. package/tests/fixtures/atlassian-case-capsule/invalid/72-edit-whole-project.json +9 -0
  278. package/tests/fixtures/atlassian-case-capsule/invalid/73-archive-whole-space.json +8 -0
  279. package/tests/fixtures/atlassian-case-capsule/invalid/74-lookalike-tenant-host.json +8 -0
  280. package/tests/fixtures/atlassian-case-capsule/invalid/75-foreign-url-host.json +8 -0
  281. package/tests/fixtures/atlassian-case-capsule/invalid/76-password-with-value.json +10 -0
  282. package/tests/fixtures/atlassian-case-capsule/invalid/77-readback-by-discover.json +9 -0
  283. package/tests/fixtures/atlassian-case-capsule/invalid/78-readback-by-other-product-tool.json +9 -0
  284. package/tests/fixtures/atlassian-case-capsule/invalid/79-readback-verifies-unknown-write.json +8 -0
  285. package/tests/fixtures/atlassian-case-capsule/invalid/80-completed-mixed-before-after-expiry.json +9 -0
  286. package/tests/fixtures/atlassian-case-capsule/invalid/81-completed-read-only-with-stray-readback.json +16 -0
  287. package/tests/fixtures/atlassian-case-capsule/invalid/82-two-creates-one-readback.json +20 -0
  288. package/tests/fixtures/atlassian-case-capsule/invalid/83-duplicate-op-id.json +8 -0
  289. package/tests/fixtures/atlassian-case-capsule/invalid/84-userinfo-host-spoof.json +8 -0
  290. package/tests/fixtures/atlassian-case-capsule/invalid/85-userinfo-on-real-site.json +8 -0
  291. package/tests/fixtures/atlassian-case-capsule/invalid/86-bare-lookalike-host.json +8 -0
  292. package/tests/fixtures/atlassian-case-capsule/invalid/87-agent-id-labelled-human-requester.json +8 -0
  293. package/tests/fixtures/atlassian-case-capsule/invalid/88-create-readback-other-project.json +9 -0
  294. package/tests/fixtures/atlassian-case-capsule/invalid/89-create-readback-wrong-type.json +10 -0
  295. package/tests/fixtures/atlassian-case-capsule/invalid/90-bare-foreign-host.json +8 -0
  296. package/tests/fixtures/atlassian-case-capsule/invalid/91-foreign-url-inside-jql.json +8 -0
  297. package/tests/fixtures/atlassian-case-capsule/valid/01-t1-read-incident-review.json +114 -0
  298. package/tests/fixtures/atlassian-case-capsule/valid/02-t3-create-remediation.json +122 -0
  299. package/tests/fixtures/atlassian-case-capsule/valid/03-t4-archive-superseded-runbook.json +97 -0
  300. package/tests/fixtures/atlassian-case-capsule/valid/04-t3-completed-with-readback.json +149 -0
  301. package/tests/fixtures/atlassian-case-capsule/valid/05-t1-injection-flagged-as-untrusted.json +123 -0
  302. package/tests/fixtures/atlassian-case-capsule/valid/06-t3-proposed-awaiting-approval.json +114 -0
  303. package/tests/fixtures/atlassian-case-capsule/valid/07-t3-no-go-rejected-record.json +114 -0
  304. package/tests/fixtures/atlassian-case-capsule/valid/08-t3-expired-record.json +122 -0
  305. package/tests/fixtures/atlassian-case-capsule/valid/09-t3-completed-return-to-delegator.json +150 -0
  306. package/tests/fixtures/atlassian-case-capsule/valid/10-t3-safety-prose-and-atlassian-named-owner.json +123 -0
  307. package/tests/fixtures/atlassian-case-capsule/valid/11-t1-completed-read-only-review.json +115 -0
  308. package/tests/fixtures/atlassian-case-capsule/valid/12-t1-query-with-dotted-literals.json +114 -0
  309. package/tests/fixtures/atlassian-maestro-routing/expected/01-happy-incident-prevention.json +6 -0
  310. package/tests/fixtures/atlassian-maestro-routing/expected/02-happy-control-evidence.json +6 -0
  311. package/tests/fixtures/atlassian-maestro-routing/expected/03-happy-knowledge-integrity.json +6 -0
  312. package/tests/fixtures/atlassian-maestro-routing/expected/04-happy-adr-superseded.json +6 -0
  313. package/tests/fixtures/atlassian-maestro-routing/expected/05-happy-ai-cost.json +6 -0
  314. package/tests/fixtures/atlassian-maestro-routing/expected/06-cross-incident-knowledge.json +7 -0
  315. package/tests/fixtures/atlassian-maestro-routing/expected/07-cross-audit-incident.json +7 -0
  316. package/tests/fixtures/atlassian-maestro-routing/expected/08-gate-create-and-publish.json +6 -0
  317. package/tests/fixtures/atlassian-maestro-routing/expected/09-adv-injection-in-comment.json +6 -0
  318. package/tests/fixtures/atlassian-maestro-routing/expected/10-adv-prohibited-approval.json +6 -0
  319. package/tests/fixtures/atlassian-maestro-routing/expected/11-adv-bulk-delete.json +6 -0
  320. package/tests/fixtures/atlassian-maestro-routing/expected/12-adv-restriction-change.json +6 -0
  321. package/tests/fixtures/atlassian-maestro-routing/expected/13-ambiguous-help.json +4 -0
  322. package/tests/fixtures/atlassian-maestro-routing/expected/14-unsupported-delivery-bottleneck.json +4 -0
  323. package/tests/fixtures/atlassian-maestro-routing/expected/15-direct-authoring-no-specialist.json +4 -0
  324. package/tests/fixtures/atlassian-maestro-routing/expected/16-draft-only-must-not-gate.json +6 -0
  325. package/tests/fixtures/atlassian-maestro-routing/expected/17-adv-restriction-change-no-product-word.json +6 -0
  326. package/tests/fixtures/atlassian-maestro-routing/expected/18-adv-permission-grant.json +6 -0
  327. package/tests/fixtures/atlassian-maestro-routing/expected/19-adv-alert-acknowledge.json +6 -0
  328. package/tests/fixtures/atlassian-maestro-routing/expected/20-adv-purge-without-product-word.json +6 -0
  329. package/tests/fixtures/atlassian-maestro-routing/expected/21-adv-space-ai-instructions.json +6 -0
  330. package/tests/fixtures/atlassian-maestro-routing/expected/22-adv-injection-by-issue-key.json +6 -0
  331. package/tests/fixtures/atlassian-maestro-routing/expected/23-negated-write-does-not-gate.json +6 -0
  332. package/tests/fixtures/atlassian-maestro-routing/expected/24-noun-change-request-not-a-write.json +6 -0
  333. package/tests/fixtures/atlassian-maestro-routing/expected/25-comment-on-whether-not-a-write.json +6 -0
  334. package/tests/fixtures/atlassian-maestro-routing/expected/26-requested-update-gates.json +6 -0
  335. package/tests/fixtures/atlassian-maestro-routing/inputs/01-happy-incident-prevention.json +7 -0
  336. package/tests/fixtures/atlassian-maestro-routing/inputs/02-happy-control-evidence.json +7 -0
  337. package/tests/fixtures/atlassian-maestro-routing/inputs/03-happy-knowledge-integrity.json +7 -0
  338. package/tests/fixtures/atlassian-maestro-routing/inputs/04-happy-adr-superseded.json +7 -0
  339. package/tests/fixtures/atlassian-maestro-routing/inputs/05-happy-ai-cost.json +8 -0
  340. package/tests/fixtures/atlassian-maestro-routing/inputs/06-cross-incident-knowledge.json +7 -0
  341. package/tests/fixtures/atlassian-maestro-routing/inputs/07-cross-audit-incident.json +7 -0
  342. package/tests/fixtures/atlassian-maestro-routing/inputs/08-gate-create-and-publish.json +7 -0
  343. package/tests/fixtures/atlassian-maestro-routing/inputs/09-adv-injection-in-comment.json +8 -0
  344. package/tests/fixtures/atlassian-maestro-routing/inputs/10-adv-prohibited-approval.json +8 -0
  345. package/tests/fixtures/atlassian-maestro-routing/inputs/11-adv-bulk-delete.json +8 -0
  346. package/tests/fixtures/atlassian-maestro-routing/inputs/12-adv-restriction-change.json +8 -0
  347. package/tests/fixtures/atlassian-maestro-routing/inputs/13-ambiguous-help.json +7 -0
  348. package/tests/fixtures/atlassian-maestro-routing/inputs/14-unsupported-delivery-bottleneck.json +7 -0
  349. package/tests/fixtures/atlassian-maestro-routing/inputs/15-direct-authoring-no-specialist.json +7 -0
  350. package/tests/fixtures/atlassian-maestro-routing/inputs/16-draft-only-must-not-gate.json +7 -0
  351. package/tests/fixtures/atlassian-maestro-routing/inputs/17-adv-restriction-change-no-product-word.json +8 -0
  352. package/tests/fixtures/atlassian-maestro-routing/inputs/18-adv-permission-grant.json +8 -0
  353. package/tests/fixtures/atlassian-maestro-routing/inputs/19-adv-alert-acknowledge.json +8 -0
  354. package/tests/fixtures/atlassian-maestro-routing/inputs/20-adv-purge-without-product-word.json +8 -0
  355. package/tests/fixtures/atlassian-maestro-routing/inputs/21-adv-space-ai-instructions.json +8 -0
  356. package/tests/fixtures/atlassian-maestro-routing/inputs/22-adv-injection-by-issue-key.json +8 -0
  357. package/tests/fixtures/atlassian-maestro-routing/inputs/23-negated-write-does-not-gate.json +7 -0
  358. package/tests/fixtures/atlassian-maestro-routing/inputs/24-noun-change-request-not-a-write.json +8 -0
  359. package/tests/fixtures/atlassian-maestro-routing/inputs/25-comment-on-whether-not-a-write.json +8 -0
  360. package/tests/fixtures/atlassian-maestro-routing/inputs/26-requested-update-gates.json +7 -0
  361. package/tests/fixtures/atlassian-maestro-routing/taxonomy.json +68 -0
  362. package/tests/validate-atlassian-case-capsule.py +24 -0
  363. package/tests/validate-catalog.py +1 -0
  364. package/tests/validate-skill-references.py +5 -1
@@ -0,0 +1,70 @@
1
+ # Fictional worked example: checklist status filter
2
+
3
+ This example is an authoring fixture. The application, data, and brief below are fictional. No repository, Jira project, or running implementation has been inspected.
4
+
5
+ ## Synthetic input brief
6
+
7
+ Add a status filter to a checklist that currently displays all items. Offer **All**, **Open**, and **Completed**. The initial selection is **All**. Open shows incomplete items; Completed shows completed items. Preserve the original relative order of visible items. Switching filters must not change an item's text, completion flag, or stored position. When a selected filter has no matches, show “No matching items.” Persisting the filter selection and changing how items are completed are outside this request.
8
+
9
+ Use this supplied fixture in its listed order:
10
+
11
+ | ID | Text | Completed |
12
+ |---|---|---|
13
+ | item-1 | Pack charger | false |
14
+ | item-2 | Book train | true |
15
+ | item-3 | Pack coat | false |
16
+
17
+ ## Completed ticket draft
18
+
19
+ ### Add a status filter to the checklist
20
+
21
+ **Content pattern:** Implementation.
22
+ **Configured Jira work type:** Unresolved; no Jira project was supplied.
23
+ **Authoring readiness:** Needs clarification — the behavior specification is complete, but the actual repository and execution target are unresolved.
24
+ **Jira workflow status:** Unspecified.
25
+
26
+ ### Outcome and reason
27
+
28
+ Let checklist users view all, open, or completed items so they can focus on the items relevant to them. Filtering changes which items are visible while preserving the checklist data.
29
+
30
+ ### Facts and open decisions
31
+
32
+ - **Verified source facts:** The synthetic input brief specifies the three options, initial selection, membership rules, order preservation, nonmutation requirement, and empty-state copy. These are verified requirements of this fixture, not observations of an implemented application.
33
+ - **Reported facts:** The brief says the current checklist displays all items; no running application was inspected.
34
+ - **Assumptions:** None needed for the specified filtering behavior.
35
+ - **Questions:** The target repository, existing interface conventions, and configured Jira work type are not supplied. They must be established before taking action in a real project.
36
+
37
+ ### Scope
38
+
39
+ - **In scope:** Filter selection, visible membership, relative ordering, unchanged underlying item data, and the stated empty state.
40
+ - **Out of scope:** Persisting the selected filter, changing completion behavior, and reordering stored items.
41
+ - **Implementation context:** No repository or existing test command is asserted. Apply the actual project's conventions when that context is provided.
42
+
43
+ ### Acceptance criteria
44
+
45
+ 1. **AC-01 — Initial view:** With the supplied fixture, the initial selected option is All, and the visible IDs are item-1, item-2, item-3 in that order.
46
+ 2. **AC-02 — Membership and order:** Selecting Open shows item-1 and item-3 in that order. Selecting Completed shows only item-2. Selecting All again restores all three visible items in their original order.
47
+ 3. **AC-03 — Negative case: no data mutation:** After switching from All to Open to Completed to All, each item's text, completion flag, and stored position equal their values before the switches.
48
+ 4. **AC-04 — Empty match set:** With a fixture containing only item-1 and item-3, selecting Completed shows “No matching items.” and no item rows. Switching to All shows both items in their original order.
49
+
50
+ ### Criterion-to-verification mapping
51
+
52
+ These are planned checks. They do not assert that tests exist or have passed.
53
+
54
+ | Criterion | Planned check and fixture | Pass condition | Evidence to retain | Evidence status |
55
+ |---|---|---|---|---|
56
+ | AC-01 | Initialize the checklist with the three-item fixture; inspect selection and visible IDs. | All selected; visible IDs exactly item-1, item-2, item-3. | Observed selection and ordered IDs. | Not run |
57
+ | AC-02 | Select Open, Completed, and All in sequence using the three-item fixture. | Each visible ID sequence matches AC-02 exactly. | Selection-to-visible-ID results. | Not run |
58
+ | AC-03 | Snapshot the three items before the selection sequence and compare the underlying data afterward. | Text, completion flags, and stored positions are unchanged for every item. | Before/after comparison result. | Not run |
59
+ | AC-04 | Initialize with item-1 and item-3 only; select Completed, then All. | Exact empty-state copy with zero rows, followed by item-1 and item-3 in order. | Empty-state observation and restored visible IDs. | Not run |
60
+
61
+ ### Dependencies and handoff
62
+
63
+ No cross-ticket dependency is specified in the synthetic brief. Before real execution, identify the target repository and inspect its interface and verification conventions. This example does not identify or create a parent issue, dependency link, or Jira status transition.
64
+
65
+ ### Completion evidence
66
+
67
+ - **Changes delivered:** None; this is a ticket draft.
68
+ - **Verification results:** Not run for AC-01 through AC-04.
69
+ - **Implementation artifacts:** None.
70
+ - **Remaining uncertainty:** Real project context is absent. No claim is made about implementation, test success, deployment, or external publication.
@@ -0,0 +1,87 @@
1
+ # Synthetic worked example: invoice retries within an agreed idempotency contract
2
+
3
+ > **EXPLICITLY SYNTHETIC.** Every product decision, interface, fixture, and failure scenario below is hypothetical and exists only to demonstrate a good ticket. No real system was inspected. No code was implemented. All tests are **NOT RUN**. The fictional mini brief is the sole requirements source; it is not evidence of actual behavior.
4
+
5
+ ## Fictional mini brief — source S1
6
+
7
+ A hypothetical invoice API has a creation operation and an authenticated tenant identity. Its accepted creation request contains exactly `customer_ref` (a string), `amount_minor` (a positive integer), and `currency` (an uppercase three-letter string). Existing validation remains in force. A valid `Idempotency-Key` is an opaque, case-sensitive string.
8
+
9
+ For this illustration, the hypothetical product decisions are:
10
+
11
+ 1. An idempotent operation is identified by **authenticated tenant identity + Idempotency-Key**. Tenants may reuse the same key independently. Client-supplied tenant fields cannot replace the authenticated identity.
12
+ 2. The canonical fingerprint compares the validated tuple `(customer_ref, amount_minor, currency)`: string values compare exactly; the amount compares as an integer. JSON whitespace and field order do not affect equality. Changing any tuple value changes the fingerprint. This defines the behavior without choosing a storage hash or schema.
13
+ 3. The first successful creation returns HTTP `201` with its invoice response. A completed retry with the same scoped key and fingerprint replays the original HTTP status, JSON response body, and Content-Type; it creates no additional invoice. Transport metadata such as Date and request IDs is outside the replay contract.
14
+ 4. Reusing an unexpired scoped key with a different fingerprint returns HTTP `409` and changes neither the original invoice nor the stored result. No replacement invoice is created.
15
+ 5. While one request owns an active claim for a scoped key, any concurrent request for that scoped key returns HTTP `409` without creating an invoice. After the successful commit, a matching retry follows the completed-replay rule. Different tenants remain independent.
16
+ 6. The completed record remains valid for **24 hours from the successful atomic commit**, using the authoritative service time. A retry received before expiry replays; at or after expiry it may start a new operation and create another invoice. An active claim cannot expire into a second concurrent owner.
17
+ 7. Claim ownership, invoice creation, and the replayable success result have one atomic success boundary: a successful commit contains the invoice and completed result together. Failure before commit leaves no committed invoice or stale claim that prevents a subsequent valid attempt. Failure after commit but before delivery leaves a replayable result. How the target stack enforces these properties requires repository evidence.
18
+ 8. This example changes valid keyed creation requests only. In the fictional baseline, invalid bodies or invalid supplied keys are rejected before invoice creation or successful replay storage; preserve that behavior. Requests without a key follow the existing non-idempotent creation contract, which is also unchanged. Historical duplicate repair, payments, invoice cancellation, and a new client retry policy are excluded.
19
+
20
+ ## Ticket: prevent additional invoices from valid retries of one scoped operation
21
+
22
+ - **Type:** Bug
23
+ - **Readiness assessment (not Jira status):** Draft — the hypothetical business contract is specified; real target context, reproduction evidence, implementation feasibility, and verification commands are unknown.
24
+ - **Owner:** TBD
25
+ - **Target context:** Fictional invoice service only. Real repository, revision, environment, and relevant files: **Unknown**.
26
+
27
+ ### Business outcome and impact
28
+
29
+ Allow a tenant to retry a creation request after a lost response without creating an additional invoice within the agreed retention window.
30
+
31
+ - **Confirmed real impact:** None established; no actual evidence was supplied.
32
+ - **Hypothetical reported impact:** A request times out after the service may have committed an invoice; a retry reportedly creates another invoice.
33
+ - **Suspected mechanism:** Two attempts may cross the invoice-creation boundary without a shared enforced claim. This is an unverified hypothesis, not a root-cause finding.
34
+ - **Affected frequency, population, monetary impact, severity, and priority:** Unknown. Do not derive them from this example.
35
+
36
+ ### Sources and evidence limits
37
+
38
+ | Anchor | Source | What it establishes / limits |
39
+ | --- | --- | --- |
40
+ | S1 | Fictional mini brief above, decisions 1–8 | Hypothetical desired behavior; no observed implementation evidence. |
41
+ | S2 | Hypothetical report in the impact section | Illustrative symptom only; not a reproduction or measured impact. |
42
+ | V1–V7 | Proposed verification plan below | Expected proof to collect; every check is NOT RUN. |
43
+
44
+ ### Observed versus expected and sanitized reproduction plan
45
+
46
+ - **Reported observation:** In S2, a retry following an uncertain first response produces an additional invoice.
47
+ - **Expected:** S1 determines whether the request replays, conflicts, or becomes a new operation after expiry.
48
+ - **Reproduction state:** Not attempted. No real trace, log, environment, or failing test exists here.
49
+ - **Proposed safe setup:** An isolated fixture with two synthetic authenticated tenants, a valid request, a valid key, a controllable clock, a concurrency barrier, and controllable failures around the transaction boundary. Whether the real stack supports these mechanisms is Unknown.
50
+ - **Proposed steps:** Send one valid creation request; interrupt response delivery after its successful commit; retry the same request as the same tenant with the same key; compare responses and committed invoice count. This is a test plan, not an observed reproduction.
51
+ - **Expected reproduction evidence:** Sanitized request order, exact target/revision, captured first and replayed application responses, and a durable-state assertion. Actual evidence: **NOT RUN**.
52
+
53
+ ### Scope
54
+
55
+ - **In:** Valid keyed creation requests, authenticated tenant isolation, canonical equivalence/conflict, concurrent claims, the retention boundary, and failure recovery around the atomic success boundary.
56
+ - **Out:** Missing/invalid-key behavior changes, new validation rules, client retry policy, payments, cancellation, historical repair, and unrelated cleanup.
57
+ - **Implementation constraints:** Preserve the S1 behavior. Do not prescribe a database, file, lock mechanism, or migration until the actual target and its guarantees are inspected.
58
+
59
+ ### Acceptance criteria and expected verification
60
+
61
+ All criteria below express **hypothetical decisions from S1**, not claims about an existing API.
62
+
63
+ | AC ID | Observable pass condition | Method / expected proof | Actual result |
64
+ | --- | --- | --- | --- |
65
+ | AC-01 | Before expiry, a completed retry by the same tenant with the same key and canonical fingerprint returns the original 201 status, body, and Content-Type; the committed invoice count for that operation stays one. | **V1:** Sequential retry and lost-response replay tests capture the first result, compare the replay, and inspect durable state after each attempt. | NOT RUN |
66
+ | AC-02 | Two authenticated tenants using the same key remain independent. Neither receives the other's invoice or stored response. | **V2:** A two-tenant fixture proves independent creations and replays; inspect returned tenant ownership and stored scopes. | NOT RUN |
67
+ | AC-03 | JSON field order or whitespace changes replay the original result. Changing any fingerprint field under an unexpired scoped key returns 409 with no mutation to the invoice or stored result. | **V3:** Table-driven equivalent/conflicting-payload checks cover each tuple field and compare durable state before/after conflicts. | NOT RUN |
68
+ | AC-04 | With the first request held after acquiring its claim and before commit, concurrent requests for the same scoped key return 409 and create nothing. Releasing the first request produces one committed invoice; a subsequent matching retry replays it. | **V4:** A deterministic barrier holds the winner in flight. Contenders must complete with 409 before release. After release, assert exactly one invoice and one replayable result. | NOT RUN |
69
+ | AC-05 | A request immediately before the 24-hour expiry replays. At the expiry boundary a request can create a new operation. Concurrent attempts at expiry still permit only one active owner for that scoped key. | **V5:** Use a controlled authoritative clock around the precise boundary and a concurrency barrier during expired-record turnover; inspect responses and committed operations. | NOT RUN |
70
+ | AC-06 | Failure before commit leaves neither a committed invoice nor a stale blocking claim. Successful commit persists invoice and replayable result together. Losing delivery after commit does not permit a second invoice. | **V6:** Inject failure after claim acquisition, after invoice write but before commit, and after commit but before delivery. Restart/retry as supported by the confirmed stack; inspect durable state and replay behavior. These checks must establish the atomic claim/commit property, not only successful sequential retries. | NOT RUN |
71
+ | AC-07 | Existing validation and missing/invalid-key behavior are unchanged. Invalid requests do not create an invoice or a successful replay record. | **V7:** Run the confirmed existing contract checks plus targeted invalid-request cases, comparing against the evidenced baseline. | NOT RUN |
72
+
73
+ ### Unknowns and blockers before implementation handoff
74
+
75
+ | Unknown | Why it blocks readiness | Required next evidence / decision |
76
+ | --- | --- | --- |
77
+ | Actual target, revision, interfaces, and authenticated tenant source | Prevents locating the change and verifying isolation. | Confirm the target and inspect its current contracts. Owner: TBD. |
78
+ | A real reproduction or other sufficient defect proof | S2 is fictional; it establishes no real bug. | Obtain a sanitized failing trace/test or other agreed evidence. Owner: TBD. |
79
+ | Transaction, claim, recovery, and persistence guarantees | A plausible idempotency design can still fail under concurrency or crashes. | Inspect the implementation boundary and demonstrate a feasible approach against V4–V6. Owner: TBD. |
80
+ | Existing validation baseline and test harness | Commands, fixtures, fault hooks, and expected unchanged behavior cannot be guessed. | Locate known checks and establish their applicability at the confirmed revision. Owner: TBD. |
81
+ | Review and execution ownership | No real team or reviewer was identified. | Confirm the appropriate owners before assignment. Owner: TBD. |
82
+
83
+ ### Handoff and definition of done
84
+
85
+ The ticket remains **Draft / Needs discovery** until the real prerequisites above are resolved. The next handoff is for target confirmation and bounded evidence gathering; no implementation is authorized by this example.
86
+
87
+ For a subsequent implementation ticket, preserve AC-01 through AC-07, record the delivered artifact/revision, map actual results to V1–V7, and request human review of the tenant boundary and atomicity proof. A sequential happy-path test cannot satisfy AC-04 or AC-06. `NOT RUN` never becomes `PASS` because the design looks reasonable.
@@ -0,0 +1,84 @@
1
+ # Worked example: a sparse duplicate-invoice report
2
+
3
+ ## Supplied brief — source S1
4
+
5
+ > “Retry causes duplicate invoices.”
6
+
7
+ This is the only supplied information. It is a user report, not a verified reproduction. The ticket below is an original drafting example; no system was inspected, no implementation was performed, and all verification is **NOT RUN**.
8
+
9
+ ## Triage result
10
+
11
+ Draft a bounded discovery spike. An implementation bug is **not ready**: the report does not identify the system, the operation's business identity, the tenant boundary, the intended retry contract, or proof of the failure. Do not import a 24-hour window, an Idempotency-Key, HTTP 409, a database design, or other decisions from a different example.
12
+
13
+ ## Ticket: establish the failure and intended retry behavior for invoice creation
14
+
15
+ - **Type:** Spike
16
+ - **Readiness assessment (not Jira status):** Draft — the research question is clear; exact target, evidence access, investigation budget, and decision ownership remain unresolved. Initial clarification can proceed; system investigation awaits a confirmed boundary.
17
+ - **Owner:** TBD
18
+ - **Target context / revision / environment:** Unknown — not supplied.
19
+ - **Decision recipient:** TBD
20
+
21
+ ### Business outcome and research question
22
+
23
+ Establish enough evidence and an agreed contract to scope a change that prevents unintended additional invoices during retries.
24
+
25
+ **Question:** Under which conditions does a retry create an unintended additional invoice, and which observable behavior should the identified operation provide instead?
26
+
27
+ ### Evidence and limits
28
+
29
+ | Anchor | Evidence | Established / unestablished |
30
+ | --- | --- | --- |
31
+ | S1 | The exact supplied brief above | Establishes that a user reports duplication associated with retrying. It does not prove cause, occurrence rate, financial impact, or the intended contract. |
32
+
33
+ - **Confirmed impact:** The report exists; no actual affected invoice, customer, or financial effect is confirmed.
34
+ - **Suspected impact:** Unintended invoice records may confuse users or downstream processing. Whether money moved is Unknown and must not be inferred.
35
+ - **Observed versus expected:** Observed behavior is reported only. Expected retry behavior and whether the two invoices represent the same business operation are Unknown.
36
+ - **Root cause:** Unknown. Missing idempotency, client behavior, concurrent processing, and repeated distinct business requests are possibilities to distinguish, not findings.
37
+
38
+ ### Questions that determine implementation scope
39
+
40
+ | Question | Why it matters | Decision / evidence owner |
41
+ | --- | --- | --- |
42
+ | Which product/service, operation, environment, and revision are involved? | Establishes the exact target and applicable behavior. | TBD |
43
+ | What sanitized sequence reproduces the issue, including the first response or timeout and both resulting records? | Separates a reported symptom from a demonstrated failure. | TBD |
44
+ | What identifies one business operation, and what should happen for a repeat, a changed payload, and simultaneous requests? | Defines success and conflict behavior without inventing rules. | TBD |
45
+ | How is tenant/account identity established, and where must duplicate detection be scoped? | Prevents cross-tenant collisions or disclosure. | TBD |
46
+ | Is reuse ever allowed, and is there an agreed retention/expiry rule? | Determines which repeats are intentional new work. | TBD |
47
+ | What survives a timeout or crash, and what are the confirmed side effects? | Establishes transaction and recovery boundaries, including any downstream effects. | TBD |
48
+ | Who can confirm the business contract, and what investigation budget is available? | Provides a bounded decision path without a fabricated deadline. | TBD |
49
+
50
+ ### Bounded investigation plan
51
+
52
+ - **In:** Obtain the missing target and sanitized report; inspect permitted existing contracts and evidence; attempt a safe reproduction if an approved environment is available; locate the failure boundary; document options and their limits.
53
+ - **Out:** Code changes, live operations, historical data repair, selecting an unconfirmed idempotency contract, and implementing a proposed fix.
54
+ - **Budget:** Unknown — agree an effort cap before investigation. No deadline or estimate has been supplied.
55
+ - **Stopping rule:** Stop once the agreed question is answered or the agreed cap is reached. Deliver an evidence-backed conclusion or an explicit inconclusive result, with unresolved questions and their impact on implementation readiness.
56
+ - **Dependencies / blockers:** Exact target and permitted evidence access; safe reproduction context; budget; a recipient for business decisions. Owners: TBD.
57
+
58
+ ### Discovery acceptance and verification
59
+
60
+ These criteria accept an investigation deliverable. They do not silently accept the eventual implementation.
61
+
62
+ | AC ID | Observable discovery deliverable | Verification method and expected evidence | Actual result |
63
+ | --- | --- | --- | --- |
64
+ | AC-01 | The report is reproduced in the confirmed safe context, or the bounded attempt is documented as inconclusive with its limits. | Review sanitized preconditions, exact revision/environment, action order, observed results, expected-behavior source, and evidence locations. If not attempted, state why. | NOT RUN |
65
+ | AC-02 | A decision record defines the operation identity, tenant boundary, repeated/changed/concurrent-request behavior, and any retention rule, or marks each unresolved rule as an implementation blocker. | Review confirmed decisions with their sources and decision owners; unresolved answers must remain Unknown rather than assumed defaults. | NOT RUN |
66
+ | AC-03 | Findings distinguish demonstrated failure mechanisms from hypotheses and compare bounded options against the confirmed contract. | Review source-linked observations, contrary evidence, limitations, and checks still needed. Do not accept a code-location guess as root-cause proof. | NOT RUN |
67
+ | AC-04 | The handoff recommends separately scoped follow-up work and explicitly assesses its readiness. | Review the discovery artifact and proposed child scopes. A ready implementation ticket requires the gate below; otherwise hand off unresolved questions or another bounded discovery step. | NOT RUN |
68
+
69
+ ### Gate for a separate implementation ticket
70
+
71
+ An implementation ticket may be drafted after discovery, but assess it **Ready for implementation** only when all material items are resolved:
72
+
73
+ - The exact target/revision and the actual defect are supported by evidence.
74
+ - The business operation, tenant boundary, retry/concurrency/expiry behavior, and relevant side effects have an agreed contract.
75
+ - The proposed work has bounded in/out scope, known dependencies, and stable implementation AC IDs mapped to feasible verification methods and expected proof.
76
+ - Required decisions and target access are resolved; ownership and review arrangements are recorded honestly.
77
+
78
+ If discovery is inconclusive, it may still produce a useful completed decision brief. The unresolved implementation remains **Needs discovery**. Do not combine “investigate and implement the correct fix” into one ready ticket.
79
+
80
+ ### Handoff and definition of done
81
+
82
+ Deliver the sourced investigation record, the decision table, the consumed budget if known, and proposed follow-up tickets to the confirmed human reviewer (currently TBD). Record actual evidence against AC-01 through AC-04. Unknown answers may be legitimate discovery results, but they stay visible as blockers where material.
83
+
84
+ **Current handoff:** Draft discovery scope only. Artifact/revision for an investigation result: Unknown. Human review: PENDING. Implementation: not performed. All checks: **NOT RUN**.
@@ -0,0 +1,8 @@
1
+ <svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
2
+ <path d="M19.58 4.38996C18.05 2.86996 15.68 2.88996 14.18 4.38996L5.26999 13.33C4.25999 14.34 3.84999 14.92 3.59999 16.26L3.06999 19.56C2.88999 20.47 3.50999 21.09 4.43999 20.93L7.74999 20.39C9.06999 20.18 9.64999 19.76 10.66 18.75L19.58 9.82996C21.1 8.30996 21.12 5.93996 19.58 4.40996V4.38996Z" fill="#FEBD08"/>
3
+ <path d="M19.58 9.81997C21.1 8.29997 21.12 5.92997 19.58 4.39997C18.05 2.87997 15.68 2.89997 14.18 4.39997L13.77 4.80997L19.18 10.22L19.58 9.81997Z" fill="#FF928C"/>
4
+ <path d="M13.7694 4.81308L12.3552 6.22729L17.7646 11.6367L19.1788 10.2224L13.7694 4.81308Z" fill="#D9D9D9"/>
5
+ <path opacity="0.5" d="M12.36 6.22998L5.26998 13.34C4.25998 14.35 3.84998 14.93 3.59998 16.27L3.06998 19.57C2.97998 20.02 3.08998 20.4 3.32998 20.65L15.05 8.92998L12.36 6.22998Z" fill="white"/>
6
+ <path d="M4.60001 14.05C4.06001 14.69 3.79001 15.27 3.60001 16.26L3.51001 16.81L7.18001 20.48L7.75001 20.39C8.74001 20.23 9.31001 19.96 9.95001 19.41L4.60001 14.05Z" fill="#FFDDBC"/>
7
+ <path d="M3.50999 16.8101L3.06999 19.5601C2.88999 20.4701 3.50999 21.0901 4.43999 20.9301L7.17999 20.4801L3.50999 16.8101Z" fill="#4D4D4D"/>
8
+ </svg>
@@ -0,0 +1,49 @@
1
+ # Handoff: {{ticket_title_or_confirmed_issue_key}}
2
+
3
+ > Record what exists, what was checked, and what remains. Use `Unknown — {{question}}` when evidence is missing, `TBD` for an unconfirmed owner, and `N/A — {{reason}}` when appropriate. Copy AC IDs exactly from the source ticket. Do not convert a plan into claimed implementation or test results.
4
+
5
+ - **Prepared by:** {{confirmed_human_or_agent_identifier_or_Unknown}}
6
+ - **Source ticket / agreed scope:** {{confirmed_link_or_source_anchor_and_revision_or_Unknown}}
7
+ - **Handoff assessment (not Jira status):** {{Draft_or_Ready_for_review_or_Blocked_with_reason}}
8
+ - **Next owner / reviewer:** {{confirmed_recipient_or_TBD}}
9
+
10
+ ## Intended outcome and delivered scope
11
+
12
+ - **Intended outcome:** {{agreed_business_or_user_result}}
13
+ - **Delivered:** {{actual_artifacts_or_work_completed_with_evidence_or_None}}
14
+ - **Scope deviations:** {{what_changed_from_the_agreement_why_and_decision_source_or_None}}
15
+
16
+ ## Artifact and revision
17
+
18
+ | Artifact | Exact location and revision | What it establishes / limits |
19
+ | --- | --- | --- |
20
+ | {{code_document_config_or_investigation_record}} | {{confirmed_path_link_revision_or_Unknown}} | {{actual_content_and_environment_limitations}} |
21
+
22
+ ## Acceptance criteria → verification → results
23
+
24
+ Use the actual command or review method only when known. Record the target/revision and environment with the evidence. Use `NOT RUN`, `PASS`, `FAIL`, `BLOCKED`, or `N/A — reason`; a command's existence is not proof that it ran or passed.
25
+
26
+ | AC ID from source | Test / review method | Expected evidence / result | Actual evidence location and result |
27
+ | --- | --- | --- | --- |
28
+ | AC-01 | {{actual_method_or_Unknown}} | {{agreed_assertion_and_output}} | NOT RUN |
29
+ | AC-02 | {{actual_method_or_Unknown}} | {{agreed_assertion_and_output}} | NOT RUN |
30
+ | AC-03 | {{actual_method_or_Unknown}} | {{agreed_assertion_and_output}} | NOT RUN |
31
+
32
+ ## Unresolved work and blockers
33
+
34
+ | Remaining work / unknown | Effect on acceptance or readiness | Next action | Owner |
35
+ | --- | --- | --- | --- |
36
+ | {{unmet_AC_missing_proof_or_material_question}} | {{blocking_or_nonblocking_with_reason}} | {{bounded_next_action}} | {{confirmed_owner_or_TBD}} |
37
+
38
+ **Risk / recovery information relevant to the handoff:** {{evidence_backed_limitations_or_NA_with_reason}}
39
+
40
+ ## Unrelated findings
41
+
42
+ {{separate_observations_outside_the_agreed_scope_with_evidence_and_proposed_follow_up_or_None; do_not_silently_expand_this_ticket}}
43
+
44
+ ## Human review and completion decision
45
+
46
+ - **Review requested:** {{specific_decisions_or_checks_for_confirmed_reviewer_or_TBD}}
47
+ - **Review outcome / evidence:** PENDING — {{record_only_after_review}}
48
+ - **Completion assessment:** {{incomplete_ready_for_review_or_complete_with_evidence}}. Required failed, blocked, or unrun checks and material unresolved rules/tenant boundaries/targets/proof prevent a completion claim.
49
+ - **Execution boundary:** {{state_whether_this_is_only_a_ticket_or_plan_handoff_or_an_evidenced_implementation_handoff}}. A ticket-authoring handoff must state that no implementation or live change was performed.
@@ -0,0 +1,62 @@
1
+ # {{observable_failure_in_a_specific_flow}}
2
+
3
+ <!-- Separate reports, observations, and hypotheses. Use `Unknown — {{question}}` for missing facts, `TBD` for an unconfirmed owner, and `N/A — {{reason}}` for inapplicable fields. Sanitize credentials, personal data, customer payloads, and logs. Keep AC IDs stable; do not invent a reproduction or test result. -->
4
+
5
+ <!-- Default authoring readiness to Draft until an evidence-backed assessment justifies another applicable verdict. -->
6
+
7
+ - **Content pattern:** Bug
8
+ - **Configured Jira work type:** {{AVAILABLE_PROJECT_WORK_TYPE_OR_UNRESOLVED}} — map this pattern to the target project configuration.
9
+ - **Jira workflow status:** {{KNOWN_CURRENT_STATUS_OR_UNSPECIFIED}} — separate from authoring readiness.
10
+ - **Authoring readiness (not Jira status):** {{DRAFT_OR_NEEDS_CLARIFICATION_OR_NEEDS_DECOMPOSITION_OR_READY_FOR_TRIAGE_OR_READY_FOR_IMPLEMENTATION}} — {{readiness_reason_and_material_gaps}}
11
+ - **Owner:** {{confirmed_owner_or_TBD}}
12
+ - **Target context:** {{confirmed_repository_service_revision_environment_or_Unknown}}
13
+
14
+ ## Business outcome and impact
15
+
16
+ {{which_user_or_business_process_should_recover_and_why}}
17
+
18
+ - **Confirmed impact:** {{evidence_backed_affected_behavior_population_and_extent_or_Unknown}}
19
+ - **Suspected impact:** {{unverified_risk_and_why_it_is_suspected_or_None}}
20
+ - **Severity / priority:** {{confirmed_value_and_basis_or_Unknown; do_not_infer_from_urgency_alone}}
21
+
22
+ ## Observed versus expected
23
+
24
+ - **Reported or observed:** {{failure_with_explicit_reported_or_independently_observed_label}}
25
+ - **Expected:** {{source_backed_contract_or_Unknown}}
26
+ - **Source anchors:** {{S1_request_or_spec_location; S2_sanitized_log_trace_test_or_artifact_location_and_revision}}
27
+
28
+ ## Sanitized reproduction
29
+
30
+ - **Reproduction state:** {{Not_attempted_or_Reproduced_or_Not_reproduced_with_evidence}}
31
+ - **Preconditions:** {{environment_version_test_identity_tenant_boundary_and_safe_fixture_or_Unknown}}
32
+ - **Steps:** {{minimal_ordered_actions_or_Unknown}}
33
+ - **Actual result:** {{observed_result_with_evidence_or_NOT_RUN}}
34
+ - **Expected result:** {{assertable_result_and_contract_source_or_Unknown}}
35
+ - **Evidence gaps:** {{missing_steps_artifacts_access_or_safe_fixture}}
36
+
37
+ ## Diagnosis boundary and unknowns
38
+
39
+ - **Established evidence:** {{facts_supported_by_the_anchors_above}}
40
+ - **Root-cause hypotheses:** {{explicitly_unverified_explanation_and_falsifying_check_or_Unknown}}
41
+ - **Material questions:** {{business_rules_tenant_scope_exact_target_and_proof_still_needed; decision_owner_or_TBD}}
42
+
43
+ ## Scope
44
+
45
+ - **In:** {{specific_failure_path_and_required_regression_coverage}}
46
+ - **Out:** {{unrelated_cleanup_new_features_historical_data_repair_or_other_exclusions}}
47
+
48
+ ## Acceptance and verification
49
+
50
+ | AC ID | Observable pass condition | Verification method and expected evidence | Actual evidence / result |
51
+ | --- | --- | --- | --- |
52
+ | AC-01 | Given {{confirmed_reproduction_preconditions}}, when {{trigger}}, then {{expected_behavior}}. | {{regression_check_showing_the_original_failure_and_corrected_result}} | NOT RUN |
53
+ | AC-02 | {{relevant_retry_concurrency_failure_or_boundary_case_preserves_the_contract}}. | {{method_fixture_and_expected_assertions}} | NOT RUN |
54
+ | AC-03 | {{adjacent_supported_behavior_and_tenant_or_permission_boundary_remain_correct}}. | {{compatibility_or_isolation_check_and_expected_artifact}} | NOT RUN |
55
+
56
+ ## Dependencies, handoff, and definition of done
57
+
58
+ - **Dependencies / blockers:** {{required_decisions_evidence_access_and_order_or_None_identified_with_limits}}
59
+ - Preserve an explicitly requested bug-report form. Mark the symptom as reported/unconfirmed and reproduction as Not attempted where applicable. Missing evidence blocks implementation readiness, not creation of the bug report. Record investigation as the next action; propose a separate bounded investigation only when useful, without replacing the requested report.
60
+ - Use **Ready for triage** when the report has enough context to route the next investigation. Keep implementation **Draft / Needs clarification** while material business rules, tenant/security boundaries, exact target, or required supporting proof are unresolved. Explain which activity is ready and which remains blocked.
61
+ - Hand off to {{executor_or_TBD}} only after readiness is justified. For triage completion, record the clarified symptom, evidence gaps, and next routing action. For implementation completion, provide the artifact/revision, AC-to-result evidence, any residual impact, and any review required by the existing project process (reviewer: {{known_reviewer_or_unassigned_if_required}}).
62
+ - The author drafts the ticket; they do not diagnose by changing code or live systems under this template.
@@ -0,0 +1,68 @@
1
+ # {{cross_ticket_business_outcome}}
2
+
3
+ <!-- An epic coordinates child work; it is not one executable agent assignment. Use `Unknown — {{question}}`, `TBD` for unconfirmed owners, and `N/A — {{reason}}` as appropriate. Use proposed child names until real issue keys exist. Do not invent ownership, releases, dates, or results. Keep AC IDs stable. -->
4
+
5
+ <!-- Default authoring readiness to Draft until an evidence-backed assessment justifies another applicable verdict. -->
6
+
7
+ - **Content pattern:** Epic
8
+ - **Configured Jira work type:** {{AVAILABLE_PROJECT_WORK_TYPE_OR_UNRESOLVED}} — map this pattern to the target project configuration.
9
+ - **Jira workflow status:** {{KNOWN_CURRENT_STATUS_OR_UNSPECIFIED}} — separate from authoring readiness.
10
+ - **Authoring readiness (not Jira status):** {{DRAFT_OR_NEEDS_DECOMPOSITION}} — {{decomposition_and_decision_gaps}}
11
+ - **Owner:** {{confirmed_epic_owner_or_TBD}}
12
+ - **Target context:** {{confirmed_products_repositories_services_revisions_or_Unknown}}
13
+
14
+ ## Business outcome
15
+
16
+ {{user_or_business_outcome_across_the_children_and_why_it_matters}}
17
+
18
+ **Success signal:** {{agreed_observable_outcome_and_source_or_Unknown}}
19
+
20
+ ## Evidence, scope, and unknowns
21
+
22
+ - **Source anchors:** {{S1_spec_or_request_location; other_exact_evidence_anchors}}
23
+ - **Confirmed rules:** {{business_compatibility_tenant_and_permission_contracts_with_sources}}
24
+ - **In:** {{bounded_capabilities_and_integrations}}
25
+ - **Out:** {{excluded_capabilities_migrations_or_operational_actions}}
26
+ - **Material unknowns / decision owners:** {{question_required_evidence_and_owner_or_TBD}}
27
+
28
+ ## Child breakdown and dependency order
29
+
30
+ Each child needs its own ticket, target/revision, owner, AC IDs, and readiness assessment. The labels below are local planning labels, not Jira issue keys.
31
+
32
+ | Child label / real issue link if supplied | Type and bounded outcome | Depends on | Owner | Readiness / blocker |
33
+ | --- | --- | --- | --- | --- |
34
+ | C1 — {{child_name}} | {{type_and_deliverable}} | {{None_or_prerequisite}} | {{owner_or_TBD}} | Draft — {{gap_or_evidence}} |
35
+ | C2 — {{child_name}} | {{type_and_deliverable}} | {{C1_or_other_confirmed_dependency}} | {{owner_or_TBD}} | Draft — {{gap_or_evidence}} |
36
+ | C3 — {{integration_or_validation_child}} | {{type_and_cross_ticket_result}} | {{required_children}} | {{owner_or_TBD}} | Draft — {{gap_or_evidence}} |
37
+
38
+ ## Cross-ticket contracts
39
+
40
+ | Producer → consumer | Shared interface / invariant | Source or decision needed | Integration proof expected |
41
+ | --- | --- | --- | --- |
42
+ | {{child_or_component}} → {{child_or_component}} | {{schema_behavior_versioning_tenant_boundary_or_ordering_contract}} | {{anchor_or_Unknown_with_decision_owner}} | {{cross_child_check_and_expected_artifact}} |
43
+
44
+ **Dependency order and parallel work:** {{which_children_must_finish_first_which_can_overlap_and_why}}
45
+
46
+ ### External dependency gates (when applicable)
47
+
48
+ | External item / verified reference | Responsible role / confirmed owner | Required input and evidence | Needed by: forecast or commitment / source | Affected children / consequence if blocked |
49
+ | --- | --- | --- | --- | --- |
50
+ | {{item_or_Unknown}} | {{role_or_TBD}} | {{input_and_observable_gate}} | {{date_type_and_authority_or_Unknown}} | {{child_labels_and_consequence}} |
51
+
52
+ Use evidence-backed commitments only; a proposed date or owner is not an agreement. Keep this table only when external coordination affects the children.
53
+
54
+ ## Epic acceptance and verification
55
+
56
+ | AC ID | Observable cross-ticket pass condition | Verification method and expected evidence | Actual evidence / result |
57
+ | --- | --- | --- | --- |
58
+ | AC-01 | {{end_to_end_business_outcome_is_met_across_named_children}}. | {{integrated_check_and_expected_output}} | NOT RUN |
59
+ | AC-02 | {{shared_contract_and_tenant_permission_or_compatibility_boundary_hold}}. | {{cross_component_contract_or_isolation_check}} | NOT RUN |
60
+ | AC-03 | {{required_handoffs_and_operational_ownership_are_resolved}}. | {{review_of_child_evidence_and_outstanding_blockers}} | NOT RUN |
61
+
62
+ ## Handoff and definition of done
63
+
64
+ - **Dependencies / blockers:** {{external_dependencies_and_unresolved_decisions_with_owner_or_TBD}}
65
+ - Use **Draft** or **Needs decomposition** for this coordination artifact and report readiness separately for each child; do not present the epic as one implementation assignment.
66
+ - Material business rules, tenant/security boundaries, exact targets, or required proof block the affected children from **Ready for implementation**. One child's readiness does not make its dependents ready.
67
+ - Completion requires child artifact/revision links, actual cross-ticket AC evidence, resolved or explicitly accepted remaining work, and any review required by the existing project process (reviewer: {{known_reviewer_or_unassigned_if_required}}). A list of closed child tickets alone is not outcome evidence.
68
+ - The author decomposes and drafts work; implementation and live operations require separately scoped authorization.
@@ -0,0 +1,59 @@
1
+ # {{user_problem_or_desired_capability}}
2
+
3
+ > Describe the problem before choosing a solution. Use `Unknown — {{question}}` for missing facts, `TBD` for an unconfirmed owner, and `N/A — {{reason}}` only when appropriate. Label suggestions as proposals. Do not invent customer demand, metrics, priority, commitments, or test results. Keep AC IDs stable.
4
+
5
+ - **Type:** Feature request
6
+ - **Readiness assessment (not Jira status):** Draft — {{triage_readiness_and_material_gaps}}
7
+ - **Owner / decision recipient:** {{confirmed_owner_or_TBD}}
8
+ - **Product / user group:** {{known_product_and_affected_users_or_Unknown}}
9
+ - **Priority proposal and rationale:** {{evidence_backed_proposal_or_Unknown; urgency_alone_is_not_severity}}
10
+
11
+ ## Problem, user, and business value
12
+
13
+ - **User problem:** {{what_the_user_cannot_do_today_and_in_which_situation}}
14
+ - **Current approach:** {{current_workaround_or_process_and_its_evidenced_limits_or_Unknown}}
15
+ - **Value of solving it:** {{observable_customer_or_business_benefit_in_plain_language}}
16
+ - **Demand and impact:** {{confirmed_feedback_or_usage_and_its_limits; distinguish_reported_from_measured_impact}}
17
+
18
+ ## Evidence and customer feedback
19
+
20
+ | Anchor | Source and exact location | What it supports / limitations |
21
+ | --- | --- | --- |
22
+ | S1 | {{sanitized_feedback_request_research_or_usage_anchor}} | {{observed_need_and_limits_of_the_sample}} |
23
+
24
+ **Material unknowns:** {{questions_about_users_business_rules_tenant_permissions_or_success_with_decision_owner_or_TBD}}
25
+
26
+ ## Desired behavior and options
27
+
28
+ - **Desired user experience:** When {{user_and_situation}}, the user can {{action}} and observes {{result}}. {{State_which_parts_are_requested_versus_agreed}}.
29
+ - **Business rules and boundaries:** {{confirmed_rules_eligibility_tenant_permissions_and_compatibility_constraints_or_Unknown}}
30
+ - **Options:** {{requested_option; viable_alternative_or_improving_current_process; no_change_option_where_relevant}}
31
+ - **Tradeoffs / dependencies:** {{evidenced_benefits_costs_dependencies_and_open_decisions; no_invented_estimates}}
32
+ - **Non-goals:** {{related_needs_or_implementation_work_excluded_from_this_request}}
33
+
34
+ ## Success measure
35
+
36
+ | Measure | Baseline and source | Target and decision source | How it would be checked |
37
+ | --- | --- | --- | --- |
38
+ | {{observable_user_or_business_outcome}} | {{evidenced_baseline_or_Unknown}} | {{agreed_target_or_Unknown}} | {{measurement_method_or_Unknown}} |
39
+
40
+ An unknown baseline or target stays unknown; do not manufacture a percentage to make the request look complete.
41
+
42
+ ## Triage acceptance and verification
43
+
44
+ These criteria accept a decision about the request. They do not claim that a feature has shipped. Put implementation acceptance criteria in the resulting story or task.
45
+
46
+ | AC ID | Observable decision deliverable | Verification method and expected evidence | Actual evidence / result |
47
+ | --- | --- | --- | --- |
48
+ | AC-01 | {{problem_user_and_value_are_supported_or_evidence_gaps_are_explicit}}. | {{review_of_source_linked_problem_statement_and_unknowns}} | NOT RUN |
49
+ | AC-02 | {{relevant_options_are_compared_against_confirmed_rules_and_business_value}}. | {{review_of_options_tradeoffs_and_open_decisions}} | NOT RUN |
50
+ | AC-03 | {{accept_defer_decline_or_discover_decision_has_a_rationale_and_next_owner}}. | {{decision_record_and_follow_up_links_or_reason_no_follow_up_is_needed}} | NOT RUN |
51
+
52
+ ## Decision and handoff
53
+
54
+ - **Decision / source:** {{Pending_or_confirmed_decision_with_rationale_and_anchor}}
55
+ - **Dependencies / blockers:** {{needed_evidence_decisions_or_access_with_owner_or_TBD}}
56
+ - **Follow-up:** {{confirmed_PRD_epic_story_or_discovery_link_or_proposed_title; no_fabricated_issue_key}}
57
+ - Assess **Ready for triage** when the need, available evidence, and decision sought are clear. Use **Ready for investigation** only for a bounded agreed discovery scope. Neither means **Ready for implementation**.
58
+ - Implementation requires its own agreed behavior, exact target, business and tenant/security rules, required supporting proof, bounded scope, and feasible AC verification. Keep unresolved material questions visible in that follow-up.
59
+ - Complete this request's triage only when a human decision and disposition are recorded. The author prepares the request and handoff; no implementation, delivery commitment, or live action occurs by drafting it.
@@ -0,0 +1,68 @@
1
+ # {{CONCISE_OBSERVED_FINDING}}
2
+
3
+ <!-- Remove comments, unused optional sections, and unresolved placeholders from the final ticket. Capturing a finding preserves evidence; it does not expand the originating task or authorize a fix. Keep a suspected problem distinct from a demonstrated defect. -->
4
+
5
+ **Content pattern:** Finding / technical debt capture.
6
+ **Configured Jira work type:** {{AVAILABLE_PROJECT_WORK_TYPE_OR_UNRESOLVED}}.
7
+ **Authoring readiness:** {{DRAFT_OR_NEEDS_CLARIFICATION_OR_READY_FOR_INVESTIGATION}}.
8
+ **Jira workflow status:** {{KNOWN_CURRENT_STATUS_OR_UNSPECIFIED}} — separate from authoring readiness.
9
+ **Originating work:** {{KNOWN_WORK_ITEM_OR_SESSION_CONTEXT}}.
10
+
11
+ ## Finding and reason to retain it
12
+
13
+ During {{BOUNDED_ORIGINATING_ACTIVITY}}, {{OBSERVATION}} was found at {{VERIFIED_LOCATION_OR_REPORTED_LOCATION_LABELLED_AS_SUCH}}.
14
+
15
+ Retain this finding because {{KNOWN_OR_POSSIBLE_IMPACT_DISTINGUISHED_EXPLICITLY}}. The capture outcome is an evidence-backed record and a proposed next step, not an unrequested repair.
16
+
17
+ ## Facts and open decisions
18
+
19
+ - **Verified source facts:** {{DIRECT_OBSERVATIONS_WITH_LOCATIONS_AND_RELEVANT_CONTEXT_OR_NONE_CHECKED}}.
20
+ - **Reported facts:** {{CLAIMS_NOT_INDEPENDENTLY_CHECKED_AND_THEIR_SOURCES_OR_NONE}}.
21
+ - **Assumptions:** {{POSSIBLE_EXPLANATIONS_OR_IMPACT_ASSUMPTIONS_AND_EFFECT_IF_FALSE_OR_NONE}}.
22
+ - **Questions:** {{WHAT_REMAINS_UNKNOWN_OWNER_IF_KNOWN_AND_EFFECT_ON_NEXT_WORK}}.
23
+
24
+ ## Evidence and impact
25
+
26
+ - **Evidence:** {{SANITIZED_OBSERVATION_LOG_SNIPPET_ARTIFACT_OR_REPRODUCTION_AND_WHAT_IT_PROVES}}.
27
+ - **Conditions:** {{KNOWN_ENVIRONMENT_VERSION_INPUT_OR_STATE_OR_UNKNOWN}}.
28
+ - **Reproduction status:** {{REPRODUCED_REPORTED_ONLY_NOT_ATTEMPTED_OR_NOT_APPLICABLE_WITH_REASON}}.
29
+ - **Demonstrated impact:** {{OBSERVED_EFFECT_OR_NOT_YET_ESTABLISHED}}.
30
+ - **Potential impact:** {{EXPLICITLY_LABELLED_RISK_OR_HYPOTHESIS_WITH_BASIS_OR_NONE}}.
31
+ - **Related or duplicate record:** {{VERIFIED_EXISTING_KEY_OR_NOT_CHECKED_OR_SEARCH_SCOPE_WITH_NO_MATCH}}.
32
+
33
+ ## Scope and relationship to current work
34
+
35
+ - **In scope for this capture:** {{FACTS_AND_CONTEXT_TO_PRESERVE}}.
36
+ - **Out of scope:** {{REPAIR_REDESIGN_OR_OTHER_ACTION_NOT_INCLUDED_IN_THE_ORIGINATING_TASK}}.
37
+ - **Effect on originating work:** {{BLOCKS_WITH_REASON_OR_CAN_CONTINUE_WITH_REASON_OR_UNRESOLVED}}.
38
+ - **Proposed next action:** {{BOUNDED_TRIAGE_INVESTIGATION_OR_REPAIR_PROPOSAL}} — label it as proposed until its scope is established.
39
+
40
+ ## Capture acceptance criteria
41
+
42
+ 1. **AC-01 — Evidence is recoverable:** The record includes {{OBSERVATION_AND_LOCATION}} with {{CONDITIONS_AND_SOURCE_DETAIL}} sufficient for another person or agent to find the evidence, and labels anything not independently checked.
43
+ 2. **AC-02 — Disposition is explicit:** The record states {{KNOWN_IMPACT_OR_UNCERTAINTY}}, its relationship to {{ORIGINATING_WORK}}, and {{BOUNDED_NEXT_ACTION_OR_OPEN_TRIAGE_QUESTION}} without claiming an unperformed fix.
44
+
45
+ ## Verification plan
46
+
47
+ | Criterion | Review or check | Pass condition | Evidence to retain | Evidence status |
48
+ |---|---|---|---|---|
49
+ | AC-01 | {{CHECK_RECORD_AGAINST_AVAILABLE_SOURCE_EVIDENCE}} | {{OBSERVATION_LOCATION_AND_UNCERTAINTY_ARE_TRACEABLE}} | {{SOURCE_REFERENCE_AND_REVIEW_NOTE}} | Not run |
50
+ | AC-02 | {{CHECK_SCOPE_RELATIONSHIP_AND_PROPOSED_DISPOSITION}} | {{IMPACT_LIMITS_AND_NEXT_ACTION_ARE_EXPLICIT}} | {{DISPOSITION_AND_ANY_VERIFIED_RELATED_RECORD}} | Not run |
51
+
52
+ ## Dependencies and readiness
53
+
54
+ {{DEPENDENCIES_OR_EXPLICIT_NONE_OR_NOT_YET_CHECKED}}. State any evidence, access, owner decision, or known issue needed for the proposed next step. Keep the originating task, parent hierarchy, and blocking relationship distinct.
55
+
56
+ **Readiness reason:** {{SPECIFIC_GAP_OR_EVIDENCE_THAT_A_BOUNDED_INVESTIGATION_CAN_BEGIN}}. Ready for investigation does not mean a repair is scoped or complete.
57
+
58
+ ## Completion evidence for capture
59
+
60
+ - **Evidence preserved:** {{ACTUAL_RECORD_AND_SOURCE_REFERENCES_TO_ADD_AFTER_CAPTURE}}.
61
+ - **Verification results:** Not run — replace with observed checks of AC-01 and AC-02.
62
+ - **Disposition:** {{ACTUAL_TRIAGE_DECISION_OR_EXPLICITLY_UNDECIDED_PROPOSAL}}.
63
+ - **Follow-up:** {{VERIFIED_FOLLOWUP_KEY_IF_CREATED_OR_UNCREATED_PROPOSAL}}.
64
+
65
+ <!-- OPTIONAL: retain if a potential fix is useful to triage; it remains a hypothesis until investigated. -->
66
+ ## Optional — Possible remediation
67
+
68
+ {{PROPOSED_CHANGE_WITH_SUPPORTING_REASON_AND_UNKNOWNS}}. Identify evidence needed before selecting this approach and any compatibility risks it might introduce.