olympus/infra-tracker

Fork 0

agents: configure the engineering skills for this repo #5

Merged

pit merged 2 commits from hermes/agent-skills into main

2026-10-09 08:22:38 +00:00

pit commented

2026-10-09 08:19:09 +00:00

Owner

Summary

 /
+├── AGENTS.md                        # new: the ## Agent skills block
+├── docs/agents/
+│   ├── issue-tracker.md            # where issues live: Vikunja, project 3
+│   ├── triage-labels.md            # the five label strings and their ids
+│   └── domain.md                   # single-context: GLOSSARY.md + docs/adr/
 ├── npm/                            # Edge stack (unchanged)
 ├── vikunja/                        # guest + service stacks (unchanged)
 └── Makefile

No code or stack changes. This adds the per-repo configuration the engineering
skills read:

Issue tracker — to-tickets, to-spec, triage, wayfinder call the
Vikunja MCP tools against Infra Tracker (id 3, INFRATRACK) instead of gh.
Triage labels — triage maps the five canonical roles to the labels now
created in the instance (needs-triage … wontfix, ids 1–5).
Domain docs — domain-modeling (via grill-with-docs,
improve-codebase-architecture) reads root GLOSSARY.md + docs/adr/, both
created lazily.

Evidence

Before: no AGENTS.md, no docs/; the five labels did not exist in
Vikunja (labels_list → total: 0).
After: labels_list → total: 5 (ids 1–5), and:

$ git show --stat --format=%h HEAD
8f4be72 agents: configure the engineering skills for this repo
 AGENTS.md                    | 15 +++++++++++++++
 docs/agents/domain.md        | 63 ++++++++++++++++++++++++++
 docs/agents/issue-tracker.md | 59 +++++++++++++++++++++++++
 docs/agents/triage-labels.md | 15 ++++++++++++++
 4 files changed, 152 insertions(+)

Merge Danger

Door: two-way

Docs-only; git revert 8f4be72 restores the tree exactly. Nothing consumes
docs/agents/ until an engineering skill runs.

Blast Radius: docs-only

No provisioning, no deployed host, no secrets touched. One caveat: Vikunja
labels are instance-wide, so the five labels created during setup are global —
reverting this PR leaves them in place (harmless, and re-adoptable).

## Summary ```diff / +├── AGENTS.md # new: the ## Agent skills block +├── docs/agents/ +│ ├── issue-tracker.md # where issues live: Vikunja, project 3 +│ ├── triage-labels.md # the five label strings and their ids +│ └── domain.md # single-context: GLOSSARY.md + docs/adr/ ├── npm/ # Edge stack (unchanged) ├── vikunja/ # guest + service stacks (unchanged) └── Makefile ``` No code or stack changes. This adds the per-repo configuration the engineering skills read: - **Issue tracker** — `to-tickets`, `to-spec`, `triage`, `wayfinder` call the Vikunja MCP tools against `Infra Tracker` (id 3, `INFRATRACK`) instead of `gh`. - **Triage labels** — `triage` maps the five canonical roles to the labels now created in the instance (`needs-triage` … `wontfix`, ids 1–5). - **Domain docs** — `domain-modeling` (via `grill-with-docs`, `improve-codebase-architecture`) reads root `GLOSSARY.md` + `docs/adr/`, both created lazily. ## Evidence - **Before:** no `AGENTS.md`, no `docs/`; the five labels did not exist in Vikunja (`labels_list` → `total: 0`). **After:** `labels_list` → `total: 5` (ids 1–5), and: ```text $ git show --stat --format=%h HEAD 8f4be72 agents: configure the engineering skills for this repo AGENTS.md | 15 +++++++++++++++ docs/agents/domain.md | 63 ++++++++++++++++++++++++++ docs/agents/issue-tracker.md | 59 +++++++++++++++++++++++++ docs/agents/triage-labels.md | 15 ++++++++++++++ 4 files changed, 152 insertions(+) ``` ## Merge Danger **Door:** two-way Docs-only; `git revert 8f4be72` restores the tree exactly. Nothing consumes `docs/agents/` until an engineering skill runs. **Blast Radius:** docs-only No provisioning, no deployed host, no secrets touched. One caveat: Vikunja labels are instance-wide, so the five labels created during setup are global — reverting this PR leaves them in place (harmless, and re-adoptable).

pit added 1 commit

2026-10-09 08:19:09 +00:00

agents: configure the engineering skills for this repo 8f4be726b3

Set up the per-repo configuration that the engineering skills assume, so
`to-tickets`, `triage`, `to-spec`, `wayfinder`, `domain-modeling` and friends
know where issues live and how to read domain docs.

- Issue tracker: tasks in self-hosted Vikunja (project `Infra Tracker`, id 3,
  identifier `INFRATRACK`), driven through the Vikunja MCP tools. No CLI path.
- Triage labels: the five canonical labels (`needs-triage`, `needs-info`,
  `ready-for-agent`, `ready-for-human`, `wontfix`), created in the instance and
  recorded here with their ids.
- Domain docs: single-context — root `GLOSSARY.md` plus `docs/adr/`, created
  lazily by `/domain-modeling`.

`AGENTS.md` carries the `## Agent skills` block pointing at the three files
under `docs/agents/`.

pit added 1 commit

2026-10-09 08:21:55 +00:00

agents: require the pr skill's format for PR bodies 34c6a7afcf

Record the rule in AGENTS.md so every session writes PR bodies with the
`pr` skill's `## Summary` / `## Evidence` / `## Merge Danger` structure.

pit merged commit 173907a948 into main

2026-10-09 08:22:38 +00:00

pit deleted branch hermes/agent-skills

2026-10-09 08:22:38 +00:00

pit referenced this pull request from a commit

2026-10-09 08:22:39 +00:00

Merge pull request 'agents: configure the engineering skills for this repo' (#5) from hermes/agent-skills into main

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

olympus/infra-tracker!5

No description provided.

Rows
Columns