# Questions & Answers

## Q1: For F1: What configuration file format do you prefer? Options: (a) k4000.toml - TOML format, common in Rust projects, (b) k4000.json - JSON format, universal but less readable, (c) .k4000 - dotfile with custom format. I recommend k4000.toml to match the Cargo.toml convention.
**Category:** clarification
**Answer:** Use TOML format, saved at tasks/.config/config.toml

## Q2: For F2: Should the default be 'auto' (agent proceeds automatically - current behavior) or 'manual' (always wait for approval)? I recommend 'auto' for backward compatibility.
**Category:** clarification
**Answer:** Default to 'manual' - require approval by default, projects can opt-in to autonomous mode

## Q3: For F4/F5: In manual mode, how should the agent wait for approval? Options: (a) Agent calls approve_next_feature tool after user confirms in chat, (b) User runs a CLI command like 'k4000 approve', (c) Agent just pauses and asks user 'Shall I continue?' in chat (no new tool needed). I recommend option (c) as simplest - the response from mark_feature_verified tells agent to pause and ask.
**Category:** clarification
**Answer:** Option (c) - Agent pauses and asks user in chat. No new tool needed, just modify the response from mark_feature_verified to instruct the agent to pause and ask for confirmation.

## Q4: Should there be a way to override the project setting for a specific task? For example, a project set to 'auto' but one critical task needs manual approval per feature.
**Category:** missing_requirement
**Answer:** Yes, allow task-level override but only via human approval. Add a setting in the task that can override the project setting.

## Q5: For F1: Should the config file support other future settings beyond feature approval mode? If yes, I'll design a more extensible schema. Examples might include: max_review_iterations, default_agent_name, auto_commit settings.
**Category:** clarification
**Answer:** Yes, design for extensibility but only implement feature_approval_mode for now. Other settings can be added later.

## Q6: Should the feature approval mode be displayed in the list_project_tasks output so users can quickly see which mode each project uses?
**Category:** edge_case
**Answer:** Yes, show the approval mode in list_project_tasks output so users can quickly see the mode.
