feat: add rpg method prd example template#1285
Conversation
🦋 Changeset detectedLatest commit: b74e4a9 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
WalkthroughAdds an RPG (Repository Planning Graph) PRD template and an assets copy, new RPG method documentation, expands Quick Start guidance to compare templates, and updates project init to provision the RPG template. No exported/public API changes. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor U as User
participant I as scripts/init.js
participant FS as Filesystem (templates)
U->>I: Run project initialization
I->>FS: Copy `example_prd.txt`
Note right of FS #f9f7ef: Existing behavior
I->>FS: Copy `example_prd_rpg.txt`
Note right of FS #eef9f3: New step — RPG template provisioned
I-->>U: Init complete
sequenceDiagram
autonumber
participant TM as Task Master
participant PRD as RPG PRD (.taskmaster/docs/prd.txt)
participant P as Parser
participant DG as Dependency Graph Builder
participant PL as Planner
TM->>PRD: load PRD
TM->>P: parse-prd(PRD)
P-->>TM: structured PRD (capabilities, modules, deps)
TM->>PL: analyze-complexity / expand
PL->>DG: build dependency graph (explicit deps)
DG-->>PL: tasks ordered topologically by phase
TM->>PL: validate-dependencies
PL-->>TM: validated, executable plan
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (1)**/*.js📄 CodeRabbit inference engine (.cursor/rules/tests.mdc)
Files:
🧠 Learnings (3)📚 Learning: 2025-09-24T15:12:12.658ZApplied to files:
📚 Learning: 2025-07-18T17:14:29.399ZApplied to files:
📚 Learning: 2025-07-18T17:10:53.657ZApplied to files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
🔇 Additional comments (2)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (2)
.changeset/nice-ways-hope.md(1 hunks)apps/docs/getting-started/quick-start/prd-quick.mdx(2 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
.changeset/*.md
📄 CodeRabbit inference engine (.cursor/rules/changeset.mdc)
.changeset/*.md: When runningnpm run changesetornpx changeset add, provide a concise summary of the changes for theCHANGELOG.mdin imperative mood, typically a single line, and not a detailed Git commit message.
The changeset summary should be user-facing, describing what changed in the released version that is relevant to users or consumers of the package.
Do not use your detailed Git commit message body as the changeset summary.
Files:
.changeset/nice-ways-hope.md
.changeset/*
📄 CodeRabbit inference engine (.cursor/rules/new_features.mdc)
Create appropriate changesets for new features, use semantic versioning, include tagged system information in release notes, and document breaking changes if any.
Files:
.changeset/nice-ways-hope.md
.changeset/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
Changeset entries should be user-facing, describing the end-user impact rather than code specifics
Files:
.changeset/nice-ways-hope.md
🧠 Learnings (5)
📚 Learning: 2025-07-18T17:10:12.881Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:12.881Z
Learning: Applies to .taskmaster/docs/*.txt : Place Product Requirements Documents (PRDs) for features or initiatives in `.taskmaster/docs/` with descriptive filenames (e.g., `.taskmaster/docs/feature-xyz-prd.txt`).
Applied to files:
apps/docs/getting-started/quick-start/prd-quick.mdx
📚 Learning: 2025-09-24T15:12:58.855Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/AGENTS.md:0-0
Timestamp: 2025-09-24T15:12:58.855Z
Learning: Applies to assets/.taskmaster/docs/*.{txt,md} : Keep PRDs as .txt or .md under .taskmaster/docs and parse them with task-master parse-prd (use --append for incremental updates)
Applied to files:
apps/docs/getting-started/quick-start/prd-quick.mdx
📚 Learning: 2025-07-18T17:10:12.881Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:12.881Z
Learning: For PRD-driven feature development, create a dedicated tag, draft a PRD in `.taskmaster/docs/`, parse it into tasks, and add a high-level reference in the master tag.
Applied to files:
apps/docs/getting-started/quick-start/prd-quick.mdx
📚 Learning: 2025-07-31T22:08:16.039Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/taskmaster.mdc:0-0
Timestamp: 2025-07-31T22:08:16.039Z
Learning: After initializing a project with Taskmaster, you must parse a PRD in order to generate tasks. There will be no tasks files until then.
Applied to files:
apps/docs/getting-started/quick-start/prd-quick.mdx
📚 Learning: 2025-09-24T15:12:12.658Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-09-24T15:12:12.658Z
Learning: Start new projects with task-master init or parse a PRD via task-master parse-prd --input=<file> to generate an initial tasks.json
Applied to files:
apps/docs/getting-started/quick-start/prd-quick.mdx
🪛 markdownlint-cli2 (0.18.1)
.changeset/nice-ways-hope.md
5-5: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
17-17: Files should end with a single newline character
(MD047, single-trailing-newline)
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
scripts/init.js (1)
860-892: Consider mentioning the RPG template in the "next steps" guidance.The detailed "Getting Started" instructions reference
example_prd.txtin step 2, but don't mention the newly addedexample_prd_rpg.txttemplate. Users may benefit from knowing they have both options available.Consider adding a note about the RPG template option. For example, you could update step 2:
${chalk.white('2. ')}${chalk.yellow( - 'Discuss your idea with AI and ask for a PRD using example_prd.txt, and save it to scripts/PRD.txt' + 'Discuss your idea with AI and ask for a PRD using example_prd.txt (or example_prd_rpg.txt for dependency-aware planning), and save it to scripts/PRD.txt' )}
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
scripts/init.js(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.js
📄 CodeRabbit inference engine (.cursor/rules/tests.mdc)
**/*.js: Declare and initialize global variables at the top of modules to avoid hoisting issues.
Use proper function declarations to avoid hoisting issues and initialize variables before they are referenced.
Do not reference variables before their declaration in module scope.
Use dynamic imports (import()) to avoid initialization order issues in modules.
Files:
scripts/init.js
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Test
This PR was automatically generated to update documentation based on recent changes. Original commit: feat: add rpg method prd example template (#1285)\n\n\n Co-authored-by: Claude <claude-assistant@anthropic.com>
What type of PR is this?
Description
Related Issues
How to Test This
# Example commands or stepsExpected result:
Contributor Checklist
npm run changesetnpm testnpm run format-check(ornpm run formatto fix)Changelog Entry
For Maintainers
Summary by CodeRabbit
New Features
Documentation