Requirement, architecture, standards

Write what Stall is before building it: the goal, this project's technical decisions, and the rules that must stay true.

The idea

Three kinds of writing, three jobs. Do not mix them.

• Requirement. The product in human terms. Who uses it, why it must work this way, what “done” feels like. Benefits and goals. No tech stack yet.
• Architecture. This project's technical fingerprint: stack, shape, and practices that apply to the whole Stall. You say what you want to start with (here: Node.js, SQLite, Next.js). OpenCode may accept that or recommend a better fit, with reasons. Another shop would choose differently.
• Standard. One rule you protect for a long time, on one feature or habit. Money is integer cents. Sold-out cannot be ordered. Every food item has an allergen note. A standard is smaller than architecture. It is the thing you do not want the AI to “improve” away next month.

Requirement: the goal

Start in OpenCode plan mode, in the Stall folder. You do not paste a finished document. You talk like a person. There are two ways. Both end with a requirement saved in orkai. Neither builds Stall.

Talk it out

You have an idea, not a spec. Load the Product Owner workflow from the starter pack. Brainstorm until the goal is clear. Then OpenCode saves it with the requirements tool.

I need a web project to manage my orders online, with offers on Saturday. Stall is a local shop: catalog + orders, no payments.

Load the Product Owner workflow and help me with the requirement. Let's brainstorm until we have a great requirement.

You already know

You can say the goal in a few sentences. OpenCode still uses the requirements tool. You are not pasting a template. You are stating intent.

Create this requirement in orkai using the requirements tool.

I need Stall, a local shop: people see what I sell and place orders, including Saturday offers. Sold-out items cannot be ordered. No payments, no accounts, no delivery.

Architecture: this project's decisions

After the requirement exists, load the Architect workflow. Say the stack you want to start with. OpenCode can agree or recommend something else. Then it saves the architecture in orkai.

The Stall requirement is in orkai. Load the Architect workflow and help me write the architecture for this project.

What I want to start with:
- Node.js, current stable version
- SQLite, native in Node.js
- Next.js, so frontend and backend live in the same project

Catalog is not orders. No payments.

This is my starting point. If you recommend something else, say why. Then save the architecture in orkai.

Standards: rules that must stay true

Each standard guards one habit for the long term. For Stall v1, at least: integer cents, sold-out cannot be ordered, allergen note required.

Help me write Stall standards in orkai. Protect these for the long term: money in integer cents, sold-out cannot be ordered, every food item has an allergen note.

Do this in OpenCode

1. Stay in the Stall folder. Confirm .orkai.yaml has a category id.
2. OpenCode in plan mode. Pick one requirement path above. Stop when the requirement is in orkai.
3. Then the architecture prompt. Then the standards prompt.
4. Ask OpenCode to call overview() for this project. You should see the requirement, architecture, and standards. Still no Stall files.

Recap

Stall now has a requirement, an architecture, and standards in orkai. You got there by talking, not by pasting a spec. There are still no app files. Next we turn that into a plan with milestones and tasks.