executing-plans
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
Discover databases project management skills, compare source repositories and read the instructions for each workflow.
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
Designs scalable system architectures and technical documents. Use when planning features, evaluating tradeoffs, documenting decisions, or analyzing complexity.
Create implementation plans with tasks grouped by subsystem. Related tasks share agent context; groups parallelize across subsystems.
Git branching and commit best practices. Use when working with git branches, commits, or merges.
Use when setting up CI/CD, implementing versioning, optimizing workflows, or managing releases with monorepo development workflows including version management, publishing, and team collaboration practices.
Use when facilitating BDD collaboration between developers, testers, and business stakeholders. Use when running discovery workshops and example mapping sessions.
Use when configuring Sentry alerts, managing issues, or setting up notifications. Covers alert rules, issue triage, and integrations.
Use when planning git branching strategies or managing branches for development. Helps create clear development narratives through effective branch organization and workflow patterns.
Use when structuring Standard Operating Procedures with proper sections, organization, and markdown formatting. Covers SOP anatomy and section organization.
Use when updating, versioning, deprecating, or maintaining existing Standard Operating Procedures. Covers keeping SOPs accurate, relevant, and synchronized with implementation changes.
Use when configuring GitLab CI/CD pipelines, defining stages, or setting up workflow rules. Covers pipeline structure, stage ordering, and execution flow.
Use when planning commit strategies or determining when to commit changes. Helps developers commit early and often to tell the story of their development process.
Use when annotating code with structured metadata, tags, and markers for AI-assisted development workflows. Covers annotation formats, semantic tags, and integration with development tools.
Use when creating incident response procedures and on-call playbooks. Covers incident management, communication protocols, and post-mortem documentation.
Use when defining and configuring Mise tasks in mise.toml. Covers task definitions, dependencies, file tasks, and parallel execution.
Use when creating structured operational runbooks for human operators. Covers runbook organization, documentation patterns, and best practices for clear operational procedures.
Use when responding to production incidents following SRE principles and best practices.
Use when creating implementation plans for features or tasks. Focuses on tactical execution planning with clear tasks, dependencies, and success criteria.
Automatically discover diagram and visualization skills when working with flowcharts, sequence diagrams, architecture diagrams, ER diagrams, Gantt charts, mindmaps, or any visual documentation using Mermaid.js....
Automatically discover Modal platform skills when working with Modal. Activates for modal development tasks.
Automatically discover realtime communication skills when working with realtime. Activates for realtime development tasks.
Automatically discover workflow and task management skills when working with Beads. Activates for workflow development tasks.
Automatically discover collaboration and teamwork skills when working with collaboration. Activates for collaboration development tasks.
Classify task complexity (1-10) to route to optimal model. Use when starting any non-trivial task to determine resources and approach. Triggers include: 'classify', 'complexity', 'what model', 'how complex'.
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.