Boost efficiency with task automation and organizers.
Fetches calendar events from all accounts (M365 Prisma/Personal/Family/DataBusiness + Google) and populates schedule sections in daily briefing. Triggers on "Get my calendar events for today", "Populate the calendar sections", "Update calendars in briefing entry [id]". Called by briefing-generator after create-briefing-entry. Calculates meeting count and deep work hours. Transitions Phase from 1-Email to 2-Calendar.
Interactive callable tool that creates BMAD planning documents (requirements, architecture, epics) in main repository on contrib branch. Three-persona Q&A system generates comprehensive planning before feature development. Use when: On contrib branch, planning phase, need requirements/architecture Triggers: plan feature, requirements, architecture, BMAD
Guide for creating sprint definitions in SPRINT.yaml. This skill should be used when users want to create sprint, new sprint planning, sprint definition best practices, or define steps for autonomous execution. Triggers on "create sprint", "new sprint", "sprint definition", "define steps".
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, editing PR details, or preparing code for review. (project)
Work item management for Workbench CLI. Use when creating, updating, linking, or closing work items and tracking execution status.
Atlas Simulator scan flow and next-step guidance for markdowntown. Use when working on folder scanning, tool detection, cwd handling, results panels, or scan-to-workbench CTAs.
This skill should be used when the user asks to "check my tasks", "show my tasks", "what should I work on", "add task", "update task", "complete task", mentions "Vikunja" or "Boosted tasks". By default, focus on the Boosted project (ID 3) unless the user specifies a different project.
This skill should be used when managing the file-based todo tracking system in the .claude/todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
Display rich content (markdown, code, diffs, mermaid diagrams) to users in a browser viewer. Use when you need to show complex content that benefits from rich rendering - reports, documentation, code with syntax highlighting, git diffs, or diagrams.
Automatically create weekly folder structures for Gastrohem WhatsApp conversations. This skill should be used when the user asks to create weekly folders, set up a new week, or prepare folder structure for WhatsApp documentation (e.g., "Create weekly structure", "Set up folders for next week", "Create structure for 27.10 - 02.11"). Creates Monday-Sunday folders with chat.md files in each department.
Coordinate multi-commit epic work using git worktrees, feature branches, PRs, and CI. Use when working on epics or large features that span multiple tasks.
User feedback patterns including success/error messages, loading states, confirmations, and progress indicators. Use when implementing notifications, toasts, or status updates. (project)
GitHub PR workflows including creation, review cycles, merge strategies, and stacked PRs. Use when creating PRs, reviewing code, merging branches, or managing stacked PR workflows. Covers rebase decision trees and AI-generated descriptions.
Update the project learning logs (PowerShell/cmd, Git/GitHub/Copilot, AWS, TypeScript, Next.js/React, Playwright) by merging new knowledge into existing categories across one or more files.
Implement advanced task features - Priorities, Tags, Due Dates, Reminders, Recurring Tasks, Search, Filter, and Sort. Use when adding Phase 5 advanced functionality. (project)
Invoke for complex multi-step tasks requiring intelligent planning and multi-agent coordination. Use when tasks need decomposition, dependency mapping, parallel/sequential/swarm/iterative execution strategies, or coordination of multiple specialized agents with quality gates and dynamic optimization.
Debug and investigate GitHub Actions workflow failures using gh CLI. Use when workflows are failing or when you need to understand CI/CD issues.
PROACTIVELY activates for ANY task with clear success criteria. This skill should be used when the user provides tasks like: "fix the bug", "add tests", "implement feature X", "refactor Y". Explicit triggers: "ralph this", "auto ralph", "loop it", "iterate". Auto-detects Ralph-suitable tasks (score >= 3/4): - Clear success criteria (tests pass, error gone, feature works) - Benefits from iteration (not one-shot) - Well-defined scope (specific files/functions) - Verifiable completion (can honestly output promise) Does NOT activate for: explanations, questions, vague requests. Output: Romanian. Input: Any (ro/en/ru/mixed).
Enterprise interactive survey orchestrator with AskUserQuestion tool integration, multi-select support, conditional branching, error recovery, and production-grade decision automation across all Alfred workflows; activates for requirement clarification, architectural decisions, risky operations, feature selection, and complex multi-step user interactions
Git workflow best practices and patterns. Use this skill when working with git operations, creating commits, managing branches, handling pull requests, or establishing team git workflows. Provides guidance on commit messages, branching strategies, and collaboration patterns.
Log key learnings to progress.txt during PRD iteration. Use when you discover codebase patterns, encounter gotchas, make important decisions, or learn something that would help future work sessions. Triggers on: log learning, add to progress, capture insight, record pattern, note gotcha, save lesson.
