Initializes session with environment check and task status overview. Use when user mentions ใปใใทใงใณ้ๅง, ไฝๆฅญ้ๅง, ็ถๆณ็ขบ่ช, what should I work on, start session. Do NOT load for: ๅฎ่ฃ ไฝๆฅญ, ใฌใใฅใผ, ใปใใทใงใณ้ไธญใฎไฝๆฅญ.
Waypoint plans methodology and session survival patterns for Claude Code. Use when working on long-running features, need to resume after context reset, want to document task progress, or need to survive session interruptions. Covers three-file structure (plan/context/tasks), SESSION PROGRESS tracking, quick resume instructions, update frequency, and context handoff patterns.
Collaborative programming framework for production-ready development. Use when starting features, writing code, handling security/errors, adding comments, discussing requirements, or encountering knowledge gaps. Applies to all development tasks for clear, safe, maintainable code.
Use when starting, pausing, completing, or transitioning task status in the development workflow.
Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent for each task with code review between tasks.
Create and update Linear project milestones via CLI (write operations)
ๆขๅคไนๅไฟๅญ็ไผ่ฏไธไธๆใๅๅบๆๆๅพ ๅค็็ session๏ผ่ฏปๅ้ๅฎ session ็ไปปๅกไฟกๆฏ๏ผๆดๆฐ่ฟๅบฆ๏ผไปปๅกๅ จ้จๅฎๆๅๅ ้คๆไปถใ
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
Jeffrey Emanuel's comprehensive markdown planning methodology for software projects. The 85%+ time-on-planning approach that makes agentic coding work at scale. Includes exact prompts used.
Create or update numbered task docs using repo context, DOC_TEMPLATE.md, and naming conventions.
Manage features.yml for tracking requirements and progress; use proactively ONLY when features.yml already exists, or invoke manually to create one; complements TodoWrite for persistent project state.
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
Changes phases in the GitHub Elements workflow by closing the current thread and opening the next phase thread. Use when user wants to END current phase and BEGIN next (e.g., "transition to TEST", "move to REVIEW", "demote to DEV", "merge this"). Do NOT use for status checks, claiming issues, saving progress, or generating reports.
This skill should be used when creating or working with modular project plans stored as Obsidian-compatible markdown wikis. Use when the user asks to create a plan, roadmap, or documentation system that needs to be navigable in Obsidian, or when working with existing plan wikis that use the %% [ ] %% task tracking format.
Battle-tested code review practices optimizing for codebase health and team velocity
Overview of the project's tech stack, directory structure, and architectural patterns.
็ณป็ตฑๅ็ๅ้กๅๆๅฐๅฎถๆ่ฝ๏ผ่ชๅๅ่ชฟไบๅๅฐ้ไปฃ็้ฒ่กๆทฑๅบฆๅ้กๅๆใ ้ฉ็จๆผ๏ผ - ไฝฟ็จ่ ๆ PM ๅ ฑๅ็็ทไธๅ้ก - ้็ผๅ้ๅๆ ็ๆ่กๅ้ก - ๆธฌ่ฉฆ็ผ็พ็ bug - ็็ข็ฐๅขๅ่ญฆๅ็ฐๅธธ
Scan conductor/ directory for project direction, workflows, and task planning when present
ไปๆง้งๅ้็บ๏ผSDD๏ผใฏใผใฏใใญใผใ่ชๅ็บๅใงๅผทๅถใSubtask้ๅงๆใซAC็ขบ่ชใTDDๅฎ่กใๅฎไบๆใซACใใงใใฏใๅฎๆฝใในใณใผใๅคๅฎ่ฃ ใ็ฆๆญขใUse when implementing features, creating new functionality, or when "ๅฎ่ฃ ใใฆ", "ไฝๆใใฆ", "้็บใใฆ" keywords appear.
Use when coordinating dependency-aware task planning with beads (bd) CLI and bv graph sidecar - covers ready work selection, priority management, and robot flags for deterministic outputs
Create or update comprehensive GitHub issues that capture ALL context, requirements, and implementation details. Use when creating or updating tickets, issues, feature requests, or bug reports. Ensures no context is lost between ticket creation and implementation - the moment you ask for a ticket, there's maximum context available that will be lost if not captured now.
Complete product launch workflow coordinating 15+ specialist agents across research, development, marketing, sales, and operations. Uses sequential and parallel orchestration for 10-week launch timeline.
