eros-schedule-validator
Validate schedules against hard gates and score quality. Phase 3 of EROS pipeline. Invoked automatically after schedule generation completes.
Validate schedules against hard gates and score quality. Phase 3 of EROS pipeline. Invoked automatically after schedule generation completes.
Copilot agent that assists with systematic requirements review using Fagan Inspection and Perspective-Based Reading (PBR) techniques Trigger terms: requirements review, specification review, SRS review, Fagan inspection, perspective-based review, requirements validation, requirements verification, quality gate review, formal inspection, requirements checklist Use when: User requests involve requirements review, validation, or inspection tasks.
Полная реализация проекта по готовым спецификациям м первого раза(requirements.md, tasks.md, design.md). Использовать когда: нужно реализовать проект с нуля по спецификациям, выполнить все таски идеально. Скилл обеспечивает: идеальное выполнение с первого раза, работу по таскам, верификацию через субагентов, практическое тестирование на серверах, коммиты в git.
JIRA 티켓 기반 전체 개발 파이프라인 자동화. 티켓 분석→구현→빌드→PR까지 semi-auto로 실행. "jira", "ticket", "workflow", "pipeline" 키워드 시 활성화
避免常见错误和遵循项目规范 - 记录项目中反复出现的错误和正确的解决方案
ガイドライン自動読み込み - プロジェクトの技術スタックを検出し、必要なガイドラインのみをセッションに適用。トークン節約。
Send lightweight status updates to a human during long-running agent work
Creates a WorkPlan (Schedule of Intent) and logs U.Work.
Apply project planning conventions when creating or organizing plans. Use when user asks to create a plan, add a feature plan, document a bug, or work with the plans/ directory.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
순차적 사고, 분석, 문제 해결, 복잡한 문제, 단계별 분석 - Use when solving complex problems. Systematic thinking workflow using Sequential Thinking MCP for multi-step analysis, trade-off evaluation, and architectural decisions.
See the main On-Call Playbooks skill for comprehensive runbook templates and examples.
生成GOAL/SubPlan依赖DAG和关键路径分析,并执行SubPlan划分。当需要分析技术依赖、业务依赖、识别关键路径、发现并行执行机会、执行SubPlan分配时使用。基于GOAL的dependencies字段和业务逻辑分析生成Mermaid依赖图和SubPlan划分方案。
Use when working through any task checklist (not just OpenSpec). Complete one task, verify, mark done, then next. No skipping, no adding, no reordering.
Use for ANY bug, test failure, or unexpected behavior. Use BEFORE proposing fixes. Four phases: investigate, analyze, hypothesize, implement. Ensures understanding before attempting solutions.
This skill MUST be used when the user asks to "search issues", "find issues", "JQL search", "query Jira", "list issues matching", "find tickets where", "search for bugs", "find my issues", or otherwise requests searching for Jira issues using criteria or JQL.
Do planreview step of the PLANNING phase of star-team workflow.