noobygains

Use when about to say that work is done, fixed, passing, working, deployed or ready, before committing, opening or merging a pull ...

Use when a fix attempt has failed more than once for the same problem, when a fix for one problem causes another, when the same fi...

Use when a test fails, a build breaks, a bug is reported, behaviour is unexpected, performance degrades or an integration stops wo...

Use when the user wants something new built or existing behaviour changed, such as a feature, component, page, API, module or proj...

Use when a substantial task finishes, when the user corrects the agent or states a preference, when a non-obvious cause or project...

Use when implementation on a branch is finished and reviewed and the work needs to land, be proposed as a pull request, be parked ...

Use when creating a new project or repository, scaffolding a codebase from nothing, turning a prototype into something that will b...

Use when finishing tasks, shipping significant features, or before landing changes to ensure work meets standards through automate...

Use when the user asks for new work such as a feature, component, integration, service or dependency, especially when the request ...

Use when code review feedback arrives from the user, a reviewer subagent, another model, a human colleague or an automated tool, b...

Use when an approved design, specification or clear requirement exists for work that touches more than one file or behaviour, befo...

Use when a task needs several agents that must coordinate with each other while they work, such as negotiating an interface across...

Use when implementing a feature, fixing a bug, refactoring, or changing behaviour in any codebase, before writing the production c...

Use when starting feature work that should not touch the current checkout, before executing an implementation plan, or when severa...