workflow▌

Test-Driven Development workflow guiding the RED-GREEN-REFACTOR cycle. \n \n Structured three-phase cycle: write failing tests (RED), implement minimal code to pass (GREEN), then improve code quality (REFACTOR) \n Emphasizes behavior-driven test design using the AAA pattern (Arrange, Act, Assert) with one assertion per test \n Provides test prioritization guidance (happy path, error cases, edge cases, performance) and identifies anti-patterns to avoid \n Supports multi-agent workflows where diff

Use this skill when you need lane-style automation inside the CLI using:

Structured workflow for requirements analysis, technical design, and task planning across feature development and architecture projects. \n \n Enforces four sequential phases: requirements documentation with EARS syntax, technical solution design, task breakdown, and execution, with user confirmation required between each phase \n Integrates UI design skill for frontend-heavy projects, determining design style and color palette during requirements phase \n Provides templates for requirements doc

Durable execution infrastructure for reliable, fault-tolerant workflows across distributed systems. \n \n Covers sequential, parallel, and orchestrator-worker patterns with support for event-driven and scheduled task execution \n Compares four major platforms (n8n, Temporal, Inngest, DBOS) with explicit tradeoffs between accessibility, performance, and operational complexity \n Highlights critical sharp edges: idempotency keys for external calls, checkpointed steps, activity timeouts, and expone

AI-assisted automation for GitHub workflows including PR reviews, issue triage, CI/CD integration, and Git operations. \n \n Automated PR reviews with diff analysis, issue detection, and formatted feedback comments \n Issue triage with AI classification, auto-labeling, severity assessment, and stale issue management \n Smart test selection and deployment validation based on changed files and risk analysis \n Git operations including automated rebasing, conflict resolution, cherry-pick assistance

Define, validate, and run repo-local multi-step automations with .asc/workflow.json and asc workflow commands. \n \n Author workflows in .asc/workflow.json with support for global/workflow-level env, before/after hooks, error handlers, and conditional steps using if directives \n Run workflows locally or in CI with asc workflow run <name> , preview execution with --dry-run , and validate structure with asc workflow validate \n Supports sub-workflows (including private helper workflows), run

Durable, resumable workflows with step-based orchestration, hooks for external events, and built-in AI agent support. \n \n Supports three execution modes: workflow functions (orchestration layer), step functions (full Node.js access with automatic retry and result persistence), and DurableAgent for AI-powered workflows with tool integration \n Pause workflows at hooks to wait for external events, then resume from API routes; hooks support single events or iterable multi-event patterns with dete

Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation.

Generates detailed implementation blueprints by analyzing project architecture, technology stacks, and workflow patterns. \n \n Auto-detects project type, entry points, persistence mechanisms, and architecture patterns (.NET, Java/Spring, React, microservices, etc.) to tailor documentation \n Documents complete end-to-end workflows across entry points, service layers, data access, error handling, and response construction with actual code examples \n Configurable output detail levels, workflow c

Fetch your next meeting's agenda, attendees, and linked documents from Google Calendar. \n \n Retrieves the upcoming event with full attendee list and description details \n Supports multiple calendar selection via --calendar flag (defaults to primary calendar) \n Read-only operation; never modifies calendar data \n Output formats include JSON, table, YAML, and CSV for integration flexibility \n