A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I1019
One skill runs the whole loop, and is itself in the graph
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
4- Waiting on
- Holds back
- Behind it in all
2- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1018 | I1018 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Provide a skill that discovers capabilities, validates the graph, reports what is missing documentation, tests, exposure or enforcement, regenerates the projections and reports drift — registered, documented, tested and visible like any other.
- Why
- The loop this milestone creates should be runnable by a worker without knowing which command does which part. And a repository that models skills as data should have its own automation as one of them.
- Now
- Skills are a registered kind with a contract. None covers this loop.
- Wanted
- One skill does the whole loop, follows the existing skill contract, and appears in the graph, the interface and the search like everything else.
- Done when
- unknown: the record declares no `completion`
- Risk
- A skill that wraps commands adds a layer that can drift from them. It sequences and reports; it does not decide anything the commands do not.
Acceptance
- The skill sequences the existing commands rather than reimplementing their behaviour
- It follows the existing skill contract and needs no special-casing to be registered
- It appears in the graph, the interface and the search through the ordinary derivation
- It is tested behaviourally, on a repository state where something is genuinely missing
- Validation
bash test/run.shbin/majordomus doctor- Evidence required
skill_registeredskill_tested- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.ai/repo/skills- Not
Several thin skills where one is enoughA skill that reimplements what the commands already do rather than sequencing them- Depends on
- Priority
- p2
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-06
- Updated
- 2026-09-06
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.