Menu
Execute mapped tasks with stream discipline, dependency safety checks, and evidence updates. Use when tasks are ready for implementation.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | execution-skill |
| description | Execute mapped tasks with stream discipline, dependency safety checks, and evidence updates. Use when tasks are ready for implementation. |
ready and dependency-safe; planned tasks need readiness review before execution.project/projects/<slug>/updates/bash .agents/scripts/pm/in-progress.shbash .agents/scripts/pm/standup.shbash .agents/scripts/pm/next.shreferences/runbook.mdtemplates/blocker-update.mdtemplates/stream-update.mdDefine and approve a measurable outcome and Spec. Use when a new delivery request has unclear scope, missing outcome, or missing owner.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
Decompose an approved plan into atomic tasks with dependencies and acceptance criteria. Use when planning is complete and execution must be prepared.
Verify release readiness and enforce quality gates with risk-based checks and evidence capture. Use before closure or merge.
Open and run repo-native research intake before mutating canonical delivery artifacts. Use when a Delano request has unclear intent, unresolved options, external evidence needs, or material uncertainty that should be investigated before changing spec, plan, workstreams, or tasks.