القائمة
Use before acting on any request that will change a repo, or that asks for a design decision, debugging help, or planning — decides which skill (or no skill) handles it next.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use once a spec is approved and ready to become an executable task list — turns spec requirements into a wave-based plan of write-scoped, testable tasks that waves can dispatch. Invoke via route or explicit command.
Use when a plan already exists and is ready to run — dispatches each wave's tasks, reviews every return before trusting it, and gates advancement on evidence. Invoke via route or explicit command.
Use when writing a new galdr skill, editing an existing one, or running the pack's quarterly prune review.
Continuation protocol for resuming work after a break, handing off to another session, a subagent, or Codex, and parking fast under a usage limit. Invoke via route or explicit command.
Use once per repo to create or refresh docs/agents/galdr.md — the config verify, waves, review, branches, and route read for gate commands, invariants, models, and smoke details. Slash-command only, not router- or model-invoked.
Use when the user runs /galdr:core to install, uninstall, or check galdr's core rules block on this machine for Claude, Codex, or Antigravity. Run install once per agent to write the marked block into that agent's rules file (or the Claude enabled flag); uninstall to remove it; status to report state without writing.
| name | route |
| description | Use before acting on any request that will change a repo, or that asks for a design decision, debugging help, or planning — decides which skill (or no skill) handles it next. |
Runs before action on any substantive request. Trivial talk (greetings, questions about galdr itself) does not need routing.
Announce the destination in one line, then act:
routing: <destination> — <one-line reason>
Examples:
routing: debug — unexpected behavior reported (SSE handler dropping events)
routing: tdd-fast-path — single file, existing coverage, no cross-repo/registry/i18n/migration surface
| Signal | Route |
|---|---|
| Question / discussion / no repo mutation | answer directly, no ceremony |
| Bug or unexpected behavior reported | debug |
| Fast path: single file, existing test coverage, no cross-repo / registry / i18n / migration surface | tdd directly (announce "fast path") |
| Feature or change, spec/plan already exists | plan (if plan missing) or waves (if plan exists) |
| Feature, no spec, requirements clear enough to state | shape in synthesis mode → spec without interview |
| Feature, requirements fuzzy, user has a position to test | shape in grill mode |
| Feature, open-ended, no position yet | shape in explore mode |
| Multi-session fog (no spec possible yet) | shape with wayfinder map reference |
| Architecture pain, no specific feature | rearchitect |
| Design question answerable by building | prototype |
Canonical route names, in table order (the exact tokens other skills and the accuracy
tests use): answer, debug, tdd-fast-path, plan / waves, shape-synthesis,
shape-grill, shape-explore, shape-wayfinder, rearchitect, prototype.
Route to tdd-fast-path only when ALL of these hold:
And NONE of these apply:
If any one of these applies, or the file lacks existing test coverage, route to plan
(or waves if a plan already exists) instead — the change still needs the normal
ceremony. One boundary: this plan-exit is for changes that are already fully specified
and merely excluded from the fast path. Feature-sized work with no spec still goes
through shape first — the decision table's spec-first rows govern feature scale.
A repo's setup config (docs/agents/galdr.md) may override these criteria. Follow the
repo's override when one is configured; use the list above by default.
One word from the user wins. If the user names a different skill or route, switch immediately. Do not re-litigate the router's own call.
On trivial turns (answer, tdd-fast-path), the router's own output is at most 2 lines:
the announce line, plus at most one line leading into the answer or the first test. No
extra framing, no re-explaining the decision table.
tdd-fast-path skips planning ceremony, not discipline. The Iron Laws still apply in
full: write the failing test first, verify completion with fresh evidence, find the root
cause of any fix. "Fast path" names a shorter path to tdd, not an exemption from it.