Code Run Feature Test

When implementation of a feature or task is otherwise complete and it's time to verify it before raising a PR: a confirmed build, a fresh Acme-provisioned database, the full test suite, a written test scenario, and a client handed to the user to execute it.

Run How do I test a feature after implementation? end to end:

1. Its Prerequisites section — build/test if needed, validate schemas, then ready the environment (fresh database, Acme Corporation provisioned by you, not the user). Non-negotiable, in order.
2. Its Writing and running the scenario section — a test_scenario doc covering every aspect of the feature (CRUD + eventing + history for an entity), then a client started with the scenario preloaded and handed to the user to execute.

Leave Clients in = Scenario Info= genuinely empty* for a single-client scenario (the common case) — any non-empty value there, even a placeholder like "single client", makes the Runner load zero steps, silently.

• How do I test a feature after implementation?
• How do I ready up an environment?
• How do I run the tests?

• Archetype: doc_test_scenario.org.mustache — the test_scenario doc shape.
• Devops Run Client — the sibling skill this one hands off to for --open-scenario.
• doc-run-manual-screenshots — sibling skill sharing the same environment-readying recipe, applied to manual-chapter screenshots instead of feature verification.