spec-route

Locates relevant AGENTS.md sections by scenario and reads only targeted segments.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/lldwb/lldwb-claude-skills --skill spec-route-lldwb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-route
Source: https://github.com/lldwb/lldwb-claude-skills/tree/main/skills/spec-route
Command: npx skills add https://github.com/lldwb/lldwb-claude-skills --skill spec-route-lldwb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large AGENTS.md convention files are expensive to load in full and easy to misquote from memory. This Skill maps a task scenario to the exact AGENTS.md section that governs it, reads only that segment, and returns the conventions with file:line citations—without copying or paraphrasing the rules into a second source of truth. ## Core Features & Use Cases - Scenario-to-section routing: A project-maintained route table maps common scenarios (commit conventions, layering rules, persistence changes, error codes) to AGENTS.md section anchors. - Segmented loading: Uses Grep to locate section headings by line number, then Read with offset/limit to load only the target section—never the whole file. - Cited output: Every returned convention includes its AGENTS.md line number and section name; misses are reported honestly instead of guessed. - Use Case: Before modifying a persistence-layer mapper, ask which project conventions apply; the Skill locates the relevant AGENTS.md sections, reads just those paragraphs, and returns the rules with exact line references. ## Quick Start Use the spec-route skill to find which AGENTS.md sections govern my planned database schema change and quote the relevant conventions with line numbers.

Frequently Asked Questions about spec-route

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which AGENTS.md section applies to my code change?

Use the route table to map your scenario to a section anchor, then Grep the section heading in AGENTS.md to get its line number and Read only that segment with offset/limit. The Skill returns the matching conventions with file:line citations.

How to read part of a large AGENTS.md without loading the whole file?

Run Grep with the section heading pattern (for example "^## ") to get heading line numbers, then use Read with offset and limit to load only the target section up to the next heading. Never read the entire file at once.

Does this work if my project has no AGENTS.md file?

No. The Skill requires AGENTS.md as the authoritative convention source; without it the Skill does not apply and you should follow general practices instead. CLAUDE.md is treated only as a pointer, not as convention content.

What happens when conventions conflict with actual code behavior?

The Skill does not resolve conflicts itself; it lists the conflicting items for the user to decide. If documentation needs to be aligned with code, the task is handed off to the doc-sync skill.

Can I reuse one route table across multiple projects?

No. Each route table corresponds to one project's AGENTS.md section structure, so switching projects requires building a new route table. The template in references/route-table-template.md explains the registration steps.