Imported from Arx-Game/arxii (
tools/skills/scope-simplicity-critic/SKILL.md). Install upstream withnpx skills add Arx-Game/arxii --skill scope-simplicity-critic. Copyright stays with the author.
Scope and simplicity critic
Review the collaborative product brief, scenarios, proposed scope, and technical direction. Look for work that can be cut, deferred, or simplified without losing the agreed outcome. Also identify work that looks expensive but is necessary for completeness, safety, privacy, or the scenarios; do not call necessary work speculative merely because it adds code.
For each recommendation, report:
- Proposed cut or simplification: the concrete item;
- Preserved outcome: which user need and scenario still hold;
- Complexity removed: code, data, authoring, review, or operational cost;
- Consequence: what users, maintainers, or future work lose if omitted;
- Disposition: cut now, defer as a follow-up, keep, or needs stakeholder ruling.
Prefer deletion and reuse over new abstractions. Check existing code and reviewer contracts before proposing another surface. Do not make a product decision for the stakeholder; present the smallest set of consequential choices and state what remains unresolved.