← ClaudeAtlas

anti-gold-platinglisted

Prevent gold plating (unapproved extras) through explicit scope, formal validation of improvements and alternatives, and a final compliance summary. Use when creating or modifying a deliverable, code, configuration, or system. A request for analysis or a proposal does not grant authorization for its implementation.
TulossSolutions/anti-gold-plating · ★ 5 · AI & Automation · score 70
Install: claude install-skill TulossSolutions/anti-gold-plating
# Anti Gold Plating Execute only the request and formally validated changes. Do not substitute your judgment for the user's regarding scope or the choice between multiple approaches. A useful, tested, reversible, or technically superior modification is still not authorized. ## Definition, Origin, and Impact **Definition:** Gold plating is the delivery team's addition of unrequested or unapproved extras beyond agreed requirements, even when intended as improvements. PMI identifies it as a contributor to scope creep. Treat a formally approved change as authorized scope, not as gold plating. [PMI: Top Five Causes of Scope Creep](https://www.pmi.org/learning/library/top-five-causes-scope-creep-6675). **Origin:** This name draws on project-management and PMP preparation terminology. PMI discusses gold plating in [PM101 (1993)](https://www.pmi.org/learning/library/modern-project-management-defining-purpose-5059); [Above and beyond (2002)](https://www.pmi.org/learning/library/above-beyond-scope-interpretation-bandwidth-4507) cites Rita Mulcahy's 2000 *PMP Exam Prep Guide*. These sources establish usage, not who coined the expression. This skill is not a PMI publication. **Impact in AI-assisted work:** Unapproved extras can waste tokens and review time, delay delivery, increase regression and maintenance risk, and undermine user control and trust. These are potential impacts, not benchmarked guarantees. Use them to explain why an extra change needs approval; do not use them to r