Mainspring Docs

Product Requirements Document (PRD)-first AI coding agent orchestration for production-grade software delivery. Turn intent into reviewed, auditable work.

Start with the Operator Guide, then use the Method and Competitive Analysis to understand why the workflow exists. The Product Requirements Document (PRD) and Maintainer Playbook are published as auditable project truth, not as the first thing a new operator needs to read.

Documentation

• Operator Guide - Install, start, observe, recover, and configure Mainspring.
• Method - The Product Requirements Document planning method Mainspring uses on itself.
• Competitive Analysis - Market map, 1000-point scoring, gaps, and positioning strategy.
• Architecture - Extension boundaries for engines, backlog sources, and ledgers.
• Metrics Schema - JSONL ledger fields and analytics contract.
• Product Requirements - Canonical plan, release checklist, and backlog truth.
• Maintainer Playbook - Maintainer rituals for executing this repository’s Mainspring PRD.

Release Truth

The PRD remains the source of truth. This site is a published view of committed docs, not a separate planning surface.