orchestration-rules
TheOneKit Orchestration Rules
Section titled “TheOneKit Orchestration Rules”Classify every user request and route to the matching T1K command; role→agent identity resolves through t1k-routing-*.json fragments.
Decision Tree
Section titled “Decision Tree”Priority order: T1K commands (registry-routed) → skills (keyword-activated) → standard tools (trivial only). Task-Type routing: delegating to a specialist is the default; pick the narrowest; general-purpose is the LAST RESORT. Cheap tier is by question shape (what something IS → cheap; WHY/recommendation → never cheap). model: is the FALLBACK tier. t1k-rule-creator/t1k-skill-creator are SKILLS, not spawn targets. Issue/PR via gh: /t1k:issue (/t1k:sync-back for fragments), never a general-purpose sub-agent. Testing → t1k-tester.
Mandatory Skill Usage (NEVER bypass)
Section titled “Mandatory Skill Usage (NEVER bypass)”/t1k:sync-back and /t1k:issue (background sub-agent) · /t1k:triage (never browse issues by hand) · /t1k:git for ALL git ops, never raw git in the main session, the patch-under-20-lines exception does not apply (exception: t1k-tree.cjs subcommands run native). Full text: docs/orchestration-rules.md.