# Questions & Answers

## Q1: Should this be documentation-only (updating CLAUDE.md) or should we also add programmatic validation in save_features to warn about oversized features?
**Category:** other
**Answer:** Programmatic validation - add code to enforce this, not just documentation.

## Q2: For F3: If we add validation, what heuristics should trigger a warning? Options: (a) description length > N characters, (b) presence of words like 'entire', 'all', 'complete', (c) LLM-based analysis during save, (d) just rely on documentation/agent behavior
**Category:** other
**Answer:** LLM-based analysis during save - the agent should analyze each feature's complexity.

## Q3: Should the validation be a hard block (reject oversized features) or a soft warning (allow but warn)?
**Category:** other
**Answer:** Hard block - reject oversized features. Only the human can override it in the agent (not programmatically bypassed).

## Q4: Where in CLAUDE.md should this guidance appear? Options: (a) New top-level section, (b) Under 'Phase 1.5: Feature List', (c) Under 'Phase 1: Task Definition', (d) Multiple locations
**Category:** other
**Answer:** New top-level section in CLAUDE.md, BUT also include in plan.md template so projects without CLAUDE.md still follow it.

## Q5: Should the plan.md template include a mandatory checklist item for 'Feature size verified' before implementation?
**Category:** other
**Answer:** Yes - include mandatory checklist item AND include the description/guidelines in plan.md so it can be followed even without CLAUDE.md.

## Q6: For the '2-3 sentence' rule - should this be applied to individual features or to the overall task description?
**Category:** clarification
**Answer:** The 2-3 sentence rule applies to individual features, not the overall task.
