원클릭으로
takt-workflow
// Design or review Takt workflows. Use when working on orchestration, dependencies, and step wiring across actions.
// Design or review Takt workflows. Use when working on orchestration, dependencies, and step wiring across actions.
| name | takt-workflow |
| description | Design or review Takt workflows. Use when working on orchestration, dependencies, and step wiring across actions. |
Workflows compose actions into repeatable operations.
This skill is a routing guide. Treat takt schema workflow --format toon and workflow manifests as the source of truth.
takt generate workflow <name> --uses <action> first, then edit the generated JSON.takt validate workflow <name-or-path> --format toon.takt run workflow <name> --format toon.| Task | Command |
|---|---|
| Get workflow schema | takt schema workflow --format toon |
| Generate workflow | takt generate workflow <name> --uses <action> |
| Validate workflow | takt validate workflow <name-or-path> --format toon |
| Validate all manifests | takt validate all --format toon |
| Plan workflow run | takt run workflow <name> --format toon |
takt generate workflow <name> --uses <action>.workflows/.takt schema workflow --format toon.takt validate workflow <name-or-path> --format toon.Use takt generate workflow <name> --uses <action> to scaffold a workflow
manifest, then edit the generated JSON.
Design or review a Takt package manifest. Use when working on capabilities, the package Node version, handlers, schemas, or registry-facing package structure.
Design or review Takt actions. Use when working on project-local configured uses of capabilities, including defaults, secret bindings, labels, and ownership metadata.
Interactive getting-started walkthrough for new Takt users. Guides through inspecting the package, understanding the core nouns, scaffolding a first action or workflow, and validating the result. Triggers on "getting started", "new to takt", "first time", "walkthrough", "onboarding", "quickstart", "how do I start", "what do I do first", "learn takt", or whenever the user needs the package, capability, action, and workflow model explained before deeper work.