release

Name: release
Availability: InStock
Author: PDLC-OS

Force-release blocked roadmap claims and update Beads, ROADMAP.md, and DECISIONS.md.

Updated Aug 23, 2026

Search Tags:#adr #beads #roadmap #claim #administrative #force-release

Ready to run

npx skills add https://github.com/pdlc-os/pdlc --skill release-pdlc-os

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/pdlc-os/pdlc/tree/main/skills/release
Command: npx skills add https://github.com/pdlc-os/pdlc --skill release-pdlc-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Force-release a blocked roadmap claim to reclaim work ownership, clear bottlenecks, and keep the product cycle moving.

Core Features & Use Cases

Orchestrates a controlled force-release flow across Beads tasks, ROADMAP.md, and DECISIONS.md.
Enforces safeguards: prevents releasing your own active claims and requires a reason for audit.
Optional notifications to relevant parties when a release occurs.

Quick Start

Execute the force-release flow for a given roadmap claim by running /pdlc release F-NNN.

Frequently Asked Questions about release

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

FAQPage Schema

How do I force-release a blocked roadmap claim to reassign ownership?▼

To force-release a blocked roadmap claim, you execute a controlled flow that updates Beads tasks, ROADMAP.md, and DECISIONS.md. This restores progress by clearing bottlenecks and reassigning work ownership while maintaining a documented audit trail.

What safeguards prevent accidental force-release of active roadmap claims?▼

Safeguards prevent you from force-releasing your own active claims and require a justification reason for the audit trail. These constraints ensure blocked work is reclaimed safely without disrupting your own ongoing progress.

Can I send notifications when force-releasing a roadmap claim?▼

Yes, you can send optional notifications to relevant parties when a force-release occurs. This ensures stakeholders are informed after the Beads, ROADMAP.md, and DECISIONS.md status changes and documentation updates are completed.

How do I document a force-release decision for audit trails?▼

Documenting a force-release decision requires providing a justification reason that is recorded in DECISIONS.md. The process coordinates status changes across Beads and ROADMAP.md to ensure the entire audit trail remains consistent.

Why does force-releasing a stuck claim require a justification reason?▼

Force-releasing a stuck claim requires a justification reason to maintain a clear audit trail. This ensures that every ownership reassignment and status change across Beads, ROADMAP.md, and DECISIONS.md is documented for review.

When should I force-release a roadmap claim instead of waiting?▼

You should force-release a roadmap claim when progress is blocked and work ownership needs to be reclaimed. This action clears bottlenecks and keeps the product cycle moving by orchestrating updates across Beads, ROADMAP.md, and DECISIONS.md.