implement
/implement
Make failing tests pass with minimal code.
Usage
/implement
The implementer will automatically find failing tests from the most recent /write-tests run.
When to Use
- After
/write-testshas created failing tests - When you have specific tests that need implementation
- Never before tests exist
When NOT to Use
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.
19work-on-issue
Start work on a GitHub issue. Extracts requirements, creates worktree, sets up TDD workflow.
17