ArchSeed
Docs menu

Documentation

Install the CLI and create a project contract.

Describe your project, confirm the decisions that matter, then give .archseed/agent-context.md to Cursor, Claude Code, Codex, Gemini, OpenCode, or another coding agent before implementation.

Current version

v0.3.2

Current offer

Founder Beta — $12/month

Install and run archseed initCLI safety

Quickstart

Quick Start: describe, confirm, then hand off context.

Install @archseed/cli, run archseed init, confirm the V1 boundary, then give .archseed/agent-context.md to your coding agent before implementation.

  1. 1

    Create or enter the project directory

    archseed init writes .archseed/ into the current directory.

    mkdir my-project
cd my-project
  2. 2

    Install the CLI

    Requires Node.js 18+. No account required for Quick Start.

    npm install -g @archseed/cli
  3. 3

    Run archseed init

    Describe the project in your own words, confirm the V1 boundary and a few relevant decisions, review the contract, then approve file creation.

    archseed init
  4. 4

    Review the generated project contract

    Start with .archseed/agent-context.md. Use project-contract.md for the full source of truth.

  5. 5

    Give the context to your coding agent

    Ask the agent to propose the smallest plan that satisfies the V1 outcome and to ask before inventing open decisions. Review plans against the contract — instructions are not runtime enforcement.

Install

Install the CLI.

Requires Node.js 18+ and a package manager. Pick npm, pnpm, yarn, or bun — then verify with archseed --help.

Package manager

Install

npm
npm install -g @archseed/cli

Update

npm
npm install -g @archseed/cli@latest

Verify

Help
archseed --help
Version
archseed --version

Start a project

archseed init

Run from inside your project directory. Describe the project, confirm the contract, then approve creation of .archseed/. Start with .archseed/agent-context.md. Nothing is written until you confirm.

Commands

Full CLI reference.

Everything you can run after installing @archseed/cli. Binary name: archseed.

archseed --help

Show all commands and global options.

archseed --help

archseed --version

Print the installed CLI version (current publish: 0.3.2).

archseed --version

archseed init

Quick Start: project type, one project description, confirm the contract, targeted follow-ups, guardrails, then create .archseed/ after you approve (project-contract, agent-context, implementation-plan, review-checklist).

Run from inside your project directory. Refuses if .archseed/ already exists. Nothing is written before final confirmation.

archseed init

archseed init --pro

Extended Pro discovery (domain, integrations, method). Requires archseed login + Pro plan.

Create a Clerk user API key in your account, then: archseed login --token <key>

archseed init --pro

archseed adopt

Pro. Adopt an existing Next.js + TypeScript repository: scan signals, decide target conventions, write .archseed/ baseline. Does not refactor source code.

Requires archseed login and an active Pro plan. Next.js + TypeScript only. Other stacks exit with a clear no-change message.

archseed adopt

archseed adopt scan

Pro. Scan-only mode. Prints a signal report and saves .archseed/adopt-inventory.json without running the decision interview.

Requires archseed login and an active Pro plan.

archseed adopt scan

archseed check

Pro. Check changed files (or a path) against Adopt baseline decisions. Distinguishes inherited debt from new repetitions.

Requires Pro, plus .archseed/baseline.yml from a prior adopt. Exit code 1 only for blocking issues.

archseed check src/features/invoices/InvoiceBadge.tsx

archseed sync

Sync .archseed/ pointers into CLAUDE.md, AGENTS.md, and .cursor/rules/archseed.mdc when Cursor is detected. Preserves user content outside Archseed markers.

Does not install Git hooks, CI, or automatic checks. Run archseed check manually before meaningful commits.

archseed sync --dry-run

archseed login

Open the browser to authorize the CLI. Polls until you click Authorize on archseed.co.

Fallback: archseed login --token <key>. Credentials stored under ~/.config/archseed (or %APPDATA%\archseed).

archseed login

archseed login --token <key>

Paste a Clerk user API key instead of using the browser flow.

archseed login --token ak_...

archseed whoami

Show the logged-in user id and Free/Pro plan.

archseed whoami

archseed logout

Remove saved CLI credentials.

archseed logout

archseed review

Review an existing project package (spec/plan quality) and write .archseed/review-report.md when .archseed/ exists. Does not scan implemented source code.

Run after init (before coding), or after you edit the markdown artifacts. This is not an automated code reviewer.

archseed review

archseed review --pro

Full Pro spec review (deeper risk checks). Requires login + Pro plan. Still reviews docs, not code.

archseed review --pro

First run

What a session looks like.

ArchSeed asks concrete questions—not open-ended prompts. Your answers shape the generated files.

terminal
$ archseed init
Quick Start — describe, confirm, generate
? What kind of project is this?
  SaaS / dashboard
? Describe what you want to build.
  Next.js SaaS for freelancers to send proposals…
? Does this project contract look right?
  Yes, continue
✓ Created .archseed/project-contract.md
✓ Created .archseed/agent-context.md
✓ Created .archseed/implementation-plan.md
✓ Created .archseed/review-checklist.md
Next: open .archseed/agent-context.md and give it to your coding agent

Quick Start writes four files under .archseed/ after you confirm. Start with .archseed/agent-context.md.

Project contract package

A clear source of truth before implementation starts.

Archseed creates a project contract your coding agent can read before it plans or implements: V1 outcome, boundaries, open questions, and explicit guardrails.

.archseed/project-contract.md
Approved source of truth for outcome, scope, non-goals, decisions, assumptions, and open questions. Uses Confirmed / Open / Suggested evidence status.
.archseed/agent-context.md
Start here. Working instructions for Cursor, Claude Code, Codex, Gemini, OpenCode, or another coding agent. Not runtime enforcement — review plans against the contract.
.archseed/implementation-plan.md
Phased plan derived only from the confirmed contract. Uncertain areas are validation points, not invented facts.
.archseed/review-checklist.md
Review questions for scope alignment, non-goals, guardrails, testability, and unresolved assumptions.

Methods

Pick a workflow for your project type.

Simple Project is free. Advanced methods require Pro.

  • Simple Project

    free

    Focused beta workflow for MVPs, SaaS, CRUD apps, and client features. Progressive disclosure—not an enterprise questionnaire.

  • Harness Architecture

    pro

    Structures agent-assisted work with explicit boundaries and conventions.

  • TDD Architecture

    pro

    Behavior specs and test boundaries defined before implementation.

  • Clean Architecture

    pro

    Explicit domain, use case, and adapter layers for maintainable codebases.

Select a method with --method on init. See pricing for Pro methods.

Release log

Offer and version history.

Public record of the current Archseed offer and CLI version. Newest entries appear first.

2026-09-13

Current

Founder Beta — Peerlist Launchpad

Architecture-first, CLI-first, IDE-agnostic workflow for clarifying scope, non-goals, architecture, and constraints before you build with a coding agent.

Offer
Founder Beta — $12/month
Price lock
Locked while you remain subscribed
CLI package
@archseed/cli
CLI version
0.3.2
Binary
archseed
Adopt
Pro — archseed adopt, scan, and check

Includes

  • Guided discovery for new and early-stage projects
  • V1 scope and non-goal definition
  • Architecture decisions and technical constraints
  • Structured project artifacts and agent-ready context
  • Simple Project mode for focused builds

Does not claim

  • Not an IDE or coding-agent replacement
  • Not a general code generator
  • Not a fully automated PR-review product
  • Not runtime enforcement of agent behavior today
  • Adopt does not refactor source or analyze stacks other than Next.js + TypeScript
Join the Founder Beta

FAQ

Common questions.

Do I need the web app?
No. Install the CLI and run projects from your terminal. The web app is only for account and billing management.
What are the CLI requirements?
Node.js 18+ and npm, pnpm, or bun. Install with npm install -g @archseed/cli, then run archseed --help.
What's the difference between init and init --pro?
archseed init is Free and works offline with no sign-in. archseed init --pro requires archseed login and an active Pro subscription. It asks extended questions (domain, integrations, method) and goes deeper on decisions and edge cases.
Does init ask about tech stack?
Yes. You answer Preferred stack (runtime, framework, database—or flexible). Be concrete when you already know the stack (e.g. Next.js + Postgres + Clerk). Use flexible only when you want stack decisions deferred.
How do I use the output with Cursor or another coding agent?
Give .archseed/agent-context.md to your coding agent before implementation (and architecture.md when needed). Tell the agent: Stay inside V1 scope and non-goals. Do not modify protected areas without a decision change. Ask before inventing a critical requirement. Record major deviations in decision-log.md.
Where are the generated files?
In the current project directory. The five context artifacts live under .archseed/. responses.json sits at the project root as a sidecar for regeneration and review.
Does ArchSeed install Knip, Stryker, or other tools?
No. guardrails.md only recommends checks for your risks. Nothing is installed or executed automatically in the beta.
How do I review a package I already generated?
From the project directory that contains .archseed/, run archseed review. Add --pro for the full Pro review. Output lands under .archseed/review-report.md. This checks plan quality before coding—not your source code.
Is this a coding assistant?
No. ArchSeed runs before you code—it helps you define scope, decisions, and agent-ready context. Use a coding agent afterward with the generated files.
Can I use the output with any coding agent?
Yes. Output is plain markdown. Use agent-context.md with Cursor, Claude Code, Codex, Gemini, OpenCode, or any agent that can work from project context.
How do I update the CLI?
Run npm install -g @archseed/cli@latest, then confirm with archseed --version.
Will there be a VS Code extension?
Planned for later. Today the CLI and local markdown files are the full workflow.

Ready to clarify your next project?

Install the CLI and run Archseed on a real early-stage project. Join Founder Beta when you are ready to ship with the workflow.

Install CLIJoin the Founder Beta

Install

npm
npm install -g @archseed/cli