github-delivery-os
v1.8.0
Published
A GitHub-native Delivery Governance Framework for structured sprint execution, QA review, and collaborative production release control.
Maintainers
Readme
GitHub Delivery Operating System
A GitHub-native Delivery Governance Framework for structured sprint execution, QA review, and collaborative production release control.
Delivery OS embeds structured intake, sprint orchestration, QA governance, and collaborative release gates directly into your GitHub repos — replacing informal coordination (manual approvals, inconsistent sprint tracking, socially enforced releases) without replacing your CI/CD or disrupting how you already work.
Install
npx github-delivery-os install --with-templates .From your repo root. Add --with-labels to create labels via gh CLI, --with-skill for the Claude Code skill, --dry-run to preview first. See the landing page for every flag combination and when to use it, or Consumer Setup for the clone-and-run alternative, configuration, and troubleshooting.
What you get
| | |
|---|---|
| Sprint child creation | One issue per feature line, automatic burn-down, auto-close at 100% |
| Dual approval gates | Release approver + QA sign-off required before deploy |
| Auto-assign QA & Telegram alerts | QA-labeled issues get assigned automatically; optional alerts for bugs, QA, sprints, releases |
| Claude Code skill (--with-skill) | Operate it all in plain language — see below |
The Claude Code skill (.claude/skills/delivery-ops/SKILL.md) can:
- Create issues that trigger real automation — sprint planning, production release, QA request, and bug issues shaped exactly as the installed workflows expect, not just plain issues
- Comment as an approver — release/QA sign-off in the phrasing
authorize-deploymentactually recognizes - Check status — labels, latest comments, sprint burn-down
- Run autonomous task tracking — notice tasks/bugs while working in a session, file them, group them into phases via sprints, maintain a roadmap issue, and update/close them as work progresses
- Turn a spec into a full breakdown — an SRS/PRD or a plain-language feature description becomes real phase (sprint) and task issues, not just a document
- Run a cleanup sweep — finds stale/orphaned/inconsistent issues and roadmap drift, always confirmed before anything is touched
Full workflow table, quick start, and Claude Code walkthroughs are on the landing page.
Documentation
| Document | Description | |----------|-------------| | Landing page & quick start | Overview, full command reference, workflows, Claude Code walkthroughs | | PRFAQ | Product overview and FAQs for all audiences (npm launch, install, governance) | | Press release (npm) | Formal announcement: Delivery OS on npm | | Consumer Setup | Installation, configuration, variables, labels, Telegram, uninstall | | How To | Create sprints, request releases, approve, report bugs, QA requests | | Architecture | Workflows, templates, data flow | | Governance | Lifecycle, approval gates, automation rules |
License
MIT License. See LICENSE for details.
