What problem does it solve? Writing well-scoped engineering tickets from a rough proposal requires manual codebase investigation to find real file paths, existing tests, and acceptance criteria. This Skill automates that investigation and produces ready-to-implement ticket files. ## Core Features & Use Cases - Proposal Comprehension: Parses any natural-language markdown proposal into discrete concerns without requiring the author to supply file paths or acceptance criteria. - Multi-Step Investigation: Searches knowledge graphs, doc registries, prior ticket history, source code, and existing tests to derive concrete, testable acceptance criteria per concern. - Structured Ticket Writing: Generates TCK-YYYYMMDD-<SHORT-SCOPE>.md files with deduplication, tag-registry validation, dependency sequencing via SEQUENCE.md, and optional linking to an epic ticket. - Use Case: A product manager writes a feature proposal in docs/plans/proposal.md; run the skill to produce a folder of investigation-backed tickets, then hand them to /implement-epic for implementation. ## Quick Start Ask the agent to run create-tickets with source pointing at your proposal markdown file, for example: create tickets from docs/plans/proposal.md.