product-manager
Expert in agile product management, MVP scoping, backlog prioritization, and iterative planning
Expert in agile product management, MVP scoping, backlog prioritization, and iterative planning
Swiss Public Transport real-time information. Use when querying train, bus, tram, or boat schedules in Switzerland. Supports station search, departure boards, journey planning from A to B, and connection details. Use for queries like "When does the next train leave from Zürich?" or "How do I get from Bern to Geneva?" or "Show departures at Basel SBB".
Persistent TODO scratch pad for tracking tasks across sessions. Use when user says "add to TODO", "what's on the TODO", "mark X done", "show TODO list", "remove from TODO", or asks about pending tasks. Also triggers on heartbeat to remind about stale items.
This snippet should be used when creating technical execution plans in HTML format with mandatory quality review before display.
Your approach to handling packages graph. Use this skill when working on files where packages graph comes into play.
PRD structure and patterns for SpecFlux. Use when creating or refining product requirement documents. PRDs should be concise for humans but detailed enough for AI agents to implement.
[TMUX MODE] Send plan to Codex via tmux file-based IPC. Only use when user explicitly runs /codex-plan-review command. For natural language requests, use the delegate_codex_plan_review MCP tool instead.
Updates the list of job leads and prioritizes actions. Use for weekly lead review.
Fetches ALL open issues from any GitHub repository using pagination and generates a comprehensive analysis including category breakdown, age distribution, stale issues (30+ days), top discussed issues, prioritization, and detailed recommendations for triage. Handles large repositories (5000+ issues) efficiently.
Epic and task structure patterns for SpecFlux. Use when breaking PRDs into epics and tasks. Epics should be self-contained with clear acceptance criteria.
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
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
Plan-first development methodology that creates detailed specifications before coding. Use when building features, refactoring code, or implementing complex changes. Creates structured plans with phases, file-level details, and verification steps to prevent drift and ensure production-ready code.
Expert in calculating critical path project timelines using PERT/CPM methodology with statutory deadline integration for expropriation projects. Use when managing complex project schedules, tracking OEA statutory deadlines (3-month registration, Form 2/7 service), identifying timeline risks, or optimizing resource allocation. Key terms include critical path, PERT analysis, CPM scheduling, statutory deadlines, float analysis, resource leveling
Systematic methodology for reading and understanding large codebases efficiently. Use when (1) Understanding a new or unfamiliar codebase quickly, (2) Preparing to modify or extend existing code safely, (3) Debugging complex issues requiring deep code understanding, (4) Onboarding new team members to a codebase, (5) Performing code audits or security reviews, (6) Refactoring legacy code with confidence, (7) Creating documentation for existing systems, (8) Tracing execution flows and data transformations
Your approach to handling packages ports. Use this skill when working on files where packages ports comes into play.
Analyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.
Use when pair programming with humans - enforces XP values (communication, simplicity, feedback, courage, respect) to deliver high-quality software; push back on YAGNI violations regardless of seniority or sunk cost
PDCA (Plan-Do-Check-Act) methodology knowledge. Covers documentation-first development, design-implementation sync, continuous improvement. Triggers: PDCA, plan, design, check, act, 계획, 설계, 検証, 改善
规划工作流 - 从想法到实现计划的结构化流程。通过迭代细化单个 Markdown 文档将模糊想法转化为清晰实现计划。
Your approach to handling packages react. Use this skill when working on files where packages react comes into play.
PDCA document templates for consistent documentation. Plan, Design, Analysis, and Report templates with proper structure. Triggers: template, plan document, design document, analysis document, report, 템플릿, 계획서, 설계서, 분석서, 보고서, テンプレート, 計画書, 設計書