---
name: review-concept
description: Review the CONCEPT.md document's contents using a structured 3-tier severity checklist.
argument-hint: "Relative path of the concept document to review (default: docs/CONCEPT.md)"
---

Read and review the contents of the target CONCEPT.md document in the workspace using a structured checklist with three severity levels (問題, 要確認, 提案).

## Review Checklist

### 1. 問題 (Issue/Problem - High Severity)

*Critical errors, logic flaws, or gaps that must be corrected.*

*   **構成要素の不足 (Missing Core Sections)**: Check if required sections are present: "概要", "対象ユーザー・背景", "機能", and "動作環境".
*   **矛盾・論理の破綻 (Contradictions & Logic Flaws)**: Internal contradictions between the project overview and main functions.
*   **参照・リンク切れ (Broken Links & References)**: References to non-existent files or directories (e.g., outputs REQUIREMENTS.md).
*   **事実誤認 (Factual Errors)**: Inaccurate technical environment specs or wrong target user descriptions.

### 2. 要確認 (Needs Confirmation/Clarification - Medium Severity)

*Items that require clarification or validation.*

*   **前提条件の妥当性 (Unstated / Ambiguous Assumptions)**: Ambiguous assumptions regarding target operating environments (OS, browser, node version, etc.) or user contexts.
*   **用語の不整合・定義不足 (Inconsistent / Undefined Terminology)**: Inconsistent names for core features or undefined domain-specific terms.
*   **技術的実現性・リスク (Feasibility & Risks)**: Outlined core functions that may have significant technical hurdles or unmitigated risks.

### 3. 提案 (Suggestion/Recommendation - Low Severity)

*Constructive ideas to improve clarity, aesthetics, or user experience.*

*   **可読性・明瞭性の向上 (Readability & Clarity)**: Suggestions to use tables or bullet lists for list of features or target environments.
*   **体裁・構成の改善 (Visual & Formatting Enhancements)**: Use of diagrams (e.g., Mermaid) for visual flow or better Markdown styling.

---

## Execution Flow

1. **Locate Target File**:
   *   If a file path is provided as an argument, use it as the target.
   *   If no argument is provided, default to `docs/CONCEPT.md`.
2. **Read Content**:
   *   Read the file content.
3. **Conduct Review**:
   *   Analyze the document line-by-line or section-by-section against the checklist.
4. **Save Report to File**:
   *   Save the formatted review report to `.review/[relative-path-to-target-document]` relative to the project root (e.g., `.review/docs/CONCEPT.md`).
   *   Ensure the directories inside `.review/` are created automatically if they do not exist.
   *   If the report file already exists, overwrite it with the new review content.
5. **Output Report**:
   *   Present the structured review report in the chat and notify the user of the path to the saved file.

---

## Output Report Format

Output the review report using the following structure:

```markdown
# Document Review Report: [file basename]

Review of: `[relative/path/to/file]`

## Executive Summary

| Severity | Count | Key Focus |
| --- | --- | --- |
| 🔴 問題 (High) | 0 | Critical issues requiring immediate correction |
| 🟡 要確認 (Medium) | 0 | Items requiring user confirmation or alignment |
| 🟢 提案 (Low) | 0 | Suggestions for readability and quality |

---

## Detailed Findings

### 🔴 問題 (High Severity)
*List critical issues.*

- **[Short Summary of Issue]**
  - **Location**: Line X-Y / Section name
  - **Original Text**: `[original text]`
  - **Description**: [Why it is a problem]
  - **Recommended Action**: [Specific, actionable fix]

### 🟡 要確認 (Medium Severity)
*List items needing confirmation.*

- **[Short Summary]**
  - **Location**: Line X-Y / Section name
  - **Original Text**: `[original text]`
  - **Description**: [What needs confirmation and why]
  - **Recommended Action**: [Specific clarification questions or options]

### 🟢 提案 (Low Severity)
*List suggestions.*

- **[Short Summary]**
  - **Location**: Line X-Y / Section name
  - **Original Text**: `[original text]`
  - **Description**: [How it could be improved]
  - **Recommended Action**: [Concrete suggested text or structure]
```
