gtd-capability-router
Use when a GTD task can be executed through multiple tools, plugins, connected sources, reviewers, agents, or GitHub actors and the agent must choose the smallest safe stack with explicit ownership, live-state authority, verification, review, and landing boundaries. Also use for continuation work, repository/PR missions, and skill/plugin engineering where stale state or overlapping capabilities can cause duplicate or unsafe work. Do not use for simple one-step tasks with an obvious single tool, or to replace GTD's blocker router or domain-pack selection.
Pinned to revision 533f44133836, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/gtd-capability-router/SKILL.md
- skills/gtd-capability-router/agents/openai.yaml
- skills/gtd-capability-router/agents/roles.yaml
- skills/gtd-capability-router/assets/large-logo.svg
- skills/gtd-capability-router/assets/small-logo.svg
- skills/gtd-capability-router/references/capability-registry.yaml
- skills/gtd-capability-router/references/core-contract.md
- skills/gtd-capability-router/references/plugin-skill-playbook.md
- skills/gtd-capability-router/references/repository-playbook.md
- skills/gtd-capability-router/references/router.yaml
- skills/gtd-capability-router/references/security-boundaries.md
- skills/gtd-capability-router/references/source-lineage.md
Every link opens the file at its source, pinned to the revision this page describes.