Stats
Actions
Tags
From pdm-quality-testing
Define formal quality gates between delivery phases — so teams don't proceed to the next phase until the current one meets agreed standards.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-quality-testing:quality-gatesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Define formal quality gates between delivery phases — so teams don't proceed to the next phase until the current one meets agreed standards.
Define formal quality gates between delivery phases — so teams don't proceed to the next phase until the current one meets agreed standards.
Gate 1: Dev → QA (Code Ready) Criteria to pass:
Gate 2: QA → UAT (QA Complete) Criteria to pass:
Gate 3: UAT → Release Candidate (Business Approval) Criteria to pass:
Gate 4: Release Candidate → Production (Go-Live) Criteria to pass:
If a gate is not passed:
/launch-checklist or /assess-readinessnpx claudepluginhub devmuslim/pdm-skills --plugin pdm-quality-testingScans the codebase for `ponytail:` comments and compiles a debt ledger of deliberate shortcuts and deferrals, flagging entries with no upgrade path.