Intake
Context Engine
Ingests whatever you have — a rough spec, a ticket, a Figma mockup, a doc — and reconciles every claim against the actual repository.
Large Projects
The quarter-long project becomes a design you approve and PRs that merge.
Take a large feature from a rough spec to shipped code with a fleet of agents working as one.
Cosmos turns your objective into a repo-grounded design doc, gets it reviewed by your team, then orchestrates a fleet of agents that carries the implementation to merge.
cosmos / projects / usage-metering-v2
usage-metering-v2.designapproved by @eng-leads
- 01problem · goals · success criteriaproduct
- 02architecture · affected componentscontext engine
- 03rollout · flags · test plantechnical
- 04implementation briefworker agents
Implementation · one-shotdesign → 1 PR · worker pr-author-02 · isolated env
- design-docapproved · @eng-leads
- feat/usage-metering-v2pr-author · 3,214 loc
- pair-reviewverifying vs design
- ci · integration teststests · 312/340
- #eng-projectsslack ping on ready
Every PR is verified against the approved design14:07 UTC
Meet Cosmos
A fleet of agents behind every project.
Agents already write the code, review the PRs, and investigate the incidents. Large projects still stall in everything around the code: settling the design, deciding what to build in what order, and keeping the work aligned with the objective. Cosmos hands that layer to the fleet — the design grounded in your repo, the implementation orchestrated to merge.
How the work changes
Hours
From rough spec to a reviewable design doc
1
Human checkpoint before implementation begins
100%
Of PRs verified against the approved design
0
Coordination meetings on the critical path
One fleet takes the project from objective to merged.
Cosmos runs the whole arc. The Context Engine distills your starting point into a working understanding, the Planner writes the design doc your team approves, PR Authors take self-contained briefs and implement, and the review fleet verifies every draft against the design before a human ever looks.
Project lifecycleone design, end to end
Intake
Context Engine
Ingests whatever you have — a rough spec, a ticket, a Figma mockup, a doc — and reconciles every claim against the actual repository.
Design · Approval
Project Planner
Drafts one design covering product and technical: goals, architecture, affected components, alternatives, rollout, and test plan — grounded in the real repo.
Human
Reviews and approves the design. Nothing gets implemented until sign-off.
Build · orchestrated
PR Authors
Take self-contained briefs — the design sections, the target repo, the definition of done — then implement, respond to review comments, and fix CI.
Review
Review Fleet
Verifies every draft against the approved design before pinging the team on Slack. Humans make the merge decisions.
Feature merged · design is the record
Approved Design
The source of truth · Every brief and review checks against it
Fig 1 · Project fleet
How the project runs
Review the design, not the diff.
The design doc is where human judgment enters — you iterate on it with Cosmos, and nothing gets implemented until it's approved. Small PRs were always a workaround for human review bandwidth. With the design already approved and the review fleet on every diff, one coherent change beats several agents stitching together partial context.
The meeting-driven model
Built around coordination
- Weeks of alignment before the first commit
- Design lives in heads and stale documents
- Small PRs stitched together from partial context
Cosmos projects
Built around the design
- Design doc grounded in the actual repository
- One human checkpoint: approve the design
- The fleet carries PRs through CI and review to ready
- Coherent changes verified against the design
Where projects start
Built for the projects that used to stall.
If the work spans more systems than one ticket can hold, it runs better design-first. Three places teams start.
New features01
From PRD to production.
Feature work that spans several systems. Cosmos ingests the PRD or the mockup, designs across every affected component, and ships it as one coherent, reviewed change.
SCOPE: objective → design → 1 PR
New services02
Greenfield, on your conventions.
Standing up a new service without inventing a new architecture. The Context Engine grounds the design in the patterns and infrastructure you already run, down to the rollout and flagging strategy.
SCOPE: new service · design + rollout plan
Platform capabilities03
Rollouts that respect dependencies.
Capabilities that touch every team. The ticketed path breaks the approved design into dependency-ordered units in Linear or Jira, one PR per unit, with humans wherever audit or rollout requires.
SCOPE: design → 14 tickets · ordered
LinearJiraFigmaSlackGDPR · CCPA · HIPAA
Highly customizable to your workflow.
Talk to Cosmos Advisor to shape the fleet around your team: what the design must cover, who approves it, and how the work ships. Keep your VCS, your CI, and your compliance posture.
One-shot a single coherent PR, or take the ticketed path: dependency-ordered units filed in Linear or Jira, one PR per unit, and humans in the loop wherever audit or rollout requires.