tasks

Generate dependency-ordered user stories and tasks from spec.md and plan.md.

96|5|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/ArvorCo/Relentless --skill tasks-arvorco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/ArvorCo/Relentless/tree/main/.claude/skills/tasks
Command: npx skills add https://github.com/ArvorCo/Relentless --skill tasks-arvorco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning a project plan into a structured backlog by converting a feature plan into dependency-ordered user stories and actionable tasks, reducing manual planning time and ensuring traceability.

Core Features & Use Cases

  • Generates a set of user stories (e.g., US-001, US-002) from spec.md and plan.md.
  • Produces a tasks.md that groups tasks by user story and enforces dependencies for incremental delivery.
  • Automatically converts the tasks into prd.json with routing information to guide model/harness selection.

Quick Start

To begin, ensure the feature directory contains spec.md and plan.md, then trigger the Relentless workflow to read these files and produce tasks.md and prd.json.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I generate dependency-ordered user stories from a feature plan?

To generate dependency-ordered user stories, you provide a feature plan in spec.md and plan.md. The skill extracts requirements and outputs a tasks.md file that groups actionable tasks by user story while respecting dependencies for incremental delivery.

How does test-driven development factor into automated user story generation?

Test-driven development is enforced by requiring test criteria within each generated user story. This ensures that every actionable task grouped in the tasks.md file includes specific testing requirements for validation.

Can I automatically convert user stories into a prd.json format?

Yes, the generated user stories are automatically converted into a prd.json file. This output includes routing information designed to guide model and harness selection for downstream processing.

What is the best way to structure a backlog from spec.md and plan.md files?

The best way to structure a backlog is to extract requirements from spec.md and plan.md files. This process produces a tasks.md file that groups tasks by user story and enforces dependencies for incremental delivery.

Why does automated backlog generation require a spec.md and plan.md file?

Automated backlog generation requires spec.md and plan.md files because they contain the foundational feature requirements and project plans. The skill reads these specific files to extract requirements and enforce dependency ordering.