runbooks-ops
Comprehensive guide to creating operational runbooks including incident response, deployment procedures, troubleshooting guides, and on-call playbooks
Comprehensive guide to creating operational runbooks including incident response, deployment procedures, troubleshooting guides, and on-call playbooks
Coordinates repo snapshot, gate runs, and optional WF cycle operations for a single station execution.
Use this when working on tasks in this repo that require bd (beads) issue tracking, status updates, and the mandatory end-of-session push workflow.
Compiles production-ready EU grant proposals from EU Grant Hunter briefs, UBOS narrative banks, partner commitments, and budget templates. Reuses the proven 1,850:1 ROI methodology that secured €6M Xylella funding. Coordinates the full assembly workflow: intelligence gathering, narrative compilation, budget construction, partner onboarding, compliance checks, quality scoring, and final packaging (PDF/LaTeX). Target score: ≥4.6/5 (Horizon 13.8/15). Use when preparing submissions, tracking proposal status, or managing consortium deliverables.
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
Start a new work session for a feature, bug, or chore. Gathers requirements, creates an optimized session plan broken into context-efficient phases, and guides implementation.
Log the current coding session to project memory. Use at the end of a session to record accomplishments, decisions, and follow-ups. Triggers on: log this session, save session, end session, record what we did.
Use the /phase-report slash command to generate progress updates and log them. Use when: reporting status or phase completion.
Create traceability matrix mapping intents (INT-*) to requirements (REQ-*) and requirements to all downstream artifacts (design, code, tests, commits, runtime). Use to visualize and verify complete traceability.
监控执行计划的进度和健康状态,跟踪 SubPlan 完成度和 Round 执行状态,识别阻塞点并同步 Dashboard。当需要检查执行进度、更新 Round 状态、记录阻塞项、生成进度报告、计算进度偏差、分析趋势、预测完成日期时使用。支持资源消耗跟踪、风险状态更新、燃尽图分析和利益相关者报告生成。
Execute the implementation planning workflow using the plan template to generate design artifacts.
Skill for conducting retrospectives using YWT and KPT. Used for (YWT) (1) deep-diving into technical failures, (2) analyzing unexpected tool/system behavior, (3) documenting key learnings from complex bug fixes; and (KPT) (1) improving task estimation and planning accuracy, (2) refining step-by-step procedures, (3) optimizing communication or tool usage workflows.
최신 기술 트렌드나 도구를 빠르게 파악하고 요약하여 아카이빙하는 워크플로우입니다. (Efficiency Focus)
**IMPACT ANALYZER v1.0** - '영향도', '영향 범위', '변경 영향', '리팩토링 영향', '이거 바꾸면', '어디에 영향', '위험도' 요청 시 자동 발동. codebase-graph 기반 변경 전파 분석. 직접/간접 영향, 위험도 점수, 테스트 범위 제안. 코드 수정 전 필수 분석.
Refines an existing implementation plan through discussion with the user. Takes a GitHub issue number. Use when the user wants to refine a plan, discuss a plan, change a plan, or says "refine plan X" or "let's discuss the plan for issue
This skill should be used when creating new JIRA tickets, when the user wants to file a bug report, story, or task in JIRA, or when interactively building a well-structured ticket.
Use when executing implementation plans with independent tasks in the current session
프로젝트 구조를 분석하여 최적의 에이전트 컨텍스트 파일(AGENTS.md) 시스템을 구축합니다.
Use when checking the status of an autonomous mizu plan execution - reads state files to show progress percentage, current task, completed tasks, and recent execution notes
Complete OpenSSF Scorecard achievement guide. Understand all 18 security checks, fix false positives, navigate controversial recommendations, and progress from 7 to 10/10.
Fast routing triage for workflow messages; points to docs/workflow-routing-map.md.