Spec Author

Turns a fuzzy feature request, idea, or ticket into a precise, testable specification an agent can build against without re-deriving intent: a problem statement (the why, before any solution), explicit scope and NON-goals, acceptance criteria written as checkable assertions, enumerated edge cases, interface/contract sketches, and an explicit criterion→eval handoff. Use when asked to write a spec, turn an idea / ticket / PRD into requirements or acceptance criteria, scope a feature before building, define "done", or "spec this out". Do not trigger for: choosing between competing architectures, data models, or a build-vs-buy / rewrite-vs-refactor call — deciding the HOW (us…