Getting to Know MissionForge

Turns complex tasks into organized agent teams — shown here with a real example: transforming a process catalog into interactive documentation.

đŸ—ī¸ Company SpawningđŸŽ¯ Zero-Drop Guarantee🌊 Wave-BasedđŸ“Ļ Export as .skill
01

What is MissionForge?

The Problem — By Example

Imagine: You have a process catalog with 40 processes. You want to turn it into interactive documentation where each process is shown as an editable workflow.

If you give this to an AI as one big task: The first 15 processes look great, then it loses track. Process 23 gets missed, formats don't match, quality checks are absent.

The Solution: From Chaos to Company

📄 Process Catalog PDF
→
đŸ—ī¸ MissionForge
→
✅ 40 Interactive Workflows

MissionForge breaks this task into pieces, assigns each piece to a specialized agent, and verifies at the end that all 40 processes are complete and consistent.

What MissionForge Does for You

đŸĸ
Company Spawning
From your task, a complete organization with teams, agents, and rules is created automatically.
đŸŽ¯
Nothing Gets Lost
All 40 processes are captured, assigned, and checked against a checklist at the end.
⚡
Parallel Waves
Independent processes (e.g. Procurement + HR) run simultaneously — up to 3 in parallel.
đŸ“Ļ
Reusable
New process catalog next quarter? Same mission, new document — done.
💡Key insight: MissionForge isn't a process viewer — it's the project manager ensuring 40 agents work on 40 processes and none is forgotten.
02

Live Example: Processing a Catalog

How to Start the Mission

"Spawn a company that analyzes our process catalog document [file], turns each process into an editable workflow, and outputs it as interactive documentation."

What MissionForge Creates

Click "Play" to see how MissionForge processes your request step by step.

MissionForge — Process Catalog
👤
Spawn a company that analyzes our process catalog, turns each process into an editable workflow, and outputs interactive documentation.
đŸ—ī¸
Phase 1 — Analysis: Identified 42 processes in 6 departments: Procurement (8), HR (7), Finance (9), IT (6), Sales (7), Production (5). Creating 14 work packages.
đŸ—ī¸
Phase 2–4: Company spawned. 3 teams, 6 department agents. Skills: Process Extraction, Workflow Builder, Consistency Checker.
đŸ—ī¸
Wave Plan:
🌊 Wave 1: Procurement + HR + IT (3× parallel)
🌊 Wave 2: Finance + Sales + Production
🌊 Wave 3: Navigation + overall structure
🌊 Wave 4: Zero-Drop Audit

👉 Approve?
👤
Yes, go!
đŸ—ī¸
Execution: Wave 1 ✅ (24 workflows) → Wave 2 ✅ (18 workflows) → Wave 3 ✅ Navigation → Wave 4 ✅ Audit passed.
đŸ—ī¸
🎉 Mission complete! 42/42 processes documented. Zero-Drop Audit passed. Export as .skill?

The Wave Plan

WaveWork PackagesAgentsParallel
🌊 1Procurement, HR, IT3 Department Agents3 ×
🌊 2Finance, Sales, Production3 Department Agents3 ×
🌊 3Navigation, linkingIntegration Agent1 ×
🌊 4Zero-Drop AuditQuality Agent1 ×
✨Dependency: Wave 3 only starts when ALL processes from Wave 1+2 are done — so none is missing from the navigation.
03

The 9 Phases in Detail

Click any phase — the process catalog example shows what happens concretely.

1
📋 Task Analysis
Your task is broken into requirements and success criteria.
→ 42 processes, 6 departments, 14 work packages
2
đŸĸ Spawn Company
The "company" is created: directory structure and manifest files.
→ .mission-forge/ with COMPANY.md, 3 teams, 8 agents
3
👑 Orchestrator Hierarchy
Mission Orchestrator delegates to sub-orchestrators.
→ 1 lead, 3 sub-leads, escalation chain to you
4
🔧 Skill Assignment
Available skills are detected, missing ones generated.
→ Process Extractor, Workflow Builder, Consistency Checker
5
🌊 Wave Planning
Work packages are grouped into waves by dependencies.
→ 4 waves, you approve the plan
6
âš™ī¸ Execution
Wave by wave, agents complete their packages.
→ 3 agents in parallel: Procurement + HR + IT
7
✅ Verification
5-level check: individual package to full audit.
→ 42/42 processes verified, format consistent
8
📊 Completion
Final report with results and lessons learned.
→ MISSION-REPORT.md: 42/42 ✅, 0 missing
9
đŸ“Ļ Export
Export the proven company as a .skill file.
→ process-catalog.skill for next quarter
â„šī¸Your checkpoint: Phase 5 shows you the plan — no agent runs until you approve.
04

The Organization — By Example

The Hierarchy

Click any level to see its role in the process catalog project.

👤 You
↓
👑 Mission Orchestrator
↓
📋 Analysis
âš™ī¸ Processing
✅ Verification
↓
🤖 Department Agents

Process Lifecycle

Each of the 42 processes follows this lifecycle — tracked end to end.

OPEN→IN_PROGRESS→DONE→VERIFIED
âš ī¸When Agent-HR gets stuck: After 2 repair attempts, it escalates — up to you. You decide: skip, fix manually, or abort.

The 6 Building Blocks

đŸĸ
COMPANY
"Process Catalog Task Force" — mission, goals, rules.
đŸ‘Ĩ
TEAM
Analysis, Processing, Verification — clear responsibilities.
🤖
AGENT
Agent-Procurement, Agent-HR, Agent-IT — each with dedicated skills.
📁
PROJECT
Groups all procurement processes as a bundle.
📋
TASK
"Process Procurement-03: Supplier approval as workflow"
🔧
SKILL
Workflow Builder, Process Extractor — reusable.
05

Power Features

Scaling

PackagesStructureProcess Catalog
1–2Direct executionOnly 2 processes? No team needed.
3–153 teamsSmall catalog: standard mode.
16–25ExtendedMid-size: 4 waves.
25+Multiple missionsEnterprise: one per department.

Export — Build Once, Use Forever

✅ Q1 done
→
đŸ“Ļ Export
→
â™ģī¸ Q2: new document
"Run process-catalog.skill for the updated Process Catalog Q2-2026.pdf"

5-Level Verification

Level 1
Each process individually: workflow complete?
Level 2
Wave: Do Procurement, HR, IT fit together?
Level 3
Phase: All waves coherent?
Level 4
Mission: Really all 42 documented?
Level 5
Quality: Formats consistent? Navigation OK?
06

Test Your Knowledge & FAQ

Agent-HR fails after 2 attempts on "Onboarding." What happens to the other agents?
Everyone stops — the mission aborts.
HR processes are silently skipped.
Agent-Procurement and Agent-IT keep working. The HR issue escalates to you.
MissionForge automatically creates a second HR agent.
Why does Wave 3 (Navigation) only start after Waves 1+2?
Because only one agent can run at a time.
Because navigation must know ALL processes — otherwise some would be missing.
Because the orchestrator needs a break.
No reason — just a convention.

Frequently Asked Questions

Do I need programming skills?â–ŧ

No. Describe your task in natural language — just like the process catalog example.

What about very large documents?â–ŧ

MissionForge scales: more processes = more waves. Beyond 25+ packages, it splits into missions.

Can I change the plan before execution?â–ŧ

Yes. Phase 5 shows the full wave plan. Nothing moves until you approve.

What if I need this again next quarter?â–ŧ

Export as .skill. Next time: "Run process-catalog.skill for [new PDF]".

What are the prerequisites?â–ŧ

Claude Code or compatible agent runtime. Tools: Bash, Read, Write, Edit.

🎉
You Made It!
You now know how MissionForge turns a process catalog into complete, verified documentation — and how to repeat it next time with a single sentence.