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.

[TheDarkSkyXD]

He plans to add in parallel execution.

[CyberClash]

I think this would still be a beneficial feature. Currently I have a PRD and a Task list thats already broken down in to stories or ticketable items (tasks for kanban). It would save a ton of time for a greenfield project to be able to simply take my already worked out specs and info and place them in a format auto-claude wants so that it can create tasks for all of those items. It would be a tremendous time saver. Currently its taking hours.. many many hours to covert these into tasks. Making basic tasks with the info I have already to start with then growing those tasks individually as needed, using the raodmap tools, ideation tool, etc would be more ideal than starting from scratch if I already have a lot of the work done.

Does this make sense? You almost need a prompt or toggle, import from template or start from scratch.

[CyberClash]

alternatively you could place those initial tasks in GitHub issue log, pull those into the kanban. Create sub tickets/tasks and manage from there as well with clear hierarchy from sub ticket labeling from github. This is how I would normally manage them but I use python scripts to create the initial set of tasks in github issue log from a PRD like' file.. Then claude code to manage that ticket log when breaking them into smaller sub tasks. So from task 1. I use claude code to create sub tickets 1.1, 1.2, however many I need. Then I prioritize and pull them into kanban style workflow. it much faster on the initial task load.

Im not going to pretend to know how that would break what you have here or that its better, im just thinking out loud for discussion sake. my task to create tasks from this PRD file is still running and its been i dunno, 4 to 6 hours and I dont know who successful it will or wont be yet. I can see it working, creating files with info for the subtasks, etc currently.

[CyberClash]

Update to thoughts on this. I noticed using todays system, the format Auto-Claude uses makes it REALLY easy for us to do this ourselves by just using claude code to script the import of these tasks right into the Kanban if desired. I was able to do this with zero issues in seconds. There is no formatting on the kanban which def hurts, but we can have it use markdown formatting which would be a big improvement. I plan to manage my project both human tasks and ai tasks via this Kanban. A quick win may be a call out to using this method to achieve the task.