About this skill

Problem

Simon Test 1 targets a narrow acceptance-testing problem: the final result must be stored as a field-level JSON object, but asking for every field at once often produces missing keys, inconsistent ordering, malformed values, or unconfirmed content mixed into the structure. The skill splits acceptance into multiple turns, requesting the current field first and deciding the next step from the response. This makes it useful for tests, demos, form-like collection, and pre-write field alignment. It is especially suitable for acceptance cases with few fields and clear steps.

How It Works

The core behavior is step-by-step solicitation and stepwise writing. It follows a defined acceptance path, asks for the required field or content, advances after receiving an answer, and organizes confirmed values into the target JSON. Users should already know the rough acceptance steps; if fields depend on external APIs, business calculations, or human approval, validation and fallback logic must be added outside the skill. Treat it as a structured acceptance test for clear steps and explicit output, not as a general-purpose form engine. If acceptance rules change, update field descriptions and write order accordingly.

Screenshots

Use Cases

Before release, request each acceptance field in order and emit JSON.
When debugging field collection, confirm required fields step by step and check JSON output.
For demo scripts, collect test fields by steps and write them into JSON.
When validating external data, request field values one by one and summarize JSON.

Best For

QA engineers who need to confirm fields step by step and write JSON.
Backend developers integrating APIs who need ordered field collection and JSON checks.
Product engineers building demo scripts who need stepwise test-field prompts.
Test engineers preparing validation data who need reviewable JSON output.