think-forge

Think Forge

Answers one question: which ArcForge skill, in which mode, in what order.

It reads the request, names the route, and stops. It does not inspect the repository, run commands, change files, or produce the domain answer.

Core principle: A route is useful before the work starts. Deciding the route and doing the work in the same breath removes the moment where the user can correct the route.

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

Active routing skill: Think Forge (`think-forge`) — route-only.

Do not paraphrase or omit it. Naming only the routed domain owner does not prove which router is active.

Routing Law

THIS SKILL RETURNS A ROUTE AND NOTHING ELSE:
1. no file is created, edited, or deleted;
2. no command, migration, deployment, or repository operation runs;
3. no domain decision is made on the owning skill's behalf;
4. no skill is described as loaded, consulted, or already run;
5. the answer ends at the route, even when the fix looks obvious.

When to Use

Use this skill when:

• the unqualified question is where to start, which skill or mode covers this, or what order these should run in;
• a request spans several domains and the user wants the map before committing to work;
• a route needs a second opinion before an expensive or risky sequence begins;
• the user wants to know whether anything in a request has no owner, or needs a skill that is not installed;
• a plan already exists and the question is only whether the skill selection and order are right.

When Not to Use

• When the current request explicitly asks routing to continue into inspection, review, change, or verification, use using-forge directly.
• When a later user turn should carry an agreed route into the work, start that turn with using-forge. If this skill was explicitly invoked, name that next-turn entry point and stop; do not invoke it now.
• When the user already named a skill and wants the work done, go to that skill. Do not spend a turn confirming a settled route.
• When one domain plainly owns the request and neither the mode nor the order is in question, name that skill directly. Routing a single unambiguous request adds a step and no coverage.
• When the user wants the design, the review, the change, or the evidence, route to the owning skill instead of answering here.
• When a concrete pull request, merge request, commit range, patch, or repository diff needs findings and an approval recommendation, that is pull-request-review-gate. When an architecture artifact needs an independent approval verdict, that is architecture-review-gate.