route-docslisted
Install: claude install-skill thettwe/nyann
# route-docs
Standalone doc-routing and scaffold regeneration. Composes
`bin/route-docs.sh` (produces a DocumentationPlan) and
`bin/scaffold-docs.sh` (materializes the local-target portion) so the
user can change doc storage after initial bootstrap without
re-running the full pipeline.
## 1. Resolve profile and current state
1. Load the active profile via `bin/load-profile.sh <name>`.
2. Run `bin/detect-stack.sh --path .` for a StackDescriptor (optional;
used by scaffold-docs for stack-aware architecture templates).
3. Check which doc targets already exist (`docs/`, `memory/`,
`docs/decisions/`, etc.) so the user sees what will change.
## 2. Determine the routing spec
The user's intent maps to a `--routing` value:
| User says | Routing spec |
|---|---|
| "everything local" | `all:local` (default) |
| "docs in Obsidian" | `all:obsidian` |
| "docs in Notion" | `all:notion` |
| "PRDs in Notion, ADRs in Obsidian, rest local" | `prd:notion,adrs:obsidian,research:local,architecture:local` |
If the user's intent is ambiguous, **you MUST call the `AskUserQuestion`
tool** (not plain text):
```json
{
"questions": [
{
"question": "Where should documentation be stored?",
"header": "Routing",
"multiSelect": false,
"options": [
{ "label": "Local (Recommended)", "description": "docs/ directory in the repo" },
{ "label": "Obsidian", "description": "Route to an Obsidian vault via MCP" },
{ "label": "Notion", "description": "R