adlc
v0.8.2Agentic Delivery Lifecycle: interview-driven repo intake, app classification, hardened Dockerfiles, Terraform on Azure, GitHub Actions CI/CD with immutable tags, deployment verification and Jira tracking. Every platform choice is an interview option.
By Abdelazim Ali0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 9 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install adlc for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install adlc@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/integranz/adlcClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/adlc/.
Plugin files
├── .claude-plugin/plugin.json├── skills/bootstrap/SKILL.md├── skills/deploy/SKILL.md├── skills/dockerize/SKILL.md├── skills/plan/SKILL.md├── skills/ticket/SKILL.md├── skills/verify/SKILL.md└── .mcp.json
Included Skills6
Use when the user asks to onboard, containerise, "set up delivery", CI/CD, deployment or infrastructure for a repository, to run the ADLC intake, or to change delivery options (cloud, compute, registry, runner, versioning, branching, tracker, secret store, base image). Interviews the user for the options that shape generated files, classifies the apps with the explore sub-agent, writes .adlc/config.yaml, scaffolds the repo-side files deterministically and opens a tracking ticket.
Trigger the CD workflow for an immutable image tag, wait for the environment approval, and monitor the run to completion.
Build the hardened multi-stage container image for one app from the adlc templates, run it locally, and prove it answers its health endpoint with the expected version as a non-root user.
Run terraform fmt, validate and plan for one infrastructure layer of this repository and summarise the changes. Never applies; tells the human exactly how to approve and apply.
Create, transition or comment on the tracking ticket in the configured tracker (Jira via the Atlassian MCP) with a structured description and evidence links.
Run falsifiable post-deployment checks for an environment and tag and write an evidence file. Delegates to the verify sub-agent.
MCP servers3
- url
- https://mcp.atlassian.com/v2/mcp
- command
- npx
- args
- -y @azure/mcp@latest server start --namespace acr --namespace containerapps --namespace keyvault --namespace group --namespace role --namespace subscription --namespace monitor --read-only
- url
- https://api.githubcopilot.com/mcp/x/actions
Plugin manifests1
{
"name": "adlc",
"version": "0.8.2",
"description": "Agentic Delivery Lifecycle: interview-driven repo intake, app classification, hardened Dockerfiles, Terraform on Azure, GitHub Actions CI/CD with immutable tags, deployment verification and Jira tracking. Every platform choice is an interview option.",
"author": {
"name": "Abdelazim Ali"
},
"keywords": [
"devops",
"azure",
"terraform",
"github-actions",
"docker",
"jira",
"delivery"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[adlc on Agent Plugins Marketplace](https://pluginsmp.com/plugins/adlc)