Find and safely claim the next Beads task with conflict checking. Use when looking for work, when finishing a task and need the next one, when the user mentions "next task" or "what should I work on", or when coordinating with other agents on task ownership.
Use when given 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
Full 9-phase workflow for complex features, epics, and security-critical changes (2-4 hours)
Create comprehensive Product Requirements Documents (PRD) that define what to build and why, focusing on goals, scope, user stories, and success criteria without implementation details. Use this skill when: - User asks to "write a PRD", "create PRD", "write requirements document" - User mentions "requirements document", "product requirements", "product spec" - Running /pm.plan command to create version planning document - Starting a new product, major feature, or initiative that needs formal requirements - Need to document goals, scope, user stories, functional requirements, and success criteria Output: ALWAYS write PRD files to docs/reference/pm/versions/{version-name}.md
풀스택 워크플로우를 시작합니다. 계획 수립(prd.md + task.md) -> Agent 분담 실행 -> 코드 리뷰 -> 완료 순서로 체계적인 개발을 진행합니다. "풀스택 워크플로우", "/fullstack-workflow", "풀스택으로" 등의 명령으로 활성화됩니다.
Maintain development momentum and prevent project stalls through progress tracking, blocker resolution, quick wins identification, energy management, and continuation strategies. Task-based operations for detecting stalls, breaking through obstacles, maintaining forward progress, and ensuring completion. Use when progress stalling, facing blockers, losing energy, needing motivation, or ensuring project continuation to completion.
PRODUCTION SCALE LAUNCHER v1.0 - 4 Level Maturity Model
This skill should be used when the user asks to "add a component", "change architecture", "refactor X", "implement feature", "fix bug", "create new service", "update diagram", or "remove component". Requires .c3/ to exist. All changes flow through ADR process. For questions, route to c3-query instead.
Use after completing a refactor, implementing a major feature, or when skills may be outdated. Analyzes code changes, identifies affected skills, and proposes updates to keep team knowledge current. Also use when you notice a skill contains outdated patterns. Ask clarifying questions if changes are confusing.
Conduct in-depth feature interviews to gather requirements. Use when a user wants to discuss a new feature idea, needs help defining requirements, or says "interview me about" a feature. Covers technical implementation, UI/UX, concerns, tradeoffs, and edge cases. Supports full-stack, web/UI, and infrastructure/DevOps features.
Create technical architecture specification with data models, component hierarchy, and risk analysis. Use after PRD approval for large features.
Structured planning and review sessions for project rhythm. Use when: "planning session", "review session", "project kickoff", "schedule planning".
Use when planning and tracking work - creates visible, emergent work breakdown using TypeScript API with just-in-time planning and hierarchical task trees
Build optimized weekly schedule items from CreatorContext. Phase 2 of EROS pipeline. Invoked automatically after preflight completes.
Fast decision-making methodology for time-critical situations. Use when you have minutes (not hours) to decide, during incidents, emergencies, or hard deadlines. Optimizes for "good enough now" over "perfect later". Unlike other patterns that maximize quality, RTR maximizes decision speed while maintaining acceptable quality floors.
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
매일 아침 업무 시작 전 어제 작업 내역을 정리하여 Daily Note에 반영. 서브 에이전트 기반 병렬 처리로 메인 컨텍스트 절약. "어제 작업 정리해줘", "daily log", "업무 내역 정리" 등의 요청 시 자동 적용.
