Essential command-line tools and system utilities.
Deterministic team development workflow for Claude Code. Enforces a mandatory sequence of phases (Setup → Brainstorm → Plan → Execute → Quality Check → Ship) with Linear integration, TDD requirements, and quality gates. Activates when working on issues/tasks, when user mentions Linear issues (e.g., ENG-123), when starting development work, or when preparing to ship code. Commands: /team:task, /team:quality-check, /team:ship.
Migrate tasks from Things 3 to Todoist with duplicate detection and merge support. Use when the user asks to migrate, export, sync, or move tasks from Things to Todoist.
Generate comprehensive daily briefings by orchestrating data from calendar, email, Teams, and Wrike into a Notion page. Triggers on "Generate my daily briefing", "Create today's briefing", "What's on my schedule today?" (comprehensive view), or "Give me my daily briefing for [date]". Do NOT trigger for simple calendar/email queries - use this only for full briefing generation.
Work with OpenSpec change proposals (openspec/changes/*). Draft proposals, validate/show, apply tasks, and archive.
Microsoft PowerPoint (.pptx) presentation creation, editing, and analysis.
Analyze, refactor, and enhance existing Workscript workflow JSON files based on user feedback. Use when asked to improve, optimize, refactor, fix, or enhance an existing workflow. Triggers on requests like "improve this workflow", "optimize the X workflow", "add error handling to", "make this workflow more robust", "refactor for flat structure", or when users provide critique, suggestions, or requirements for workflow improvements. Complements the new-workflow skill by handling post-creation refinements.
Find relevant designs and scopes for a project. Should be used whenever a user mentions a design / scope doc for a project.
Detect project tech stack, build tools, test frameworks, CI/CD, and code quality tools. Use when you need to know how to build, test, lint, or run a project.
Use for code review and quality feedback from both Codex and Gemini. Triggers on "council review code", "council code review", "have council review this", "get council feedback on code".
코드 탐색, 코드 분석, 탐색, 코드 구조, 심볼 분석 - Use when exploring or analyzing code. Systematic code exploration workflow using Serena MCP tools for symbol navigation and reference tracking.
Automatically process reported issues and feature requests through the full development workflow. Roleplay as CTO for decision-making, then execute the development workflow directly.
This skill MUST be used when the user asks to "get backlog", "list backlog issues", "show backlog", "what's in the backlog", "backlog summary", "list Jira issues", "show issues in project", "what issues are pending", "show sprint issues", "active sprint", "past sprints", or needs a quick overview of multiple issues. Use this for bulk issue listing - use jira-issue for single issue details.
Unified Specification-Driven Development (SDD) workflow. Auto-detects user intent and routes to correct phase. Handles the complete development lifecycle from product definition to implementation. Triggers on: "create feature", "implement", "plan", "audit", "define product", "feature", "/feature", "/implement", "/plan", "/audit", "/define-product", "/generate-constitution", "what's the SDD status", "next step". REPLACES: define-product, generate-constitution, specify-feature, clarify-specification, create-implementation-plan, generate-tasks, implement-and-verify, sdd-orchestrator.
Linear integration via CLI. Triggers on "create issue", "new ticket", "create a ticket", "linear issue", "update status", "post comment".
Linear 이슈에 대한 작업 계획을 수립하고 sub-task를 생성합니다. "이슈 계획", "작업 분할", "sub-task 생성" 요청 시 사용
Dispatches work to Jules agents via the CLI. Automatically generates context-rich prompts from Beads issues and spawns async sessions. Use when user says "send to jules", "assign to jules", "dispatch task", or "run in cloud".
Use when working with Linear issues across development workflow - uses Linearis CLI with JSON output for zero-context issue management. Get details, create issues, update status, and add comments without consuming tokens in main session.
Plan and execute Azure DevOps migrations between organizations or projects. Use when migrating Azure DevOps resources or consolidating projects.
Epic and story planning with GitHub integration. This skill should be used when creating epics, detailing stories, managing acceptance criteria, or setting up GitHub issue templates. Triggers on "create epic", "plan epic", "detail story", "add gherkin", "acceptance criteria", "issue template".
This skill should be used when executing work plans, specifications, or todo files systematically while maintaining quality and shipping complete features.
Write or update phase summary documentation. Use when asked to create, write, or update a phase summary, document a phase, or summarize what was built in a phase.
