Skip to content

docs: route the skill by subject, not by requirement number - #241

Merged
retr0h merged 1 commit into
mainfrom
docs/skill-routes-by-subject
Oct 1, 2026
Merged

retr0h merged 1 commit into
mainfrom
docs/skill-routes-by-subject

Conversation

@retr0h

@retr0h retr0h commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Every routing table in add-a-domain cited FR numbers. The components/ pages have carried headings rather than requirement numbers since the spec-kit removal, so all 58 citations pointed at something that no longer existed. An agent following the skill hit a dead pointer at step one of every layer.

FR- references in .claude/skills/   58  ->  0
broken links and anchors             0

Each row now links a heading, and I checked every link and anchor resolves against the file it names rather than assuming.

Three things came out with them

The SDK rules routed to the wrong page. They pointed at domains.md when sdk.md states them.

Two passages were archaeology. sdk.md and api.md narrated what an earlier version of the file had claimed and that the claim was wrong:

There is no sdk-standards capability. Earlier versions of this file said the binding rules were "the sdk-standards capability in this repository", that they bound osapi-orchestrator too, and that the capability won any disagreement. Nothing of the sort has been written.

The constitution forbids that for the same reason it forbids restating a rule: a reader cannot tell a record of a correction from the thing being corrected. What binds is now stated plainly, in four lines instead of twelve.

The README justified relative links with tooling that no longer exists. It said scripts/validate-skills.py resolves them and just skill-lint fails when one breaks. Both were removed earlier in the spec-kit cleanup. The reason given is now the one that is still true: a relative link breaks visibly when the target moves, where an absolute URL goes on resolving to a page that no longer says what the row claims.

What this unblocks

This was the blocker for "go implement X soup to nuts". The skill is 832 lines across seven files and covers the pipeline; it just could not be followed.

just test passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c

Every routing table in add-a-domain cited FR numbers. The components pages
have carried headings rather than requirement numbers since the spec-kit
removal, so all 58 citations pointed at something that no longer existed. An
agent following the skill hit a dead pointer at step one of every layer.

Each row now links a heading, and the links and anchors are checked: all 52
resolve.

Three things came out with them.

The SDK rules routed to domains.md when sdk.md states them, and the CLI rows
had nowhere to point until cli.md was written.

Two passages were archaeology, narrating what an earlier version of the file
claimed and that the claim was wrong. The constitution forbids that for the
same reason it forbids restating a rule: a reader cannot tell a record of a
correction from the thing being corrected. What binds is stated plainly
instead.

The README justified relative links by saying scripts/validate-skills.py
checks them and `just skill-lint` fails when one breaks. Both were removed
earlier; the reason for relative links is now the one that is still true.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown

Thank you for contributing to this project! 😊🕹️

@retr0h
retr0h merged commit 8cec199 into main Oct 1, 2026
5 checks passed
@retr0h
retr0h deleted the docs/skill-routes-by-subject branch October 1, 2026 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant