forge

<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/LucasDuys/forge/main/docs/assets/forge-banner-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/LucasDuys/forge/main/docs/assets/forge-banner-light.svg"> </picture> </p>

<p align="center"> <strong>Turn a one-line idea into a branch with tested, reviewed, committed code.</strong> <br> The brainstorm-to-commit pipeline for Claude Code. </p>

<p align="center"> <a href="https://github.com/LucasDuys/forge/blob/main/LICENSE"></a> <a href="https://github.com/LucasDuys/forge/stargazers"></a> <a href="https://github.com/LucasDuys/forge/issues"></a> </p>

---

Using Claude Code for non-trivial tasks today looks like this:

1. Describe what you want in a prompt
2. Manually review the output
3. Realize it missed half the requirements
4. Re-prompt with more context
5. Lose track of what was done vs. what remains
6. Hit the context window limit
7. Start over in a new session, losing all progress

Forge replaces that entire loop with three commands.

  /forge:brainstorm                /forge:plan                    /forge:execute

  "Add real-time collab    --->   Spec decomposed into     --->  Autonomous loop:
   with conflict resolution       ordered task frontiers          implement, test,
   and live cursors"              with dependency DAG             review, commit

  Interactive Q&A that            Smart depth detection:          Runs unattended.
  produces a formal spec          quick |