packages-graph
Your approach to handling packages graph. Use this skill when working on files where packages graph comes into play.
codex-plan-review
[TMUX MODE] Send plan to Codex via tmux file-based IPC. Only use when user explicitly runs /codex-plan-review command. For natural language requests, use the delegate_codex_plan_review MCP tool instead.
update-leads
Updates the list of job leads and prioritizes actions. Use for weekly lead review.
comprehensive-issue-analyzer
Fetches ALL open issues from any GitHub repository using pagination and generates a comprehensive analysis including category breakdown, age distribution, stale issues (30+ days), top discussed issues, prioritization, and detailed recommendations for triage. Handles large repositories (5000+ issues) efficiently.
epic-template
Epic and task structure patterns for SpecFlux. Use when breaking PRDs into epics and tasks. Epics should be self-contained with clear acceptance criteria.
executing-plans
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
project-board-enforcement
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
sdd-plan
Plan-first development methodology that creates detailed specifications before coding. Use when building features, refactoring code, or implementing complex changes. Creates structured plans with phases, file-level details, and verification steps to prevent drift and ensure production-ready code.
expropriation-timeline-expert
Expert in calculating critical path project timelines using PERT/CPM methodology with statutory deadline integration for expropriation projects. Use when managing complex project schedules, tracking OEA statutory deadlines (3-month registration, Form 2/7 service), identifying timeline risks, or optimizing resource allocation. Key terms include critical path, PERT analysis, CPM scheduling, statutory deadlines, float analysis, resource leveling
codebase-reading
Systematic methodology for reading and understanding large codebases efficiently. Use when (1) Understanding a new or unfamiliar codebase quickly, (2) Preparing to modify or extend existing code safely, (3) Debugging complex issues requiring deep code understanding, (4) Onboarding new team members to a codebase, (5) Performing code audits or security reviews, (6) Refactoring legacy code with confidence, (7) Creating documentation for existing systems, (8) Tracing execution flows and data transformations
packages-ports
Your approach to handling packages ports. Use this skill when working on files where packages ports comes into play.
sentry-code-review
Analyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.
extreme-programming
Use when pair programming with humans - enforces XP values (communication, simplicity, feedback, courage, respect) to deliver high-quality software; push back on YAGNI violations regardless of seniority or sunk cost
pdca-methodology
PDCA (Plan-Do-Check-Act) methodology knowledge. Covers documentation-first development, design-implementation sync, continuous improvement. Triggers: PDCA, plan, design, check, act, 계획, 설계, 検証, 改善
planning-workflow
规划工作流 - 从想法到实现计划的结构化流程。通过迭代细化单个 Markdown 文档将模糊想法转化为清晰实现计划。
packages-react
Your approach to handling packages react. Use this skill when working on files where packages react comes into play.
bkit-templates
PDCA document templates for consistent documentation. Plan, Design, Analysis, and Report templates with proper structure. Triggers: template, plan document, design document, analysis document, report, 템플릿, 계획서, 설계서, 분석서, 보고서, テンプレート, 計画書, 設計書
expectations
Working expectations and documentation practices. Use when capturing learnings or understanding how to work with this codebase.
plot-workflow
编排和协调大情节点与详细情节点的一键生成工作流。适用于长篇故事的结构化分析、需要模块化智能体协作的复杂任务
chaos-experiment
Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use for resilience testing, game days, failure injection experiments, and building confidence in system stability.
research
Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.
system-engineer
Expert MBSE engineer for system models, specifications and architectures. Use when exploring, updating and refactoring requirements, specifications and system model, adding features, managing verifications and creating tasks from introduced changes in requirements and system model.
sequential-thinking
顺序思维 - 使用 sequentialthinking MCP 工具进行动态反思性问题求解的指南。