with one click
implement
Implement a piece of work based on a PRD or set of issues.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Implement a piece of work based on a PRD or set of issues.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run Magento, PHP, Composer, or SQL commands in a create-magento-app (magento-scripts) project — always via the `exec` package script into Docker, never on the host. Use when running bin/magento or composer, querying the MariaDB database, starting/stopping/checking the stack, importing a DB dump, or reading container logs.
Run Magento, PHP, Composer, or SQL commands in a create-magento-app (magento-scripts) project — always via the `exec` package script into Docker, never on the host. Use when running bin/magento or composer, querying the MariaDB database, starting/stopping/checking the stack, importing a DB dump, or reading container logs.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the goal is clear.
| name | implement |
| description | Implement a piece of work based on a PRD or set of issues. |
| disable-model-invocation | true |
Implement the work described by the user in the PRD or issues.
Use /tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once done, use /code-review to review the work.
Commit your work to the current branch.