Forge workflows

Governed paths, not blank prompts.

Instead of starting from a blank prompt, Forge routes each request to a workflow — an ordered sequence of governed steps that runs the same way across every engineer and every session. Workflows adapt to the task, so only the steps a job needs actually run. These are Forge's built-in defaults; open any workflow to see its typical path.

Every workflow — and every step inside it — can be enabled, disabled, reordered, or customized for your team in the Forge dashboard.
Planning

Shape and scope the work before any code is written — discovery, definition, PRDs, and readiness.

Product Discovery
Early-stage research without committing to a ticket — check existing work, gather context, frame the problem, score impact, and produce rough estimates.
Steps
  1. Check for existing work
  2. Gather context from connected docs
  3. Analyze roadmap fit
  4. Frame the problem
  5. Clarify the idea
  6. Score impact (RICE)
  7. Produce a rough estimate
Define a Feature
Product definition end-to-end — discover, clarify, write the problem statement, collect NFRs, RICE-score, generate a PRD, create the tracker ticket, and hand off to engineering.
Steps
  1. Check for existing work items
  2. Gather background context
  3. Clarify requirements
  4. Collect non-functional requirements
  5. Write the problem statement
  6. Score impact (RICE)
  7. Preview & create the tracker work item
  8. Generate the PRD
  9. Build the tech handoff plan
Design

Map the system and shape the technical approach for an existing work item.

Explore Architecture
Scan the system architecture and conduct an interactive discussion to map services, boundaries, and key decisions for an existing work item — no new ticket is created.
Steps
  1. Scan the system architecture
  2. Interactive architecture discussion — record decisions
Development

Turn a ready work item into shipped code, wave by wave.

Implement a Feature
Execute the engineering phase on an existing tracker work item — receive handoff, review stories, plan branches and dependencies, implement wave by wave, open PRs, and complete delivery.
Steps
  1. Receive the engineering handoff
  2. Readiness check
  3. Break the work into stories
  4. Plan dependencies & implementation waves
  5. Analyze change impact (blast radius)
  6. Technical discovery
  7. Define the test strategy
  8. Implement wave by wave
  9. Review the PR
  10. Complete & summarize delivery
Testing

Verify quality before and after the change lands — test strategy and structured PR review.

QA Test Planning
Plan a test strategy without writing code — AC quality, story coverage, change-impact surface, and test types mapped per acceptance criterion.
Steps
  1. Fetch the work item
  2. Readiness check
  3. Check AC quality & testability
  4. Review stories (INVEST)
  5. Analyze change impact
  6. Technical discovery
  7. Define the test strategy
Review a Pull Request
Structured pull request review — branch freshness, automated analysis, AC traceability matrix, OWASP security scan, customer impact, and manual deploy tasks.
Steps
  1. Fetch the work item
  2. Check branch freshness
  3. AI-augmented PR review — analysis, AC traceability, OWASP scan
  4. Customer impact analysis
  5. Surface manual deploy tasks
Maintenance

Capture and resolve defects end to end.

Fix a Bug
Complete bug lifecycle — capture, triage, create ticket, optional engineering handoff, fix, review, and ship.
Steps
  1. Capture the bug — severity, area, reproduction
  2. Preview & create the ticket
  3. Hand off to engineering
  4. Implement the fix (optional)
  5. Review the PR & surface deploy tasks (optional)
Track & manage

Stay on top of work already in flight — status, documentation, and edits.

Check Work Item Status
Read-only status snapshot of a tracked work item — progress, acceptance criteria, PR health, and prior Forge activity.
Steps
  1. Fetch the work item
  2. Report status — progress, acceptance criteria, PR health
Gather Work Item Documentation
Fetch all documentation attached to a tracked work item — PRDs, design docs, tracker comments, and linked Confluence/Notion pages — categorized by artifact type.
Update Work Item
Direct field edit on an existing tracked work item — title, description, acceptance criteria, priority, assignee, labels, and status.