You keep re-explaining your project.

sequo.app · 2026-08-20 · by Long Nguyen ·generic
You keep re-explaining your project; your agent keeps forgetting it. Sequo writes the plan and the decisions into files you keep in your repo, then hands you one prompt per step.

You keep re-explaining your project.

YOUR REPO

▾ docs/

idea.md

specification.md

architecture.md

development-plan.md

decisions.md

invariants.md

coding-standards.md

CLAUDE.md

AGENTS.md on Codex

Sequo writes these, plus a prompt for every step. Your agent writes the code.

docs/ ·7CLAUDE.mda prompt per step

1

You keep re-explaining your project.

2

Your agent keeps forgetting it.

3

Sequo writes the plan and the decisions into files you keep in your repo, then hands you one prompt per step. Every prompt names the files to read first, so you stop being the one who remembers.

Describe your project idea

idea.mdplain english · 1–2 sentences

1

▍ a gym session tracker for my climbing gym

no account until the plan is writtenWrite the plan⌘↵

Your idea stays yours, account or not — we don’t show it to other users, use it in marketing, or train on it, and we delete it if you ask. Privacy policy

§ 02

How it works

01

Describe your idea

One or two sentences in plain English. No template, no form to fill in.

docs/idea.md

02

Answer a few clarifying questions

The ones that change the build: who signs in, what ships in v1, what waits. Your answers become decisions on the record.

docs/decisions.md

03

Get an ordered plan and eight living documents

The whole build in dependency order, plus the documents that describe your product — written for your repo, not left in a chat.

docs/ · 8 files

04

Copy one prompt per step into your agent

Each prompt names the documents to read first and the scope to stay inside. Run it, check it works, mark it done.

copy · run · mark done

05

Continue after the last stepPRO

Pick what to build next and a new phase is planned on top of what exists, with the documents updated to match.

docs/ updated

You write no code in Sequo.·Sequo writes none of yours.

§ 03

Why not just CLAUDE.md or AGENTS.md?

A markdown file works. Until the project outgrows it.

One file is the right call early. You write down the stack and a few decisions, the agent reads it, and everything holds.

Then the project grows. The file gets long, the decisions pile up, and the agent starts skipping it — no error, no warning, it just stops arriving with the context. You find out when finished work comes back rewritten.

From there you have three options. Keep the documents current by hand, which is a second job. Re-explain the project at the start of every session, which is the thing you were avoiding. Or let something else own it.

Sequo writes the documents as you go and names them in every prompt, so the file being read is never a question. And you get the plan itself: the whole build in dependency order, one prompt at a time.

§ 04

Inside a step

Every step splits in two: what your agent runs, and what only you can do.

STEP 3 OF 10Designer sign-inphase 1

❯ RUN — FOR YOUR AGENT

Read docs/architecture.md and docs/decisions.md first.

Implement magic-link sign-in with Supabase Auth. Guard every project route. Leave the upload flow alone.

Copy prompt

◆ PREPARE — YOUR PART0 OF 2

Create a Supabase project, copy the URL and anon key

How? ⓘ

Put them in .env.local

NEXT\_PUBLIC\_SUPABASE\_URL

NEXT\_PUBLIC\_SUPABASE\_ANON\_KEY

↔ IT ASKED BACK — YOU PASTE WHAT IT SAID

“permission denied for schema public”

SEQUO ANSWERS FROM YOUR OWN DOCS

That’s the anon key running a migration. It needs DATABASE\_URL — here’s the follow-up prompt to hand back.

Copy follow-up

§ 05

After the last step

Shipping v1 isn’t the end of the plan. Pick what comes next and a new phase is planned on top of everything already built, with the documents updated to include it.

PLAN10 of 10 steps donephase 1 complete

YOU DEFERRED THESE YOURSELF

Version history on each mockup

Client sign-off on a final round

FOLLOWS FROM WHAT YOU BUILT

Daily digest of new comments

Review links that expire

OR IN YOUR OWN WORDS

Let clients pay a deposit before I start a round.

→ phase 2planned on top of the 10 steps already builtspecification.md · decisions.md · development-plan.md updated

§ 06

Pricing

Build one thing free. Pay when you keep building.

FREE

No card

For building one thing. The whole product, one project at a time.

no VAT · no trial to cancel · no expiry

·One project at a time

·An ordered plan, written for the agent you chose

·Eight living documents

·One copy-ready prompt per step

Start free

PRO

$20/month + VAT

For more than one project, and for everything that comes after v1.

VAT added at checkout where it applies.

·Keep building after the last step

·Up to 10 new projects a month

·Plans sized to the product, not capped

·Rewrite anything that comes out wrong — a step's prompt, a document, or the whole plan

Create an account to go Pro

Cancel any time — everything you've built stays yours.Full pricing details →

§ 07

Who it’s for

FOR YOU IF

You build with Claude Code or Codex and the agent is fast but forgetful.

You want the decisions written down where the agent has to respect them.

You'd rather work through an ordered plan than improvise session by session.

NOT FOR YOU IF

You want the AI to build the whole thing unattended.

You won't read a plan before running it.

Sequo writes files, not conversation — if you want another chat window, this isn't one.

Describe the thing you’re building. The questions, your idea structured, and how big the plan will be — all before you make an account.

Describe your project idea

idea.mdplain english · 1–2 sentences

1

▍ a gym session tracker for my climbing gym

no account until the plan is writtenWrite the plan⌘↵

sequo.app · 8 links

Comments (0)

No comments yet