Tickets PMs love.
That devs actually understand.
Purpose-built for turning rough ideas into complete specs. Designed for the AI era.
HOW IT WORKS
From idea to dev-ready spec in minutes
Not days. Not hours. Minutes.
Describe
What you want built — rough idea, Slack message, anything.
AI Refines
Forge asks smart questions, fills in technical gaps, and structures the spec.
Approve
Review the complete spec. Assigns developer automatically. Tracks SLA.
Develop
Click Develop — AI implements in a cloud sandbox, runs tests, and opens a PR. You review the code, not write it.
WEB APP
Create, review, and approve — all from the browser
- ✓AI-enriched specs with quality scores and acceptance criteria
- ✓Drag-and-drop ticket management with status tracking
- ✓Developer review and PM approval workflow built in
→ Pulling spec… creating branch feat/sso-login…
→ 6 files affected · 3 endpoints · 6 acceptance criteria
DEVELOPER TOOLS
Pick up tickets without leaving your IDE
- ✓Browse and claim tickets from Claude Code or your terminal
- ✓Full codebase context included — file paths, APIs, patterns
- ✓MCP bridge for two-way sync between IDE and Forge
npm i forge-aecCLOUD DEVELOP
From approved ticket to pull request
AI implements your spec in a cloud sandbox. You review code, not write it.
Full Flow
Spec-first development
Write a detailed spec with AI assistance, review with your team, then click Develop. AI implements autonomously and opens a PR with full change record.
Quick Flow
Skip the spec, ship fast
Select a repo, type what you want changed in plain text. AI implements immediately and auto-generates a ticket with full context for the record.
Connect your repos
Link one or multiple repositories with role assignments — backend, frontend, shared.
Choose skills
Pick from curated skills like TDD, Security Audit, or Clean Architecture — or let AI recommend.
Watch it work
Live session monitor shows file edits, test runs, and decisions in real time. Cancel anytime.
Review the PR
AI opens a pull request with full change record — every decision documented, every test passing.
BEFORE & AFTER
Sound familiar?
Forge replaces hours of back-and-forth with a single, dev-ready spec.
hey can you pick up the login ticket?
which login ticket?
the one for adding social login
google only or also github?
both I think? check with design
where's the design?
not sure, ask Sarah
also — existing auth table or new one?
whatever makes sense
...
built it with Google only, separate table
wait we needed GitHub too, and auth table already has a provider column
🙃
Add Social Login (Google + GitHub)
Acceptance Criteria
- ✓Users can sign in with Google or GitHub OAuth
- ✓New provider entries use existing auth_providers table
- ✓Graceful fallback if OAuth provider is unavailable
Relevant Files
src/auth/providers/src/auth/models/User.tssrc/auth/auth.module.tsImplementation Plan
- 1.Add Google & GitHub strategy to OAuthProviderFactory
- 2.Extend auth_providers table with provider-specific metadata
- 3.Add OAuth callback routes and token exchange flow
Stop wasting time on bad tickets
Forge your first ticket in minutes. Free forever for individuals.
Try Forge Free