utility-pm-release-conductor

Walks a guided 6-gate release runbook from readiness checks through tagging and pushing a pm-skills release.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill utility-pm-release-conductor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: utility-pm-release-conductor
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/utility-pm-release-conductor
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill utility-pm-release-conductor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cutting a release involves many error-prone steps—readiness checks, adversarial review, version bumps, CHANGELOG prep, re-verification, tagging, and post-tag hygiene—and skipping any of them risks shipping a broken release. This Skill enforces a structured 6-gate runbook (G0 through G4) that refuses gate bypasses and tags only the re-verified commit SHA.

Core Features & Use Cases

  • Guided 6-Gate Release Flow: Walks G0 readiness, G1 adversarial review, G2 version bump and CHANGELOG, G2.5 commit and re-verify, G3 tag and push, and G4 post-tag hygiene, pausing for explicit maintainer confirmation at each gate.
  • Cross-Client Dispatch: Uses the native pm-release-conductor sub-agent on Claude Code, and on other clients (Codex CLI, Cursor, Windsurf, Copilot, Gemini CLI) reads the canonical agent definitions and inlines the auditor and curator behaviors via a reference-and-execute-inline pattern.
  • Gate-Bypass Refusal and Dry-Run Mode: Refuses attempts to skip gates, supports a --dry-run rehearsal that simulates all gates without tagging or pushing, and emits gate-by-gate status output.
  • Use Case: A maintainer on Codex CLI wants to ship pm-skills v2.33.0 with the same discipline as Claude Code. They invoke the skill with the target version, confirm each gate as audits and CHANGELOG drafts run inline, and the release is tagged only at the re-verified SHA.

Quick Start

Ask the AI to walk you through the guided release runbook for your target pm-skills version, for example by saying to run the 6-gate release flow for v2.33.0 in dry-run mode first.

Frequently Asked Questions about utility-pm-release-conductor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I cut a pm-skills release with a guided runbook?

Invoke the skill with your target version, optionally with --dry-run first. It walks six gates from pre-tag readiness through tag and push, pausing at each gate for your explicit confirmation before advancing.

Can I run the release conductor on Codex CLI, Cursor, or other non-Claude clients?

Yes. On clients without native pm-skills sub-agent support, the skill reads the canonical agent definitions and executes the auditor and curator behaviors inline. Dry-run was validated on Codex CLI; other clients are experimental, so rehearse with --dry-run first.

What happens if I try to skip a release gate?

The conductor refuses gate bypasses by design. Each gate must pass and receive explicit maintainer confirmation before advancing, and the tag at G3 is created only for the SHA captured during the G2.5 re-verification step.

When should I use the release conductor instead of the skill auditor or changelog curator?

Use the conductor only for a full release cut. If you only need a governance audit, use the skill auditor; if you only need a CHANGELOG draft, use the changelog curator. The conductor inlines those behaviors at gates G0, G2, and G2.5 as part of the release flow.

What are the limitations of inline execution on non-Claude clients?

The conductor, auditor, and curator all run in one context window, so long releases may approach context limits. The client also needs Bash, Read, Edit, Grep, and Glob access, and a refusal from an inlined child fails the corresponding gate.