Find agent skills by outcome

- Follow the plan exactly as it is written

picking up with the next unchecked step in the implementation plan document. You MUST NOT skip any steps.

Only make the changes explicitly specified in the plan. If the user has not passed the plan as an in...

respond with: Implementation plan is required.

Implementador de Tarefas

2. Documentation: Read existing feature documentation

architecture decisions in codebase

Use official documentation and reputable sources. If uncertain about patterns

research before proposing.

3. Dependencies: Research any external APIs

libraries

6. If feedback received

revise plan and go back to Step 1 for any research needed

1. Code Context: Semantic search for related features

existing patterns

Files: {List affected files: Service/HotKeyManager.cs

Models/PresetSize.cs

- For SIMPLE features

consolidate into 1 commit with all changes.

If #tool:runSubagent is unavailable

execute via tools yourself.

- For COMPLEX features

break into multiple commits

STOP & COMMIT: Agent must stop here and wait for the user to test

stage

A development plan defines a clear path to implement the user's request. During this step you will n...

you will research

Planjedor de Tarefas

{COMPLETE

TESTED CODE - NO PLACEHOLDERS - NO TODO COMMENTS}

STOP & COMMIT: Agent must stop here and wait for the user to test

stage

{COMPLETE

TESTED CODE - NO PLACEHOLDERS - NO TODO COMMENTS}

- Document APIs

syntax

{COMPLETE

TESTED CODE - NO PLACEHOLDERS - NO TODO COMMENTS}

If not

move them to the correct branch. If the branch does not exist

- Project type

technology stack

For the entire project described in the master plan

research and gather:

- Specific

observable