What problem does it solve? Rough ideas discussed in a coding session often never become actionable work items, or get filed as vague issues that no one can execute later. This Skill investigates the codebase, checks the issue board for duplicates and conflicts, and files a detailed GitHub issue that a fresh agent could execute with zero prior context. ## Core Features & Use Cases - Evidence-grounded investigation: Reads the actual code, cites file:line references, checks git history, and verifies the claim still holds on the current branch before writing anything. - Board hygiene checks: Detects duplicates (including recently closed issues), direction drift against open issues, and dependency relationships (blocked by, blocks, parent/child) before filing. - Structured issue authoring: Produces issues with a plain-language summary for stakeholders, technical detail for executors, evidence, scope boundaries, and an observable "Done when" condition; supports splitting into multiple issues or epics. - Use Case: After discussing a bug where several tools break on the deployed site, say "/newissue" and the Skill investigates the code, confirms the bug still exists, checks the board, and files a labeled, cross-linked GitHub issue with reproduction evidence. ## Quick Start Ask the assistant to turn the bug or feature idea you just discussed into a GitHub issue using the newissue skill.