culture-engagement
Master team culture, psychological safety, engagement, communication, and inclusion for engineering teams
tasklist-generator
Generate high-level tasks and gated sub-tasks from a PRD, with relevant files and testing guidance.
sla-tracking
Generic SLA (Service Level Agreement) tracking for lead response times. Use when monitoring response performance, ensuring timely follow-ups, or building accountability systems. Framework for project-specific implementations.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
requirements-gathering
(opencode-project - Skill) Template and guidelines for creating comprehensive requirements specifications
plan-mode-aegis-v25-development
AEGIS v2.5開発の包括的Planモード。数学データ収集、形式証明環境構築、GRPO訓練パイプライン、MCP/A2Aエージェント開発、進捗監視を実装。SO(8)四重推論再現のための完全開発ワークフロー。
meeting-facilitator
Plan and structure effective meetings with agendas and follow-ups
probe-estimation
Use to apply PROBE (PROxy-Based Estimation) method for story sizing. Uses historical data for accurate effort estimation.
adaptive-ux-scheduling
Adapt UI scheduling behavior dynamically based on runtime conditions and user context.
vrau-reviewer
Use when spawned to review vrau brainstorm or plan documents with fresh eyes
using-skills
Check for relevant skills before starting any task
verification-sweep
This skill should be used when checking plan status, running verification commands, updating task statuses, or determining what work remains. Provides the verification sweep algorithm and status update procedures.
verification-checklist
Use before marking any task complete to ensure all requirements are met
software-engineering-lead
Expert software engineering lead who translates product requirements into comprehensive engineering plans using GitHub Projects. Reviews PRDs and user stories, identifies gaps and conflicts, pushes back constructively on poor requirements, applies software engineering best practices, creates detailed technical plans with tasks and milestones, and ensures production-ready architecture. Use when translating product specs into actionable development plans, validating requirements, or designing system architecture.
create-epic
Create Epic issue in docs repository. Use when (1) ideate 스킬에서 자동 호출, (2) epic-master needs to create new Epic, (3) 요구사항 → Epic 변환.
sprint-planning
Agile sprint planning toolkit. Create user stories following INVEST criteria, plan sprints with capacity management, define acceptance criteria, and track dependencies across sprints for incremental software delivery.
seasonal-planning
Use in rapidly evolving industries like AI where 6-month plans become obsolete, when needing to balance direction with agility, or when traditional annual roadmaps fail
