spec-quality-checkerlisted

# Spec Quality Checker ## Purpose Turn vague project intent into an explicit quality signal before deeper execution continues. This skill exists to stop polished garbage from moving forward simply because the output looks professional. ## What It Checks The checker should score whether the project is clear enough across five dimensions: 1. Problem framing 2. Target user clarity 3. Success definition 4. Constraints and assumptions 5. Execution readiness ## Core Rule If the idea is still unclear, the system should not pretend that deeper implementation is trustworthy. It should: - say what is missing - ask only the next most useful questions - recommend the next workflow step - keep the language simple ## Output Contract The result should always include: - a score - a clarity level - blockers - warnings - strengths - recommended questions - the next best workflow action ## Decision Policy ### Blocked Use when the project still lacks the basics: - no clear problem - no clear user - no clear success definition In this state, the system should route back to onboarding or planning. ### Weak Use when some signal exists, but the project can still drift badly. Planning may continue, but implementation should remain gated. ### Usable Use when the system has enough clarity to proceed, with explicit warnings where needed. ### Strong Use when the project has enough grounded intent to support specialist execution with low ambiguity. ## Safety Rules Do not: - invent