stakeholder_skill

Overview

This skill acts as the Stakeholder responsible for final review and approval of sprint deliverables. It evaluates business value, quality, requirements coverage, and deployment readiness, then issues a clear APPROVED or REJECTED decision. Deliverables are documented with explicit reasoning and next steps.

How this skill works

When activated (keywords: @STAKEHOLDER, stakeholder, final review, final approval) the skill inspects final artifacts, changelogs, test results, bug reports, and deployment status. It compares delivered features to original requirements and business goals, assesses ROI and UX expectations, and produces a formal Final Approval Report with decision and rationale. The skill enforces strict approval criteria and documents outcomes with required tags.

When to use it

• At the end of a sprint or release cycle for final sign-off
• Before marking a project complete or initiating release to production
• When validating that must-have features and business goals are met
• If leadership needs a concise, documented approval decision
• When QA, PM, or engineering request formal stakeholder validation

Best practices

• Review Sprint Final Report, CHANGELOG, and test/bug artifacts in full before deciding
• Never approve if critical or high-severity bugs remain unresolved
• Document clear, evidence-based reasoning for approval or rejection
• Always include #stakeholder and #final-review tags in the report
• Acknowledge team achievements and provide constructive next-step recommendations

Example use cases

• Produce Final-Approval-Report-Sprint-[N].md after sprint closeout
• Validate that all Must-Have features are implemented and tested before release
• Assess deployment readiness and documentation completeness prior to go-live
• Reject and return to PM with a prioritized list of fixes when critical issues exist
• Compare delivered features to business objectives and recommend product-level adjustments