Loading...
Loading...
Found 7,961 Skills
Explore-first wave pipeline. Decomposes requirement into exploration angles, runs wave exploration via spawn_agents_on_csv, synthesizes findings into execution tasks with cross-phase context linking (E*→T*), then wave-executes via spawn_agents_on_csv.
Automate document workflows with n8n - 7800+ workflow templates
High-level workflows for managing work using Fizzy cards — start, work on, complete, and delegate cards using the Fizzy CLI.
Set up, develop, test, and deploy Render Workflows. Covers first-time scaffolding (via CLI or manual), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, install the Render Workflows SDK (Python or TypeScript), scaffold a workflow service, add or modify tasks, test locally, or deploy to Render.
Wave-based comprehensive project documentation generator with dynamic task decomposition. Analyzes project structure and generates appropriate documentation tasks, computes optimal execution waves via topological sort, produces complete documentation suite including architecture, methods, theory, features, usage, and design philosophy.
Unified TDD workflow skill combining 6-phase TDD planning with Red-Green-Refactor task chain generation, and 4-phase TDD verification with compliance reporting. Triggers on "workflow-tdd-plan", "workflow-tdd-verify".
Use when a migration is already known to stay on the LangGraph orchestration side, including stages, routing, checkpoints, interrupts, persistence, streaming, and subgraph boundaries.
Use when the user needs workflow orchestration such as branching, concurrency, approvals, waiting and resume, runtime stream, restart-safe execution, mixed sync/async function or module orchestration, event-driven fan-out, process-clarity refactors that make stages explicit, performance-oriented refactors that collapse split requests, or explicit draft-review-revise style multi-stage flows. The user does not need to say TriggerFlow explicitly.
[DEPRECATED] Use /ce:review instead — renamed for clarity.
[DEPRECATED] Use /ce:compound instead — renamed for clarity.
Commit message conventions, staging practices, and commit best practices. Covers conventional commits, explicit staging workflow, logical change grouping, humble fact-based communication style, and automatic issue detection. Use when user mentions committing changes, writing commit messages, git add, git commit, staging files, or conventional commit format.
Captures, enriches, tags, and prioritizes roadmap tasks. Use when the user wants to note work quickly, add missing task details, organize a backlog, or reprioritize an existing list of tasks.