executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Discover databases project management skills, compare source repositories and read the instructions for each workflow.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
General overview of instructions to the project
実装前に計画を提示し、影響範囲・実行コマンド結果を必ず報告する
Automatically analyze test coverage when user asks which code is tested, mentions coverage gaps, or shows code asking about testing. Identifies untested code paths and suggests test additions. Invoke when user...
Automatically extract technical requirements from design references when user mentions Figma, uploads images, or says "implement this design". Analyzes colors, typography, spacing, layout, and maps to WordPress...
Log and analyze workouts. Use when the user wants to (1) record a workout at the gym via conversation, (2) parse workout markdown files to CSV, (3) query exercise history with DuckDB, or (4) track fitness progr...
Workflow bug triage for OpenEvent. Use when you have a regression/bug report (wrong step, wrong detour, HIL stuck, site visit issues) and need a minimal reproduction trace plus a fix plan tied to workflow invar...
Fast routing triage for workflow messages; points to docs/workflow-routing-map.md.
Fast routing triage for workflow messages; points to docs/workflow-routing-map.md.
Workflow bug triage for OpenEvent. Use when you have a regression/bug report (wrong step, wrong detour, HIL stuck, site visit issues) and need a minimal reproduction trace plus a fix plan tied to workflow invar...
Canonical OpenEvent email workflow architecture (intake, date confirmation, room availability, offer review, negotiation, confirmation) and file map.
Help leaders give effective feedback using Kim Scott's Radical Candor framework. Use this skill when asked to: draft feedback for team members, prepare for difficult conversations, review feedback for tone an...
Creates GitHub issue with task checklist based on architecture documents (specs.md, frontend.md, backend.md). Run after reviewing the planning documents.
Explores user intent, requirements and design before implementation. You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
GitLab CLI (glab) for merge requests, issues, and CI/CD pipelines. Use when working with GitLab repositories for MR creation/review, issue management, pipeline debugging, or any GitLab API operations. Triggers...
Creates or updates pull requests by analyzing code changes, creating branches, committing, pushing, and managing PRs with the project template. Use when creating a new PR, updating an existing PR, opening a PR,...
Expert guidance for creating, writing, building, and refining Opencode Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best pr...
Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that the agent will execute. Produces agent-executable plans with verification criteria, no...
Use when translating a program/app idea into a VibeDev MCP Job (deliverables, definition of done, invariants, and a small step plan) and preparing it to transition to READY without implementing features yet
Orchestrate feature development through 5 phases - discuss, BOM, architect, test plan, implement
Plan and design UI/UX flows, navigation, and user journeys with Mermaid diagrams
This skill provides a systematic approach for investigating and fixing bugs and issues in the codebase. Use this skill when users report bugs, unexpected behavior, test failures, or request fixes for specific i...
Automatically analyze tasks and route to optimal agent(s). Use when receiving complex requests to determine which agents to spawn.
Writes comprehensive handoff note at session end. Captures work done, files changed, remaining tasks, and next steps. Use before ending any work session or switching contexts.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.