Archpilot is an open-source agentic pipeline that transforms a single high-level requirement into deep discovery, EARS-compliant requirements, HLD, LLD × N services, and a scored guardrail review — enforced by 36 enterprise rule files.
Each phase is an AI agent with a defined mandate, guardrail rules, and a structured output contract. Every artifact feeds the next phase. The review agent scores the full set against 12 dimensions and gates on 80+.
Every rule file is a structured, LLM-ready document. The pipeline enforces the relevant rules at each phase — or feed them directly to Claude, Kiro, Cursor, or Copilot to enforce standards across your project.
Agentic Era — Rule 50: The pipeline orchestration rule that enforces the 10:10:15:50 mandate — 15+ discovery dimensions, 10–20 Epics, 50–150 Stories, 3–5 LLDs, review score ≥80. This is the rule that gates the full pipeline run.
Spec-Driven Development treats the specification as the primary source of truth. Code becomes a derivative artifact — regenerable, verifiable, and always aligned with the approved design. The pipeline enforces this contract at every phase.
WHEN / IF / WHILE / WHERE / Ubiquitous — five patterns that make every requirement unambiguous, testable, and directly mappable to implementation tasks. Every story in Phase 1 must be EARS-compliant or the pipeline fails.
Every story traces forward to an HLD component, an LLD service, and a test. The review agent validates this chain. No requirement ships untested. No code ships unspecified.
The lint tool scans all artifacts for deferred text before any artifact is accepted. 10:10:15:50 mandates are machine-checked, not human-eyeballed.
Five sentence patterns enforced by the pipeline on every story in Phase 1. Non-compliant stories block progression to Phase 2.
| Pattern | Template | Example |
|---|---|---|
| Ubiquitous | The [system] shall [action]. | The Payment Service shall use TLS 1.3 for all inter-service communication. |
| Event-Driven | When [trigger], the [system] shall [action]. | When a user submits valid credentials, the Auth Service shall issue a signed JWT within 200ms. |
| State-Driven | While [state], the [system] shall [action]. | While the mobile app is offline, the system shall queue operations and sync on reconnection. |
| Unwanted | If [condition], then the [system] shall [action]. | If the Payment Gateway returns 5xx, then the service shall retry 3 times with exponential backoff. |
| Optional | Where [feature enabled], the [system] shall [action]. | Where multi-tenancy is enabled, the API shall enforce tenant-scoped data access on every request. |
Archpilot is model-agnostic and tool-agnostic. The pipeline runs natively in Claude Code. Each platform also gets a dedicated configuration file pre-tuned to its instruction format.
archpilot run — Claude Code acts as each phase agent directly. No API key needed. Highest output quality.Initialize a project, write your requirement, and run the pipeline. Six production-grade artifacts generated in one session.
From greenfield pipeline runs to individual rule enforcement — Archpilot covers every stage of the architecture lifecycle.
archpilot run. Receive six production-grade artifacts: discovery, requirements, HLD, 3–5 LLDs, and a scored review report — all lint-clean.A complete pipeline run against a real enterprise requirement. Eight production-grade artifacts generated from a single Input.md. Score: 94.1/100.
Stop letting AI guess your standards. Give it 36 rules, 15 discovery dimensions, and a scored guardrail gate — then watch it produce architecture that passes your ARB.