Repository navigation
Conversation
fstagni
force-pushed
the
docs_agent-skills-config
branch
from
October 21, 2026 10:20
b8f9b00 to
e648f41
Compare
aldbr
reviewed
Oct 21, 2026
aldbr
left a comment
aldbr
left a comment
Contributor
There was a problem hiding this comment.
What's the goal here?
Can you prove it would bring any added value to the project? (e.g. consuming less token on average, better accuracy)
I doubt it's useful in its current form + I think it would require some discussions in ddev first.
I am closing the PR, but feel free to open a Feature issue and provide further details.
Thanks
| ├── GLOSSARY.md | ||
| ├── docs/adr/ | ||
| │ ├── 0001-event-sourced-orders.md | ||
| │ └── 0002-postgres-for-write-model.md |
|
|
||
| When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `GLOSSARY.md`. Don't drift to synonyms the glossary explicitly avoids. | ||
|
|
||
| If the concept you need isn't in the glossary yet, that's a signal: either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for `/domain-modeling`). |
Contributor
There was a problem hiding this comment.
What is /domain-modeling exactly?
|
|
||
| If your output contradicts an existing ADR, surface it explicitly rather than silently overriding: | ||
|
|
||
| > _Contradicts ADR-0007 (event-sourced orders), but worth reopening because…_ |
|
|
||
| ## Wayfinding operations | ||
|
|
||
| Used by `/wayfinder`. The **map** is a single issue with **child** issues as tickets. |
Contributor
Author
|
The only reason I opened this was for discussing if it would be felt useful to add these types of agents' helpers. I opened this for having a visual reference in a DDev . |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the in-repo configuration that engineering AI agents read, plus the first domain artifacts.
AGENTS.mdkeeps the only always-loaded part (three context pointers); the bodies live behind them:GLOSSARY.mdfixes the project vocabulary agents must reuse (Job vs Pilot vs Payload, Task vs Job vs Task Queue, Site vs Resource vs Element, ...). Definitions were extracted from code and docstrings, not invented; grid acronyms stay indocs/source/UserGuide/glossary.rst(single source of truth).docs/adr/0001records that agent config is in-repo and that the upstream tracker is the single source of tracked work.Evidence
GLOSSARY.mdwas checked against the code (e.g. Site/Resource disjointness verified againstResourceStatusDBtables; Task→Job/Request mapping againstWorkflowTaskAgent/RequestTaskAgent). Any agent asked to file an issue reads one file and runs the exactghcommands documented there.Merge Danger
Door: two-way
Docs-only, additive; reverting is trivial.
Blast radius: agents only — no runtime code, no CI changes.
Deliberately not included: a triage-label vocabulary and the "external PRs as triage surface" flag. Those change tracker behaviour for maintainers (new labels, AI-posted comments on issues) and deserve their own decision; see ADR-0001's consequences.