PRD parsing

[Infinitam0]

Problem Statement

Having to manually create tasks or sprints.

Proposed Solution

Parse PRDs inspired by https://github.com/eyaltoledano/claude-task-master

Alternatives Considered

Manually creating tasks.

Component

Python Backend (auto-claude/)

How important is this feature to you?

Important for my workflow

Contribution

• I'm willing to submit a PR for this feature

Additional Context

No response

[AndyMik90]

@Infinitam0 are you thinking about the # Parse a PRD and generate tasks
task-master parse-prd your-prd.txt from task master?

Auto Claude if you reference a PRd to it will break it down into subtasks.

This will be even clearer when we now integrate the BMAD method, since it will focus on epics with stories.

[Infinitam0]

Hi @AndyMik90 ,

I was indeed talking about the task-master parse-prd your-prd.txt method. Your idea of combining the parse-prd function with the BMAD method sounds very promising. Kind regards.

[johann-taberlet]

The current approach of decomposing a specification directly into subtasks does not support parallel execution (e.g. via worktrees), unlike a decomposition into higher-level tasks.

It would be valuable to introduce a higher-level decomposition layer where an entire app_spec (such as the Anthropic Claude.ai clone example) can first be broken down into tasks, and only then further decomposed into subtasks.

Tasks should be structured according to priority, dependencies, and isolation. This would enable an automatic execution mode that respects priorities and dependencies, and—when sufficient isolation is guaranteed—runs tasks in parallel. Doing so would significantly reduce later worktree merge conflicts.