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
component-runtimeInspect FATE component CLI commands, component descriptors, task schema, and custom component discovery without running service-backed jobs.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when you need to inspect, explain, or smoke-check the local FATE component runtime exposed by python -m fate.components.
python -m fate.components and the component group.task-schema command.desc, list, task-schema, and artifact-type as safe probes.../pipeline-workflows/SKILL.md.../local-launchers/SKILL.md.../deployment/SKILL.md.execute and cleanup as reference-only unless a live config/backend is explicitly available.python -m fate.components CLI also exposes a test group, but this sub-skill stays on component inspection.references/component-cli.md for the exact CLI surface and save-file behavior.references/component-catalog.md for the built-in component families and artifact shapes.references/task-schema.md when validating TaskConfigSpec or debugging config mismatches.references/component-development.md for custom component discovery, stage support, and guide points.references/troubleshooting.md for missing pkg_resources/setuptools, unknown names, unsupported stages, entry-point failures, and schema confusion.scripts/check_component_cli.py in a Python environment that already has FATE installed.../deployment/SKILL.md../pipeline-workflows/SKILL.md../local-launchers/SKILL.md