atlas-full
Full 9-phase workflow for complex features, epics, and security-critical changes (2-4 hours)
Full 9-phase workflow for complex features, epics, and security-critical changes (2-4 hours)
풀스택 워크플로우를 시작합니다. 계획 수립(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.
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", "업무 내역 정리" 등의 요청 시 자동 적용.
Enterprise Skill for advanced development
複雑なプロジェクトタスクを小さな実行可能なステップに分解します。1コミット粒度の細粒度タスクへの分割、依存関係の特定、実行優先度の決定をサポートします。大規模プロジェクトの計画化、段階的な実装ロードマップの作成が必要な場合に使用してください。
親IssueからSubtaskを検出し、依存関係を考慮した実行順序(トポロジカルソート)を決定するロジック
다단계 분석, 수정 능력 및 가설 검증이 필요한 복잡한 작업을 위해 구조화되고 성찰적인 문제 해결 방식을 적용합니다. 복잡한 문제 분해, 적응형 계획 수립, 경로 수정이 필요한 분석, 범위가 불분명한 문제, 다단계 해결책 및 가설 기반 작업 시 사용합니다.
Convert a plan into ordered, self-contained feature documents for cross-session development. Use when user says "plan to features", "split plan into features", "create feature docs", or after completing a large plan that should be broken into separate development tasks. Creates numbered feature files in /.agent-features/ folder.
인수 테스트를 기반으로 남은 작업을 분석하고 다음 작업을 계획합니다. "작업 계획", "다음 작업", "할 일 확인", "남은 작업" 등의 요청 시 활성화됩니다.