qmu/delivery-lead
plugins/standards/skills/lead-delivery/SKILL.md
Owns the CI/CD pipeline stages, deployment strategies, and artifact promotion flow from source to production for the project.
$ install --global
skillsauthnpx skillsauth add qmu/workaholic delivery-leadInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 4:35 AM300.4s1 file scanned
SKILL.md
- name:
- delivery-lead
- description:
- Owns the CI/CD pipeline stages, deployment strategies, and artifact promotion flow from source to production for the project.
- user-invocable:
- false
Delivery Lead
Role
The delivery lead owns the project's delivery policy domain. It analyzes the repository's CI/CD pipelines, build processes, deployment strategies, and release processes, then produces policy documentation that accurately reflects what is implemented.
Goal
- The
.workaholic/policies/delivery.mdaccurately reflects all implemented delivery practices in the repository. - No fabricated policies exist.
- Every statement cites its enforcement mechanism.
- All gaps are marked as "not observed".
Responsibility
- Every policy scan produces delivery documentation that reflects only implemented, executable practices.
- CI/CD pipelines are analyzed: what pipeline tools exist, what stages are defined, how they are triggered.
- Build processes are documented with citations to the enforcement mechanisms.
- Deployment strategies are documented: what deployment methods are used, what environments exist, how artifacts are promoted.
- Release processes are documented: how versions are managed, what release workflows exist.
- Gaps where no evidence is found are clearly marked as "not observed" rather than omitted.
Policies
Practices
Standards
Related Skills
qmu/write-release-note
documentation
VerifiedTrustedCommunity
Release note content structure and guidelines for GitHub Releases.
1SKILL.mdUpdated May 28, 2026
qmu/ship
testing
VerifiedTrustedCommunity
Ship workflow - merge PR, deploy via CLAUDE.md, and verify production.
1SKILL.mdUpdated May 28, 2026
qmu/review-sections
development
VerifiedTrustedCommunity
Generate branch-story sections 4-7 (Outcome, Historical Analysis, Concerns, Successful Development Patterns) from archived tickets and carry-over verdicts. Used by the report workflow when assembling a PR story.
1SKILL.mdUpdated May 28, 2026
qmu/report
business
VerifiedTrustedCommunity
Story writing, PR creation, and release readiness assessment for branch reporting.
1SKILL.mdUpdated May 28, 2026