executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
planning-workflowsRun AiZynthFinder retrosynthesis planning and one-step expansion through CLI, Python APIs, and optional notebook interfaces.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to execute or script AiZynthFinder retrosynthesis planning, construct an aizynthcli command, call AiZynthFinder or AiZynthExpander from Python, debug target SMILES setup, checkpoint a batch run, or launch the optional notebook interface.
aizynthfinder is importable and the aizynthcli entry point is on PATH.../configuration-and-data/SKILL.md.--smiles is a literal single SMILES or a text file with one SMILES per row; multiprocessing requires a file.../route-analysis/SKILL.md.../extension-and-development/SKILL.md.scripts/build_aizynthcli_command.py and then run the printed command in the intended environment.references/cli-reference.md.references/workflows.md.references/api-reference.md.references/troubleshooting.md.aizynthcli --config CONFIG --smiles SMILES, optionally with --output trees.json.aizynthcli --config CONFIG --smiles smiles.txt --output output.json.gz, optionally with --checkpoint checkpoint.json.gz.--nproc N only when --smiles names an existing file.AiZynthFinder, select stock/policy/filter keys, set target_smiles, run prepare_tree(), tree_search(show_progress=False), build_routes(), then call extract_statistics() and stock_info().AiZynthExpander, select policies and optional filters, then call do_expansion(smiles, return_n=5, filter_func=None).aizynthapp --config CONFIG or create an AiZynthApp inside Jupyter only when an interactive notebook environment is available.