using-forge

Using Forge

The executing router for the ArcForge skill set. It reads an explicit route-and-continue request, decides which skill owns each surface, chooses the mode, resolves companions, puts them in a safe order, and then begins the routed first step.

This skill routes. It does not answer the domain question itself.

Core principle: A request has one owner per surface, a mode, and a companion set. Name all three before work starts, or the request gets a partial answer from whichever skill happened to activate.

Every response produced by this skill MUST begin with this exact identity line, before any other prose:

Active routing skill: Using Forge (`using-forge`) — route-and-continue.

Do not paraphrase or omit it. Naming the routed domain owner without naming this active router is incomplete.

Routing Law

NO DOMAIN WORK WITHOUT:
1. the requested outcome and the affected surfaces identified;
2. one owning skill chosen per surface, not one skill for the whole request;
3. the mode chosen from what the user actually wants: decide, inspect, apply, or prove;
4. required companions resolved before the owner they constrain, not after it finishes;
5. missing or uninstalled depth named with its exact technical ID.

When to Use

Use this skill when:

• the user explicitly asks to route a request and continue into inspection, review, change, or verification in the same turn;
• an explicitly executable request spans more than one domain and the full set is not obvious — checkout, signup, tenant isolation, migration, release, incident follow-up;
• the owning skill is clear but the mode is not, and the user wants the work to continue after routing;
• a previous answer covered one domain and silently skipped an adjacent one;
• a companion skill is needed but which one, and in what order, is unresolved;
• part of the needed depth may not be installed and the route must stay honest about that.

When Not to Use

• When the user already named a skill, use that skill directly. Do not re-route a settled request.
• When one domain plainly owns the request and no companion is in question, invoke that skill directly. Routing a single-domain request adds a step and no coverage.
• An unqualified question about where to start, which skill or mode to use, or what order to follow defaults to think-forge.
• When think-forge has already returned a route in the current user turn, do not re-enter this skill. Wait for an explicit later-turn request to continue into work.
• When a concrete pull request, merge request, commit range, patch, or repository diff needs findings and an approval recommendation, use pull-request-review-gate. When an architecture artifact needs an independent approval verdict, use architecture-review-gate. Routing is not review.
• For the domain decision itself, hand off. This skill never substitutes its own answer for the owning skill's work.