ใคใณใทใใณใ่ชฟๆปใงๆ นๆฌๅๅ ใ็นๅฎใใใใใฎใชใใชใๅๆใใกใทใชใใผใทใงใณใใผใซใงใใๆจๆธฌใ้ฟใใใฆใผใถใผใฎ็บ่จใ่จ้ฒใใใชใขใซใฟใคใ ใงใใคใณใใใชใผใไฝๆใใฆๅ จไฝใๅฏ่ฆๅใใพใใ่คๅ่ฆๅ ใๅๅฒใใๆไฝ1ใคใฎๆ นๆฌๅๅ ใ็นๅฎใใพใใ
Primary orchestration hub that FIRST enforces skill discipline (checking for applicable skills before any action), then manages deliverables, deadlines, team coordination, priority coaching, and work-life balance. Provides structured task management, daily standups, and orchestrates specialized skills when technical deep-dives are needed.
Event Storming ๅผๅฐๅฐๅฎถ๏ผ้้ Plan Mode ๅ็ญๅธถ้ ไฝฟ็จ่ ๅฎๆ Event Storming ๅทฅไฝๅ๏ผ่ญๅฅ Domain EventsใCommandsใActorsใPolicies ็ญๅ ็ด ๏ผๆ็ต็ๆ Markdown ๆไปถใ
Issue่งฃๆฑบใฎใใใฎ้ซๅบฆใชๆ่ใใญใปในใจๆ้ ใๅฎ็พฉใใในใญใซใๆ่ปใชๅคๆญใๆฑใใใใIssueๅฏพๅฟๅ จ่ฌใๆ ๅฝใใใ
Brutal, honest critique of strategies, plans, and analyses. Use when someone explicitly wants their thinking torn apart, stress-tested to destruction, or called out on weak logic. Triggers include requests like "tear this apart", "be brutal", "what's wrong with this", "play devil's advocate", "tell me why this won't work", or "poke holes in this". This is adversarial by design, not for collaborative exploration, but for ruthless pressure-testing.
่ค้ใชใฟในใฏ๏ผ3ในใใใไปฅไธใป่คๆฐใใกใคใซๅคๆด๏ผใฎๅฎ่ฃ ๅใซไฝฟ็จใ่จ็ปใใกใคใซใไฝๆใ้ฒๆใ่ฟฝ่ทกใ
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
Create or audit requirements-to-design-to-code-to-test traceability. Builds a traceability matrix (REQ โ design/ADR โ implementation files โ tests โ evidence) and flags gaps (unimplemented requirements, untested changes, undocumented decisions). Use when you need a requirements traceability check for a PR/release, regulated/compliance work, or when requirements are drifting from implementation.
๊ตฌํ ๊ณํ ์๋ฆฝ. Use when (1) "๊ณํ ์ธ์์ค", "์ค๊ณํด์ค", (2) ๋ณต์กํ ๊ธฐ๋ฅ ๊ตฌํ ์ , (3) ๋ฆฌํฉํ ๋ง ๊ณํ. โ ๏ธ ํนํ๋ ๊ณํ์ ๋ณ๋ ์คํฌ ์ฌ์ฉ: - ํ ์คํธ ๊ณํ โ write-test ์คํฌ
Ably real-time messaging patterns, WebSocket channel management, message validation and processing, staleness filtering, error recovery strategies, collaborative editing with drag-and-drop, optimistic updates for voting, real-time board collaboration, and Ably integration best practices for ree-board project
Open source community building and engagement. Welcoming contributors, managing discussions, writing release notes, and fostering a healthy project ecosystem.
FreightClub/ShipStation Shipping Data Analysis v3.0 - Enhanced with Revenue Architect rubrics. Triggers on: "freightclub analysis", "shipping data analysis", "PLD analysis", "shipstation export" Use when: Customer provides shipping data export for rate analysis or FirstMile opportunity assessment.
Create or refine VibeFlow issue files under issues/. Use when turning plan items into implementable tasks with clear acceptance criteria.
Comprehensive SessionStart hook showing PhD countdown, project status, uncommitted changes, and loaded todos.
Guide for executing engineering plans through coordinated subagent work. Use when executing existing plans from knowledge/plans/ directory.
Lightweight Linear skill for fetching issue details. Returns only essential data (title, description, state, assignee) to optimize context usage compared to full Linear MCP.
Personal research backlog. Quick-capture ideas for later exploration. Check when you have unstructured time.
Cost-effective task delegation strategy using Haiku model for straightforward work. Use when planning how to approach simple, pattern-following tasks to minimize costs.
์ฅ๋น ์ ์ฒด ๋ผ์ดํ์ฌ์ดํด ๊ด๋ฆฌ ์ํฌํ๋ก์ฐ
้็บไฝๆฅญใฎใฟในใฏใชในใ๏ผtasklist.md๏ผใ็ๆใใพใใใใฎในใญใซใฏๅ็ฌใงไฝฟ็จใใใใจใใgenerate-working-docsใใๅผใณๅบใใใใใจใใใใพใใ
Apply SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) for systematic development. Use for feature development, TDD workflows, and structured problem-solving.
Manages GitHub issue blocking/blocked-by relationships using the native dependencies feature via GraphQL API. Use when showing that one issue must complete before another can proceed, querying dependency relationships, or preventing circular dependencies.
