Loading...
Loading...
Found 65 Skills
Only to be triggered by explicit /parallel-task-spark commands.
Generate a Product Requirements Document (PRD) for ralph-tui task orchestration. Creates PRDs with user stories that can be converted to beads issues or prd.json for automated execution. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
Only to be triggered by explicit /co-design commands. Parallel task executor that routes frontend/design tasks to Claude CLI print mode for superior design output.
Python port of Claude Code agent harness — tools, commands, task orchestration, and CLI entrypoint via oh-my-codex
Orchestrate autonomous AI development with task-based workflow and QA gates
Resume work from handoff document with context analysis and validation
Agent skill for planner - invoke with $agent-planner
N coordinated agents on shared task list using Claude Code native teams
Advanced Celery patterns including canvas workflows, priority queues, rate limiting, multi-queue routing, and production monitoring. Use when implementing complex task orchestration, task prioritization, or enterprise-grade background processing.
Vibe Kanban orchestration platform for AI coding agents: workspaces, sessions, task management, code review, git worktrees, multi-agent support. Keywords: Vibe Kanban, AI agents, Claude Code, Codex, Gemini, kanban board, git worktree, code review, MCP server, workspaces, sessions.
Configure delegation fleet lanes: which implementer CLI handles which kind of work, with optional model and effort (or variant) dials. Discovers installed CLIs, proposes a lane map for user approval, and writes global or project config only after explicit yes. Use when the user asks to set up, configure, or reconfigure delegation lanes, a fleet of lanes, or which implementer handles feature/tests/ui work — not for dispatching a coding task to an implementer.
Gerente do ciclo de vida de stories e orquestrador de handoffs no SynkOS. Use esta skill quando o usuário pedir para decompor um épico em stories, criar stories com critérios de aceite, fazer backlog grooming, planejar sprint, orquestrar handoffs entre roles (architect → dev → qa), ou fazer perguntas como "quebre esse épico em stories", "crie a story para X", "o backlog está priorizado?", "faça o checkpoint da story Y", "orquestre o handoff para QA". Ative também para resolver dependências entre stories, escalar stories bloqueadas, e garantir que cada story tem ownerRole e reviewRole definidos antes de entrar em implementação.