# Questions & Answers

## Q1: What slugification rules should be used? (e.g., lowercase only, replace spaces with hyphens, remove special characters, max length?)
**Category:** other
**Answer:** Lowercase only, replace spaces with hyphens, remove special characters, max length 40 characters.

## Q2: Should the tool check if a task with the same name already exists? If so, what behavior - error, overwrite, or generate unique name?
**Category:** other
**Answer:** Yes, check if task exists and return an error if it does.

## Q3: Should the task.md file have any specific format/template (e.g., frontmatter, headers) or just contain the raw description?
**Category:** other
**Answer:** Raw description only, no template or frontmatter.

## Q4: Should the tool automatically set an initial status (e.g., 'draft') in the state, or leave the task completely untracked until explicitly analyzed?
**Category:** integration
**Answer:** Yes, set initial status to 'draft'. VERY IMPORTANT: Always prompt the user immediately after creation asking if they want to begin analyzing the task.

## Q5: Should the project_path be required or default to current working directory?
**Category:** other
**Answer:** Follow the rest of this MCP - ALWAYS work in the project's ./tasks folder. No project_path parameter needed, always use current working directory.
