agent-templates 0.1.0

package/templates/tracker/gitlab/issue_templates/decision-record.md

@@ -0,0 +1,20 @@
+<!-- GitLab description template ("decision-record"). Records what was done and why —
+     the durable memory that commits cannot carry. Apply the decision-record label. -->
+
+**What** (merged in <commit/PR/MR>, YYYY-MM-DD): <one paragraph — the change as shipped.>
+
+**Key decisions & why**
+
+<!-- One bullet per decision: the decision, its reason, and the rejected alternative when
+     one was seriously considered. Cite sources — official docs, ADRs, maintainer direction
+     with date — the same grounding discipline as everything else. -->
+
+-
+
+**Evidence**
+
+<!-- Test results, verification records, links to the docs where each decision landed. -->
+
+**Links**
+
+<!-- Related issues / MRs / ADRs / tickets. -->

package/templates/tracker/gitlab/issue_templates/task.md

@@ -0,0 +1,31 @@
+<!-- GitLab description template ("task"). Mirrors the pipeline's ticket format
+     so triage can convert it mechanically. -->
+
+## Traceability
+
+<!-- What this implements or follows from: PRD §/FR, an ADR, a discussion, an upstream
+     pattern — with links. If the decision is already made somewhere, say where. -->
+
+## Background + basis
+
+<!-- Why this is needed. Cite claims; quote the load-bearing sentences rather than
+     paraphrasing from memory. -->
+
+## Goal
+
+<!-- One paragraph: the artifact(s) to produce and where they land — checkable. -->
+
+## Non-goals
+
+<!-- Each exclusion names its owner or standing reason: "No X — that is MOD-02" /
+     "No Y — stays out of scope per PRD §Z; do not add it as a side effect." -->
+
+## Affected area (best guess)
+
+<!-- Files/modules if known; the Architect finalizes the file-scope and the
+     does-not-touch list. -->
+
+## Acceptance
+
+<!-- Checkable criteria, one per line, tagged with the repo's class vocabulary if you can
+     (defaults: [machine]/[fixture]/[human]). Prefer runnable checks ("command X exits 0"). -->

package/templates/tracker/gitlab/merge_request_templates/default.md

@@ -0,0 +1,55 @@
+<!-- GitLab MR description template ("default"). "Closes #N" auto-closes on merge to the
+     default branch — the pipeline relies on this; never remove the reference. -->
+
+## Summary
+
+<!-- What does this MR do? One sentence. -->
+
+## Related issue / ticket
+
+<!-- Closes #N — plus the ticket id, e.g. [MOD-NN]. The ticket FILE stays the content
+     source of truth; the issue holds state. -->
+
+## Type
+
+- [ ] `feat` — new feature
+- [ ] `fix` — bug fix
+- [ ] `refactor` — restructuring, no behavior change
+- [ ] `docs` — documentation / ADR only
+- [ ] `test` — new or updated tests
+- [ ] `ci` / `chore` — tooling, maintenance
+
+## Changes
+
+<!-- Bullets: what changed AND why. Include what was tried and rejected if it shaped the result. -->
+
+-
+
+## Design note
+
+<!-- Hard-to-reverse or non-obvious changes: link the ADR (docs/adr/NNNN-*.md) — add one if
+     this is a durable decision. Otherwise summarize inline: problem · affected components ·
+     contract/schema changes · risks. -->
+
+## Pipeline evidence
+
+<!-- Assumes the installed pattern; the three-agent pattern's items are shown — adapt if
+     this repo runs a different pattern. -->
+
+- [ ] Plan: `docs/plans/<ticket-id>.md` (link)
+- [ ] Builder: REAL test output attached (unit / integration / E2E as the ticket requires) — never "should pass"
+- [ ] Reviewer verdict: **CLEAR**, from a fresh context (link or paste the note; bounces: <n>)
+- [ ] Deviations from the plan recorded (or "none")
+- [ ] Post-merge: `/verify-delivery <ticket-id>` runs — the issue closes only after it passes
+
+## Constraint check
+
+<!-- At install time, copy this repo's non-negotiables from its CLAUDE.md here as
+     checkboxes. Tick what this MR touches; mark the rest N/A. Two universal items: -->
+
+- [ ] No hardcoded secrets (keys, tokens, credentials) in code / config / logs / docs
+- [ ] Docs / ADR / ticket updated if behavior or a decision changed (feedback obligation)
+
+## Evidence
+
+<!-- Test output, before/after screenshots (UI), command + output (CLI/API), or a short repro. -->