What problem does it solve? Approved designs often live only in conversation context and vanish when a session ends. This Skill persists an approved design into a durable artefact—a parent ticket carrying the full design with child tickets, or a structured Markdown document—so any future session can recover the design and resume work. ## Core Features & Use Cases - Multi-system persistence: Detects and creates tickets in GitHub Issues, Jira, GitLab, or Linear via MCP tools or CLI binaries, falling back to a structured Markdown document when no ticketing system is available. - Design-driven decomposition: Proposes ticket breakdowns read from the design's own structure, with dependency ordering, acceptance criteria, and an approval gate before anything is created. - Failure-safe creation: Creates the parent first, then children in dependency order, with explicit handling for partial failures and no destructive rollback. - Use Case: After approving an architecture design for a new feature, ask to file it as tickets; the Skill detects GitHub from the git remote, drafts an Epic-style parent with the full design plus child tickets, and creates them only after your approval. ## Quick Start Ask the AI to break the approved design into tickets and file them in the detected issue tracker.
