brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
maintenanceMaintain the ZenML repository safely with AGENTS guidance, targeted tests, formatting, linting, docs checks, migration checks, optional dependency boundaries, and PR/CI expectations.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task asks for repository changes, bug fixes, refactors, docs updates, test selection, formatting, linting, migrations, dependency updates, CI parity, PR readiness, or release-label guidance in a ZenML checkout.
develop branch, release notes labels, optional extras, import boundaries, full test suite avoidance, GitBook links, or Alembic branches.docs/book, generated SDK docs inputs, TOCs, GitBook URLs, or Markdown links.This sub-skill owns safe repository maintenance workflow: obeying AGENTS files, selecting focused tests, formatting/lint/docs/migration checks, guarding optional dependency boundaries, and preparing PR-ready summaries. It is not the usage route for writing ZenML pipelines, stack components, CLI commands, or server features.
@pipeline, @step, materializers, schedules as user workflow constructs, run configs, dynamic pipelines, and local pipeline smoke checks.pytest target and broaden only when needed.bash scripts/format.sh <changed paths> and targeted ruff, pydoclint, mypy, or pytest commands over broad CI scripts during iteration.zen-test provisioning, Docker/server stacks, link validation, SDK docs serving, and migration replay as expensive or mutating unless the user explicitly approves.develop, and exactly one release-notes label expectation.