Boost efficiency with task automation and organizers.
Trigger and monitor GitHub Actions workflows, CI/CD pipelines, and automated builds. Use when running workflows, triggering CI, deploying via GitHub Actions, downloading artifacts, or checking workflow status on github.com
Methodology for breaking specifications into actionable tasks organized by features. Use when creating task lists or orchestrating implementation.
/sdlc-studio [type] [action] - Manage specifications and test artifacts. Types: prd, trd, epic, story, persona, bug, test-strategy, test-spec, test-automation, code, test, status, migrate, init, hint. Use when user wants to create/update PRDs, TRDs, generate epics, stories, track bugs, test artifacts, or plan/review code.
Use after completing brainstorming/design phase. Links design document to task, parses subtasks, shows preview for approval, implements smart merge with existing subtasks. Handles post-design workflow for beads tasks.
기획 문서 기반 GitHub 이슈/마일스톤 생성 스킬. 화면 정의서, 기획서, 백로그를 분석하여 이슈와 마일스톤을 자동 생성합니다. 사용 시기: (1) 새 프로젝트 초기 이슈 생성 (2) 새 화면/기능 추가 시 이슈 생성 (3) 마일스톤 설정 (4) 이슈 커버리지 분석 (5) /github-issues 호출 시
Database investigation skill for Jira tickets with secure credential handling. Multi-Agent Swarm for 3x faster parallel execution. Auto-learns from investigations, searches similar tickets, integrates with Jira, and detects anomalies.
Daily journal management for the my-vault Obsidian vault. Use for morning routines, daily reviews, quick journal updates, checking yesterday's entry, or setting today's highlight. Triggers on "good morning", "daily review", "journal", "what did I do", "highlight".
Manage beads issues for tracking development work. Use this skill when: (1) Starting a new task or feature, (2) Creating implementation or testing plans, (3) Tracking session progress and discoveries, (4) Finding available work, (5) Closing completed work. Beads stores issues in git-tracked JSONL with rich fields for design notes, acceptance criteria, and session notes.
Generates session summaries and resume prompts for multi-session work. Use when completing features, before context limits (~50% capacity), or when user says "summary", "wrap up", "save progress", "end session". Creates markdown in docs/summaries/ with completed work, files modified, and restart instructions.
GitLab CLI (glab) for merge requests, issues, and CI/CD pipelines. Use when working with GitLab repositories for MR creation/review, issue management, pipeline debugging, or any GitLab API operations. Triggers on GitLab URLs, mentions of "merge request" or "MR" (not "PR"), gitlab.com, or glab commands.
Alpha/beta/RC tagging patterns and GitHub pre-release workflows for managing pre-production releases. Use when creating alpha releases, beta releases, release candidates, managing pre-release branches, testing release workflows, or when user mentions pre-release, alpha, beta, RC, release candidate, or pre-production versioning.
Connect Claude Code with GitHub Issues for rapid problem resolution. This skill should be used when users need to manage, analyze, prioritize, and resolve GitHub issues automatically without manual intervention.
Expert in corporate communication, employee engagement, and change management. Use when drafting internal announcements, change communications, leadership messages, or employee updates. Triggers include "internal announcement", "employee communication", "change management", "company update", "leadership message", "town hall".
NDP-specific GitHub workflow using Trunk-Based Development (TBD). Commit directly to main with conventional commits. Use this skill for ALL git operations in the Neural Data Platform project.
Fetches active Wrike tasks and categorizes by workflow status. CRITICAL - Always fetch workflows FIRST to map customStatusId to status names. Never use dates.type for categorization. Triggers on "Get my Wrike tasks", "What tasks do I have in Wrike?", "Update Wrike section in briefing entry [id]". Called by briefing-generator after get-teams-action-items. Transitions Phase from 4-Wrike to 5-Summary.
Orchestrate the planning workflow (Idea → Plan → VD → WO → TASK/FIX) for SUM Platform releases and infrastructure initiatives. Use when starting a new version or initiative, creating planning artifacts, or generating GitHub issues from planning markdown. Follows PROJECT-PLANNING-GUIDELINES.md and creates deterministic, AI-executable TASK tickets.
Create structured sprint plans with automated Git workflow. Generates TOML sprints, creates feature branches, and enforces proper development workflow.
Display project workflow progress by reading handoff documents in .docs/ directory. This skill should be used when users want to check their workflow status, see what phase they're in, or when other workflow skills need to verify prerequisites. Provides reusable prerequisite-checking templates for integration with other workflow skills.
View and manage Google Calendar events. Check today's schedule, upcoming meetings, and calendar availability.
Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.
