executing-tickets
Use to implement tickets created by writing-tickets skill
Use to implement tickets created by writing-tickets skill
Erstellt und pflegt User‑Story‑Maps als Sub‑Skill des AI‑Lead‑Orchestrators; führt Teams von Ziel & Persona über Backbone/Activities und vertikale Priorisierung zum Slicing (MVP/Walking Skeleton) und exportiert testbare Backlog‑Artefakte (JSON/CSV/Mermaid).
Use when approaching any animation task—establishing foundational thinking patterns, teaching animation principles, or when none of the specialized thinking styles quite fit the situation.
Use when creating or updating docs/plan.md, docs/tasks.md, or docs/progress.md, or when asked about plan/todo/progress and next steps.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Create PR with Linear integration and quality summary. Use when ready to merge an Epic branch to main.
Bridges approved PRDs to implementation by mapping user stories to tasks with skill assignments, effort estimates, and progress tracking. Use after PRD approval to create actionable implementation plan.
Sisyphus専用の実装フロー、Subtask処理、Phase別責任分担、チェックリスト、完了報告フォーマットを定義