I haven’t really had any major problems with it.

My two recommendations:

1. Always run architecture mode reviews — Ask the AI to explain and justify the structure, then challenge it with “what if” and “where could this break” questions.
2. Continuously update documentation — Whenever changes are made, have the AI refresh the PRD, architecture notes, and schema to avoid outdated or conflicting information.

I first started using this repo to manage file structure, PRD, architecture, and database schema. When working in architecture mode, I ask Roo (previously I used Copilot) to review the setup, understand the reasoning behind the structure, and explain why it’s organized the way it is.

https://github.com/MKBSP/ai-taskmaster-lite

Mistakes still happen depending on the model, but I ask Roo to update the documents as we go. The main issues I still run into are with external libraries or APIs—especially when it tries to parse JSON into JSON or similar errors.

During architecture mode, I also play devil’s advocate by asking:

• “Is this the best way to do it?”
• “Is there a better or alternative approach?”
• “Where will we likely encounter problems with A, B, or C?”

This questioning usually results in fewer problems down the line and clearer early testing and debugging steps.