gitlab-tbc

Get help with TBC plugin commands

Generate GitLab CI/CD configurations using To-Be-Continuous framework

List available TBC templates and their categories

Validate a TBC configuration against schemas

Guided wizard to generate GitLab CI/CD configuration with framework-first evaluation

Use this agent when the user asks to "evaluate if TBC covers a use case", "decide which TBC component to use", "check if a TBC template fits", "research TBC capabilities", "find the right TBC template", "analyze if custom step is needed", "compare TBC templates", or needs to determine whether To-Be-Continuous framework components can solve a CI/CD requirement BEFORE generating configuration. This agent performs deep research autonomously.

This skill should be used when the user asks to "generate gitlab-ci.yml", "create GitLab CI pipeline", "configure GitLab CI/CD", "use To-Be-Continuous templates", "setup TBC templates", "create CI/CD for Python/Node/Go/Java project", "configure Docker build in GitLab", "setup Kubernetes deployment in GitLab", "add SonarQube to GitLab CI", "configure Terraform with GitLab", or mentions "TBC", "To-Be-Continuous", "Kicker".

This skill should be used when the user wants to "create to-be-continuous component", "build TBC template", "extend existing component", "create variant", "contribute to to-be-continuous", "component structure", "how to create gitlab ci component", or needs guidance on component architecture, naming conventions, GitLab CI component syntax, input specifications, base job patterns, or to-be-continuous best practices and philosophy.

This skill should be used when the user asks to "evaluate if TBC covers a use case", "decide which TBC component to use", "check if a TBC template fits", "research TBC capabilities", "find the right TBC template", "analyze if custom step is needed", "compare TBC templates", or needs to determine whether To-Be-Continuous framework components can solve a CI/CD requirement before generating configuration.

This skill should be used when the user asks to "identify core need", "clarify requirements", "extract user intent", "validate distinctions", or when starting any research or analysis task that requires understanding what the user actually needs before proceeding.

This skill should be used when the user asks to "build multiple Dockerfiles", "compile varios dockerfiles", "multi-container build", "multiple Docker images in GitLab", "parallel Docker builds", "monorepo Docker builds", "build frontend backend worker containers", or needs to build multiple Docker images from different Dockerfiles in a single GitLab project using To-Be-Continuous Docker template.

This skill should be used when the user asks to "generate gitlab-ci.yml", "create GitLab CI pipeline", "configure GitLab CI/CD", "use To-Be-Continuous templates", "setup TBC templates", "create CI/CD for Python/Node/Go/Java project", "configure Docker build in GitLab", "setup Kubernetes deployment in GitLab", "add SonarQube to GitLab CI", "configure Terraform with GitLab", or mentions "TBC", "To-Be-Continuous", "Kicker", or needs help selecting CI/CD templates for their project.

This skill should be used when the user asks to "update TBC schemas", "regenerate schemas from kicker", "sync schemas with new TBC version", "extract schemas from kicker-aggregated.json", "update template schemas", or mentions "schema update", "schema regeneration", "kicker update", or "new TBC release".

This skill should be used when the user asks about "to-be-continuous templates", "gitlab ci templates", "semantic-release", "what templates exist", "show me templates for X", "pipeline templates", "deployment templates", "build templates", "S3 deployment", "kubernetes templates", "docker templates", "template variants", "vault integration", "OIDC authentication", or mentions needing GitLab CI/CD pipeline configuration. Provides interactive guidance for discovering, combining, and adapting to-be-continuous templates with cross-component variant learning.