forge

Complex task planning and verification uses a two-machine system: a Plan Forge refines plans and a Verification Chain proves correctness with persistent memory across sessions. It enforces gated, traceable decision making for reliable end-to-end workflows.

Structured workflow with independent review gates is needed when tasks touch 3+ files, have unclear scope, require architectural decisions, or need independent review. This ensures traceable decision making and reliable execution for complex software engineering tasks.

Maintaining task continuity across sessions requires persistent memory that stores state across sessions. This provides structured execution continuity, ensuring reliable end-to-end workflows even when complex planning tasks span multiple coding intervals.

A two-machine planning and verification system provides scalability guidance for small, standard, and complex tasks. While designed for complex tasks touching 3+ files, it offers recommended usage patterns to suit various task scales.

Starting an end-to-end planning and verification pipeline requires creating a new forge with the /forge command followed by your task description. This initiates the structured two-machine workflow with Plan Forge and Verification Chain.

The planning workflow provides HUD integration with status updates in the status line and notepad. This allows real-time monitoring of the gated, traceable decision making process during complex task execution.