expectations
Working expectations and documentation practices. Use when capturing learnings or understanding how to work with this codebase.
Working expectations and documentation practices. Use when capturing learnings or understanding how to work with this codebase.
็ผๆๅๅ่ฐๅคงๆ ่็นไธ่ฏฆ็ปๆ ่็น็ไธ้ฎ็ๆๅทฅไฝๆตใ้็จไบ้ฟ็ฏๆ ไบ็็ปๆๅๅๆใ้่ฆๆจกๅๅๆบ่ฝไฝๅไฝ็ๅคๆไปปๅก
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.
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.
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.
้กบๅบๆ็ปด - ไฝฟ็จ sequentialthinking MCP ๅทฅๅ ท่ฟ่กๅจๆๅๆๆง้ฎ้ขๆฑ่งฃ็ๆๅใ
This skill should be used when the user asks to "create epics", "create an epic", "new epic", "break down project into epics", "decompose project", or mentions creating epics. Supports both standalone epic creation and breaking down a project into major epics by analyzing specifications and gathering requirements.
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
Design-implementation gap analysis, code quality analysis, and report writing patterns. Used in PDCA Check phase for verification and quality assurance. Triggers: gap analysis, code review, quality check, ์ค๊ณ-๊ตฌํ ๋ถ์, ใฎใฃใใๅๆ, ๅทฎ่ทๅๆ
็ปไธไปปๅก็ฎก็ๆ่ฝ๏ผไฝฟ็จ GitHub Issues ็ฎก็ๆๆ Agent ไปปๅก๏ผๆฏๆไปปๅกๅๅปบใๆดๆฐใ่ฟฝ่ธชๅๅฎๆ
Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems.
ใใใฑใผใธ/ใขใธใฅใผใซๆง้ ใฎๅๆใจใชใใกใฏใฟใชใณใฐๆฏๆดใๅพช็ฐไพๅญใฎๆคๅบใ่ฒฌๅๅ้ขใฎๆๆกใ็งป่ก่จ็ปใฎไฝๆใ่กใใใใใใฑใผใธๆง้ ใ่ฆ็ดใใใใใใขใธใฅใผใซใฎไพๅญ้ขไฟใ่ค้ใใใใกใคใซ้ ็ฝฎใๆด็ใใใใใๅพช็ฐไพๅญใ่งฃๆถใใใใใจใใฃใๆง้ ๆนๅใชใฏใจในใใง่ตทๅใ
Project planning methodologies including work breakdown structure, task estimation, dependency management, risk assessment, sprint planning, and stakeholder communication. Use when breaking down projects, estimating work, planning sprints, or managing dependencies.
ๆบ่ฝๅ่ฐๅจ๏ผ็ผๆๅคไธชๆ่ฝๅๅฝไปคๅฎๆ็ซฏๅฐ็ซฏ็ๅทฅไฝๆตใ่ชๅจ่งๅๅๆง่กๅคๆ็ๅคๆญฅ้ชคไปปๅกใ
Execute the implementation planning workflow using the plan template to generate design artifacts.
Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.
Guide prospective hindsight analysis to identify project risks before failure occurs. Teams imagine the project has failed spectacularly, then work backward to identify causes. Increases risk identification by 30% compared to traditional planning.
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.
Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Track TODOs in project-specific markdown files in ~/Desktop/TODO/.
Enforces a structural planning phase before execution. Generates and validates PLAN.json to ensure every task has a clear objective, steps, verification method, and rollback strategy.