feat: implement claude code agents#1091
Conversation
🦋 Changeset detectedLatest commit: 2bc619b 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 |
WalkthroughNew agent specifications for "task-executor," "task-orchestrator," and "task-checker" have been added in both the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Task-Orchestrator
participant Task-Executor
participant Task-Checker
participant Task-Master
User->>Task-Orchestrator: Submit tasks / requests
Task-Orchestrator->>Task-Master: Retrieve task queue and dependencies
Task-Orchestrator->>Task-Executor: Assign task(s) with instructions
Task-Executor->>Task-Master: Fetch task details
Task-Executor->>Task-Master: Update subtask progress/status
Task-Executor->>Task-Master: Validate dependencies
Task-Executor->>Task-Master: Mark task as 'review'
Task-Orchestrator->>Task-Master: Monitor executor progress
Task-Checker->>Task-Master: Retrieve tasks marked 'review'
Task-Checker->>Task-Master: Verify implementations and run tests
Task-Checker->>Task-Master: Mark task as 'done' or send back to pending
Task-Orchestrator->>User: Report status / escalate issues
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Suggested reviewers
📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (2).changeset/*.md📄 CodeRabbit Inference Engine (.cursor/rules/changeset.mdc)
Files:
.changeset/*📄 CodeRabbit Inference Engine (.cursor/rules/new_features.mdc)
Files:
🧠 Learnings (32)📓 Common learnings📚 Learning: in the eyaltoledano/claude-task-master repository, agent files in assets/claude/agents/ are intended...Applied to files:
📚 Learning: in the eyaltoledano/claude-task-master repository, agent files are intentionally duplicated between ...Applied to files:
📚 Learning: guidelines for integrating new features into the task master cli with tagged system considerations (...Applied to files:
📚 Learning: describes the high-level architecture of the task master cli application, including the new tagged t...Applied to files:
📚 Learning: import task master's development workflow commands and guidelines, treat as if import is in the main...Applied to files:
📚 Learning: applies to scripts/modules/task-manager/**/*.js : do not call ai-specific getters (like `getmainmode...Applied to files:
📚 Learning: applies to scripts/modules/task-manager.js : use ai to generate detailed subtasks within the current...Applied to files:
📚 Learning: in the eyaltoledano/claude-task-master repository, the mcp server code in mcp-server/src/ is part of...Applied to files:
📚 Learning: for claude agent instruction files in .claude/agents/ and assets/claude/agents/ directories, ignore ...Applied to files:
📚 Learning: for major feature additions like new cli commands, eyaltoledano prefers detailed changesets with com...Applied to files:
📚 Learning: for files in .claude/agents/ and assets/claude/agents/ directories, ignore markdownlint issues like ...Applied to files:
📚 Learning: for changeset files (.changeset/*.md), the first line after the frontmatter must be a plain, unstyle...Applied to files:
📚 Learning: for claude agent instruction files located in .claude/agents or assets/claude/agents directories, cr...Applied to files:
📚 Learning: for changeset files (.changeset/*.md), crunchyman-ralph prefers to ignore formatting nitpicks about ...Applied to files:
📚 Learning: for files in .claude/agents/ or assets/claude/agents/ directories, ignore markdownlint issues as the...Applied to files:
📚 Learning: applies to .changeset/*.md : when running `npm run changeset` or `npx changeset add`, provide a conc...Applied to files:
📚 Learning: for changeset files (.changeset/*.md), avoid suggesting punctuation for bullet points as the project...Applied to files:
📚 Learning: applies to .changeset/*.md : the changeset summary should be user-facing, describing what changed in...Applied to files:
📚 Learning: applies to .changeset/*.md : do not use your detailed git commit message body as the changeset summa...Applied to files:
📚 Learning: do not add a changeset for trivial chores such as very minor code cleanup, adding comments that don'...Applied to files:
📚 Learning: applies to .changeset/* : create appropriate changesets for new features, use semantic versioning, i...Applied to files:
📚 Learning: do not add a changeset for local configuration changes, such as updates to personal editor settings ...Applied to files:
📚 Learning: every pull request containing new features, bug fixes, breaking changes, performance improvements, s...Applied to files:
📚 Learning: monitor code review comments, track common development questions, update rules after major refactors...Applied to files:
📚 Learning: pull request descriptions must use the provided template, including task overview, subtasks complete...Applied to files:
📚 Learning: for prd-driven feature development, create a dedicated tag, draft a prd in `.taskmaster/docs/`, pars...Applied to files:
📚 Learning: in the eyaltoledano/claude-task-master repository, every task is always part of a tag - there is no ...Applied to files:
📚 Learning: use the taskmaster command set (`task-master` cli or mcp tools) for all task management operations: ...Applied to files:
📚 Learning: guide for using task master to manage task-driven development workflows with tagged task lists suppo...Applied to files:
📚 Learning: for cli usage, install taskmaster globally with `npm install -g task-master-ai` or use locally via `...Applied to files:
📚 Learning: applies to .*/rules/** : each ai coding assistant rule profile (e.g., claude code, cursor, windsurf)...Applied to files:
🪛 LanguageTool.changeset/wide-actors-report.md[grammar] ~5-~5: Use hyphens correctly (QB_NEW_EN_OTHER_ERROR_IDS_29) [grammar] ~7-~7: Use correct spacing (QB_NEW_EN_OTHER_ERROR_IDS_5) [grammar] ~9-~9: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~13-~13: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~14-~14: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~15-~15: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~16-~16: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~20-~20: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~21-~21: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~22-~22: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~23-~23: There might be a problem here. (QB_NEW_EN_MERGED_MATCH) [grammar] ~27-~27: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~28-~28: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~29-~29: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~30-~30: There might be a problem here. (QB_NEW_EN_MERGED_MATCH) [grammar] ~34-~34: Use articles correctly (QB_NEW_EN_OTHER_ERROR_IDS_11) [grammar] ~34-~34: Use correct spacing (QB_NEW_EN_OTHER_ERROR_IDS_5) [grammar] ~36-~36: Use correct spacing (QB_NEW_EN_OTHER_ERROR_IDS_5) [grammar] ~55-~55: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~56-~56: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~57-~57: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~58-~58: There might be a mistake here. (QB_NEW_EN_OTHER) [grammar] ~59-~59: There might be a mistake here. (QB_NEW_EN_OTHER) 🪛 markdownlint-cli2 (0.17.2).changeset/wide-actors-report.md5-5: First line in a file should be a top-level heading (MD041, first-line-heading, first-line-h1) 11-11: Headings should be surrounded by blank lines (MD022, blanks-around-headings) 13-13: Lists should be surrounded by blank lines (MD032, blanks-around-lists) 18-18: Headings should be surrounded by blank lines (MD022, blanks-around-headings) 20-20: Lists should be surrounded by blank lines (MD032, blanks-around-lists) 25-25: Headings should be surrounded by blank lines (MD022, blanks-around-headings) 27-27: Lists should be surrounded by blank lines (MD032, blanks-around-lists) 🔇 Additional comments (2)
✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🔭 Outside diff range comments (1)
.claude/agents/task-executor.md (1)
1-71: Duplicate spec exists underassets/claude/agents/task-executor.mdMaintaining two copies will diverge quickly and confuse the agent-loader. Pick one canonical location (prefer
.claude/agents/) and delete / symlink the other.
♻️ Duplicate comments (2)
assets/claude/agents/task-executor.md (1)
1-71: See formatting & lint fixes suggested for the canonical fileAll
MD041,MD032,MD031, andMD040issues apply here as well..claude/agents/task-orchestrator.md (1)
1-131: Same duplication & formatting issues as assets copyFollow the consolidation advice and apply the markdown-lint fixes (blank lines around headings/lists, code-fence language).
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (4)
.claude/agents/task-executor.md(1 hunks).claude/agents/task-orchestrator.md(1 hunks)assets/claude/agents/task-executor.md(1 hunks)assets/claude/agents/task-orchestrator.md(1 hunks)
🧰 Additional context used
🧠 Learnings (24)
📓 Common learnings
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/git_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:31.810Z
Learning: Pull Request descriptions must use the provided template, including Task Overview, Subtasks Completed, Implementation Details, Testing, Breaking Changes, and Related Tasks
Learnt from: eyaltoledano
PR: eyaltoledano/claude-task-master#1069
File: .changeset/floppy-news-buy.md:7-38
Timestamp: 2025-08-02T14:54:52.216Z
Learning: For major feature additions like new CLI commands, eyaltoledano prefers detailed changesets with comprehensive descriptions, usage examples, and feature explanations rather than minimal single-line summaries.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-31T22:07:14.034Z
Learning: Import Task Master's development workflow commands and guidelines, treat as if import is in the main CLAUDE.md file.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/git_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:31.810Z
Learning: Pull Request titles must follow the format: Task <ID>: <Task Title>
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.
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#997
File: apps/extension/src/services/task-repository.ts:25-57
Timestamp: 2025-07-31T21:48:00.389Z
Learning: In the eyaltoledano/claude-task-master repository, every task is always part of a tag - there is no concept of untagged tasks. The tag system is mandatory and comprehensive, meaning all tasks exist within a tag context (with 'master' as the default tag if none specified).
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for integrating new features into the Task Master CLI with tagged system considerations (new_features.mdc).
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Describes the high-level architecture of the Task Master CLI application, including the new tagged task lists system (architecture.mdc).
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/architecture.mdc:0-0
Timestamp: 2025-07-18T17:07:39.336Z
Learning: Applies to scripts/modules/task-manager/*.js : Files in scripts/modules/task-manager/ should each handle a specific action related to task management (e.g., add-task.js, expand-task.js), supporting the tagged task lists system and backward compatibility.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Applies to assets/.taskmaster/tasks/**/* : Task files should follow the specified format with fields: id, title, status, dependencies, priority, description, details, and testStrategy.
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: Use the Taskmaster command set (`task-master` CLI or MCP tools) for all task management operations: listing, expanding, updating, tagging, and status changes.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/ai_services.mdc:0-0
Timestamp: 2025-07-18T17:06:57.833Z
Learning: Applies to scripts/modules/task-manager/*.js : Determine the appropriate `role` (`main`, `research`, `fallback`) in your core logic and pass it to the service.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for implementing and interacting with the Task Master MCP Server (mcp.mdc).
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Comprehensive reference for Taskmaster MCP tools and CLI commands with tagged task lists information (taskmaster.mdc).
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1069
File: .changeset/fix-tag-complexity-detection.md:0-0
Timestamp: 2025-08-02T15:33:22.656Z
Learning: For changeset files (.changeset/*.md), Crunchyman-ralph prefers to ignore formatting nitpicks about blank lines between frontmatter and descriptions, as he doesn't mind having them and wants to avoid such comments in future reviews.
📚 Learning: guidelines for integrating new features into the task master cli with tagged system considerations (...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for integrating new features into the Task Master CLI with tagged system considerations (new_features.mdc).
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: describes the high-level architecture of the task master cli application, including the new tagged t...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Describes the high-level architecture of the Task Master CLI application, including the new tagged task lists system (architecture.mdc).
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: in the eyaltoledano/claude-task-master repository, every task is always part of a tag - there is no ...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#997
File: apps/extension/src/services/task-repository.ts:25-57
Timestamp: 2025-07-31T21:48:00.389Z
Learning: In the eyaltoledano/claude-task-master repository, every task is always part of a tag - there is no concept of untagged tasks. The tag system is mandatory and comprehensive, meaning all tasks exist within a tag context (with 'master' as the default tag if none specified).
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: applies to scripts/modules/task-manager.js : use consistent formatting for task files, include all t...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tasks.mdc:0-0
Timestamp: 2025-07-18T17:14:29.399Z
Learning: Applies to scripts/modules/task-manager.js : Use consistent formatting for task files, include all task properties in text files, and format dependencies with status indicators.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.md
📚 Learning: applies to scripts/modules/task-manager.js : use ai to generate detailed subtasks within the current...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tasks.mdc:0-0
Timestamp: 2025-07-18T17:14:29.399Z
Learning: Applies to scripts/modules/task-manager.js : Use AI to generate detailed subtasks within the current tag context, considering complexity analysis for subtask counts and ensuring proper IDs for newly created subtasks.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-orchestrator.md
📚 Learning: applies to scripts/modules/task-manager/**/*.js : do not call ai-specific getters (like `getmainmode...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/utilities.mdc:0-0
Timestamp: 2025-07-18T17:18:17.759Z
Learning: Applies to scripts/modules/task-manager/**/*.js : Do not call AI-specific getters (like `getMainModelId`, `getMainMaxTokens`) from core logic functions in `scripts/modules/task-manager/*`; instead, pass the `role` to the unified AI service.
Applied to files:
assets/claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: applies to scripts/modules/task-manager/*.js : files in scripts/modules/task-manager/ should each ha...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/architecture.mdc:0-0
Timestamp: 2025-07-18T17:07:39.336Z
Learning: Applies to scripts/modules/task-manager/*.js : Files in scripts/modules/task-manager/ should each handle a specific action related to task management (e.g., add-task.js, expand-task.js), supporting the tagged task lists system and backward compatibility.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.md
📚 Learning: applies to scripts/modules/task-manager.js : extract tasks from prd documents using ai, create them ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tasks.mdc:0-0
Timestamp: 2025-07-18T17:14:29.399Z
Learning: Applies to scripts/modules/task-manager.js : Extract tasks from PRD documents using AI, create them in the current tag context (defaulting to 'master'), provide clear prompts to guide AI task generation, and validate/clean up AI-generated tasks.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.md
📚 Learning: use the taskmaster command set (`task-master` cli or mcp tools) for all task management operations: ...
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: Use the Taskmaster command set (`task-master` CLI or MCP tools) for all task management operations: listing, expanding, updating, tagging, and status changes.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: applies to assets/.taskmaster/tasks/**/* : task files should follow the specified format with fields...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Applies to assets/.taskmaster/tasks/**/* : Task files should follow the specified format with fields: id, title, status, dependencies, priority, description, details, and testStrategy.
Applied to files:
assets/claude/agents/task-executor.md
📚 Learning: view specific task details using `task-master show ` to understand implementation requirements....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: View specific task details using `task-master show <id>` to understand implementation requirements.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: implement code following task details, dependencies, and project standards....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Implement code following task details, dependencies, and project standards.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.md
📚 Learning: guide for using task master to manage task-driven development workflows with tagged task lists suppo...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guide for using Task Master to manage task-driven development workflows with tagged task lists support (dev_workflow.mdc).
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: applies to scripts/modules/task-manager/*.js : determine the appropriate `role` (`main`, `research`,...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/ai_services.mdc:0-0
Timestamp: 2025-07-18T17:06:57.833Z
Learning: Applies to scripts/modules/task-manager/*.js : Determine the appropriate `role` (`main`, `research`, `fallback`) in your core logic and pass it to the service.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: use `task-master next` to show the next task to work on, ensuring tasks are completed in the appropr...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Use `task-master next` to show the next task to work on, ensuring tasks are completed in the appropriate sequence.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: when breaking down complex tasks in taskmaster, use the `expand_task` command with appropriate flags...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:02.683Z
Learning: When breaking down complex tasks in Taskmaster, use the `expand_task` command with appropriate flags (`--num`, `--research`, `--force`, `--prompt`) and review generated subtasks for accuracy.
Applied to files:
assets/claude/agents/task-executor.md.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: import task master's development workflow commands and guidelines, treat as if import is in the main...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-31T22:07:14.034Z
Learning: Import Task Master's development workflow commands and guidelines, treat as if import is in the main CLAUDE.md file.
Applied to files:
.claude/agents/task-executor.mdassets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: use `task-master add-task` to add a new task to tasks.json using ai....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Use `task-master add-task` to add a new task to tasks.json using AI.
Applied to files:
.claude/agents/task-executor.md
📚 Learning: comprehensive reference for taskmaster mcp tools and cli commands with tagged task lists information...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Comprehensive reference for Taskmaster MCP tools and CLI commands with tagged task lists information (taskmaster.mdc).
Applied to files:
assets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: in the eyaltoledano/claude-task-master repository, the mcp server code in mcp-server/src/ is part of...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1002
File: .changeset/puny-friends-give.md:2-3
Timestamp: 2025-07-17T21:33:57.585Z
Learning: In the eyaltoledano/claude-task-master repository, the MCP server code in mcp-server/src/ is part of the main "task-master-ai" package, not a separate "mcp-server" package. When creating changesets for MCP server changes, use "task-master-ai" as the package name.
Applied to files:
assets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: guidelines for integrating ai usage telemetry across task master (telemetry.mdc)....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for integrating AI usage telemetry across Task Master (telemetry.mdc).
Applied to files:
assets/claude/agents/task-orchestrator.md
📚 Learning: guidelines for implementing and interacting with the task master mcp server (mcp.mdc)....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for implementing and interacting with the Task Master MCP Server (mcp.mdc).
Applied to files:
assets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
📚 Learning: analyze task complexity with `task-master analyze-complexity --research` before breaking down tasks....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Analyze task complexity with `task-master analyze-complexity --research` before breaking down tasks.
Applied to files:
assets/claude/agents/task-orchestrator.md.claude/agents/task-orchestrator.md
🪛 LanguageTool
assets/claude/agents/task-executor.md
[grammar] ~8-~8: Use correct spacing
Context: ...s, following best practices and project standards. Core Responsibilities: 1. **Task Anal...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~10-~10: There might be a mistake here.
Context: ...ractices and project standards. Core Responsibilities: 1. Task Analysis: When given a task, fir...
(QB_NEW_EN_OTHER)
[grammar] ~12-~12: Use correct spacing
Context: ...uirements, dependencies, and acceptance criteria. 2. Implementation Planning: Before coding...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~15-~15: There might be a mistake here.
Context: ...entify files that need to be created or modified - Note any dependencies or prerequisites ...
(QB_NEW_EN_OTHER)
[grammar] ~16-~16: There might be a mistake here.
Context: ... modified - Note any dependencies or prerequisites - Consider the testing strategy defined in...
(QB_NEW_EN_OTHER)
[grammar] ~17-~17: There might be a mistake here.
Context: ...der the testing strategy defined in the task 3. Focused Execution: - Implement one...
(QB_NEW_EN_OTHER)
[grammar] ~20-~20: There might be a mistake here.
Context: ...t one subtask at a time for clarity and traceability - Follow the project's coding standards fr...
(QB_NEW_EN_OTHER)
[grammar] ~21-~21: There might be a mistake here.
Context: ...ct's coding standards from CLAUDE.md if available - Prefer editing existing files over creat...
(QB_NEW_EN_OTHER)
[grammar] ~22-~22: There might be a mistake here.
Context: ...diting existing files over creating new ones - Only create files that are essential for...
(QB_NEW_EN_OTHER)
[grammar] ~23-~23: There might be a mistake here.
Context: ...e files that are essential for the task completion 4. Progress Documentation: - Use `tas...
(QB_NEW_EN_OTHER)
[grammar] ~26-~26: There might be a mistake here.
Context: ... to log your approach and any important decisions - Update task status to 'in-progress' when...
(QB_NEW_EN_OTHER)
[grammar] ~27-~27: There might be a mistake here.
Context: ...pdate task status to 'in-progress' when starting: `task-master set-status --id= --stat...
(QB_NEW_EN_OTHER)
[grammar] ~28-~28: There might be a problem here.
Context: ...rogress - Mark as 'done' only after verification:task-master set-status --id= --status=done` 5. Quality Assurance: - Implement the ...
(QB_NEW_EN_MERGED_MATCH)
[grammar] ~31-~31: There might be a mistake here.
Context: ...t the testing strategy specified in the task - Verify that all acceptance criteria are ...
(QB_NEW_EN_OTHER)
[grammar] ~32-~32: There might be a mistake here.
Context: ...Verify that all acceptance criteria are met - Check for any dependency conflicts or in...
(QB_NEW_EN_OTHER)
[grammar] ~33-~33: There might be a mistake here.
Context: ...any dependency conflicts or integration issues - Run relevant tests before marking task a...
(QB_NEW_EN_OTHER)
[grammar] ~34-~34: Use articles correctly
Context: ... - Run relevant tests before marking task as complete 6. **Dependency Management...
(QB_NEW_EN_OTHER_ERROR_IDS_11)
[grammar] ~34-~34: There might be a mistake here.
Context: ...n relevant tests before marking task as complete 6. Dependency Management: - Check task...
(QB_NEW_EN_OTHER)
[grammar] ~37-~37: There might be a mistake here.
Context: ...Check task dependencies before starting implementation - If blocked by incomplete dependencies, c...
(QB_NEW_EN_OTHER)
[grammar] ~38-~38: There might be a mistake here.
Context: ...plete dependencies, clearly communicate this - Use task-master validate-dependencies ...
(QB_NEW_EN_OTHER)
[grammar] ~39-~39: There might be a mistake here.
Context: ...task-master validate-dependencies` when needed Implementation Workflow: 1. Retrieve ...
(QB_NEW_EN_OTHER)
[grammar] ~41-~41: There might be a mistake here.
Context: ...ndencies` when needed Implementation Workflow: 1. Retrieve task details and understand re...
(QB_NEW_EN_OTHER)
[grammar] ~43-~43: There might be a mistake here.
Context: ...1. Retrieve task details and understand requirements 2. Check dependencies and prerequisites 3. ...
(QB_NEW_EN_OTHER)
[grammar] ~44-~44: There might be a mistake here.
Context: ... requirements 2. Check dependencies and prerequisites 3. Plan implementation approach 4. Update t...
(QB_NEW_EN_OTHER)
[grammar] ~45-~45: There might be a mistake here.
Context: ...nd prerequisites 3. Plan implementation approach 4. Update task status to in-progress 5. Imp...
(QB_NEW_EN_OTHER)
[grammar] ~46-~46: There might be a mistake here.
Context: ...ation approach 4. Update task status to in-progress 5. Implement the solution incrementally...
(QB_NEW_EN_OTHER)
[grammar] ~47-~47: There might be a mistake here.
Context: ...o in-progress 5. Implement the solution incrementally 6. Log progress and decisions in subtask up...
(QB_NEW_EN_OTHER)
[grammar] ~48-~48: There might be a mistake here.
Context: .... Log progress and decisions in subtask updates 7. Test and verify the implementation 8. Ma...
(QB_NEW_EN_OTHER)
[grammar] ~49-~49: There might be a mistake here.
Context: ... subtask updates 7. Test and verify the implementation 8. Mark task as done when complete 9. Sugge...
(QB_NEW_EN_OTHER)
[grammar] ~50-~50: There might be a mistake here.
Context: ...mplementation 8. Mark task as done when complete 9. Suggest next task if appropriate **Key ...
(QB_NEW_EN_OTHER)
[grammar] ~51-~51: There might be a mistake here.
Context: ...e when complete 9. Suggest next task if appropriate Key Principles: - Focus on completing...
(QB_NEW_EN_OTHER)
[grammar] ~53-~53: There might be a mistake here.
Context: ...Suggest next task if appropriate Key Principles: - Focus on completing one task thoroughly...
(QB_NEW_EN_OTHER)
[grammar] ~55-~55: There might be a mistake here.
Context: ...ne task thoroughly before moving to the next - Maintain clear communication about what ...
(QB_NEW_EN_OTHER)
[grammar] ~56-~56: There might be a mistake here.
Context: ...tion about what you're implementing and why - Follow existing code patterns and projec...
(QB_NEW_EN_OTHER)
[grammar] ~57-~57: There might be a mistake here.
Context: ...llow existing code patterns and project conventions - Prioritize working code over extensive d...
(QB_NEW_EN_OTHER)
[grammar] ~58-~58: There might be a mistake here.
Context: ...nsive documentation unless docs are the task - Ask for clarification if task requiremen...
(QB_NEW_EN_OTHER)
[grammar] ~59-~59: There might be a mistake here.
Context: ... clarification if task requirements are ambiguous - Consider edge cases and error handling i...
(QB_NEW_EN_OTHER)
[grammar] ~60-~60: There might be a mistake here.
Context: ...r edge cases and error handling in your implementations Integration with Task Master: You wor...
(QB_NEW_EN_OTHER)
[grammar] ~62-~62: There might be a mistake here.
Context: ...mplementations Integration with Task Master: You work in tandem with the task-orches...
(QB_NEW_EN_OTHER)
[grammar] ~65-~65: There might be a mistake here.
Context: ...e Task Master commands to: - Track your progress - Update task information - Maintain proje...
(QB_NEW_EN_OTHER)
[grammar] ~66-~66: There might be a mistake here.
Context: ...to: - Track your progress - Update task information - Maintain project state - Coordinate with...
(QB_NEW_EN_OTHER)
[grammar] ~67-~67: There might be a mistake here.
Context: ...ate task information - Maintain project state - Coordinate with the broader development ...
(QB_NEW_EN_OTHER)
[grammar] ~68-~68: There might be a mistake here.
Context: ...Coordinate with the broader development workflow When you complete a task, briefly summar...
(QB_NEW_EN_OTHER)
.claude/agents/task-orchestrator.md
[grammar] ~8-~8: Use correct spacing
Context: ...d task-executor agents to complete work efficiently. ## Core Responsibilities 1. **Task Queue A...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~10-~10: Use correct spacing
Context: ... to complete work efficiently. ## Core Responsibilities 1. Task Queue Analysis: You continuously ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~12-~12: Use correct spacing
Context: ...urrent state of work, dependencies, and priorities. 2. Dependency Graph Management: You build...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~14-~14: Use correct spacing
Context: ...ted in parallel and which must wait for prerequisites. 3. Executor Deployment: You strategically...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~16-~16: Use correct spacing
Context: ...the necessary context and clear success criteria. 4. Progress Coordination: You track the p...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~18-~18: Use correct spacing
Context: ...eassess the execution strategy as tasks complete. ## Operational Workflow ### Initial Assess...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~20-~20: Use correct spacing
Context: ...tegy as tasks complete. ## Operational Workflow ### Initial Assessment Phase 1. Use `get_tas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~23-~23: There might be a mistake here.
Context: ...-master list` to retrieve all available tasks 2. Analyze task statuses, priorities, and d...
(QB_NEW_EN_OTHER)
[grammar] ~24-~24: There might be a mistake here.
Context: ... Analyze task statuses, priorities, and dependencies 3. Identify tasks with status 'pending' tha...
(QB_NEW_EN_OTHER)
[grammar] ~25-~25: There might be a mistake here.
Context: ... status 'pending' that have no blocking dependencies 4. Group related tasks that could benefit f...
(QB_NEW_EN_OTHER)
[grammar] ~26-~26: There might be a mistake here.
Context: ...sks that could benefit from specialized executors 5. Create an execution plan that maximizes ...
(QB_NEW_EN_OTHER)
[grammar] ~27-~27: There might be a mistake here.
Context: ...Create an execution plan that maximizes parallelization ### Executor Deployment Phase 1. For each in...
(QB_NEW_EN_OTHER)
[grammar] ~31-~31: There might be a mistake here.
Context: ...loy a task-executor agent with specific instructions - Provide the executor with task ID, requi...
(QB_NEW_EN_OTHER)
[grammar] ~32-~32: There might be a mistake here.
Context: ...xecutor with task ID, requirements, and context - Set clear completion criteria and report...
(QB_NEW_EN_OTHER)
[grammar] ~33-~33: There might be a mistake here.
Context: ...clear completion criteria and reporting expectations 2. Maintain a registry of active executors ...
(QB_NEW_EN_OTHER)
[grammar] ~34-~34: There might be a mistake here.
Context: ... of active executors and their assigned tasks 3. Establish communication protocols for pr...
(QB_NEW_EN_OTHER)
[grammar] ~35-~35: There might be a mistake here.
Context: ...sh communication protocols for progress updates ### Coordination Phase 1. Monitor executor p...
(QB_NEW_EN_OTHER)
[grammar] ~38-~38: There might be a mistake here.
Context: ...r executor progress through task status updates 2. When a task completes: - Verify compl...
(QB_NEW_EN_OTHER)
[grammar] ~41-~41: There might be a mistake here.
Context: ... - Update task status if needed usingset_task_status` - Reassess dependency graph for newly unbl...
(QB_NEW_EN_OTHER)
[grammar] ~42-~42: There might be a mistake here.
Context: ...ss dependency graph for newly unblocked tasks - Deploy new executors for available work ...
(QB_NEW_EN_OTHER)
[grammar] ~43-~43: There might be a mistake here.
Context: ... - Deploy new executors for available work 3. Handle executor failures or blocks: -...
(QB_NEW_EN_OTHER)
[grammar] ~45-~45: There might be a mistake here.
Context: ... - Reassign tasks to new executors if needed - Escalate complex issues to the user -...
(QB_NEW_EN_OTHER)
[grammar] ~46-~46: There might be a mistake here.
Context: ...ded - Escalate complex issues to the user - Update task status to 'blocked' when app...
(QB_NEW_EN_OTHER)
[grammar] ~47-~47: There might be a mistake here.
Context: ... - Update task status to 'blocked' when appropriate ### Optimization Strategies **Parallel Exec...
(QB_NEW_EN_OTHER)
[grammar] ~49-~49: Use correct spacing
Context: ...ked' when appropriate ### Optimization Strategies Parallel Execution Rules: - Never assi...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~52-~52: There might be a mistake here.
Context: ... dependent tasks to different executors simultaneously - Prioritize high-priority tasks when reso...
(QB_NEW_EN_OTHER)
[grammar] ~53-~53: There might be a mistake here.
Context: ... high-priority tasks when resources are limited - Group small, related subtasks for single...
(QB_NEW_EN_OTHER)
[grammar] ~54-~54: There might be a mistake here.
Context: ...l, related subtasks for single executor efficiency - Balance executor load to prevent bottlen...
(QB_NEW_EN_OTHER)
[grammar] ~55-~55: There might be a mistake here.
Context: ...ency - Balance executor load to prevent bottlenecks Context Management: - Provide executor...
(QB_NEW_EN_OTHER)
[grammar] ~58-~58: There might be a mistake here.
Context: ...e executors with minimal but sufficient context - Share relevant completed task informatio...
(QB_NEW_EN_OTHER)
[grammar] ~59-~59: There might be a mistake here.
Context: ...completed task information when it aids execution - Maintain a shared knowledge base of proj...
(QB_NEW_EN_OTHER)
[grammar] ~60-~60: There might be a mistake here.
Context: ...ared knowledge base of project-specific patterns Quality Assurance: - Verify task compl...
(QB_NEW_EN_OTHER)
[grammar] ~63-~63: There might be a mistake here.
Context: ...erify task completion before marking as done - Ensure test strategies are followed when...
(QB_NEW_EN_OTHER)
[grammar] ~64-~64: There might be a mistake here.
Context: ...nsure test strategies are followed when specified - Coordinate cross-task integration testin...
(QB_NEW_EN_OTHER)
[grammar] ~65-~65: There might be a mistake here.
Context: ...ate cross-task integration testing when needed ## Communication Protocols When deploying ...
(QB_NEW_EN_OTHER)
[grammar] ~67-~67: Use correct spacing
Context: ...n testing when needed ## Communication Protocols When deploying executors, provide them w...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~69-~69: Use correct spacing
Context: ... When deploying executors, provide them with: TASK ASSIGNMENT: - Task ID: [specific ID] - Objective: [clear goal] - Dependencies: [list any completed prerequisites] - Success Criteria: [specific completion requirements] - Context: [relevant project information] - Reporting: [when and how to report back] When receiving executor updates: 1. Ackn...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~81-~81: There might be a mistake here.
Context: ...r updates: 1. Acknowledge completion or issues 2. Update task status in Task Master 3. Rea...
(QB_NEW_EN_OTHER)
[grammar] ~82-~82: There might be a mistake here.
Context: ...or issues 2. Update task status in Task Master 3. Reassess execution strategy 4. Deploy ne...
(QB_NEW_EN_OTHER)
[grammar] ~83-~83: There might be a mistake here.
Context: ...us in Task Master 3. Reassess execution strategy 4. Deploy new executors as appropriate ## ...
(QB_NEW_EN_OTHER)
[grammar] ~84-~84: There might be a mistake here.
Context: ...ion strategy 4. Deploy new executors as appropriate ## Decision Framework **When to paralleliz...
(QB_NEW_EN_OTHER)
[grammar] ~86-~86: Use correct spacing
Context: ...w executors as appropriate ## Decision Framework When to parallelize: - Multiple pendin...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~91-~91: Use correct spacing
Context: ...sks are well-defined with clear success criteria When to serialize: - Strong dependenci...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~96-~96: Use correct spacing
Context: ... - Integration points requiring careful coordination When to escalate: - Circular dependenc...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~102-~102: Use correct spacing
Context: ...rification - Resource conflicts between executors ## Error Handling 1. Executor Failure:...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~104-~104: Use correct spacing
Context: ...e conflicts between executors ## Error Handling 1. Executor Failure: Reassign task to new...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~106-~106: There might be a mistake here.
Context: ...cutor with additional context about the failure 2. Dependency Conflicts: Halt affected ex...
(QB_NEW_EN_OTHER)
[grammar] ~107-~107: There might be a mistake here.
Context: ...ected executors, resolve conflict, then resume 3. Task Ambiguity: Request clarification ...
(QB_NEW_EN_OTHER)
[grammar] ~108-~108: There might be a mistake here.
Context: ... Request clarification from user before proceeding 4. System Errors: Implement graceful degr...
(QB_NEW_EN_OTHER)
[grammar] ~109-~109: There might be a mistake here.
Context: ...on, falling back to serial execution if needed ## Performance Metrics Track and optimize ...
(QB_NEW_EN_OTHER)
[grammar] ~111-~111: Use correct spacing
Context: ...ial execution if needed ## Performance Metrics Track and optimize for: - Task completio...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~118-~118: Use correct spacing
Context: ...for task groups - Dependency resolution speed ## Integration with Task Master Leverage t...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~120-~120: Use correct spacing
Context: ...olution speed ## Integration with Task Master Leverage these Task Master MCP tools eff...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~122-~122: Use correct spacing
Context: ...r Leverage these Task Master MCP tools effectively: - get_tasks - Continuous queue monitoring - `get_task...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~123-~123: Use correct spacing
Context: ...ively: - get_tasks - Continuous queue monitoring - get_task - Detailed task analysis - `set_task_stat...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~124-~124: Use correct spacing
Context: ...monitoring - get_task - Detailed task analysis - set_task_status - Progress tracking - next_task - Fallb...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~125-~125: Use correct spacing
Context: ...analysis - set_task_status - Progress tracking - next_task - Fallback for serial execution - `analyz...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~126-~126: Use correct spacing
Context: ...ing - next_task - Fallback for serial execution - analyze_project_complexity - Strategic planning - `complexity_report...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~127-~127: Use correct spacing
Context: ...analyze_project_complexity- Strategic planning -complexity_report` - Resource allocation You are the strate...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~128-~128: Use correct spacing
Context: ...anning - complexity_report - Resource allocation You are the strategic mind coordinating ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
🪛 markdownlint-cli2 (0.17.2)
assets/claude/agents/task-executor.md
8-8: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
19-19: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
25-25: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
65-65: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
.claude/agents/task-executor.md
8-8: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
19-19: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
25-25: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
65-65: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
assets/claude/agents/task-orchestrator.md
8-8: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
22-22: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
23-23: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
29-29: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
30-30: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
37-37: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
38-38: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
52-52: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
58-58: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
63-63: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
70-70: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
70-70: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
81-81: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
89-89: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
94-94: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
99-99: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
114-114: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
123-123: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
.claude/agents/task-orchestrator.md
8-8: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
22-22: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
23-23: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
29-29: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
30-30: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
37-37: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
38-38: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
52-52: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
58-58: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
63-63: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
70-70: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
70-70: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
81-81: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
89-89: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
94-94: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
99-99: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
114-114: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
123-123: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
🔇 Additional comments (1)
.claude/agents/task-executor.md (1)
70-78: Code fence lacks language & surrounding blank linesThe TASK ASSIGNMENT snippet triggers
MD031 / MD040. Give the fence a language (textis fine) and keep one blank line above & below.-70~ ``` +69~ When deploying executors, provide them with: + +```text TASK ASSIGNMENT: ... -78~ ``` +``` +
Crunchyman-ralph
force-pushed
the
feat/add.claude.code.subagents
branch
from
71aaa25 to
f9861c2
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (4)
.claude/agents/task-executor.md (1)
1-6: Missing H1 heading after the YAML block
Same issue was flagged in a prior review; please add# Task Executorimmediately after the closing---to satisfyMD041.assets/claude/agents/task-orchestrator.md (1)
1-6: Redundant copy of the orchestrator spec – keep a single source of truth
This file is byte-for-byte identical to.claude/agents/task-orchestrator.md. Remove or symlink one of them to prevent divergence.assets/claude/agents/task-executor.md (1)
1-6: Duplicate of.claude/agents/task-executor.md
Maintaining two identical specs violates DRY and invites drift. Consolidate to one canonical location..claude/agents/task-orchestrator.md (1)
1-6: Top-level heading missing after front-matter
Add# Task Orchestratorbelow the YAML to satisfy MD041.
Crunchyman-ralph
force-pushed
the
feat/add.claude.code.subagents
branch
from
f9861c2 to
71350b9
Compare
Crunchyman-ralph
force-pushed
the
feat/add.claude.code.subagents
branch
from
71350b9 to
b06d59e
Compare
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (7)
.claude/agents/task-executor.md (3)
14-18: Pad bulleted lists with blank lines (MD032)Each list needs an empty line before and after to keep markdown-lint quiet.
-2. **Implementation Planning**: Before coding, briefly outline your implementation approach: - - Identify files that need to be created or modified +2. **Implementation Planning**: Before coding, briefly outline your implementation approach: + + - Identify files that need to be created or modified - Note any dependencies or prerequisites - Consider the testing strategy defined in the task +
4-8: Insert an H1 after the YAML to satisfy MD041--- model: sonnet color: blue --- + +# Task Executor +
1-3: Trim the YAMLdescriptionand move examples below front-matterLong, multi-paragraph examples inside a scalar make the YAML hard to read and brittle.
Keep the summary concise and place examples in the body.-description: Use this agent when you need to implement, complete, or work on a specific task ... <big block of examples> ... +description: > + Implementation-focused agent for completing a single, known Task-Master task. + +# Examples +<example>…</example> +…assets/claude/agents/task-executor.md (1)
1-71: Duplicate of.claude/agents/task-executor.md– remove or symlink
Keeping two copies invites drift; consolidate to a single canonical spec..claude/agents/task-orchestrator.md (2)
69-78: Code fence needs language & padding (MD031/MD040)-When deploying executors, provide them with: -``` +When deploying executors, provide them with: + +```text TASK ASSIGNMENT: ... -``` +``` +
1-6: Add H1 heading after front-matter--- model: opus color: green --- + +# Task Orchestrator +assets/claude/agents/task-orchestrator.md (1)
1-131: Redundant copy of.claude/agents/task-orchestrator.md
Please delete or link to the canonical file to avoid divergence.
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (8)
.changeset/wide-actors-report.md (1)
1-7: Top-level heading still missing (MD041)
This was flagged previously; please insert a#heading immediately after the front-matter..claude/agents/task-executor.md (3)
1-6: Missing H1 heading after YAML front-matter (MD041)
Add something like# Task Executorbeneath the---separator to satisfy docs & generators.
69-91: Lists must be surrounded by blank lines (MD032)
Several bulleted lists (e.g. “Integration with Task Master”) lack the required blank-line padding, triggering markdown-lint and hurting readability.-Always use Task Master commands to: -- Track your progress +Always use Task Master commands to: + +- Track your progress ... +
3-3: Front-matterdescriptionis far too longEmbedding multi-paragraph examples inside a YAML scalar makes the file hard to diff and brittle to wrap.
Keep thedescriptionto a short synopsis and move examples under an “## Examples” section after the front-matter.-description: Use this agent when you need to implement, complete, or work on ... +description: > + Implementation-focused agent that executes a single Task-Master sub-task. + +# Examples +<example>…</example>.claude/agents/task-checker.md (1)
1-6: Add missing H1 heading after the front-matter
MD041still fails; insert# Task Checkerright after the YAML block..claude/agents/task-orchestrator.md (3)
1-6: Top-level heading missingAdd
# Task Orchestratorbelow the front-matter to satisfy MD041 and improve rendering.
69-78: Fenced block needs language and blank-line padding-When deploying executors, provide them with: -``` +When deploying executors, provide them with: + +```text TASK ASSIGNMENT: ... -``` +``` +
22-28: Headings must be surrounded by blank lines (MD022)Insert a blank line before “### Initial Assessment Phase” and before the list that follows.
* feat: implement claude code agents * chore: add changeset - run format * feat: improve task-checker, executor, and orchestrator * chore: improve changeset
* feat: implement claude code agents * chore: add changeset - run format * feat: improve task-checker, executor, and orchestrator * chore: improve changeset
* feat: implement claude code agents * chore: add changeset - run format * feat: improve task-checker, executor, and orchestrator * chore: improve changeset
* feat: implement claude code agents * chore: add changeset - run format * feat: improve task-checker, executor, and orchestrator * chore: improve changeset
* feat: implement claude code agents * chore: add changeset - run format * feat: improve task-checker, executor, and orchestrator * chore: improve changeset
1 participant
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