Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

jamesaphoenix/task-spec-loop

Name: task-spec-loop
Author: jamesaphoenix

.claude/skills/task-spec-loop/SKILL.md

npx skillsauth add jamesaphoenix/tx task-spec-loop

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

Task Spec Loop

Use this skill when the user wants task execution tied to paired specs, especially for file-based loops that inject markdown into Codex or Claude.

Core Rules

tx remains the source of truth for task state.
tx md-export --filter open is read-only export for loop injection, not a mutation path.
Linked specs must be attached to tasks with tx doc attach, not inferred from filenames alone.
New work should be captured explicitly with tx add, tx add --parent, and dependency edits.

Working Loop

Inspect the task and current spec links.

tx show <task-id>
tx memory context <task-id>

tx show should surface linkedDocs when docs are already attached.

Attach the right docs when the task needs a PRD/design pair, runbook, or decision.

tx doc attach <task-id> <prd-doc> --type implements
tx doc attach <task-id> <design-doc> --type references
tx doc attach <task-id> <supporting-doc> --type references

Use implements for the main driving PRD. Use references for the design doc and any supporting docs.

Keep the queue moving through tx primitives.

tx add "Follow-up task"
tx add "Subtask title" --parent <task-id>
tx dep block <task-id> <blocker-id>
tx dep unblock <task-id> <blocker-id>
tx update <task-id> --status blocked
tx done <task-id>

Create new tasks whenever the implementation exposes more work. Update dependencies if the execution order changes.

Export the open queue for Ralph-style prompt injection.

tx md-export --filter open
tx md-export --filter open --path .tx/tasks-open.md

This export should contain all non-done tasks plus compact linked-doc references so the loop can inject both work items and the spec handles they depend on.

Practical Guidance

Prefer linking a task to a stable PRD/doc slug pair before asking an agent to implement it.
If a non-trivial task is missing one half of the PRD/design pair, create or find the missing doc first, then attach both docs.
If implementation discovers new constraints, create follow-up tasks and update dependency edges instead of leaving that work implicit.
If a blocked task becomes unblocked because a dependency was completed or removed, reflect that with tx dep unblock or by completing the blocker in tx.

jamesaphoenix/task-spec-loop

.claude/skills/task-spec-loop/SKILL.md

Link tasks to paired PRD/design specs, export all open work to markdown, and keep Ralph-style loops moving by creating tasks, subtasks, and dependency updates through tx primitives.

2 stars

data-ai

Updated Apr 17, 2026

$ install --global

skillsauth

npx skillsauth add jamesaphoenix/tx task-spec-loop

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Apr 17, 2026, 2:15 AM64.5s1 file scanned

SKILL.md

name:: task-spec-loop
description:: Link tasks to paired PRD/design specs, export all open work to markdown, and keep Ralph-style loops moving by creating tasks, subtasks, and dependency updates through tx primitives.
argument-hint:: [task-id-or-doc-name]

Task Spec Loop

Use this skill when the user wants task execution tied to paired specs, especially for file-based loops that inject markdown into Codex or Claude.

Core Rules

tx remains the source of truth for task state.
tx md-export --filter open is read-only export for loop injection, not a mutation path.
Linked specs must be attached to tasks with tx doc attach, not inferred from filenames alone.
New work should be captured explicitly with tx add, tx add --parent, and dependency edits.

Working Loop

Inspect the task and current spec links.

tx show <task-id>
tx memory context <task-id>

tx show should surface linkedDocs when docs are already attached.

Attach the right docs when the task needs a PRD/design pair, runbook, or decision.

tx doc attach <task-id> <prd-doc> --type implements
tx doc attach <task-id> <design-doc> --type references
tx doc attach <task-id> <supporting-doc> --type references

Use implements for the main driving PRD. Use references for the design doc and any supporting docs.

Keep the queue moving through tx primitives.

tx add "Follow-up task"
tx add "Subtask title" --parent <task-id>
tx dep block <task-id> <blocker-id>
tx dep unblock <task-id> <blocker-id>
tx update <task-id> --status blocked
tx done <task-id>

Create new tasks whenever the implementation exposes more work. Update dependencies if the execution order changes.

Export the open queue for Ralph-style prompt injection.

tx md-export --filter open
tx md-export --filter open --path .tx/tasks-open.md

This export should contain all non-done tasks plus compact linked-doc references so the loop can inject both work items and the spec handles they depend on.

Practical Guidance

Prefer linking a task to a stable PRD/doc slug pair before asking an agent to implement it.
If a non-trivial task is missing one half of the PRD/design pair, create or find the missing doc first, then attach both docs.
If implementation discovers new constraints, create follow-up tasks and update dependency edges instead of leaving that work implicit.
If a blocked task becomes unblocked because a dependency was completed or removed, reflect that with tx dep unblock or by completing the blocker in tx.

Related Skills

jamesaphoenix/verify-invariants

development

VerifiedTrustedCommunity

Implement and verify design doc invariants by annotating tests and source code with [INV-*] / @spec tags, then driving tx spec coverage from BUILD toward HARDEN (100% FCI). Works with any design doc that has an invariants block.

2SKILL.mdUpdated Apr 17, 2026

jamesaphoenix/verify-invariants