Repository navigation
chore(agents): record where issues and domain docs live - #27
Merged
Merged
Conversation
…eering skills The to-spec, to-tickets and implement-spec skills each need the issue tracker and the domain doc layout of this repo. Neither was written down, so each run had to infer them. GitHub issues on this repo are now the recorded tracker, with the conventions and the sub-issue and blocking commands spelled out. Domain docs are recorded as single-context, with GLOSSARY.md and docs/adr at the root, created when there is something to record. No triage label vocabulary: the triage skill is not installed, so the five canonical labels would have no consumer. The one label the other skills name, ready-for-agent, is created on its own.
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
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.
The engineering skills (to-spec, to-tickets, implement-spec, code-review, wayfinder) assume a per-repo configuration: where issues live, and where domain docs live. Neither was recorded in this repo, so every run had to guess.
This records the two that apply here:
ghCLI. Sub-issues and native blocking edges are available (gh 2.102).GLOSSARY.mdanddocs/adr/at the repo root, created lazily by domain-modeling when terms or decisions actually get resolved.The triage label vocabulary is deliberately not configured: the
triageskill is not installed, so the five canonical labels have no consumer. The one label the other skills do reference,ready-for-agent, is created separately.No behavior changes: documentation only.