InnovaticInnovaticDocs
Work Modes

Specforge Mode

Transform ideas into actionable specs. Specforge turns a vague need into a structured Epic and Stories ready for agents.

Transform ideas into actionable specs.

Specforge takes a vague idea — even a half-formed one — and guides it through a structured process to produce a complete Epic and a set of user Stories. The result is a spec ready to hand off to Feature agents or a dev team.

What it does

Specforge is a five-phase structured conversation. It asks the right questions, helps you think through scope, negotiates the MVP boundary, and crystallizes everything into markdown spec files. You don't need to arrive with a polished request — Specforge is designed to handle the raw and the uncertain.

When to use it

  • You have an idea but no spec yet
  • A product requirement is vague and needs structure before anyone writes code
  • You want to scope a feature before assigning it to a Feature agent
  • You're preparing work for parallel agents and need independent, actionable Stories
  • You want to negotiate an MVP scope before committing to a full build

Don't overthink your initial prompt. Give Specforge the raw idea. It's built to handle vague — the structure comes out of the conversation, not from you arriving with answers.

How it works

Specforge runs through five phases, each tracked in the sidebar:

  1. Discovery — the agent reads your codebase to understand the existing context, constraints, and patterns relevant to your idea.
  2. Clarification — a structured Q&A to fill in the unknowns: who uses it, what does success look like, what's out of scope.
  3. Structuration — the idea is transformed into an Epic with a set of candidate Stories.
  4. Negotiation — the MVP scope is defined. Which Stories are must-haves? Which are deferred? The agent helps you make that call.
  5. Crystallization — the final output: an Epic file and individual Story files written to your project's spec directory.

Key features

  • Five-phase structured process — each phase has a clear goal; progress is visible in the sidebar
  • Structured Q&A — targeted questions that surface the right decisions without overwhelming you
  • Epic + Stories output — actionable markdown files ready to use as agent tasks
  • MVP scope negotiation — helps you decide what's in and what's deferred for this iteration
  • Kanban integration — Stories can be pushed directly to your project board

Tips

Specforge works best when you let it ask questions rather than trying to answer everything upfront. The Q&A phase exists precisely because good specs come from dialogue, not monologue.

The Stories produced by Specforge are designed to be independent — each one can be assigned to a separate Feature agent and run in parallel.

On this page

On this page