Custom-language long-task workflow

One-sentence takeaway

Give Ox Alpha documentation for a custom language that cannot be in its training data, then implement the game and language feature in separate stages to test document reading, sustained coding, and regression verification.

Use cases

• Suitable tasks: Custom DSLs, internal SDKs, lightly documented applications, and game prototypes.

• Unsuitable tasks: Production repositories without a test entry point or rollback path, or tasks where generated code is treated as proof of correctness.

• Applicable model version: Ox Alpha; no version snapshot is provided.

• Applicable clients, agents, or APIs: OpenCode CLI; the post explicitly describes using OpenCode.

• Recommended reasoning levels and parameters: Not disclosed; fix the context, tool permissions, and timeout for long tasks.

Ready-to-use content

The original post does not publish complete turn-by-turn prompts. The following is a reusable workflow derived from the public sequence and should not be quoted as the original prompt:

Use the custom-language documentation in this repository to implement a simple platform game.

Stage 1: Read and summarize the documentation. List the syntax, runtime method, and uncertainties; do not guess semantics that are not documented.
Stage 2: Implement a playable platform game with 10 levels. Build the smallest runnable version first, then verify each level.
Stage 3: Run the existing checks or a minimal regression suite. Report whether each level starts, whether input works, and why any check fails.
Stage 4: Add a modulo operator. Update parsing, execution, error handling, and documentation, and add tests for positive, negative, zero, and invalid inputs.
Stage 5: Run the full regression suite again. Change only task-relevant files and finish with a file list and unresolved issues.

Reuse notes

• Put the custom-language documentation in the repository and state that it is authoritative.

• Split “implement the game” and “add the language feature” into separate rounds so regressions are visible.

• Require runtime results and failure causes after every round instead of code alone.

• Use a reversible branch; custom-language correctness must be checked by the runtime or tests.

Original case outcome

The author says that, after receiving the documentation, the model completed a 10-level platform game and added a modulo operator. The author also says the level design was not great but the functionality worked. No repository, commit, or test log is published.