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
configuration-and-cliDefine, update, inspect, and troubleshoot Sacred configuration and experiment command lines.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to define Sacred configuration, apply or inspect config updates, route experiment commands from the command line, or diagnose CLI/config parsing behavior for Sacred 0.8.7.
config_updates, or the order in which Sacred resolves configuration.cli_option, or routing custom/ingredient commands.with arguments parse unexpectedly, print_config reports added/typechanged values, config keys are rejected, a ConfigScope fails, nested config is read-only, a command is unknown, or YAML config files fail.print_config, CLI updates, a named config, a custom command, and a custom CLI option without external services.This sub-skill owns:
@ex.config config scopes, ex.add_config(...), config files, config dictionaries, @ex.named_config, ex.add_named_config(...), and @ex.config_hook.Experiment.run(config_updates=..., named_configs=..., options=...) and Experiment.run_commandline(argv=...) config behavior.with updates, dotted notation, named configs, built-in commands, command routing, CLI flags, and custom cli_option handling.Route elsewhere:
Run semantics, captured function internals, resources, and artifacts belong to experiment-core.observers-and-logging.reproducibility-and-capture.add_config.print_config before a real run to inspect the effective config and any suspicious changes.with updates for strings, lists, dictionaries, booleans, and nested dotted paths.--force.help and print_named_configs before changing experiment code.