Add a new feature

Use this process for new or changed behavior with a verifiable result. The example adds a product availability filter.

Requirements

Add an In stock switch to the catalog. Use stock in the selected warehouse and show a useful message when no products match.

1. Without the filter, existing catalog behavior remains.
2. With it enabled, only products in the selected warehouse appear.
3. Changing the warehouse updates results.
4. Empty results display correctly.

Workflow

Explore → Plan → Human approval → Implement → Check → Accept

Stage	Expected result
Explore	Locate catalog and stock data; identify constraints.
Plan	Connect an approach and checks to acceptance criteria.
Approve	Human confirms scope or returns feedback.
Implement	Code and the agreed checks.
Check	Criterion coverage, evidence, open defects and verification limits.
Accept	Human acceptance or a return to the worker.

Real projects may separate review, build and browser checks.

Project setup

Provide repositories, stock data context, check commands and preview access. For isolated execution the profile prepares working copies, containers and data.

Check HTTP availability and background processing separately. If stock updates use a queue or scheduler and the task requires automatic updates, include an end-to-end run with the normal processes. Manually invoking handlers helps diagnosis but does not replace that run. See environment readiness.

Runners and models may differ between planning and implementation.

Choose scenarios by risk

Select checks from the agreed requirements and the specific feature's risks. For this filter and related settings, the following scenarios may apply:

Area affected	What to check
Baseline and OFF/ON	Compare behavior before the change, with the filter disabled and enabled.
Persisted settings, if required	Save, close and reopen the screen; check the loaded value and results.
Intentionally empty selection, if allowed	Clear all selected values, save and reopen. Defaults must not replace the agreed meaning of an empty selection.
Disabled entities in settings	If a disabled warehouse or another entity participates in settings, verify the agreed behavior for its saved selection.
Intersecting parameters	Combine the switch, warehouse and other parameters affecting the results; check their combined effect.
Updates in an already open screen	If the result should appear without a reload, keep the screen open and check it updates after processing completes.

These are options to select, not a mandatory large suite for every small edit. An empty selection and empty results are different cases. Clarify an undefined setting before implementation rather than adding a new requirement during review. For selected scenarios, fill in the acceptance table and explicitly identify any unchecked mandatory criteria.

Example instruction

Find how the catalog reads stock and the selected warehouse.
Plan the In stock filter.
Specify a check for every acceptance criterion.
Preserve behavior with the filter disabled.
Ask a human if warehouse context is missing.

Assign the required context and expected stage result in the editor.

Rework

If a product is shown because it exists in another warehouse, return implementation with feedback to use the selected warehouse's stock and add a check. After the fix, repeat affected checks, necessary checks of existing behavior and acceptance. Apply the reviewer rules on repeat passes.

A short route may suit a clear, low-risk change if the profile supports it. Keep relevant acceptance criteria and checks.

Continue with route creation.