# Feature Approval Workflow Setting

## Overview

Add a project-based setting that controls whether the coding agent can automatically continue to the next feature in a task, or must wait for manual approval after completing each feature.

## Problem Statement

Different projects have different review requirements:
- **Some projects** need human review after each feature is completed before proceeding to the next one (more controlled, careful workflow)
- **Other projects** are fine with autonomous operation where the agent completes all features without waiting for approval between them (faster, more efficient)

Currently there's no way to configure this behavior per-project.

## Requirements

### Core Functionality
1. Add a project-level configuration setting to control feature approval workflow
2. Two modes should be supported:
   - `manual` - Agent must wait for human approval after completing each feature before starting the next
   - `auto` - Agent can proceed to the next feature automatically after completing one

### Configuration
- Setting should be stored at the project level (not per-task)
- Should have a sensible default (probably `auto` for backward compatibility)
- Configuration location TBD (could be in a project config file, environment variable, or k4000 config)

### Behavior Changes
- When `manual` mode is active:
  - After calling `mark_feature_verified`, the agent should pause and notify the user
  - Agent should wait for explicit approval before starting the next feature
  - Clear indication to user that approval is needed
  
- When `auto` mode is active:
  - Current behavior - agent proceeds through features without waiting

### User Experience
- Easy to configure per project
- Clear feedback about which mode is active
- Simple way to give approval when in manual mode

## Open Questions
- Where should this setting be stored? (project config file, environment variable, k4000-specific config)
- Should there be a way to override the project setting for a specific task?
- What should the approval mechanism look like in manual mode?
- Should this integrate with the existing review workflow or be separate?