Files
skills/.agents/adr/0001-explicit-setup-pointer-only-for-hard-dependencies.md
Remote Box AgentandClaude Sonnet 5 321658273c Remove all em-dashes from the repo
Every em-dash across docs, skill files, scripts, and JSON/YAML metadata
was rewritten by hand (commas, colons, periods, parentheses, conjunctions)
rather than mechanically substituted, so sentences still read naturally.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-19 10:03:37 +00:00

1.1 KiB

Explicit /setup-matt-pocock-skills pointer only for hard dependencies

Engineering skills depend on per-repo config (issue tracker, triage label vocabulary, domain doc layout) seeded by /setup-matt-pocock-skills. Some skills cannot meaningfully function without that config: they have to publish to a specific issue tracker or apply a specific label string. Others only use it to sharpen output (vocabulary, ADR awareness) and degrade gracefully without it.

We split these into hard-dependency and soft-dependency skills:

  • Hard dependency (to-tickets, to-spec, triage): include an explicit one-liner: "… should have been provided to you; run /setup-matt-pocock-skills if not." Without the mapping, output is wrong, not just fuzzy.
  • Soft dependency (diagnose, tdd, improve-codebase-architecture): reference "the project's domain glossary" and "ADRs in the area you're touching" in vague prose only. If the docs aren't there, the skill still works; output is just less sharp.

The split keeps soft-dependency skills token-light and avoids cargo-culting the setup pointer into places where it isn't load-bearing.