A project contract with V1 scope, non-goals, and guardrails before your coding agent writes code.
Archseed writes the few decisions that matter into the repository, so the next session starts from the same scope.
One outcome you can ship. Everything else waits.
Features and integrations you are not building yet.
Stack and auth choices the agent must not quietly change.
01
Start from one short description. Archseed turns it into the few decisions that have to be explicit before any code is written.
See the prompt
$ archseed init
? 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, continue02
Confirm the V1 outcome, non-goals, open questions, and guardrails. Those choices stay visible instead of getting invented mid-build.
See example plans$ archseed init
? Is authentication required?
Yes
? Are teams or multi-tenant accounts in V1?
No
? What should a coding agent never change or add
without your approval?
✓ Expand features beyond the stated V1 scope
✓ Add third-party integrations03
Read the project contract before Archseed writes it into .archseed/. Scope stays with the repository for the next session.
See the contract│ Final project contract
│
│ V1 outcome: Send and track one proposal
│ Non-goals: Billing, public API, mobile app
│ Open questions:
│ - None
│ Selected guardrails:
│ - Expand features beyond the stated V1 scope
│ - Add third-party integrations
│
? Create .archseed/ with this project contract?
Yes04
Open agent-context.md and start the next session from that file, in the coding agent you already use.
Install the CLI✓ Created .archseed/project-contract.md
✓ Created .archseed/agent-context.md
✓ Created .archseed/implementation-plan.md
✓ Created .archseed/review-checklist.md
│ One next step
│
│ Next: open .archseed/agent-context.md and give it
│ to your coding agent before asking it to implement.The follow-up questions change with the project. These six are complete examples. They are not a full architecture for every category.
Harbor Studio
Spring commissions are open.
Request a visitOne page with a headline, three commissions, and a single request form.
POST /v1/invoices
Authorization: Bearer •••
{
"client": "Harbor",
"amount": 2400
}201 Created
{
"id": "inv_18",
"status": "draft"
}One service. Create and read invoices for a single consumer.
A signed-in desk for writing and sending one proposal.
Clients
New client| Name | Status | Updated |
|---|---|---|
| Harbor Studio | Active | Today |
| Pier house | Active | Mar 2 |
| North room | Archived | Jan 18 |
Create, list, edit, and archive one client record.
Walk notes
Sites today
iOS only. One flow: open a site, add a note, done.
$ seed status ./harbor
3 files ready
0 writes pending
Confirm before seed writes.One command that reads a folder and prints what is ready.
Founder-assisted pilot
Bring one small app idea or a clearly scoped feature. We'll clarify the important decisions together, then I'll use Archseed and personally review your planning package.
Includes one clarification round. Planning only—no coding, implementation, repository audit, or guarantee that a coding agent will follow every decision.
Establish a baseline and run supported checks with Archseed Pro.
What this means
archseed check compared a new file with the baseline. The baseline already names one Badge path, so a second Badge primitive is blocking.
What this does not mean
Archseed did not edit the file. Paths already recorded as inherited debt are not blocking. The check does not refactor source.
$12/month · Founder price stays locked while you remain subscribed.
[BLOCKING] REUSE-001
New duplicate primitive:
src/features/invoices/components/InvoiceBadge.tsx
New file looks like another Badge primitive while `src/components/ui/Badge.tsx` is the canonical shared path.
Required action:
Reuse or compose `src/components/ui/Badge.tsx`. A feature-specific wrapper is allowed only for domain mapping; do not duplicate primitive styles, variants, or behavior.Archseed complements your coding agent. It does not try to replace it.
No. It runs in the terminal you already use. Your editor stays where the code is written.
No. Init writes the contract into .archseed/. Your coding agent writes the application.
No. Quick Start asks you to describe the project, confirm the contract, and approve the files.
Cursor, Claude Code, Codex, Gemini, OpenCode, or a similar tool. Open the handoff file and start there.
No. agent-context.md is an instruction set. It does not block an agent from drifting. Review the plan against the contract.
Yes. It is enough structure to avoid an expensive detour, without a heavy process.
archseed init is for new and early-stage projects and does not require Pro. adopt, adopt scan, and check are Pro features for an existing Next.js and TypeScript repository. They record a baseline. They do not refactor source.
Email m@mateop.com with the project you planned, what became clearer, what was missing, and whether you would return.
The CLI works before you create an account.
$ npm install -g @archseed/cli
$ archseed init
Quick Start — describe, confirm, generate