Loading...
Loading...
Found 9 Skills
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
[user/auto] 검증된 현재 브랜치 `commit`으로 하나의 GitHub `pull request`를 열거나 업데이트하며, 원격 발행 전 정확한 현재 턴 승인을 요구합니다.
The sole global workflow control plane for the Phaser 4 game repository. Handles low-risk local work based on task authorization and deterministic risk classification, distinguishes user clarification decisions, and retains precise explicit approvals only for specific A4-A6 operations and their impacts.
Only for Calendar, Tasks, Approvals, Attendance, and OKR; it is not a universal entry for all Feishu office requests. This Skill must be used when users request freebusy, finding common free time, booking meeting rooms, accepting/rejecting invitations, creating or replying to schedules, managing tasks/checklists, initiating, withdrawing, approving, rejecting, transferring, or cc'ing approvals, checking clock-in/lateness/leave statistics, querying OKR cycles, or updating progress. It is explicitly prohibited for use in user/department address books, emails, historical meeting retrieval, meeting recording, or Minutes; these use feishu-cli-platform, feishu-cli-mail, and feishu-cli-meetings respectively. Meeting notification messages use feishu-cli-messaging.
Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.
Korean business culture for foreign professionals — 품의 decision process, nunchi reading, KakaoTalk business etiquette, hierarchy navigation, and relationship-first deal mechanics
A hybrid pattern where the system pauses execution to request human approval, input, or disambiguation before proceeding with critical actions. Use when user asks to "add human approval", "require human review", "human-in-the-loop", or mentions approval workflows, human oversight, or escalation.
Plan and generate UiGraph artifacts after explicit user approval.
Implements an approved spec. Validates that the state means "Approved" (in any language), creates a git branch named after the spec, switches to it, and starts the implementation step by step with pauses to review diffs.