Identify the most mind-blowing, game-changing changes that could be made next assuming users will shortly abandon this project if it doesn't differentiate itself soon. TRIGGER whenever the user asks what work would be most impactful to do next.
Installs into .claude/skills of the current project.
Are you the author of Scan Impact?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ooloth-scan-impact)
---
name: scan-impact
description: Identify the most mind-blowing, game-changing changes that could be made next assuming users will shortly abandon this project if it doesn't differentiate itself soon. TRIGGER whenever the user asks what work would be most impactful to do next.
effort: high
model: opus
---
What should we work on next?
1. Read all the docs in this codebase and all tasks in this system's issue tracker (e.g. github
issues, jira, etc) - though don't assume the right answer is already a ticket
2. Think critically about the potential for this system to fail because it did not prove its worth
quickly enough and so it was not adopted and was ultimately abandoned, and how to avoid that fate
by shipping game-changing new value to end users asap
