task-spec-loop

Links tasks to attached PRD/design specs and exports open items to Markdown via tx doc attach and md-export.

6|3|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/jamesaphoenix/tx --skill task-spec-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-spec-loop
Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/task-spec-loop
Command: npx skills add https://github.com/jamesaphoenix/tx --skill task-spec-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align tasks with paired PRD/design specs and keep Ralph-style loops moving by ensuring tasks reference attached docs and exporting open work to Markdown.

Core Features & Use Cases

  • Link tasks to attached PRD/design specs using tx doc attach and explicit doc types.
  • Maintain continuous work flow by exporting open tasks and their linked docs to Markdown for review and handoffs.
  • Create and update subtasks and dependency edges with tx primitives to keep work coordinated across agents.

Quick Start

Attach the paired PRD/design docs to a task and export the open queue to Markdown to keep the loop moving.

Frequently Asked Questions about task-spec-loop

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

FAQPage Schema
How do I link tasks to PRD and design specs for ongoing work?

You link tasks to PRD and design specs by using tx doc attach to connect paired documents with explicit doc types. This establishes tx as the source of truth and ensures tasks maintain direct references to their attached specs.

What is the best way to export open tasks and linked docs to Markdown?

Exporting open tasks to Markdown is done using tx md-export, which outputs open items alongside their linked docs for review and handoffs. This operation keeps Ralph-style loops moving without mutating any active state.

How do I create subtasks and update dependency edges for task management?

Subtasks and dependency edges are created and updated using tx primitives within the task management flow. This maintains coordinated work across agents by explicitly managing dependency edges for ongoing tasks.

Does exporting open work to Markdown mutate active task state?

No, exporting open work to Markdown does not mutate active task state. The tx md-export operation outputs open items and their linked docs for review while preserving the active state entirely unchanged.

When do I need to export open tasks for Ralph-style loops?

You need to export open tasks for Ralph-style loops when maintaining continuous workflow requires reviewing open items and handing off linked docs. Exporting to Markdown keeps the loop moving without disrupting active state.