Files
holocron/docs/adr/0009-flat-skill-taxonomy.md
Defame1297 eae5c37b35 docs: factory integration grill — decision record, ADRs, and chunk scope update
- Decision record covering 12 decisions from the factory integration grill
- ADR-0008 (factory boundary: this repo is a provider, not a factory instance)
- ADR-0009 (flat skill taxonomy with category metadata in frontmatter)
- ADR-0010 (role skills in .agents/skills/; core/agents/ for subagent definitions)
- Issue 0013 (LESSONS.md at repo root)
- Issue 0014 (docs/spec/ living spec layer + VISION.md refactor)
- ROADMAP Chunk 3 scope expanded: skills rebuild, new skills (session-handoff,
  governance-check, git-guardrails, write-adr), IaC/Gitea global optional
- Per-skill process: implementation guidance Sections 4-5 and skills index
  referenced as starting point before web research and grilling
- factory-research-gaps-conflicts.md marked superseded

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-17 10:23:20 +00:00

1.3 KiB

Flat skill directories with category metadata, not nested paths

Skills are stored as flat directories directly under .agents/skills/ (grill-me/SKILL.md, not design/grill-me/SKILL.md). Category organisation is expressed via metadata: category: in each SKILL.md frontmatter rather than directory nesting.

Nested paths were evaluated and rejected for three reasons. First, Claude Code discovers skills exactly one level deep under ~/.claude/skills/ — a skill at ~/.claude/skills/design/grill-me/SKILL.md is invisible to the tool. Second, the agentskills.io open standard specifies that the name field must match the parent directory name, implying a flat structure at the skills root; no nested discovery is defined in the spec. Third, install.sh iterates for skill_dir in .agents/skills/*/ — one level only; nested paths would require a traversal rewrite before a single nested skill could be deployed.

Category metadata achieves the same organisational goals: the Management App can group skills by category, a generated README can cluster them, and the category is machine-readable for tooling — all without path changes, pipeline changes, or deviation from the open standard. If Claude Code adds nested discovery in a future release, paths can be restructured then with evidence rather than speculatively now.