Retrosynthesis Planning

Workflow: Two Distinct Modes

At the very beginning of the session, you MUST explicitly ask the user whether they want to use Mode A or Mode B, rather than deciding based on how the session was started. Wait for the user's response before proceeding.

Mode A: Expert-in-the-Loop MCTS Planning (Manual Stepping)

Use this if the user selects Mode A.

CRITICAL STARTUP SEQUENCE (DO NOT SKIP): 0. Environment Installation: Before doing anything else, you MUST check if the required Python environment is ready. Due to aizynthfinder constraints, the environment MUST use Python 3.10. Use conda to create it if necessary: conda create -n retro python=3.10 -y && conda activate retro. Then run pip install -r <SKILL_DIR>/requirements.txt to install rdkit, requests, urllib3, aizynthfinder, tensorflow, tensorflow-serving-api, grpcio, and protobuf. After installation, instruct the user to download the uspto models using download_public_data <DATA_DIR> where <DATA_DIR> is C:/tmp on Windows or /tmp on Linux (this command requires user interaction as it's interactive, or you can skip it if the files exist in <DATA_DIR>).

1. Setup & Context: DO NOT change directories. Remain in the user's current workspace directory so that all output files (route_state.json, tree_visualization.html) are saved safely within the user's workspace. Locate the absolute path of this SKILL.md file to determine the skill's root directory (<SKILL_DIR>). Read <SKILL_DIR>/references/api_endpoints.md and <SKILL_DIR>/assets/route_report.md for context. If you need to restart or clear a cluttered tree, run rm route_state.json (on Linux/Mac) or del route_state.json (on Windows) in the workspace.
2. Target Normalization: You MUST ALWAYS execute the python scripts using their absolute paths. Run python <SKILL_DIR>/scripts/analyze_molecule.py --smiles "<SMILES>" (or --name) first to obtain the strict Canonical_SMILES and key properties.
3. Initialization: Initialize the MCTS tree using the Canonical SMILES via python <SKILL_DIR>/scripts/route_state_manager.py --init "<Canonical_SMILES>".
4. Expansion: FIRST, consult AiZynthFinder for reactions via python <SKILL_DIR>/scripts/retro_engine.py --retro "<SMILES>". NEXT, before updating the state, call vendor proxies for each child via python <SKILL_DIR>/scripts/retro_engine.py --vendor "<SMILES>". FINALLY, submit the verified nodes into the state EXACTLY ONCE using exact arguments: python <SKILL_DIR>/scripts/route_state_manager.py --expand <Parent_Node_ID> --rxn "<Reaction_Name>" --children "<Child_1>" "<Child_2>" --purchasable true false (use literal booleans true or false depending on the vendor verification). DO NOT expand the exact same reaction twice.
5. Visualize, Recall, & Pause:
   • Execute python <SKILL_DIR>/scripts/render_tree.py and direct the user to preview tree_visualization.html.
   • To query your memory for the current state (e.g. to see which leaves are still unsolved), use python <SKILL_DIR>/scripts/route_state_manager.py --status.
   • If an explored reaction branch proves unfeasible, use your fallback mechanics to prune it: python <SKILL_DIR>/scripts/route_state_manager.py --prune <Reaction_ID> (e.g. --prune R3).
   • WAIT for the expert's decision on which M_n Node to attack next.

Mode B: Fully Autonomous Agentic Loop (RetroPilot Agent)

If the user selects Mode B, do not process using Mode A! Instead, IMMEDIATELY read agents/retropilot.md and switch your persona to follow the RetroPilot execution loop described inside it.

5. Final Reporting (Completion)

When the tree root reaches solved: True or the expert concludes the session:

• You MUST generate a final summary using the exact template located in assets/route_report.md. Do not invent your own structure. Fill in the placeholders (e.g., {{TARGET_NAME}}) using data gathered during the run.
• Present the initial routes to the human expert.
• Evaluate dynamically based on user/expert priorities (e.g., green chemistry vs. cost vs. raw materials vs. brevity).
• Emphasize potential drawbacks flexibly (e.g., low yield, expensive catalysts, toxicity risks, scalability issues).
• Actively run validation scripts (e.g., RDKit substructure checks, API calls for commercial availability of building blocks) to fact-check proposed pathways.
• Solicit feedback on specific steps.
• Iterate and refine the tree based on the user's domain knowledge, adjusting conditions or replacing steps with more elegant solutions.

Best Practices

• Step Economy: Always favor convergent syntheses over long linear sequences to maximize overall yield.
• Protecting Groups: Actively minimize the use of protecting groups. If unavoidable, explicitly plan their installation and removal sequence.
• Explainability: Justify non-obvious disconnections citing chemical principles (e.g., orbital symmetry, thermodynamics, sterics).
• Format: When presenting intermediate molecules, use standardized naming and occasionally output SMILES strings to keep the context unambiguous.