game-design-feature-prioritization — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited game-design-feature-prioritization (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Choose the strongest next move, not just the loudest idea.
Use this skill to compare candidate features or solution paths and decide what should happen now, later, or not at all. Keep the process practical. Rough structured judgment is better than fake precision, but explicit comparison is still useful.
Read references/family-conventions.md when you need the shared conventions for this GROW-derived skill family.
Generate:
Make sure the compared items are clear and meaningfully distinct.
Use rough structured scoring such as 1-5 for:
Do not choose purely by raw score. Also consider:
For each option, classify it as:
| Option | Impact | Cost | Strategic Fit | Risk | Timing | Notes |
|---|
The locally optimal choice is not always the strategically best one.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.