context-management
Manage project context effectively. Use when onboarding, context switching, or maintaining project knowledge. Covers context capture and sharing.
Manage project context effectively. Use when onboarding, context switching, or maintaining project knowledge. Covers context capture and sharing.
Multi-perspective code analysis using three AI personas (RYAN methodical analyst, FLASH rapid innovator, SOCRATES questioning facilitator) to balance thoroughness with pragmatism. Use when complex code decisions need comprehensive analysis from multiple viewpoints, or when avoiding single-perspective blind spots is critical.
Apply agile development practices. Use when planning sprints, running ceremonies, or improving team processes. Covers Scrum, Kanban, and agile principles.
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
Guide for implementing DefectDojo - an open-source DevSecOps, ASPM, and vulnerability management platform. Use when querying vulnerabilities, managing findings, configuring CI/CD pipeline imports, or working with security scan data. Includes MCP tools for direct API interaction.
Update Linear issues with debugging findings. Add comments, change status, update labels, set priority. Use after completing investigations.
Complex GSAP timelines including labels, callbacks, nested timelines, and position parameters. Use when orchestrating multi-step animations, building animation sequences, or creating coordinated motion. Essential for cinematic animations and complex UI choreography.
承認済みの設計書(DESIGN.md)からTDD準拠のTODO.mdを作成します。analyzing-requirementsスキルで設計が完了・承認された後に使用します。developingスキルで実装できる形式のタスクリストを生成します。
Manage GitHub parent-child issue relationships using the gh-sub-issue extension. Link existing issues as sub-tasks, create new sub-issues, list relationships, and remove links. Use when working with GitHub issue hierarchies, Epic breakdowns, phased development, or when users mention sub-issues, sub-tasks, parent issues, or issue hierarchies.
Use when user says KISS, pragmatic, don't overengineer, ship it, keep it simple. Also for planning features, reviewing code, or architectural decisions.
Flutterプロジェクトの画面定義書(screen specification)を作成・管理するスキル。
Validates specification consistency, identifies implementation gaps, reviews roadmap coherence. Ensures documentation aligns, tasks are realistic, and dependencies are clear.
Use when planning software development tasks, before writing code or implementation plans - refines rough technical ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. For software architecture, components, data flow, and technical design decisions. Don't use during clear 'mechanical' coding processes
Show project detail. Requires authentication. Use for project management operations
Expert at detecting stories that are too big and applying splitting heuristics. Use when user describes work that seems large, mentions multiple features in one story, or needs help breaking down requirements. Detects linguistic red flags (and, or, manage, handle) and suggests concrete splitting strategies. Use when: - Story has obvious red flags: "and", "or", "manage", "handle", "including" - User describes multiple features bundled together - Story feels vague or too large - User asks "how to split this story" Do NOT use when: - Story is already small and focused (< 1 day work) - Feature needs layered analysis without obvious split points (use hamburger-method instead) - User asks HOW to implement (use micro-steps-coach instead)
Generates structured revise reports for Epics by aggregating task comments and learnings. Use when: (1) An Epic is completed or substantially progressed, (2) You want to consolidate "Revision Learning" comments from multiple tasks, (3) You need a traceability report linking tasks to commits.
Ensure regulatory compliance. Use when implementing GDPR, HIPAA, PCI-DSS, or SOC2 requirements. Covers compliance frameworks and controls.
Create pre-registration documents for research transparency. Use when: (1) Before data collection, (2) Grant submissions, (3) Ensuring reproducibility, (4) Meeting open science standards, (5) Preventing HARKing.
模拟真实 Design Review 会议,从多角色视角审查 HLD 技术方案,重点检测 PRD→HLD 漂移风险。适用于 HLD 完成后、进入实现阶段前的技术方案评审。
Verify feature requests align with project constitutional principles - applies decision framework systematically and provides clear align/reject/revise recommendation with detailed reasoning
Document architectural decisions. Use when making significant technical decisions that should be recorded. Covers ADR format and decision documentation.
Applies Disney's 12 animation principles to UI motion design. Use when improving animation quality, designing micro-interactions, creating easing curves, or making transitions feel natural and purposeful.
Transform data into compelling executive narratives using the What/Why/Next framework from Gartner research