Stop optimizing for positive ROI and start focusing on minimizing opportunity cost—choosing the BEST possible use of time, not just a good one. Use during quarterly planning and roadmap prioritization.
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
Self-evaluation and quality validation for specifications and documents. Identifies gaps, contradictions, and missing details using structured checklists. Use after drafting specs, PRDs, or feature documents.
計画から GitHub Issue を作成する。「Issue 作成」「Issue を作って」「Issue 作成して」「計画から Issue」「Issue 追加」「Issue を追加したい」「Issue 作りたい」などで起動。1つの計画を1つの Issue にまとめて作成。
Work with ArcGIS Utility Networks for modeling and analyzing connected infrastructure. Use for network tracing, associations, and utility asset management.
Nate B. Jones's Practice Gym for knowledge workers. Evaluate decision docs, specs, and exec updates against rubrics with quoted evidence. Build team-calibrated rubrics. Convert messy situations into 15-30 min practice drills. See stronger versions with explicit gap analysis. Find systematic weakness patterns. Create artifact-based interview exercises. Triggers on "evaluate my doc", "score this", "build a rubric", "practice drill", "what did I miss", "weakness pattern", "interview exercise", "calibrate rubric".
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Memory visualization and diagramming for World Weaver systems
Init Agent의 세부 프로세스. 프로젝트 컨텍스트 설정, PRD 생성, 코드베이스 분석의 단계를 정의합니다.
排查问题、修复 BUG、定位代码、查找模块、功能开发前，必须先读取此 SKILL 并使用模块索引定位目标，不可跳过
Search GitHub Issues and PRs with 30+ qualifiers including labels, dates, users, state, milestones, and content. Use when searching for issues by keywords, metadata, or complex filters.
Use when developing rough ideas into designs, before writing code or implementation plans - refines concepts through collaborative questioning and incremental validation
Provide the task granularity for cutting subissues.
의사결정 로그 Supabase discussions 테이블에 생성. 회의/Slack/PR 등에서 결정된 사항을 기록. Use when (1) 의사결정 기록 요청, (2) 회의 결정사항 문서화, (3) summarize-meeting 스킬에서 호출.
Defines the layered output format for development plans (TL;DR, Approach, Tasks with dependencies). Ensures plans are readable at multiple levels - from executive summary to detailed implementation steps.
Use for SDLC phase transitions. Ensures proper handoff between development phases with documentation.
Use when executing implementation plans with independent tasks in the current session
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
Use when specs/product/ is empty or incomplete to create mission.md, roadmap.md and tech-stack.md through incremental brainstorming and validation.
자율 판단 + 자율 발견 워크플로우 (v2.0 - Ralph Wiggum 철학 통합). "할 일 없음 → 종료"가 아닌 "할 일 없음 → 스스로 발견". 5계층 우선순위, 9개 커맨드 자동 트리거, Context 예측 기반 관리.
