能力标签

⚙️

Agent工作流

Takt SDD 工作流

基于 TypeScript · 无代码搭建完整 AI 自动化流程

英文名：takt-sdd

⭐ 37 Stars 💻 TypeScript 📄 Apache-2.0 🏷 AI 8.0分

8.0AI 综合评分

ai-agentai-dlcsddtakttypescript

⬇ 下载源码 ZIP ⚙️ 配置说明

✦ AI Skill Hub 推荐

经 AI Skill Hub 精选评估，Takt SDD 工作流获评「强烈推荐」。这款Agent工作流在功能完整性、社区活跃度和易用性方面表现出色，AI 评分 8.0 分，适合有一定技术背景的用户使用。

📚 深度解析

Takt SDD 工作流是一套完整的 AI Agent 自动化工作流方案。随着 AI 能力的不断提升，基于 Agent 的自动化工作流正在成为提升个人和团队效率的核心方式。区别于传统的 RPA 自动化（模拟鼠标键盘操作），AI Agent 工作流通过理解任务意图、动态规划执行路径，能够处理更复杂的非结构化任务。

Takt SDD 工作流工作流的设计遵循"最小配置，最大复用"原则：核心逻辑已经封装好，用户只需配置自己的 API Key 和业务参数即可快速上手。工作流内置错误处理和重试机制，在网络波动或 API 限速等情况下仍能稳定运行，适合作为生产环境的自动化基础设施。

在实际部署时，建议先在测试环境中运行 3-5 次，验证各个环节的输出结果符合预期，再部署到生产环境。AI Skill Hub 评分 8.0 分，是同类 Agent 工作流中的精选推荐。

📋 工具概览

Spec-Driven Development工作流定义仓库

Takt SDD 工作流是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。

GitHub Stars

⭐ 37

开发语言

TypeScript

支持平台

Windows / macOS / Linux

维护状态

轻量级项目，按需更新

开源协议

Apache-2.0

AI 综合评分

8.0 分

工具类型

Agent工作流

Forks

—

📖 中文文档

以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

Spec-Driven Development工作流定义仓库

📌 核心特色

可视化 Agent 工作流编排，无需编写复杂代码
支持多步骤自动化任务链，实现全流程无人值守
与外部 API、数据库和第三方服务无缝集成
内置错误处理与自动重试机制，保障稳定运行
提供可复用的自动化模板，快速在同类场景部署

🎯 主要使用场景

自动化日常重复性工作，将精力集中于创造性任务
构建数据采集 → 处理 → 输出的完整自动化管线
实现跨平台、跨系统的数据流转和业务协同

以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。

安装命令

# 方式一：npm 全局安装
npm install -g takt-sdd

# 方式二：npx 直接运行（无需安装）
npx takt-sdd --help

# 方式三：项目依赖安装
npm install takt-sdd

# 方式四：从源码运行
git clone https://github.com/j5ik2o/takt-sdd
cd takt-sdd
npm install
npm start

📋 安装步骤说明

访问 GitHub 仓库获取工作流文件
在对应平台（Dify / Flowise / Make 等）中找到「导入工作流」功能
上传工作流文件
按照提示配置必要的环境变量和 API Key
运行测试确认流程正常后投入使用

以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。

常用命令 / 代码示例

# 命令行使用
takt-sdd --help

# 基本用法
takt-sdd [options] <input>

# Node.js 代码中使用
const takt_sdd = require('takt-sdd');

const result = await takt_sdd.run(options);
console.log(result);

以下配置示例基于典型使用场景生成，具体参数请参照官方文档调整。

配置示例

# takt-sdd 配置说明
# 查看配置选项
takt-sdd --config-example > config.yml

# 常见配置项
# output_dir: ./output
# log_level: info
# workers: 4

# 环境变量（覆盖配置文件）
export TAKT_SDD_CONFIG="/path/to/config.yml"

📑 README 深度解析真实文档完整度 58/100 查看 GitHub 原文 →

以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

takt-sdd

Write the spec. takt reliably ships the rest.

日本語

A Spec-Driven Development (SDD) workflow definition repository using takt.

Automates the entire development flow — from requirements definition through design, task decomposition, implementation, review, and validation — using takt workflows (YAML workflows) and facets.

takt-sdd is compatible with Kiro (.kiro/specs/) and can be used alongside it.

Features

takt-sdd uses takt's state-machine-based workflow control to deterministically manage AI agent execution paths.

Declarative Workflow Control — Define AI agent execution order and transition conditions declaratively in workflows (YAML). While AI output itself is non-deterministic, "which step, in what order, under what conditions" is deterministically controlled by YAML rules. Workflows progress as state machines, not free-form chat.
Faceted Prompting — Separate prompts into 5 independent concerns (Persona / Policy / Instruction / Knowledge / Output Contract). Each facet is reusable and swappable, shareable across workflows. Eliminates duplication of monolithic prompts and improves maintainability.
Multi-stage Validation — Place validation gates at each phase: requirements, design, and implementation. Gap analysis, design review (GO/NO-GO decisions), and parallel architecture/QA/implementation reviews detect quality issues early and minimize rework.
Loop Detection and Supervisory Control — Automatically detect repetitive patterns like plan→implement and review→fix. When thresholds are exceeded, a supervisor intervenes to assess progress and automatically escalates unproductive loops.
Adaptive Batch Implementation — Analyze inter-task dependencies and automatically choose between sequential and parallel execution. Independent tasks are processed in parallel by multiple workers.
Provider Agnostic — The same workflow definitions work across different providers such as Claude and Codex.

Check the {feature} name in .kiro/specs/{feature}

Prerequisites

Node.js 22+ (takt is automatically added to devDependencies during installation)

Requirements generation

npm run kiro:spec:requirements -- "description of requirements..."

Installation

To add the SDD workflow to your project, run the following in your project root:

npx create-takt-sdd

For Japanese facets and messages:

npx create-takt-sdd --lang ja

To install a specific version or the latest release:

npx create-takt-sdd --tag latest
npx create-takt-sdd --tag 0.1.2

The installer sets up the following:

.takt/ — Workflows (YAML workflows) and facets in the selected language (--lang)
openspec/config.yaml — OpenSpec project config initialized via the official OpenSpec 1.3.1 CLI
package.json — npm scripts for each phase + takt and @fission-ai/openspec@1.3.1 as devDependencies
cc-sdd — Kiro-compatible project initialization run via the pinned cc-sdd@3.0.2 CLI, propagating the selected --lang

Options:

Option	Description
`--force`	Overwrite existing `.takt/` directory
`--tag <version>`	Install a specific version (`latest`, `0.2.0`, etc.)
`--lang <en\\|ja>`	Facet and message language (default: `en`)
`--dry-run`	Preview files without writing

When package.json already exists, only npm scripts are merged (existing scripts are not overwritten). The installer also runs openspec init --tools none --force ., so OpenSpec is ready without generating extra AI-tool-specific files. It then runs the pinned cc-sdd@3.0.2 initialization with the same --lang. In --dry-run mode the cc-sdd initialization is previewed only and not executed.

Optional discovery

npm run kiro:discovery -- "feature idea..."

OpenSpec Configuration

The openspec/config.yaml file defines the schema and optional project context:

```yaml schema: spec-driven

Optional: project context shown to AI when creating artifacts

Optional: per-artifact rules

Kiro Compatibility Workflow

Use kiro:* scripts for new SDD workflow usage. Legacy cc-sdd:* scripts remain available for existing projects during migration, but new documentation and agent guidance should prefer the Kiro surface.

Phase	npm script	Workflow identity	Description
Discovery	`kiro:discovery`	`kiro-discovery`	Route a feature idea, update brief/roadmap when needed
Spec quick path	`kiro:spec:quick`	`kiro-spec-quick`	Generate requirements, design, and tasks through the closed-loop path
Requirements	`kiro:spec:requirements`	`kiro-spec-requirements`	Generate requirements in EARS format
Gap validation	`kiro:validate:gap`	`kiro-validate-gap`	Compare requirements with the current codebase
Design	`kiro:spec:design`	`kiro-spec-design`	Generate technical design and discovery notes
Design validation	`kiro:validate:design`	`kiro-validate-design`	Review design quality and return a GO/NO-GO decision
Tasks	`kiro:spec:tasks`	`kiro-spec-tasks`	Generate implementation tasks
Batch specs	`kiro:spec:batch`	`kiro-spec-batch`	Generate multiple specs from roadmap dependency order
Status	`kiro:spec:status`	`kiro-spec-status`	Report spec phase, approvals, and readiness
Implementation	`kiro:impl`	`kiro-impl`	Implement approved tasks with review/debug/verify gates
Implementation validation	`kiro:validate:impl`	`kiro-validate-impl`	Validate implementation evidence and remaining manual checks

OpenSpec Compatibility Workflow

Separate from the SDD workflow, an OpenSpec-based change management workflow is provided. This workflow manages structured changes through proposal → implementation → archival phases.

The npm run opsx:* entrypoints stay intact, but the workflow definitions now follow the official OpenSpec CLI contract (openspec new change, openspec status, openspec instructions, openspec archive --yes) instead of a repo-local helper script.

Workflow	Description
`opsx-propose`	Create a change and generate all artifacts (proposal, design, tasks)
`opsx-apply`	Implement tasks from a change
`opsx-archive`	Archive a completed change
`opsx-full`	Run propose → apply → archive in one automated sequence
`opsx-explore`	Interactive exploration and thinking (read-only, not included in full)