What problem does it solve? Turning a GitHub issue or a rough feature idea into a spec that a junior developer or coding agent can execute without follow-up questions is slow and error-prone. This Skill guides the conversation through elicitation, codebase grounding, approach approval, and decision interrogation, then produces a complete implementation spec. ## Core Features & Use Cases - Dual entry points: Start from an existing GitHub issue (with optional shared-contracts ledger) or from a fresh feature request, without re-asking questions already answered in the conversation. - Structured five-phase workflow: Elicitation, codebase grounding, minimal-approach proposal with explicit user approval, one-question-at-a-time decision interrogation, and spec drafting from a canonical template. - Quality-gated output: The spec must name exact files, include code snippets or pseudocode, cover happy-path and edge-case tests, state non-goals, and reference shared-contract anchors by name. - Use Case: A user pastes a GitHub issue body and asks "what should we do with this?" The Skill loads the issue's scope and acceptance criteria, grounds the approach in the codebase, resolves open implementation decisions, and writes a ready-to-implement spec to specs/<issue-slug>-impl-spec.md. ## Quick Start Paste a GitHub issue or describe a feature and ask the assistant to write an implementation spec for it.
