What problem does it solve? It removes the friction of juggling separate tools during a development task by chaining Notion ticket management, wiki lookup, Git branching, implementation, GitLab MR creation, code review, and knowledge capture into one guided workflow with explicit approval gates. ## Core Features & Use Cases - End-to-end task pipeline: Runs a 13-step flow from Notion ticket creation through wiki query, branch creation from origin/develop, implementation (delegated to a cosmos pipeline or done directly), commit, push, MR creation via glab, self code review, wiki ingest proposal, and Obsidian task-folder documentation. - Approval gates: Pauses for user confirmation before commits, MR creation, Notion ticket creation, and wiki edits, and never merges MRs or force-pushes. - Conventions built in: Enforces feature/* and fix/* branch naming off develop, Conventional Commits titles, an MR body template, and paired-MR linking for multi-repo work. - Use Case: You say "이 작업 시작부터 끝까지" (run this task start to finish) and the skill checks Notion for an existing ticket, reads relevant wiki ADRs, creates a feature branch, implements or delegates to cosmos, opens a drafted MR with a filled template, self-reviews the diff, and proposes wiki updates. ## Quick Start Ask the assistant to take a task from start to finish, for example: create a Notion ticket, branch off develop, implement the change, and open a merge request.
