An idea-to-artifact pipeline for Claude Code. Drop a thought into your inbox, and Forge helps you plan it, build it, and ship the content — one command at a time.
Forge is a structured workflow that turns raw ideas into shipped projects. You voice-dump or type a thought into an Obsidian inbox. From there, a set of slash commands moves the idea through every stage until it's live:
Inbox → Triage → Plan → Build → Draft → Review → Publish
Each stage has a single command. You stay in control — nothing ships without your approval.
Requirements: Claude Code CLI and Obsidian (free).
1. Clone the repo as your workspace root:
Replace
YOUR_USERNAMEwith your GitHub username before running.
git clone https://github.com/YOUR_USERNAME/forge.git my-workspace
cd my-workspace2. Initialize your vault:
claude "forge-start"This creates your Obsidian vault structure (obsidian/vault/) and sets up the workspace. Open the obsidian/vault/ folder in Obsidian.
3. Drop an idea in your inbox:
Add a note to obsidian/vault/00-inbox/ — type it or paste a voice transcription.
4. Run the pipeline:
/forge-triage → sort inbox notes into the right vault section
/forge-plan <name> → scope the MVP
/forge-build <name> → build it
/forge-draft <name> → draft the X post + Substack
/forge-review <name>→ generate a handoff file to paste into a second agent (ChatGPT, Open Code, etc.)
/forge-publish <name> → final checklist + mark as published
/forge-status → see where everything stands
obsidian/vault/
00-inbox/ ← raw ideas, voice notes, word vomit
10-projects/ ← active projects worth shipping
20-experiments/ ← POCs and sandbox thinking
30-dotfiles/ ← shell config, machine setup notes
40-areas/ ← ongoing life areas (health, career, habits)
50-resources/ ← reference and research notes
60-journal/ ← daily/weekly reflections
70-archive/ ← completed or abandoned work
Each active project in 10-projects/ gets a full folder: spec, wiki, operation log, and staged content drafts.
Forge uses obsidian/vault/ as the vault path. All commands are wired to this path out of the box.
If you want a different folder name, do a find-and-replace on obsidian/vault/ across .claude/commands/ and .claude/forge-templates/ after cloning. It's a one-time setup step.
The end goal is fully automated publishing: voice memo → MVP → GitHub repo → X post → Substack post, with no manual steps beyond your approval.
1. forge-auto — end-to-end pipeline in one command
Right now Forge requires running each stage manually. The next major update removes that. You drop a voice note or word vomit into the inbox, run one command, and the pipeline runs itself — triage → plan → build → draft — without you babysitting between stages. A second sub-agent (running inside Claude Code) acts as the critic: it reviews the plan and the built artifact before anything gets surfaced for your approval. The only human step is the final approval gate.
This will run with --dangerously-skip-permissions so Claude Code can operate unattended across the full pipeline.
2. Personal voice calibration
Right now the X post and Substack drafts are competent but generic. The next version introduces a voice profile — a curated set of your real posts and writing that the agent references when drafting content. The goal: drafts that sound like you wrote them, not like an AI summarized your idea. No editing required before approval.
3. API-wired publishing
The draft and publish stages are currently semi-manual — Forge writes the content, you paste and post. The next phase wires up the X and Substack APIs so an approved artifact posts automatically.
Forge is open source and contributions are welcome. If you're building on top of it, have ideas for the voice calibration layer, or want to help wire up the publishing APIs — open an issue or PR. The roadmap above is the active direction; anything that moves it forward is in scope.
Every artifact generated by Forge includes a Forged — [date] footer. It's a small signal that the work came through a deliberate, documented process — not a one-off.
MIT