phase-semantic
Phase 2 of assist workflow - Determine appropriate component type (Skill, Agent, Command, Hook, MCP)
Phase 2 of assist workflow - Determine appropriate component type (Skill, Agent, Command, Hook, MCP)
Record task metrics after completing work. Use after /verify or any completed task to build measurement data.
่ชๅ็ใซGitHub Issueใๅๆใใๆง้ ๅใใใๅ ๅฎนใซๆนๅใใในใญใซใ ้ใชIssueใๆ ๅ ฑไธ่ถณใฎIssueใAIใไฝๆฅญใใใใๅฝขๅผใซ่ชๅ่ฃๅฎใปๅ ็ญ่จๆญฃใใใ ใฟใคใใซใฎๆจๆบๅใๆฌๆใฎๆง้ ๅใ้ฉๅใชใฉใใซไปไธใไธ่ถณๆ ๅ ฑใฎๆๆใ่กใใ ใใใฎIssueใๆนๅใใฆใใIssueๅ ๅฎนใๆดใใฆใใจใใฃใไพ้ ผใงไฝฟ็จใ
Ability to design, implement, test, deploy, and maintain software systems that meet defined requirements. Includes translating specifications into executable code, applying appropriate programming and design practices, managing changes over time, and operating software in production environments. Applies across application, platform, and infrastructure-adjacent contexts and is independent of specific languages, frameworks, or tools. Work may be performed individually or collaboratively and may be supported by automation or artificial intelligence, with human accountability retained for correctness, security, and outcomes.
ไฝๆฅญ้ๅงๅใซใๅฎ่กๅฏ่ฝใชPlanใๅฟ ใไฝใ๏ผ้่ชๆใชไฝๆฅญใงไฝฟ็จใใ้ธๆ่ขๆฏ่ผใปๆค่จผใปใชในใฏใปใญใผใซใใใฏใปใใงใใฏใใคใณใใปๅฎไบๆกไปถใปcleanupใๅซใใ๏ผใ
Methods for validating root cause analyses. Provides checklists for 5 Whys depth, execution path accuracy, and fix strategy soundness. Use when reviewing RCA reports.
Cloudflare ้็บใป้็จใฎใในใใใฉใฏใใฃใน้ใใใญใธใงใฏใๆงๆใCI/CDใใปใญใฅใชใใฃใใใใฉใผใใณในๆ้ฉๅใใณในใ็ฎก็ใใใฉใใซใทใฅใผใใฃใณใฐใๆไพใUse when user asks about project structure, CI/CD, GitHub Actions, performance optimization, cost management, troubleshooting, or debugging. Also use when user says ใในใใใฉใฏใใฃใน, ๆ้ฉๅ, ใใฉใใซใทใฅใผใใฃใณใฐ, CI/CD, ใใใใฐ.
fetches the information about the work that should be done on the current branch. Use when the user tells you to "get the ticket info"
This skill provides patterns for identifying, categorizing, and tracking technical debt. It includes scoring methodologies, YAML schemas for tracking files, and strategies for systematic debt resolution.
Write effective progress files that enable continuity across sessions and agent handoffs in spec-driven development. Use when starting work sessions, resuming after breaks, completing tasks or milestones, encountering blockers, handing off work, recording test results, or documenting issues and resolutions. Triggers include "progress log", "session log", "write progress", "handoff notes", "work log", or when capturing session-by-session work history for continuity.
Summarize feature or product requirements into clear scope, constraints, and risks. Use when the user asks for requirement summary/้ๆฑๆป็ป/้ๆฑ่ฆ็น or wants a concise spec snapshot.
Formulates a comprehensive strategy for TDD-based implementation. Analyzes specifications (Specs) and handover items, defines shared implementation policies, and drafts specific TDD tasks (Issues).
Convert BPMN 2.0 XML files into Draw.io native format (.drawio) using the bpmn2drawio Python tool. Renders properly in Draw.io Desktop or web applications. Use this skill when a user wants to visualize a BPMN process in Draw.io, convert BPMN to editable diagrams, or create Draw.io files from process definitions. Triggers on: "convert BPMN to Draw.io", "create drawio from BPMN", "visualize BPMN in Draw.io".
์ด ์คํฌ์ ์ฌ์ฉ์๊ฐ "์์ ์๊ฐ ๊ธฐ๋ก", "์๊ฐ ๋ฑ๋ก", "ํ์ ๋ก๊ทธ", "์์ ์๊ฐ ์กฐํ", "๋ช ์๊ฐ ์ผํ์ด", "time entry", "log hours", "time tracking", "work hours" ๋ฑ์ ์ธ๊ธํ ๋ ์ฌ์ฉ๋ฉ๋๋ค. Redmine ์์ ์๊ฐ ๊ด๋ฆฌ ๊ธฐ๋ฅ์ ์ ๊ณตํฉ๋๋ค.
Decompose a phase plan into atomic beads and sub-beads. Use when breaking down a phase into tasks, when the user mentions "decompose" or "break down", when creating beads from a plan, or when structuring work for parallel execution.
Use when executing implementation plans with independent tasks in the current session
Analyze coverage of business requirements across feature plans, wave plans, and implementations to ensure completeness. Creates traceability matrices mapping requirements to features/waves/user stories, identifies uncovered or partially covered requirements, detects orphaned features, and validates acceptance criteria. Use after feature planning, before wave design, during epic reviews, for stakeholder reporting, or when validating requirement coverage.
Design comprehensive technical specifications and strategic plans for data architecture and analytics projects. This skill should be used when planning major features, creating SPEC documents, assessing product requirements, breaking down complex projects into phases, or documenting architectural strategies like SPEC-1. Guides through requirements gathering, MoSCoW prioritization, phase planning, and open items tracking.
Plan and document coding tasks with PLAN.md and ADRs in docs/ADR. Use when a task can be decomposed, when asked to create or update PLAN.md, or when capturing technical decisions.
Estimate issue complexity before implementation to prevent timeouts. Uses cheap estimation to save expensive implementation tokens.