ArchDocs
Start free

Connect the tools where the work happens

Review the design alongside pull requests, checks and linked issues from the tools your team uses. GitHub supplies pull request and check data, Linear tracks execution, and MCP gives coding clients the same record.

Plans: GitHub and Slack on Team and above. Linear and cloud import on Business and Enterprise. MCP on every plan.

DD-0021 · Shorter tender window for API carriers

Connected record

  • Pull request #482 · Merged · CI passed

    Checked via GitHub
  • Issue DSP-122 · Channel tag in Carrier Gateway · Done in Linear

    Linear statusEarly access

    Done in Linear does not ship or verify the design doc

  • Recorded change · Per-channel tender window · Recorded by Priya Raman

    Person-reported

Each fact keeps its source. The reviewer decides what they add up to.

One design doc, its pull request, check and issueRecreated from Archdocs views with sample data.

See pull requests beside the plan

Read GitHub pull requests and checks beside recorded changes.

Keep execution linked to the design

Link Linear issues to the design doc and send review updates to Slack.

Start from your deployed resources

Import cloud resources as objects that MCP clients can read.

Every connection and its plan

GitHub

Posts the "archdocs / docs drift" check on pull requests when mapped paths change. Answers @archdocs questions in pull request comments. Syncs a YAML doc from a repository on push. On Business and Enterprise, links pull requests and their CI checks to design docs as evidence.

Plans: Team and above; design doc evidence on Business and Enterprise.

Linear

Early access

Links issues and projects to design docs. Drafts issues from an approved plan for a person to confirm. Adds issue cards to diagrams. Linear owns execution; an issue marked Done never approves, ships or verifies a design doc.

Plans: Business and Enterprise.

Slack

Link unfurls, /archdocs search, and channel or direct messages when docs are created or updated and when reviews are requested, approved or sent back.

Plans: Team and above.

Cloud providers

Import from AWS (including Organizations), Azure, GCP, Kubernetes and Terraform state, with scheduled sync.

Plans: Business and Enterprise.

MCP clients

Claude Code, Codex, Cursor, VS Code and other remote MCP clients read and add to the record.

Plans: Every plan.

Embeds

Live embeds in Notion and Confluence, images for READMEs, and link unfurls.

Plans: Every plan for public; Team and above for private.

Bring pull request state into the design record

GitHub supplies pull request state, checks, commits and changed file paths. Link that data to the design doc so a reviewer can see the evidence beside the plan.

  • The "archdocs / docs drift" check flags mapped docs for review
  • Ask @archdocs questions in pull request comments
  • Sync a repository YAML doc on push

Plans: GitHub on Team and above. Linked pull requests and CI checks as design doc evidence on Business and Enterprise.

Linked pull requests and GitHub checks

Keep execution with the issue tracker

Link issues and projects to design docs. Draft issues from an approved plan, then let a person confirm them. Issue cards can also sit on diagrams.

  • Linear owns execution
  • An issue marked Done never approves, ships or verifies a design doc
Early access

Plans: Linear on Business and Enterprise.

Linear setup and limits

DD-0021 · Shorter tender window for API carriers

Work in Linear

Project: Shorter tender window

  • DSP-121

    Per-channel tender window

    Done

  • DSP-122

    Channel tag in Carrier Gateway

    Marked done by the agent

  • DSP-123

    Late acceptance handling

    Waits on Q1

Draft issues from an approved plan need a person to confirm.

A design doc linked to execution in LinearRecreated from Archdocs views with sample data.

Start a diagram from connected resources

Import cloud resources and use scheduled sync to keep the imported resource record current.

  • AWS, including Organizations
  • Azure and GCP
  • Kubernetes and Terraform state

Plans: Cloud import and scheduled sync on Business and Enterprise.

Cloud resources imported into Archdocs

A clear job for each tool

Archdocs owns technical design and verification records. Archdocs does not read your code.

Archdocs

Technical design, architecture and verification records.

Linear

Execution through issues and projects.

GitHub

Pull request and check data, commits and changed file paths.

Screenshots are from a sample workspace. Recreated views are labeled.