scrum-team-product-owner
AI-Agentic Product Owner accountable for maximizing product value through effective Product Backlog management. Use when creating PBIs, ordering backlog, or accepting sprints.
AI-Agentic Product Owner accountable for maximizing product value through effective Product Backlog management. Use when creating PBIs, ordering backlog, or accepting sprints.
This skill should be used when analyzing failed GitHub Actions CI/CD runs for Breenix kernel development. Use for diagnosing test failures, parsing QEMU logs, identifying kernel panics or faults, understanding timeout issues, and determining root causes of CI failures.
Generate an AI-synthesised summary of your GitHub activity (issues, PRs, commits) for a specified organisation and time period. Creates a natural language narrative with inline URL references. Use when user wants to summarise their work, review their contributions, or generate a work log.
Generate hand-drawn style diagrams (architecture, flowcharts, system design) as .excalidraw.json files. Use when user wants diagrams, mentions Excalidraw, or needs Mermaid-to-visual conversion.
Multi-agent coordination for parallel plan execution with the coordinate and coord_output tools.
Daily report creation skill. Summarizes GitHub activities, creates a draft, and posts as an Issue. Use when: - Asked to "create daily report" or "write daily report" - Asked to "summarize today's activities" - Requested to create a daily report or journal
Automatically save and restore development context to minimize cognitive load when resuming work. Use when switching tasks, taking breaks, or returning after interruptions. Captures mental state, file locations, and next steps. Designed for ADHD developers with high context-switching costs.
Gives guidelines on how to explain code with call graphs and pseudocode. Invoke this when creating code explanations. Common user requests: - "Explain {feature or function}" - "Show me how {feature} works" - "Create pseudocode for {feature}" - "Generate call graph for {feature}" - "Show logic for {function}"
Identifies domain modules, ownership boundaries, dependencies, and interfaces using Domain-Driven Design principles. Provides domain maps, bounded contexts, refactor recommendations. Use for "DDD", "domain modeling", "bounded contexts", or "service boundaries".
Maintain scrum.ts dashboard following Agentic Scrum principles. Use when reading and editing scrum.ts, updating sprint status, or managing Product Backlog.
Create well-structured GitHub issues focused on user problems and outcomes, not implementation. Use when user reports bugs or requests features to ensure clear, testable requirements without premature implementation details.
Validate completed implementation against plan tasks and acceptance criteria. Use when: (1) Implementation is complete, (2) User wants validation before merging/shipping, (3) Quality gate check needed after implementation. Reviews ALL plan tasks for implementation correctness, test adequacy, and code quality. Produces structured feedback (approve, request changes, or comments) - does NOT fix code.
Use when creating or developing Laravel features, before writing code or implementation plans - refines rough ideas into fully-formed Laravel designs through collaborative questioning, alternative exploration, and incremental validation.
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.
Complete backlog implementation in feature-driven development. Read backlog requirements, reference implemented features, design approach, implement code, and document. Use when implementing features, changes, bug fixes, or improvements.
This skill should be used when users request new features, improvements, fixes, or ask to create plans. It facilitates BDD planning by asking clarifying questions and producing a clean, tracker-agnostic plan with acceptance criteria.
Find the gaps in your plan before your stakeholders do. Pressure tests plans, strategies, and communications. Domain-smart advisor, not nitpicker.
Agent Client Protocol (ACP) - Standardized communication between code editors and AI coding agents. Use for building ACP-compatible agents, integrating agents with editors (Zed, JetBrains, Neovim), implementing tool calls, file operations, and session management.