generate-openenv-env
/generate-openenv-env
Build a production-ready OpenEnv environment from a use-case prompt.
Execute Workflow
When invoked, execute this workflow end-to-end.
1. Parse the use case and name the environment
Derive a repo path in the form envs/<name>_env/.
- Normalize to snake_case.
- Keep names short and domain-specific.
- Example: "generate an env for the library textarena" ->
envs/textarena_env/.
2. Research the target library/API before coding
Gather the minimum interface facts needed to implement reset, step, and state serialization.
More from meta-pytorch/openenv
write-tests
Write failing tests from requirements. Invoke for each todo before /implement.
25simplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
20alignment-review
Review code changes for bugs and alignment with OpenEnv principles and RFCs. Use when reviewing PRs, checking code before commit, or when asked to review changes. Implements two-tier review model.
20pre-submit-pr
Validate changes before submitting a pull request. Run comprehensive checks including lint, tests, alignment review, and RFC analysis. Use before creating a PR, when asked if code is ready for review, or before pushing for PR.
20rfc-check
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
19implement
Make tests pass. Invoke after /write-tests produces failing tests.
17