exec-plan
Create or resume an execution plan - a design document that a coding agent can follow to deliver a working feature or system change
Discover devops project management skills, compare source repositories and read the instructions for each workflow.
Create or resume an execution plan - a design document that a coding agent can follow to deliver a working feature or system change
This skill should be used when the user asks about "Notion knowledge management", "SECI in Notion", "documenting in Notion", "organizing knowledge in Notion", "Notion database architecture", "PARA in Notion", "...
This skill provides guidance on designing effective evaluation rubrics. Use when: - Creating criteria for content or code quality assessment - Defining weights and thresholds for evaluation - Designing check ty...
This skill provides common evaluation patterns and integration guidance. Use when: - Integrating eval-framework with other plugins - Designing evaluation workflows - Choosing between content vs behavior evaluat...
Performs root cause analysis for Jenkins pipeline failures using MCP tools with evidence-backed citations, guided workflow, and concrete remediation steps.
Converts Jira issues and backlog data to structured Markdown format using Atlassian MCP. Use when working with Jira data visualization, documentation, or reporting.
JIRA 티켓 기반 전체 개발 파이프라인 자동화. 티켓 분석→구현→빌드→PR까지 semi-auto로 실행. "jira", "ticket", "workflow", "pipeline" 키워드 시 활성화
JIRA 티켓 기반 CCU-2.0 구현 파이프라인. 요구사항 추출, 코드 구현, 빌드, 테스트를 자동화. "파이프라인", "워크플로우", "티켓 구현" 키워드시 활성화
Find bugs, security vulnerabilities, and code quality issues in branch changes. Use when reviewing code for bugs, security issues, or quality problems. Thorough but concise reporting.
This skill should be used when the user asks about "code complexity", "cyclomatic complexity", "cognitive complexity", "code metrics", "maintainability index", "code coverage", or when measuring code quality qu...
Show project detail. Requires authentication. Use for project management operations
브레인스토밍, 아이디어, 기획, 구상, 아이디어회의 - You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, require...
코드 탐색, 코드 분석, 탐색, 코드 구조, 심볼 분석 - Use when exploring or analyzing code. Systematic code exploration workflow using Serena MCP tools for symbol navigation and reference tracking.
순차적 사고, 분석, 문제 해결, 복잡한 문제, 단계별 분석 - Use when solving complex problems. Systematic thinking workflow using Sequential Thinking MCP for multi-step analysis, trade-off evaluation, and architec...
디버깅, 디버그, 버그, 에러, 오류, 버그 수정 - Specialized in identifying root causes of bugs, analyzing error logs, and providing robust fixes. Use this when the user reports an error, unexpected behavior, or n...
계획, 구현 계획, 플랜 작성, 작업 계획, 구현 플랜 - Use when you have a spec or requirements for a multi-step task, before touching code
PRD, 기획서, 요구사항, 제품 기획, MVP, 제품 전략 - Use when brainstorming product ideas, creating PRD documents, defining MVP scope, or planning new features. MUST BE USED for any product strategy or requiremen...
Skill for selecting the next issue to work on based on priority, blocked status, and session context
Skill for creating well-formed issues from discoveries during implementation or validation
Skill for managing file-based issue tracking - housekeeping, moving, scanning
Use when the user has an idea to brainstorm, wants to design a feature, needs help refining a concept, says "let's ideate", or describes a vague project needing structure. Guides structured brainstorming to pro...
Evaluate a prompt or Agent Skill (SKILL.md) for clarity, constraints, robustness, and operational fit; output a numeric score.
Generate content strategy and component recommendations for landing pages. Analyzes implementations to create StoryBrand-structured pages with brand-aligned Shadcn component queries.
Master complex multi-step form workflows. Learn wizard forms, conditional logic, cross-step validation, progress tracking, and data persistence. Essential for building registration flows, checkout processes, an...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.