Generate GitLab CI/CD configurations using To-Be-Continuous framework
Generates GitLab CI/CD configurations using To-Be-Continuous framework templates.
/plugin marketplace add rafaelcalleja/claude-market-place/plugin install gitlab-tbc@claude-market-placeOptional description of what you want to buildFIRST: Load the building-with-tbc skill using the Skill tool.
The skill provides the Framework-First Principle and all TBC knowledge. Follow this principle strictly.
Analyze user request and route to appropriate flow:
| Keywords | Flow | Action |
|---|---|---|
| create, generate, new, setup, build | GENERATE | New configuration |
| migrate, convert, upgrade, existing | MIGRATE | Convert to TBC |
| what, how, explain, list, compare | CONSULT | Answer questions |
Never assume solution. Always evaluate framework first.
Identify core need:
Evaluate framework fit:
references/component-decision.md for decision flowchartreferences/templates-catalog.md for matching templatesschemas/_meta.json + schemas/{template}.json for capabilitiesreferences/variantes.md for variantsOutput decision path (mandatory):
## Decision Path
User Request: "[request]"
│
▼
Core Need: [action + target + triggers]
│
▼
[Show branch taken from decision flowchart]
│
▼
Result: [TBC / TBC+variant / TBC+script / Custom (with reason)]
Configure global options (from skill):
Template selection - Follow skill's workflow
Configure variables - Use skill's configuration format
Generate - Follow skill's format
CRITICAL: Use SlashCommand tool with tbc:validate before presenting
.gitlab-ci.ymltbc:validate[Generated/Migrated YAML]
---
Secret Variables (configure in GitLab CI/CD Settings):
- VARIABLE_NAME: Description
---
Next Steps:
1. Copy to .gitlab-ci.yml
2. Configure secret variables
3. Commit and push