forge

Forge

Overview

Run this skill only when the current user request explicitly invokes forge or $forge. If the request merely resembles a staged coding task, do not use Forge.

Advance the work from the detected starting stage through stage 5 in one invocation unless the user explicitly asks to stop after a specific stage.

Do not implement code before stage 4.

Write prompt.md, research.md, plan.md, and review.md in the language of the current user request. Keep source code, identifiers, and code comments in English.

Create or update all stage files in the current working directory.

Forge requires subagent support for its intended stage 4 and stage 5 execution model. Do not silently collapse those stages back into a single-agent build-and-review flow.

Detect the Stage

Treat a stage file as the starting-stage resume signal only when the current user request explicitly includes the literal filename.

• If the request does not explicitly mention prompt.md, research.md, plan.md, or review.md, start at stage 1.
• If the request explicitly mentions prompt.md, start at stage 2.
• If the request explicitly mentions research.md, start at stage 3.
• If the request explicitly mentions plan.md, start at stage 4.
• If the request explicitly mentions review.md, start at stage 5.

After choosing the starting stage, continue through all later stages by default.

If the user explicitly asks to stop after a particular stage, to only generate a specific artifact, or to skip a later stage such as review, honor that narrower stop point.

If the user mentions one stage file as the resume point and a later stage file as the requested stop point or final output, treat that as a valid start-and-stop pair instead of an ambiguity.

If the user explicitly mentions multiple stage filenames and the intended starting point is ambiguous, ask which file should be treated as authoritative before changing anything.

Stage Announcement

Before starting each substantive stage, explicitly announce the active stage in one short line.