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
List and get Linear projects via CLI (read-only operations)
ๅญใจใผใธใงใณใใฎ่ตทๅใปๆ็คบใปๅ ฑๅใปๅฎๅ จ้็จใๆจๆบๅใใในใญใซใcodex ใงใฎใฟในใฏๅ่งฃใ็ขบ่ชๅคๆญใใใงใใฏใชในใใใใณใใฌใผใใๆไพใใใชใผใใผ/ๅฎ่ฃ /ใฌใใฅใผๅใจใผใธใงใณใใ่ฟทใใๅใใใใใซใใใ
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
ๆฟ่ชๆธใฟใฎ่จญ่จๆธ๏ผDESIGN.md๏ผใใTDDๆบๆ ใฎTODO.mdใไฝๆใใพใใanalyzing-requirementsในใญใซใง่จญ่จใๅฎไบใปๆฟ่ชใใใๅพใซไฝฟ็จใใพใใdevelopingในใญใซใงๅฎ่ฃ ใงใใๅฝขๅผใฎใฟในใฏใชในใใ็ๆใใพใใ
Create a task plan with dual design. Use when starting a new task or running /tp.
Parallel design by Claude and Codex with merge discussion. Use for step or task design.
Use this skill when you need to review and refactor code to make it simpler, more maintainable, and easier to understand. Helps with identifying overly complex solutions, unnecessary abstractions.
Use when a team sees repeated @codex review cycles or Codex Cloud feedback churn and needs root-cause attribution by development stage.
Workflow d'Analyse Obligatoire. Use when working with workflow analysis.
Rapid incident classification, severity assessment, and response coordination. Use when relevant to the task.
Continuous risk identification, assessment, tracking, and retirement throughout SDLC. Use when relevant to the task.
This skill should be used when planning and tracking complex feature implementations that require systematic task decomposition. Use this skill to break down large features into manageable, well-documented tasks with clear dependencies, action items, and success criteria. The skill provides a structured template and methodology for iterative planning and tracking throughout implementation.
Specification-Driven Development (SDD) methodology for building software where specifications are executable and drive code generation. Use when users want to: (1) Create feature specifications with /speckit.specify, (2) Generate implementation plans with /speckit.plan, (3) Create executable tasks with /speckit.tasks, (4) Follow test-first, library-first development, or (5) Implement constitutional architecture principles. Essential for structured AI-assisted development workflows.
่ชๅจๅๅ่ฐไธๅฎถ๏ผ็ฎก็ๅฎๆไปปๅกใๅทฅไฝๆต็ผๆใๆบ่ฝๅ่ญฆๅ็ๆง็ณป็ปใ
ๆบ่ฝๆฐๆฎไผๅๅทฅๅ ท๏ผ่ชๅจๆธ ็ๅไผๅ้กน็ฎๆไปถ
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Use when working on a Knowns task - take ownership, research, plan, implement, complete with proper tracking
Use when requirements are unclear, multiple approaches exist, or you need to explore solutions before planning
