---
description: Show all Forge commands and quick reference
allowed-tools: Read
---

# /forge:help — Forge Command Reference

## Purpose

Show the user all available Forge commands with brief descriptions. Indicate which commands are active vs. coming soon.

## Output

Display the following:

---

## 🔨 Forge — Command Reference

### ✅ Available Now

| Command | What it does |
|---|---|
| `/forge:init` | Initialize Forge in a new or existing project. Sets up domain model, architecture decisions, and the `.planning/` knowledge base. |
| `/forge:help` | You're looking at it. |

### 🔜 Coming Soon

| Command | What it will do |
|---|---|
| `/forge:status` | Morning briefing — what's in progress, what's blocked, what to focus on. |
| `/forge:build` | Describe what you want to build. Forge classifies the intent (bug, feature, extension, refactor) and handles the rest. |
| `/forge:continue` | Pick up where you left off. Forge knows what was in progress. |
| `/forge:review` | Walk through what was built since you last looked. Approve, adjust, or reject. |
| `/forge:idea` | Capture a product idea with zero friction. Forge enriches it with domain connections and impact estimates. |
| `/forge:explore` | Research a question — competitors, integrations, technical feasibility. Get a CEO-level brief, not a deep dive. |
| `/forge:decide` | Make a structured decision with tradeoffs. Forge records it as an ADR and propagates implications. |
| `/forge:pivot` | Change direction. Forge traces the impact through dependencies and adjusts gracefully. |
| `/forge:scope` | See what's in v1 vs. later vs. ideas. Interactive, adjustable, living scope. |
| `/forge:priorities` | Show and reorder current priorities based on dependencies, impact, and your signals. |
| `/forge:demo-mode` | Polish what's built, hide what's not. Prep for a customer demo or investor meeting. |
| `/forge:map-codebase` | Analyze an existing codebase — stack, patterns, conventions, domain concepts. |

### 💡 Tips

- **You don't need commands.** Just talk to Forge naturally. Describe what you want, report a bug, share an idea — Forge will figure out what to do. Commands are shortcuts, not requirements.
- **Start with `/forge:build`** when it's available. It's the most common command and handles most workflows.
- **Your `.planning/` directory** is your project's knowledge base. It's human-readable — feel free to browse it anytime.

---

## Tone

Concise, scannable, not overwhelming. The user should be able to glance at this and know what's possible in 10 seconds.