software-factory-workflow
Complete 5-agent workflow for transforming ideas into validated software
Complete 5-agent workflow for transforming ideas into validated software
How to organize, structure, and keep a project plan up to date.
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.
인수 테스트를 기반으로 남은 작업을 분석하고 다음 작업을 계획합니다. "작업 계획", "다음 작업", "할 일 확인", "남은 작업" 등의 요청 시 활성화됩니다.
Issueの初期トリアージスキル。Issueを受け取り、標準化された分析結果(分類・深刻度・影響スコープ・不確実性・次アクション参照)を生成する。GitHub/Jira/Linear等のトラッカーからissue_payload形式で受け取る。 トリガー条件: - 「Issue #N を分析して」「このIssueの深刻度は?」「このバグはCritical?」 - 「Issue本文を初期トリアージして」「Issueを取り込んで」 - 新しいIssueを受け取り、最初の分類・判断が必要な時 注意: 根本原因の断定、修正案の確定、優先度の最終決定は行わない(材料提供まで)
Beads Viewer (BV) integration for visual task management and smart task selection. Use for Kanban views, dependency graphs, and the robot-plan API for auto-selecting next tasks. Keywords: beads, viewer, kanban, dependency graph, robot-plan, task selection, bottleneck
계획, 구현 계획, 플랜 작성, 작업 계획, 구현 플랜 - Use when you have a spec or requirements for a multi-step task, before touching code
Enterprise Skill for advanced development
Short summary of what this skill accomplishes.
Diagnose and fix convergent ideation. Use when brainstorming produces the same ideas every time, when all ideas cluster around one approach, or when you need to escape domain defaults.
Fix Linear issues tagged with "bug". Either produces a PR with the fix or explains why it won't be fixed. Triggers - fix bugs, linear bugs, bug triage, resolve bugs.
Transform raw brain dumps into structured implementation artifacts. Use when user has messy ideas, scattered thoughts, or dictated stream-of-consciousness about something they want to build. Produces contracts, phased PRDs, and implementation specs written to ./docs/ideation/{project-name}/.
JIRA 티켓 기반 CCU-2.0 구현 파이프라인. 요구사항 추출, 코드 구현, 빌드, 테스트를 자동화. "파이프라인", "워크플로우", "티켓 구현" 키워드시 활성화
Structured workflow for implementing new features with planning, clarification, and documentation. Use when implementing new features, making significant changes, or when the user requests a feature that requires planning and multiple implementation steps. Triggers on feature requests, multi-step implementations, or when explicit planning is beneficial.
A structured workflow for AI-assisted development using research, planning, and systematic implementation phases
项目完成导航。触发:用户通知"项目完成"或"可以提交了"时使用;执行归档、生成changelog、git commit+push。
Spec Kit を使って要件定義や仕様作成(仕様策定・仕様書作成・仕様設計を含む)を新規作成または既存仕様へ追記し、spec.md/plan.md/tasks.mdまで生成・更新する。要件定義、要件追加/変更、TDD前提の要件整理、仕様の明文化、Spec Kitのspecify/clarify/plan/tasksフロー実行が求められるときに使用。
Spec-driven development workflow. Use when implementing new features, skills, or game mechanics. Ensures specs exist before code.