I1019 — One skill runs the whole loop, and is itself in the graph
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.
BLOCKED wave 4 · p2 · implementation profile · parallel safe
Blocked. This issue cannot start until I1018 is done. The status is derived from that, not declared.
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.
Current state
Skills are a registered kind with a contract. None covers this loop.
Desired state
One skill does the whole loop, follows the existing skill contract, and appears in the graph, the interface and the search like everything else.
Scope
- .ai/repo/skills
Out of scope
- Several thin skills where one is enough
- A skill that reimplements what the commands already do rather than sequencing them
Dependencies
What waits on this
Acceptance criteria
- 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.sh
- bin/majordomus doctor
Evidence required
- skill_registered
- skill_tested
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
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.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I1019.yaml. Read it back with majordomus plan show I1019.