Configure the engineering skills against this repo
Scaffolds the per-repo configuration that the Matt Pocock engineering skills
(triage, to-tickets, to-spec, research, implement, …) assume, so they
stop guessing and read it from here.
What was decided (Frank, 2026-10-20)
Issue tracker: Gitea on Dankclaw. The remote is dank/command-center at 192.168.0.143:3000 — neither GitHub nor GitLab, and neither gh nor tea
exists on any box, so the tracker is recorded as freeform prose: the curl + 600-config auth recipe, the endpoint table, and the traps that cost time
before (empty token answers 404 not 401; merge is form-encoded with a
lowercase do; a successful merge is 200 with an empty body). The AGENTS.md
laws the skills inherit — issue before branch, never merge without your OK, the cwd · session footer — are restated there because a skill will otherwise
renegotiate them.
Triage labels: canonical defaults kept. The repo carried zero labels,
so nothing collides. I created the five on the tracker via the API
(needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix);
the page records that renaming is a two-sided edit and that a near-duplicate
label is worse than either option.
Domain docs: single-context, inside the KB — see below.
Your instruction moved the docs into omp-docs/
The skill's templates write docs/agents/*.md and put GLOSSARY.md + docs/adr/ at the repo root. This repo caps its root at "config, docs, scripts,
harness dirs" and omp-docs/ is the one knowledge base, so the pages landed in
the KB instead:
omp-docs/skills/issue-tracker.md
omp-docs/skills/triage-labels.md
omp-docs/skills/domain-docs.md
omp-docs/decisions/index.md — ADR directory created, empty, with the format
rule (claim-as-title, Root / Decision / Rejected / Verification), because the
domain page points at it and an unlisted directory is invisible to an agent
omp-docs/skills/index.md + root omp-docs/index.md list them; omp-docs/log.md
carries the dated entry
AGENTS.md gains an ## Agent skills pointer block at the end of the SDLC
material — three sub-headings, three links, no duplicated facts.
Known cost, written down where it will be read: re-running setup-matt-pocock-skills will not recognise omp-docs/skills/* as prior output
and will offer to create docs/agents/ from scratch. The AGENTS.md pointer is
what stops a future agent accepting that offer.
Glossary deliberately not created. Every candidate term already has an owner
(host roles in system/, agent config in core/, skill tiers in skills/), and
a term list that paraphrases them is a second owner of facts already written down
— the first thing to go stale. omp-docs/glossary.md appears when a real term has
nowhere else to live.
Verification
bats tests/ green, including kb-lint (every page carries a type in
frontmatter, no frontmatter in index files, every page listed by its directory
index). Labels verified by reading the tracker back after creation rather than
trusting the 201s.
Not merged: waiting on your OK.
cwd: /home/blank/.omp/wt/wt-20261019-125509-7c8a99d · session: 01a155bb-6474-7366-be9d-629f74af0e05
Build worktree: ~/.omp/wt/wt-agent-skills off origin/main.
# Configure the engineering skills against this repo
Scaffolds the per-repo configuration that the Matt Pocock engineering skills
(`triage`, `to-tickets`, `to-spec`, `research`, `implement`, …) assume, so they
stop guessing and read it from here.
## What was decided (Frank, 2026-10-20)
- **Issue tracker: Gitea on Dankclaw.** The remote is `dank/command-center` at
`192.168.0.143:3000` — neither GitHub nor GitLab, and neither `gh` nor `tea`
exists on any box, so the tracker is recorded as freeform prose: the curl +
`600`-config auth recipe, the endpoint table, and the traps that cost time
before (empty token answers `404` not `401`; merge is form-encoded with a
lowercase `do`; a successful merge is `200` with an empty body). The AGENTS.md
laws the skills inherit — issue before branch, never merge without your OK, the
`cwd · session` footer — are restated there because a skill will otherwise
renegotiate them.
- **Triage labels: canonical defaults kept.** The repo carried **zero** labels,
so nothing collides. I created the five on the tracker via the API
(`needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`);
the page records that renaming is a two-sided edit and that a near-duplicate
label is worse than either option.
- **Domain docs: single-context, inside the KB** — see below.
## Your instruction moved the docs into `omp-docs/`
The skill's templates write `docs/agents/*.md` and put `GLOSSARY.md` +
`docs/adr/` at the repo root. This repo caps its root at "config, docs, scripts,
harness dirs" and `omp-docs/` is the one knowledge base, so the pages landed in
the KB instead:
- `omp-docs/skills/issue-tracker.md`
- `omp-docs/skills/triage-labels.md`
- `omp-docs/skills/domain-docs.md`
- `omp-docs/decisions/index.md` — ADR directory created, empty, with the format
rule (claim-as-title, Root / Decision / Rejected / Verification), because the
domain page points at it and an unlisted directory is invisible to an agent
- `omp-docs/skills/index.md` + root `omp-docs/index.md` list them; `omp-docs/log.md`
carries the dated entry
`AGENTS.md` gains an `## Agent skills` pointer block at the end of the SDLC
material — three sub-headings, three links, no duplicated facts.
**Known cost, written down where it will be read:** re-running
`setup-matt-pocock-skills` will not recognise `omp-docs/skills/*` as prior output
and will offer to create `docs/agents/` from scratch. The AGENTS.md pointer is
what stops a future agent accepting that offer.
**Glossary deliberately not created.** Every candidate term already has an owner
(host roles in `system/`, agent config in `core/`, skill tiers in `skills/`), and
a term list that paraphrases them is a second owner of facts already written down
— the first thing to go stale. `omp-docs/glossary.md` appears when a real term has
nowhere else to live.
## Verification
`bats tests/` green, including `kb-lint` (every page carries a `type` in
frontmatter, no frontmatter in index files, every page listed by its directory
index). Labels verified by reading the tracker back after creation rather than
trusting the `201`s.
Not merged: waiting on your OK.
---
cwd: /home/blank/.omp/wt/wt-20261019-125509-7c8a99d · session: 01a155bb-6474-7366-be9d-629f74af0e05
Build worktree: `~/.omp/wt/wt-agent-skills` off `origin/main`.
The Matt Pocock engineering skills (triage, to-tickets, to-spec, research,
implement) assume per-repo config for three things: where work items live, what
the triage label vocabulary is, and where domain docs sit. Nothing here declared
any of them, so every skill run re-guessed.
Frank's decisions, 2026-10-20: Gitea on Dankclaw as the tracker (no gh, no tea on
any box, so it is recorded as prose — auth via a 600 curl config, the endpoint
table, the 404-on-empty-token / form-encoded-merge / empty-200-on-merge traps,
and the AGENTS.md laws a skill must not renegotiate); the canonical triage label
vocabulary kept as-is, with the five labels created on the tracker (the repo had
zero, so nothing collides); single-context domain docs.
The configuration moved out of the skill's default docs/agents/ and into the one
knowledge base this repo allows: three pages under omp-docs/skills/, an empty
omp-docs/decisions/ carrying the ADR format rule, an "## Agent skills" pointer
block in AGENTS.md, index entries, and a log entry. The glossary is deliberately
not created — every candidate term already has an owner in system/, core/ or
skills/, and a term list that paraphrases them is a second owner of facts already
written down. Known cost: re-running setup-matt-pocock-skills will not recognise
omp-docs/skills/* and will offer to recreate docs/agents/; the AGENTS.md pointer
is what stops that.
Also closes a verification gap found on the way: kb-lint.bats only ever points
the linter at fixtures, so a page with no frontmatter or an index that stops
listing a file passes the suite silently. Two tests now run the linter and the
coverage checker against the shipped omp-docs/ tree.
Refs #18
dank
merged commit 5110060c24 into main2026-10-20 16:14:43 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Configure the engineering skills against this repo
Scaffolds the per-repo configuration that the Matt Pocock engineering skills
(
triage,to-tickets,to-spec,research,implement, …) assume, so theystop guessing and read it from here.
What was decided (Frank, 2026-10-20)
dank/command-centerat192.168.0.143:3000— neither GitHub nor GitLab, and neitherghnorteaexists on any box, so the tracker is recorded as freeform prose: the curl +
600-config auth recipe, the endpoint table, and the traps that cost timebefore (empty token answers
404not401; merge is form-encoded with alowercase
do; a successful merge is200with an empty body). The AGENTS.mdlaws the skills inherit — issue before branch, never merge without your OK, the
cwd · sessionfooter — are restated there because a skill will otherwiserenegotiate them.
so nothing collides. I created the five on the tracker via the API
(
needs-triage,needs-info,ready-for-agent,ready-for-human,wontfix);the page records that renaming is a two-sided edit and that a near-duplicate
label is worse than either option.
Your instruction moved the docs into
omp-docs/The skill's templates write
docs/agents/*.mdand putGLOSSARY.md+docs/adr/at the repo root. This repo caps its root at "config, docs, scripts,harness dirs" and
omp-docs/is the one knowledge base, so the pages landed inthe KB instead:
omp-docs/skills/issue-tracker.mdomp-docs/skills/triage-labels.mdomp-docs/skills/domain-docs.mdomp-docs/decisions/index.md— ADR directory created, empty, with the formatrule (claim-as-title, Root / Decision / Rejected / Verification), because the
domain page points at it and an unlisted directory is invisible to an agent
omp-docs/skills/index.md+ rootomp-docs/index.mdlist them;omp-docs/log.mdcarries the dated entry
AGENTS.mdgains an## Agent skillspointer block at the end of the SDLCmaterial — three sub-headings, three links, no duplicated facts.
Known cost, written down where it will be read: re-running
setup-matt-pocock-skillswill not recogniseomp-docs/skills/*as prior outputand will offer to create
docs/agents/from scratch. The AGENTS.md pointer iswhat stops a future agent accepting that offer.
Glossary deliberately not created. Every candidate term already has an owner
(host roles in
system/, agent config incore/, skill tiers inskills/), anda term list that paraphrases them is a second owner of facts already written down
— the first thing to go stale.
omp-docs/glossary.mdappears when a real term hasnowhere else to live.
Verification
bats tests/green, includingkb-lint(every page carries atypeinfrontmatter, no frontmatter in index files, every page listed by its directory
index). Labels verified by reading the tracker back after creation rather than
trusting the
201s.Not merged: waiting on your OK.
cwd: /home/blank/.omp/wt/wt-20261019-125509-7c8a99d · session: 01a155bb-6474-7366-be9d-629f74af0e05
Build worktree:
~/.omp/wt/wt-agent-skillsofforigin/main.