34df2c8bbd
This commit implements automatic tasks.json file creation when it doesn't exist:
- When tasks.json is missing or invalid, create a new one with { tasks: [] }
- Allows adding tasks immediately after initializing a project without parsing a PRD
- Replaces error with informative feedback about file creation
- Enables smoother workflow for new projects or directories
This change improves user experience by removing the requirement to parse a PRD
before adding the first task to a newly initialized project. Closes #494
26 lines
1.3 KiB
Plaintext
26 lines
1.3 KiB
Plaintext
# Task ID: 68
|
|
# Title: Ability to create tasks without parsing PRD
|
|
# Status: done
|
|
# Dependencies: None
|
|
# Priority: medium
|
|
# Description: Which just means that when we create a task, if there's no tasks.json, we should create it calling the same function that is done by parse-prd. this lets taskmaster be used without a prd as a starding point.
|
|
# Details:
|
|
|
|
|
|
# Test Strategy:
|
|
|
|
|
|
# Subtasks:
|
|
## 1. Design task creation form without PRD [done]
|
|
### Dependencies: None
|
|
### Description: Create a user interface form that allows users to manually input task details without requiring a PRD document
|
|
### Details:
|
|
Design a form with fields for task title, description, priority, assignee, due date, and other relevant task attributes. Include validation to ensure required fields are completed. The form should be intuitive and provide clear guidance on how to create a task manually.
|
|
|
|
## 2. Implement task saving functionality [done]
|
|
### Dependencies: 68.1
|
|
### Description: Develop the backend functionality to save manually created tasks to the database
|
|
### Details:
|
|
Create API endpoints to handle task creation requests from the frontend. Implement data validation, error handling, and confirmation messages. Ensure the saved tasks appear in the task list view and can be edited or deleted like PRD-parsed tasks.
|
|
|