See demo → Pro — $9/mo

For Cursor · Claude Code · GitHub Copilot users

Stop starting Cursor sessions
with no real plan

You open Cursor. The AI asks what you want to build.
You don't have a real answer yet.

SpecForge gives you that answer in 30 seconds — a complete PRD, GitHub tickets, and a CLAUDE.md. Paste your idea. Start building with actual clarity.

Product Requirements Doc GitHub Tickets (8–10) CLAUDE.md context file
0 specs generated
· No account required
· No install, runs in browser
· Free during beta
😤 CLI spec tools (BMAD/SpecKit/OpenSpec)
Requires npm install, config files, reading docs
Steep learning curve — built for enterprise teams
Tied to specific AI agent or IDE
30+ minutes to get first output
✅ SpecForge
Works in your browser, zero setup
Type your idea → output in 30 seconds
Works with any AI tool (Cursor, Claude Code, Copilot)
Solo dev friendly — no jargon, no config
Real output — for a habit tracker idea
See full example →
# DevStreak — Product Requirements Document ## Problem Statement Developers struggle to maintain consistent coding habits. Existing habit trackers are generic and don't integrate with the developer workflow. DevStreak provides a developer-native habit tracking experience with GitHub-style contribution graphs, streak tracking, and daily goal management. ## Target Users Solo developers and hobbyists who want to build consistent coding habits but find generic habit apps don't fit their workflow. ## Core Features (MVP) - Habit tracking: Create coding goals (commit daily, solve LeetCode, etc.) - Streak system: Track consecutive days, longest streak, current streak - Contribution graph: GitHub-style heatmap visualization - Daily reminders: Push notifications for PWA users - Progress dashboard: Weekly/monthly completion rates ## Out of Scope (MVP) - Social features, team challenges, leaderboards - GitHub API integration (manual check-ins only for MVP) - Premium tiers (free during beta)
## Ticket #1: Core Data Model & PWA Setup Labels: setup, foundation, backend Estimate: 3-4 hours ### Context Before any features can be built, we need the foundational data model and PWA configuration. This ticket sets up the project structure, database schema, and service worker for offline capability. ### Acceptance Criteria - [ ] Project initialized with Vite + React + TypeScript - [ ] IndexedDB schema defined (habits, check-ins, streaks tables) - [ ] Service worker registered, app installable as PWA - [ ] Basic routing configured (/, /habits, /dashboard) - [ ] Dark mode CSS variables defined globally ### Implementation Notes Use Dexie.js for IndexedDB. Start with localStorage for MVP if Dexie adds complexity. PWA manifest must include all required icon sizes (192, 512px). No backend required for MVP — all data lives in browser storage.
# CLAUDE.md — DevStreak ## Project Overview DevStreak is a developer habit tracker PWA. Users create coding goals, check in daily, and see their progress on a GitHub-style contribution graph. Solo developer project. MVP scope only — no social features, no backend. ## Tech Stack - Frontend: React + TypeScript + Vite - Storage: IndexedDB via Dexie.js (no backend for MVP) - Styling: CSS modules + CSS variables - PWA: Vite PWA plugin + service worker ## Key Constraints - No auth system in MVP (localStorage user identity) - All data stored client-side only - Must work offline (PWA requirement) - Mobile-first design (habit checking happens on phone) ## Development Workflow - Work ticket-by-ticket from the GitHub issues - Test on mobile viewport at each step - Each ticket is self-contained and independently deployable
Try an example →
0/2000
Generating your spec…
✅ Your spec is ready
📋 Product Requirements Document
🎫 GitHub Issues
🤖 CLAUDE.md — AI Context File

Got a different idea? Generate another →

How it works

Three steps. No account. No waiting.

Step 1
Describe your idea
Write a few sentences about what you're building. The more specific you are, the better the output — but even a rough idea works.
Step 2
Click Generate
SpecForge uses Claude to analyze your idea and produce three structured artifacts optimized for AI coding workflows.
Step 3
Paste into your AI tool
Copy CLAUDE.md into your project. Paste the PRD into Cursor's context. Import tickets into GitHub. Start building in seconds.

What you get

Three outputs, all in one generation. All copyable.

Product Requirements Doc
Problem statement, target users, core features, out-of-scope items, success metrics, and technical constraints. Structured and specific — not vague.
GitHub Issues (8–10)
Actionable tickets in verb-noun format, each with acceptance criteria checkboxes, technical notes, and effort estimates. Ready to paste into GitHub.
CLAUDE.md Context File
A complete AI context file: tech stack, architecture decisions, dev commands, naming conventions, MVP scope, and "what NOT to do" for your AI coding tool.
See a real generated example →

Want unlimited specs?

Upgrade to Pro for unlimited daily specs, priority generation, and early access to new features like GitHub export and custom templates.

Get Pro — $9/mo →

Or stay on the free tier — 3 specs/day, no account required.