takt-task

Generate and validate TAKT task metadata and order.md documents.

7|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/j5ik2o/fraktor-rs --skill takt-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: takt-task
Source: https://github.com/j5ik2o/fraktor-rs/tree/main/.agents/skills/takt-task
Command: npx skills add https://github.com/j5ik2o/fraktor-rs --skill takt-task

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

TAKTのタスク管理ワークフローにおける TaskRecord のエントリ生成と order.md の作成・編集を支援し、手作業によるミスと反復作業を削減します。

Core Features & Use Cases

  • TaskRecord の自動生成: YAML 形式の一意なタスクエントリを作成し、必須フィールドを検証します。
  • order.md 生成・検証: タスク仕様書となる order.md の雛形を作成し、要件/受け入れ基準が正しく記述されているか検証します。
  • 検証と参照資料の活用: references/task-schema.md や validate-order-md.sh を参照してステータス遷移の整合性を保証します。例えば新しい pending タスクを追加する際に関連ファイルを自動生成します。

Quick Start

新しい TAKT タスクのエントリと order.md を作成し、生成されたメタデータの整合性を検証してください。

Frequently Asked Questions about takt-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate TAKT task metadata generation for tasks.yaml and order.md?

Automating TAKT task metadata generation involves creating YAML task entries and corresponding order.md documents within the .takt/tasks directory. This process enforces required TaskRecord fields and validates order.md structure using built-in schema definitions and validation scripts.

What is the best way to validate task status transitions in a TAKT workflow?

Validating task status transitions in a TAKT workflow requires checking TaskRecord entries against strict status rules defined in references/task-schema.md. The built-in validation script ensures consistency when adding or editing pending tasks.

How does order.md validation work for TAKT task specifications?

Order.md validation for TAKT task specifications works by leveraging the validate-order-md.sh script to check that requirements and acceptance criteria are correctly documented. It enforces the required order.md structure based on the references/takt schema definitions.

Do I need specific schema definitions to manage TAKT task metadata in YAML?

Yes, managing TAKT task metadata in YAML requires references/task-schema.md to guide the generation and validation of TaskRecord fields. These schema definitions ensure required fields are present and strict status transitions are enforced.

Why does my TAKT order.md validation fail when adding a new pending task?

TAKT order.md validation fails when requirements or acceptance criteria are incorrectly structured, or when TaskRecord fields are missing. The validate-order-md.sh script enforces strict order.md structure and required metadata fields based on the task-schema.md definitions.