atlas-mcp-server
by cyanheads
Verified
create_task
Create a new task in the hierarchical task system.
Core Task Properties:
- Path: Hierarchical identifier (e.g., "project/backend/auth")
- Max length: 1000 chars
- Max depth: 10 levels
- Allowed chars: alphanumeric, hyphen, underscore, forward slash
- Forward slashes indicate hierarchy levels
- Name: Clear, action-oriented task title
- Max length: 200 chars
- Should describe concrete objective
- Description: Detailed task explanation
- Max length: 2000 chars
- Include context, requirements, success criteria
- Type: TASK or MILESTONE
- TASK: Concrete work item with specific deliverable
- MILESTONE: Organizational container for related tasks
Validation & Dependencies:
- Dependencies: Tasks that must complete first
- Max dependencies: 50 tasks
- Tasks blocked until dependencies met
- Circular dependencies prevented
- Parent-Child Rules:
- Parent task must exist if parentPath specified
- Child tasks inherit certain parent properties
- Parent status affects child task constraints
- Proper task hierarchy maintained
Notes & Documentation: Each category limited to 100 notes, 1000 chars per note
- Planning Notes: Initial task preparation
- Progress Notes: Implementation updates
- Completion Notes: Final outcomes
- Troubleshooting Notes: Issue resolution
Metadata Categories:
- Core Fields:
- Priority: low/medium/high
- Tags: Keywords for categorization (max 100)
- Reasoning: Decision rationale (max 2000 chars)
- Technical Details:
- Language & Framework
- Dependencies (max 50)
- Environment specifications
- Validation & Progress:
- Acceptance criteria (max 20)
- Test cases (max 20)
- Progress percentage (0-100)
- Milestone tracking
- Timestamps
- Resource Tracking:
- Tools used (max 100)
- Resources accessed (max 100)
- Context references (max 100)
- Status Information:
- Block tracking
- Resolution details
- Timestamps
- Version Control:
- Version numbers
- Branch information
- Commit references
- Version history (max 10)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| completionNotes | No | Task completion notes. Max 100 notes, each max 1000 chars. | |
| dependencies | No | Paths of tasks that must be completed first. Tasks will be blocked until dependencies are met. | |
| description | No | Detailed explanation including context, requirements, and success criteria. Max length 2000 chars. | |
| metadata | No | Task metadata with structured validation: 1. Core Fields: - priority: Task urgency (low/medium/high) - tags: Keywords for categorization (max 100 tags, each max 100 chars) - reasoning: Document decision rationale (max 2000 chars) 2. Technical Details: technicalRequirements: { - language: Programming language used - framework: Framework/libraries used - dependencies: Array of required dependencies (max 50) - environment: Runtime environment details - performance: Resource requirements } 3. Validation & Progress: acceptanceCriteria: { - criteria: Success validation points (max 20, each max 500 chars) - testCases: Test scenarios (max 20, each max 500 chars) - reviewers: Required reviewers list (max 10) } progress: { - percentage: Task completion (0-100) - milestones: Key progress points (max 20) - lastUpdated: Last status update timestamp - estimatedCompletion: Target completion timestamp } 4. Resource Tracking: resources: { - toolsUsed: Tools/utilities used (max 100) - resourcesAccessed: Data/systems accessed (max 100) - contextUsed: Related information (max 100, each max 1000 chars) } 5. Status Information: blockInfo: { - blockedBy: Task causing the block - blockReason: Block description (max 500 chars) - blockTimestamp: When block occurred - unblockTimestamp: When block was resolved - resolution: How block was resolved (max 500 chars) } 6. Version Control: versionControl: { - version: Current version number - branch: Active branch name - commit: Latest commit hash - previousVersions: Version history (max 10) } 7. Custom Fields: customFields: Record of additional string fields for extensibility | |
| name | Yes | Clear, action-oriented name describing the task objective. Max length 200 chars. | |
| parentPath | No | Path of parent task. Use for organizing subtasks under a milestone. | |
| path | Yes | Hierarchical path (e.g., "project/backend/auth"). Max length 1000 chars, max depth 10 levels. Must be alphanumeric with -_/ characters. Use forward slashes to indicate task hierarchy. | |
| planningNotes | No | Initial planning notes for the task. Max 100 notes, each max 1000 chars. | |
| progressNotes | No | Progress tracking notes. Max 100 notes, each max 1000 chars. | |
| troubleshootingNotes | No | Notes about issues and their resolution. Max 100 notes, each max 1000 chars. | |
| type | No | TASK for concrete work items, MILESTONE for organizing related tasks. | TASK |