plugin-ideation

To validate a Claude plugin idea, apply a 7-criteria checklist that scores whether the concept addresses a repeatable workflow pain point. This ensures the plugin is shareable, repeatable, and testable before development begins.

Problem-first plugin ideation frames a plugin around solving recurring workflow friction rather than personal convenience. It prevents wasted development effort on one-off or already-solved plugins.

Transform vague plugin concepts into concrete plans by applying pain-point mining guidance and a structured validation checklist. This converts abstract ideas into problem-first definitions ready for research and building.

Common plugin ideation anti-patterns include building self-only tools, starting tool-first rather than problem-first, and allowing scope creep. Recognizing these traps ensures ideas address genuine repeatable pain points.

Yes, the plugin ideation process applies to developers and teams evaluating whether a proposed plugin addresses a repeatable workflow pain point. It provides structured criteria to decide whether to build.

After validating a plugin idea, pass the concrete concept to subsequent skills for research, architecture, building, evaluation, and validation. This workflow hand-off ensures structured development progression.