Configure the engineering skills against this repo and this KB
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
This commit is contained in:
1 parent
6af3714bd0
commit
6f1f55345a
9 files changed
+254
No files matched your search
@@ -16,6 +16,22 @@ lesson, a few lines. Full incident narratives are recoverable from git
|
||||
(`git log --follow omp-docs/log.md`); knowledge that outlives an entry lives
|
||||
on its concept page, linked here. Never re-expand an entry in place.
|
||||
|
||||
## 2026-10-20 — engineering skills configured against this KB
|
||||
|
||||
`setup-matt-pocock-skills` ran, and its output moved out of the skill's default
|
||||
`docs/agents/` into the knowledge base: [issue tracker](skills/issue-tracker.md)
|
||||
(Gitea on Dankclaw is the tracker — no `gh`, no `tea`, token via a `600` curl
|
||||
config), [triage labels](skills/triage-labels.md) (the five canonical roles,
|
||||
created on the repo, which carried zero labels before), [domain
|
||||
docs](skills/domain-docs.md) (single-context; glossary withheld until a term has
|
||||
no other owner), plus an empty [decisions](decisions/index.md) with its format
|
||||
rule. `AGENTS.md` gained an `## Agent skills` pointer block. Law: this repo has
|
||||
one knowledge base, so per-tool configuration is a concept page in `omp-docs/` —
|
||||
a second `docs/` tree means a second set of index rules, which is where
|
||||
documentation starts disagreeing with itself. Known cost: re-running that setup
|
||||
skill will not recognise `omp-docs/skills/*` and will offer to recreate
|
||||
`docs/agents/`; the `AGENTS.md` pointer is the thing that stops it.
|
||||
|
||||
## 2026-10-19 — dankvoice auto-speak armed at startup
|
||||
|
||||
Sessions spoke only on explicit `/say`: the settings file carried no `auto`
|
||||
|
||||
Reference in new issue
Block a user