-
Notifications
You must be signed in to change notification settings - Fork 688
Implement PRD Generator: AI-assisted Product Requirements Document creation workflow #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: next
Are you sure you want to change the base?
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oupsy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a patch for inquires dependency, not activated atm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just /ignore the .cursor/rules :'D sorry abouut the language, sometimes it rebels against me
@eyaltoledano this is the good one, rest you can delete, forget the .txt an .cursor etc, was late and didnt payed so much attention sorry sir |
LMK if you need help with the merge conflicts. We dont want to overwrite the new work that was done. |
AS LONG AS I REMEMBER, there were not merge conflicts, corefunctionality has been uploaded isolated, so it was 100% working when I did PR'd (Well, didnt check for user bugs etc...). The difference between this 92 issue and last one was just regarding the isolation of the functionalities. |
That's nearly impossible, as my update touched like 250 files which is p much the whole project lol i.e. scripts/modules/commands.s and dev.js and the rules |
Ok yes, @eyaltoledano now I get what you mean. I was about to go sleep, if it's not done when I'm back, I'll give an eye :) |
I think you were talking about if I was having problem during my merge tests (i did a commit bout that and mocked one test lmao) |
@Zyra-V23 please resolve conflicts, will be reviewing asap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
initial review done.
Will do a deeper one.
// Mock the storage provider if ContextManager uses one internally | ||
// jest.mock('../storage/some-storage-provider.js'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cleanup ?
// Reset or create a new instance for each test | ||
contextManager = new ContextManager(); | ||
// Clear any potentially persisted context from previous tests | ||
// This might involve mocking storage or using an internal reset method if available | ||
// Example: contextManager.resetAllContexts(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cleanup
prd/prd.txt
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably needs to be removed
scripts/modules/error-handler.js
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pretty sure we already have an error handler ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes! we do have one in mcp-server/src/logger.js :) removing it
scripts/modules/logger.js
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we already have a logger, find it and use that instead.
Remove this, unless this is a refactor.
@Crunchyman-ralph For the services to be accessible via task-master ideate or similar commands, we need to: Register the commands in commands.js Would you like me to add the command registration to commands.js in a follow-up PR, or would you prefer to integrate them differently into the MCP architecture? I was told to just do the logic and leave the mcp connection part to you guys @eyaltoledano , let me know :) |
Seems like it is failing the format-check and test. Please fix those failing unit tests |
It's failing because error-handler was removed, I will upload it soon and make sure it's clear defined its for handling errors related to prd service
Enviado desde Proton Mail para Android
…-------- Mensaje original --------
El 15/4/25 18:09, Ralph Khreish ha escrito:
Seems like it is failing the format-check and test. Please fix those failing unit tests
—
Reply to this email directly, [view it on GitHub](#92 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BPXASXXWI3ZAWKH2TX7ICJ32ZUVNHAVCNFSM6AAAAAB2NECSXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBWGY3DIOBUG4).
You are receiving this because you were mentioned.Message ID: ***@***.***>
Crunchyman-ralph left a comment [(eyaltoledano/claude-task-master#92)](#92 (comment))
Seems like it is failing the format-check and test. Please fix those failing unit tests
—
Reply to this email directly, [view it on GitHub](#92 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BPXASXXWI3ZAWKH2TX7ICJ32ZUVNHAVCNFSM6AAAAAB2NECSXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBWGY3DIOBUG4).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
PR Title
"Implement PRD Generator: AI-assisted Product Requirements Document creation workflow"
PR Notes
🚀 Overview
This PR introduces a complete PRD (Product Requirements Document) generation workflow powered by AI models like Claude and Perplexity. The system transforms basic product ideas into comprehensive, professional requirement documents through a guided, multi-stage process that simulates expert input and discussion.
🧩 Key Components
New Core Services
New Data Models
Idea
: Represents initial product concepts with metadataDiscussion
: Captures expert discussions and key insightsPRD
: Structures the final document with proper versioningWorkflow Integration
prd/
directory🔄 PRD Generation Workflow
The complete workflow consists of four main commands:
Ideation
node scripts/dev.js ideate --idea="Product idea description" [--research]
Transforms an initial idea into a structured concept document.
Round Table
Simulates a discussion between expert roles about the concept.
Concept Refinement
node scripts/dev.js refine-concept --concept-file=prd/concept.txt [--discussion-file=prd/discussion.txt]
Improves the concept using insights from the expert discussion.
PRD Generation
Creates the final PRD document based on the refined concept.
💡 UI Improvements
ora
for loading indicators during AI operations🧪 Testing Status
📋 Cursor Rules Updates
Updated
.cursor/rules/
files with documentation about:🔍 Implementation Notes
This feature creates a bridge between initial product ideation and structured task generation, allowing teams to:
This completes the full circle of the Task Master CLI, from idea to implementation tracking.