pm-closure-validation

What This Skill Does

The pm-closure-validation skill acts as an authoritative Product Owner and Release Manager agent within the OpenClaw ecosystem. It enforces a strict, standardized 3-gate quality assurance process to determine if a software increment is truly ready for closure. By auditing task completion, test coverage, and documentation parity, it prevents incomplete code or technical debt from entering the main branch. It specifically looks for P1, P2, and P3 task priorities, cross-references acceptance criteria, and flags scope creep that may have occurred during the sprint lifecycle.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-pm-closure-validation

Ensure your project repository follows the standard OpenClaw increment directory structure (.specweave/increments/{id}/) so the agent can properly map your specification, plan, and task files.

Use Cases

• Pre-Release Auditing: Use this before issuing a /sw:done command to ensure the increment is production-ready.
• Scope Creep Detection: Identify tasks that were injected into the increment without proper documentation or approval.
• Quality Gate Reviews: Formalize the handover process between development and product management by generating a verifiable checklist report.
• Documentation Sync: Ensure that CLAUDE.md, README.md, and CHANGELOG updates match the actual code changes implemented.

Example Prompts

1. "Perform a 3-gate validation check for increment 0042. Let me know if I have any pending P1 tasks."
2. "I am ready to close this increment. Run the pm-closure-validation to ensure all test requirements are met and documentation is up to date."
3. "Validate this sprint. Are there any deferred P2 tasks that I need to explicitly address before closing?"

Tips & Limitations

• Tip: Run this skill at least 24 hours before your projected deadline to allow enough time to address any discovered technical debt or unfinished documentation.
• Tip: Ensure your tasks.md file contains embedded test results for the most accurate evaluation during the Gate 2 audit.
• Limitation: The agent relies on the presence of specific files in .specweave/increments/. If your project structure deviates from this standard, the agent may be unable to load the necessary context for the audit.