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
BMAD ์คํ์ผ ์์ด์ ํธ ๋ฉ๋ชจ๋ฆฌ ๊ด๋ฆฌ ํฌํผ ํจ์๋ค
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 ์์ธก ๊ธฐ๋ฐ ๊ด๋ฆฌ.
