Archseed

Documentation

Install the CLI and generate agent-ready context.

Archseed Founder Beta runs in your terminal. Install @archseed/cli, run archseed init, then use .archseed/agent-context.md with your preferred coding agent.

Current version

v0.2.1

Current offer

Founder Beta — $12/month

Install CLIRelease log

Quickstart

Six steps to your first architecture files.

Install @archseed/cli, run archseed init, then archseed review before handing off to your coding agent.

  1. 1

    Install the CLI

    Requires Node.js 18+. Install globally with npm, pnpm, or bun. No account required to run the Free interview.

    npm install -g @archseed/cli
  2. 2

    Verify the install

    Confirm the binary is on your PATH.

    archseed --help
  3. 3

    Run archseed init

    Answer focused questions about V1 scope, non-goals, decisions, assumptions, and validation. Name a concrete Preferred stack when you know it—or write flexible.

    archseed init
  4. 4

    Open .archseed/

    The CLI creates a folder named after your project (e.g. ./invoice-api/). Context lives in .archseed/. Start with agent-context.md.

  5. 5

    Review readiness, then code

    Check the CLI readiness summary and any blockers in architecture.md. Optionally run archseed review on the project folder to check plan quality—not your source code.

    archseed review
  6. 6

    Give your coding agent the context

    Open the project in Cursor, Claude Code, Codex, Gemini, OpenCode, or another agent. Attach .archseed/agent-context.md (and architecture.md when needed). Ask the agent to stay inside V1 scope and non-goals.

  7. 7

    Record decision changes

    When a major choice changes, append a new entry in decision-log.md—do not overwrite the original reason. Guardrails.md is recommendations only; nothing is installed or enforced automatically.

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

Runs an interactive interview and writes files to a folder named after your project (e.g. ./invoice-api/). For the extended interview, use archseed init --pro.

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.2.1).

archseed --version

archseed init

Interactive Free interview. Creates a project folder with responses.json and .archseed/ (architecture, implementation plan, agent context, decision log, guardrails).

Run from the directory where you want the project folder created.

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 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 ./invoice-api

archseed review --pro

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

archseed review --pro ./invoice-api

First run

What a session looks like.

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

terminal
$ archseed init
— Project context —
? Project name
  invoice-api
? What is the smallest useful version of this project?
  Freelancers can create and mark one invoice paid
? What must this project explicitly not do in v1?
  Payroll, multi-tenant admin, mobile apps
— Decisions and constraints —
? Decisions locked before coding?
  Auth — email magic link because freelancers hate passwords
✓ Generated responses.json
✓ Generated .archseed/architecture.md
✓ Generated .archseed/implementation-plan.md
✓ Generated .archseed/agent-context.md
✓ Generated .archseed/decision-log.md
✓ Generated .archseed/guardrails.md
Readiness summary
  Ready: 8
  Accepted assumptions: 1
  Deferred decisions: 2
  Blockers: 0
Next: Review .archseed/agent-context.md before asking your coding agent to implement.

Files are written to a folder named after your project (e.g. ./invoice-api/). Open handoff/README.md first, then pass the package to your coding agent.

Project handoff package

Implementation-ready artifacts, one clear plan.

Every session produces core docs plus a handoff/ folder to orient developers and coding agents. Content depth depends on your plan and method.

responses.json
Raw interview answers from archseed init. Kept as a sidecar for regeneration and review compatibility.
.archseed/architecture.md
Full source of truth: V1 scope, non-goals, decision lock-ins, assumptions, edge cases, integrations, validation, and readiness.
.archseed/implementation-plan.md
Ordered phases with acceptance criteria, dependencies, and explicitly deferred work.
.archseed/agent-context.md
Concise brief for your coding agent: goal, scope, non-goals, active decisions, protected areas, guardrails, and acceptance criteria.
.archseed/decision-log.md
Append-only record of important decisions and why they were made, plus a change template.
.archseed/guardrails.md
Recommended checks and policies for project risks. Recommendations only—nothing is installed or executed automatically.
.archseed/review-report.md
Optional. Generated by archseed review when you run it. Spec/plan quality notes—not a code review.

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.2.1
Binary
archseed
Adopt
Upcoming private beta — apply at /adopt

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 AI IDE or coding-agent replacement
  • Not a general code generator
  • Not a fully automated PR-review product
  • Not mature architecture enforcement today
  • Not public existing-repository analysis today
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?
Open the generated project folder. Attach or @-mention .archseed/agent-context.md (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 a project folder named after your project (e.g. ./invoice-api/). responses.json sits at the root; the five context artifacts live under .archseed/.
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?
cd into the project folder (or pass the path) and run archseed review. Add --pro for the full Pro review. Output lands under .archseed/review-report.md when that folder exists. 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