# Questions & Answers

## Q1: Should features be stored in a separate `feature-list.md` file (as mentioned in task.md), or integrated into `plan.md` alongside the implementation tasks?
**Category:** clarification
**Answer:** Use a separate `feature-list.md` file

## Q2: Should feature extraction happen automatically during `analyze_task`, or should there be a separate `save_features` tool that Claude calls after analysis (similar to how `save_questions` works)?
**Category:** clarification
**Answer:** Automatically during `analyze_task`, but still ask clarifying questions if needed

## Q3: Should features have additional metadata beyond id, description, and completed status? For example: priority, complexity estimate, dependencies on other features?
**Category:** missing_requirement
**Answer:** Yes, include additional metadata if needed (priority, complexity, dependencies)

## Q4: How should feature completion be tracked? Should `set_task_status` automatically mark features complete, or should there be a separate `mark_feature_complete` tool?
**Category:** clarification
**Answer:** Via a `mark_feature_complete` tool

## Q5: Should the feature list influence question generation? For example, generating questions per-feature to ensure each feature is well-defined?
**Category:** integration
**Answer:** Yes, feature list should influence question generation

## Q6: Should there be validation that all features are marked complete before allowing task status to be set to 'done'?
**Category:** edge_case
**Answer:** Yes, validate all features are complete before allowing status = 'done'
