Skip to content

v0.1.0

Choose a tag to compare

View all tags
@DailenG DailenG released this 25 Jul 15:56
v0.1.0
26eb907

This release lets you install Forge into Claude Code with two commands and run a single command, /forge, that carries a project from a blank folder all the way to a tagged release. It works out what phase you are in, asks the right questions until it understands the problem, sets up the toolchain, then builds the thing test-first, keeping enough written state that you can walk away and pick up later in a fresh session.

New here? Read the illustrated guide: https://daileng.github.io/forge-workflow/

Install

claude plugin marketplace add DailenG/forge-workflow
claude plugin install forge-workflow@dailen

Prefer a manual install? Download forge-workflow.zip below and extract it to ~/.claude/skills/forge-workflow/ (%USERPROFILE%\.claude\skills\forge-workflow\ on Windows).

Added

  • /forge orchestrator command: detects the current phase, reconciles the recorded state against the repository, and does the next thing.
  • Phase 1 (/forge-spec): requirements discovery to 95 percent confidence, producing docs/SRS.md behind a mandatory approval gate.
  • Phase 2 (/forge-env): toolchain and repository bootstrap, testing harness, git hooks, and CI. Windows and PowerShell specific today.
  • Phase 3 (/forge-code): test-driven implementation in vertical slices, branch per slice, with a pre-push gate running build, tests, lint, and a secret scan.
  • forge-standards: always-loaded engineering standards covering typography, testing discipline, git lifecycle, and resumability.
  • SessionStart, PreToolUse, PostToolUse, and Stop hooks for state injection and drift detection, backed by four Node scripts.
  • Project file templates for CONTINUE.md, TODO.md, traceability, docs and image manifests, CI, and release tooling.
  • Illustrated user guide hosted on GitHub Pages.
  • Marketplace distribution via the dailen marketplace, plus a manual skills-directory install path.

Notes

This is an early release (0.1.0). Forge has had a partial shakedown, not a complete one. Phase 2 assumes Windows and PowerShell today; the rest is platform-neutral. The hooks need Node.js on your PATH, and without it cross-session resume becomes best-effort. See the README for details.

Assets 3
Loading