Extend the requirement

Same Stall requirement, new feature. Product Owner, Architect, you review in orkai, then Feature Planner.

You will learn

  • Why a scope change updates the same requirement instead of starting a new product
  • How to extend with Product Owner, then Architect, then Feature Planner
  • How to read the changes in orkai open (Documents) before anyone codes

The idea

Shops add a rule without reinventing the stall. Dietary tags are still Stall: catalog plus orders. You extend the requirement you already saved. History stays. A new requirement is for unrelated work, later.

You do not dump requirement, architecture, standard, and plan into one prompt. One role at a time. You read the documents in orkai before you approve the plan.

Do this in OpenCode

  1. Start a new chat in the Stall folder. AGENTS.md loads overview. Paste the Product Owner line. Explain the feature in detail, like the example below.
  2. When the requirement looks right, paste the Architect line. Let it say whether architecture or a new standard must change.
  3. Open the orkai window. Read the documents yourself.
  4. Back in OpenCode, paste the Feature Planner line. Same plan, new milestone. Approve only when the work is tags on the page, not accounts.
  5. Then implement all tasks, test the way the agent describes, and save the session.

Task status: Plans, milestones and tasks.

Product Owner: extend the requirement

Load the Product Owner workflow to extend the requirement. The new feature is: products have dietary tags (vegetarian, vegan, gluten-free as they apply). The shop shows the tags. An optional filter is enough. Still catalog plus orders. No payments, no accounts.

Architect: architecture or a new standard?

Load the Architect workflow to validate if the new feature needs to extend the architecture or a new standard.

Read it in orkai

Run orkai open if the window is not already open. Select Stall in the project dropdown. Open Documents. Read the requirement, architecture, and standards. This is you reviewing, every time, not only in this lesson.

orkai open

Feature Planner: same plan, new milestone

A new plan is for a different piece of work. Dietary tags stay on Stall v1. After it writes the milestone and tasks, open Project Manager and read them.

Load the Feature Planner workflow. Add this work to the existing Stall v1 plan. A new milestone on the same plan is enough. Stop for my approval.

Implement

Same as v1. OpenCode stops after a task unless you tell it otherwise.

Let's implement all the tasks and let me know at the end how to test it manually.

Save the session

When the work in this chat is done, save. Always.

Save the session, I will continue in a new one.

When there is a shop to open

The three products show dietary tags as data (vegetarian, vegan, gluten-free as they apply). The shop lists them. A filter is optional. Still no payments, no accounts. Catalog math did not change.

Recap

One requirement grew. You read it in Documents. The same plan got a new milestone. You shipped tags without a second Stall. Next we point review at the house rules so a bad commit cannot land.