# concept.md — {{project_name}}

This document defines why the `{{project_name}}` project exists. 
- **Problem space**: problem statement, why, pain points, target users, value criteria
- **Solution space**: solution statement, goals, scope, constraints
- **Value mapping**: Pain point to solution mapping

For requirements and behavior (what), see [`features.md`](features.md). For implementation details (how), see [`tech-spec.md`](tech-spec.md). For a breakdown of the implementation plan (step-by-step tasks), see [`stories.md`](stories.md). For project-specific must-know facts (workflow rules, hidden coupling, tool-wrapper conventions that the LLM would otherwise random-walk on), see [`project-essentials.md`](project-essentials.md). For the workflow steps tailored to the current mode (cycle steps, approval gates, conventions), see [`docs/project-guide/go.md`](../project-guide/go.md) — re-read it whenever the mode changes or after context compaction.

## Problem Space
 
### Problem Statement
{{problem_statement}}

**Why this problem exists:**
{{problem_why}}

### Pain Points
{{pain_points}}

## Solution Space
`{{project_module_name}}` is a {{programming_language}} project to {{one_liner}}. 

### Solution Statement
{{solution_statement}}

### Goals
{{goals}}

### Scope
{{scope}}

### Constraints
{{constraints}}

## Value Mapping
{{pain_point_to_solution_mapping}}
