Readiness gates
Each draft is scored out of 100 against baseline rules. A vague section is a blocker; missing failure paths, roles or audit notes lower the score. You still review the facts and scope.
Specification · Readiness · Handoff
Write the spec before the agent codes.
Loop turns product intent into a versioned LOOP.md, flags the decisions you haven’t made, and exports a handoff your coding agent can follow.
Free to draft · No card required · Sign in with your Efolusi account
# Checkout Revamp > executable spec · schema 1.0 ## Problem Guest checkout abandons at the address step. Success is a paid order in under ninety seconds. ## Critical journey Add to cart → guest address → pay → signed webhook confirms the order. ## Verification - [x] Blocking decisions resolved - [x] Failure states specified - [x] Completion evidence defined
What Loop checks before code.
Every spec has eight sections: problem, users, journeys, domain, permissions, architecture, security and verification. Each is held to rules you can test.
Surfaced decisions
Loop names the decisions you haven’t made yet, like who can do what or what happens when payment fails, and pins each to its section.
Section-by-section drafting
Describe the product in plain words and Loop drafts all eight sections. Regenerate one section and the rest stays as you reviewed it.
Versioned history
Every generation, regeneration and save records a version you can reopen. Team approval workflows are not available yet.
Four-file handoff
Export LOOP.md with the loop rules, spec.md for intent, plan.md for architecture and security, and tasks.md for ordered, verifiable work.
Evidence-based completion
The exported instructions ask your agent to record verification evidence. You review the results; the studio does not enforce an external agent’s decisions.
From intent to handoff.
Three steps, and you stay the reviewer at each one.
- 01
Describe the product
Write what you want to build in plain language. Loop structures it into problem, users, journeys, architecture and verification.
- 02
Resolve blocking decisions
Loop scores readiness and lists the gaps: risk, permissions, failure states and completion evidence. Close them before development.
- 03
Hand off to your agent
Export the bundle and give it to the agent you choose. Review what you share and verify its output; Loop does not yet launch or enforce approval of an agent run.
Why a spec, not a prompt.
A prompt disappears after one run. A spec can be reviewed, versioned and checked again.
Objective gates
Done means checked evidence, such as passing builds, sandbox journeys and signed events. An agent saying so is not enough.
Reviewable versions
Saved revisions keep earlier drafts. Review the version you hand off; a formal owner-approval workflow is still planned.
Scoped context
You choose what to export. The exported text may contain sensitive details you entered, so review it before sharing.
Who works this way.
Solo founders
You own the product and the review. Loop makes you settle failure states and completion evidence before an agent runs unattended.
Product teams
Share an exported spec for review in your existing workflow. Shared editing, roles and approval controls are planned, not included today.
Coding agents
The bundle tells the agent to read first, implement an unblocked task and record evidence. Remove sensitive content before sharing.
Start free. Upgrade once.
Prices in Indonesian rupiah. Upgrades are paid via QRIS through Efolusi Pay.
Free
Rp0
Sign in with your Efolusi account and start drafting specs. No card required.
Start draftingPro
Rp149.000
For individual builders. Upgrade from inside the studio, paid once via QRIS through Efolusi Pay.
Sign in to upgradeTeam Planned
Rp499.000
Planned team offering. Shared workspaces, member roles and approvals are not available for purchase yet.
Questions before you start.
What exactly is a LOOP.md?
A markdown contract for an autonomous development goal. The bundle contains LOOP.md (loop rules and file index), spec.md (problem, users, journeys, domain, permissions), plan.md (architecture and security) and tasks.md (measurable outcomes and how to verify them).
Which coding agents does Loop work with?
Any agent that can read markdown. The handoff is plain files, with no SDK, plugin or vendor lock-in. Point Claude Code, Cursor or your own harness at the bundle.
How is readiness scored?
With fixed rules, not an AI judging your writing. Each of the eight sections needs a concrete, testable description, and specific sections must name failure paths, roles, server-side checks, auth, audit, secret handling and tests. Blockers cost more than warnings. A score of 100 passes the baseline; it does not prove that every fact is correct or that the application is safe to ship.
Can I write the spec by hand?
Yes. AI drafting is a starting point, not a requirement. Every section is editable, and you can regenerate one section without touching the rest.
How does payment work?
Drafting is free, with no card required. Pro is a one-time upgrade made from inside the studio, paid via QRIS through Efolusi Pay. Team is not on sale yet. Card and provider credentials never reach Loop; payment confirmation arrives as a signed webhook.
Do I need another account?
No. Loop uses your Efolusi account, the same one as every Efolusi product. Loop never keeps a password.
Who can see my specifications?
Project reads and writes are checked against your signed-in account. Anyone you send an exported file to can read it, so review it first. Team access controls are still planned.
Prepare before you build.
Draft your first spec for free and see what’s still undecided.
Start drafting for free