Coding
Spec intake to RFC, ADR, and ticket breakdown
Turn a product brief, customer request, or Slack thread into a repo-aware RFC with acceptance criteria, ADRs, test strategy, and implementation tickets.
[ workflow / coding ]
Spec intake to RFC, ADR, and ticket breakdown
Cosmos turns ambiguous intake into implementation-ready work. It gathers product context, searches the codebase for similar changes, identifies impacted systems, drafts the RFC or ADR, decomposes the work into tickets, and routes the package for human approval before any code is written.
09 nodes
08 edges
Brief · epic · Slack request
Customer evidence · designs · prior PRs
Repo search + ownership graph
Goals · risks · acceptance criteria
Decision
Architecture decision needed?
Dependencies · tests · owners
Decision
Architecture decision needed?
Dependencies · tests · owners
Options + recommendation
Workflow prompt
Paste this into Augment to reproduce the workflow end-to-end.
Cosmos, whenever a product brief, customer escalation, Linear epic, Jira issue, or Slack request is marked ready for engineering intake, build an implementation-ready planning package. Pull the source request, related customer evidence, linked designs, similar prior PRs, and affected code areas. Draft an RFC with goals, non-goals, user stories, technical approach, risks, acceptance criteria, telemetry requirements, and rollout plan. If the work changes architecture or ownership boundaries, draft an ADR with options considered and the recommended decision. Break the work into sequenced tickets with dependencies, test expectations, and suggested owners. Post the package for product and tech-lead approval before starting implementation.