archways.
4Install Archways
Docs
PatreonBuy Me a Coffee
Documentation for coding agentsUse either tool. Or both.
CAPSTONE+QUARRY

Give your coding agent context across repositories.

Capstone documents your codebase and guides feature development. Quarry makes those references searchable across repositories.

Start with one repository and ask a question about its code. Add other repositories when you need them.

Start with one repository
Document a repo. Query across repos.
BUILD STRONGER FOUNDATIONSarchways.

The stack: Capstone and Quarry, working together.

Install Archways

npx skills add GentBajko/capstone && cargo install --locked --git https://github.com/GentBajko/quarry --rev 78c71fab5f5818662dc02d5867246cec963567a9
Node/npm, Git 2.30+, Bash, Rust 1.85+ and a C toolchain. Select all Capstone skills, including core.Installation guides ↗

Free & open source. Docs stay in Git.

Watch the tools in action

See what each tool does.

Capstone

Document your code.
Plan and implement changes.

Agent skills that write architecture docs with source links. Start with an existing repo, or use a guided feature workflow with a plan you approve.

Download video ↓
Quarry

Query documentation
across repositories.

A CLI that indexes committed references in a shared Git repo. Search locally, trace documented dependencies, and compare contract fields without a model.

Download video ↓
How they work together

Use other repos’ context
in your next change.

With Quarry configured, Capstone can consult other services’ documented interfaces as it defines and plans a feature.

  1. 01
    CAPSTONE

    Document the code.

    Generate a reference for each repository, with architecture, business rules, and source links.

  2. 02
    QUARRY

    Share the references.

    Import docs from the source default branches into a shared Git repository and local index.

  3. 03
    CAPSTONE + QUARRY

    Plan with dependencies.

    Capstone queries relevant interfaces in Quarry and brings those constraints into the feature plan.

  4. 04
    YOU + CAPSTONE

    Approve and implement.

    You review the plan. Capstone implements the approved change, verifies it, and refreshes affected docs.

  5. 05
    QUARRY

    Publish the update.

    After the docs reach the default branch, run quarry update. Other repositories can sync the new reference.

An example change across repositories

For example

“Add CSV support
to ingestion.”

Quarry shows the documented path from ingestion to storage to reports. The storage service lists JSON and XML. Capstone includes that constraint in the CSV feature plan, then refreshes the docs after implementation.

The next change can use the updated reference.
Ingestion → storage → reportsEXAMPLE
$ quarry docs deps ingest-api --downstream --depth 2
ingest-api
└─ sqs file-ingest → record-store
   └─ http GET /records → report-builder
$ quarry docs section record-store "file-ingest (v2)"

# JSON and XML are documented; coordinate CSV support.

› /capstone:feature add CSV ingest support

# Approve the plan, implement, then merge updated docs.

$ quarry update

Try it in one repository.

After installing Capstone, open an existing repo in your coding agent. Generate its reference, then ask about the code. Add Quarry when you need other repositories’ docs.

In your coding agent/capstone:map

Then ask: “Where is authentication enforced? Use the reference and cite the source files.”