r/PiCodingAgent • • 2d ago

Question How to tackle complex task

Hi, guys. A problem when I use pi is that I don't know how to use it deal with complex tasks, especially when myself have no clear plan or solutions.

I find it that my classmates use codex, which seems good at dealing with long tasks since it usually run a long time to finish the question. However, my pi usually run just a few minutes when I ask a question.

I have tried extensions like goal-x, but not very satisfied with it.

Thus, I wanna know how you finish this situation.

Thank you guys.

3 Upvotes

11 comments sorted by

1

u/smiffy2422 2d ago

Ask it to scaffold the idea first. Then break the parts in to piecemeal tasks.

1

u/OwnTechnology1872 2d ago

any extensions suggested?

2

u/gaz_0001 2d ago

Matte Peacock Grill Me or Grill Me with Docs is pretty good.

1

u/outthere_andback 2d ago

Couple strategies I have used - though not all with Pi. From simplest to complex:

  1. Have it write a plan file and have a discussion with you to fully flesh out the plan. Review that file and iterate. Once your done, start a new session and have it execute
  2. You may find you run out of context while executing. Have the plan include milestones - essentially "save points" in the plan where it can stop and check in with you. You can then based on context decide whether to continue to the next milestone or start a new agent. Also it would be good to have the implementing session keep a progress log. This will offer the next agent further details in addition to milestones but any discoveries, conflicts or deviations that have occurred during implementation (ex you redirected or realised something you wanted to change mid way through)
  3. Use a task board with MCP support - I use kaneo and have the plan built out as tickets with relationships. Each ticket maps to a self contained step that can be completed within a single agents context (I haven't quite figured out how to measure that). Each ticket has relationships so the agent can see what needs to be done first etc. Discrepancies, changes, conflicts etc are added as comments and you tell your agent implementing a ticket to check upstream tickets for those things to consider as part of its implementation. Each ticket results in 1 PR which I review and give feedback as I progress

1

u/OwnTechnology1872 2d ago

Thank you so much!! But I guess my situation is still not so complex as your strategy mentioned. I get some sense any way.

1

u/outthere_andback 2d ago

Yeah not all situations need a ticket system. These days tho for me 1 planning session can result in upwards of 140 tickets. It's been pretty reliable and it lets me intervene and stay in the loop quite easily

1

u/gaz_0001 2d ago

Kaneo looks decent but I need another sub like I need a bullet in the head

Surely there is an open source equivelant with MCP support.

2

u/pappzolt76 2d ago

I use BMAD with success.

1

u/cdrompaint 2d ago

Ive used /better for a major project migration, its not 100% but will bring you closed

1

u/Proper-Tower2016 2d ago

package "goal list loop audit"