- Default to Plan Mode: For any task requiring >3 steps or architectural decisions, you MUST generate/update a plan in
tasks/todo.mdbefore writing any code. - Verification Steps: Every plan must include explicit verification criteria (e.g., "Check logs for X," "Run test Y").
- Stop-and-Pivot: If an implementation fails twice or hits a logic wall, STOP. Re-read the requirements, update the plan, and confirm with the user before proceeding.
- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
- If something goes sideways, STOP and re-plan immediately - don't keep pushing
- Use plan mode for verification steps, not just building
- Write detailed specs upfront to reduce ambiguity
- Use subagents liberally to keep main context window clean
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| try { | |
| TrustManager[] trustAllCerts = new TrustManager[] { | |
| new X509TrustManager() { | |
| public java.security.cert.X509Certificate[] getAcceptedIssuers() { | |
| return null; | |
| } | |
| public void checkClientTrusted(X509Certificate[] certs, String authType) { } | |
| public void checkServerTrusted(X509Certificate[] certs, String authType) { } | |
| } |