spec-driven-ci
Automates CI/CD pipeline generation for DevForgeAI projects, enforcing strict validation phases.
Install
mkdir -p .claude/skills/spec-driven-ci && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13474" && unzip -o skill.zip -d .claude/skills/spec-driven-ci && rm skill.zipInstalls to .claude/skills/spec-driven-ci
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Generate CI/CD pipeline workflows through spec-driven workflow generation with structural anti-skip enforcement. Implements 5 phases covering preflight validation, configuration loading, workflow template generation, cost optimization, and final validation using the Execute-Verify-Gate pattern at every step. Designed to prevent token optimization bias through lean orchestration and binary CLI gate enforcement. Currently supports GitHub Actions with cost-optimized Codex API integration (prompt caching, Haiku preference, max-turns limits). Use when setting up CI/CD automation for DevForgeAI projects. Always use this skill when the user runs /setup-github-actions. Also use when the user mentions GitHub Actions setup, CI/CD pipeline generation, headless DevForgeAI execution, or workflow automation for /dev and /qa commands.Key capabilities
- →Generate GitHub Actions workflows for headless `/dev` execution
- →Create PR quality gates with automated `/qa` validation
- →Configure parallel story execution with a matrix
- →Generate optional workflows for DevForgeAI installer testing
- →Optimize CI costs with prompt caching and model preferences
- →Pre-configure `ask the user` responses with `ci-answers.yaml`
How it works
The skill generates CI/CD pipeline workflows based on specifications, enforcing anti-skip rules and integrating cost optimization strategies.
Inputs & outputs
When to use spec-driven-ci
- →Set up GitHub Actions pipelines
- →Configure automated CI/CD workflows
- →Initialize headless DevForgeAI build processes
About spec-driven-ci
Generates CI/CD workflows using an Execute-Verify-Gate pattern. It enforces structural anti-skip rules and integrates with Codex for cost-optimized execution.
>
When not to use it
- →The user does not want to set up CI/CD automation for DevForgeAI projects
- →The user does not want to use GitHub Actions
Limitations
- →It currently supports only GitHub Actions
- →It requires GitHub Secrets for API keys
- →It relies on specific context files like `tech-stack.md` and `source-tree/`
How it compares
This workflow automates the generation of CI/CD pipelines with built-in anti-skip enforcement and cost optimization, providing a structured and efficient setup compared to manual configuration.
Compared to similar skills
spec-driven-ci side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| spec-driven-ci (this skill) | 0 | 1mo | Review | Advanced |
| github-workflow-automation | 11 | 2mo | Review | Advanced |
| github-actions-templates | 7 | 3mo | No flags | Intermediate |
| hooks-automation | 3 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by bankielewicz
View all by bankielewicz →You might also like
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
hooks-automation
ruvnet
Automated coordination, formatting, and learning from Claude Code operations using intelligent hooks with MCP integration. Includes pre$post task hooks, session management, Git integration, memory coordination, and neural pattern training for enhanced development workflows.
cli-commands
windmill-labs
MUST use when using the CLI.
dev
atopile
LLM-focused workflow for working in this repo: compile Zig, run the orchestrated test runner, consume test-report.json/html artifacts, and discover/debug ConfigFlags.
toolhive-release
stacklok
Creates ToolHive release PRs by analyzing commits since the last release, categorizing changes, recommending semantic version bump type (major/minor/patch), and triggering the release workflow. Use when cutting a release, preparing a new version, checking what changed since last release, or when the user mentions "release", "version bump", or "cut a release".