Single Task Pipeline
Single Task Pipeline is a simple way to implement concrete features or fixes in your project when using the full Manager agent would be overkill. It’s ideal for smaller, well-defined changes such as creating a new page, fixing a bug, or implementing a particular functionality.
Working process
You will be prompted to describe the task Clean Coder need to execute. Write the description or enable microphone just to say it.
The same rules for creating good tasks for human programmers apply here.
- Describe your task as detailed as you can.
- Focus on one feature per task. Break complex features into smaller, manageable tasks.
Your task will be executed by Clean Coder agents in sequence: Researcher, Planner, Executor, and Debugger.
Researcher Agent
Researcher examines files in the project directory and tries to identify necessary files to work on. It will take a minute.
Once complete, found files will be displayed. Accept them or provide feedback if you think Researcher missed some important files.
Planner Agent
Planner drafts code modification plans. Review and request changes until the plan is satisfactory. Don’t accept plans you don’t understand - debugging will be painful without understanding your code.
Executor Agent
Executor implements planned changes to your project files.
Debugger agent
If the Executor’s changes don’t fully solve the task, you’ll need the Debugger - a more powerful and intelligent agent that can access logs and visual feedback. Use it to polish code after the Executor’s work.
For safety, you must approve all changes. Interrupt if you see wrong changes being made. Don’t accept changes you don’t understand - again, debugging will be painful. Keep your IDE open to monitor code modifications in real-time.
Demo video
Happy coding! 😋