@ripla/godd-mcp 1.0.1 → 1.0.2-canary.2

package/notes-app/src/components/IssueList.tsx

@@ -1,4 +1,4 @@
-import { useState, useEffect, useCallback } from "react";
+import { useState, useEffect, useRef } from "react";
 import {
   listIssuesApi,
   getErrorMessage,
@@ -18,24 +18,44 @@ export default function IssueList({ onSelect, selectedIssue }: IssueListProps) {
   const [loading, setLoading] = useState(true);
   const [error, setError] = useState<string | null>(null);
   const [stateFilter, setStateFilter] = useState<"open" | "closed">("open");
+  const [reloadKey, setReloadKey] = useState(0);
+  const requestSeq = useRef(0);
 
-  const loadIssues = useCallback((signal?: AbortSignal) => {
+  const requestReload = () => {
+    requestSeq.current += 1;
     setLoading(true);
     setError(null);
-    listIssuesApi({ state: stateFilter, per_page: 50, signal })
-      .then((data) => { setIssues(data.issues); })
-      .catch((e) => {
-        if (isAbortError(e)) return;
-        setError(getErrorMessage(e));
-      })
-      .finally(() => { setLoading(false); });
-  }, [stateFilter]);
+    setReloadKey((key) => key + 1);
+  };
+
+  const changeStateFilter = (nextState: "open" | "closed") => {
+    if (nextState === stateFilter) return;
+    requestSeq.current += 1;
+    setLoading(true);
+    setError(null);
+    setStateFilter(nextState);
+  };
 
   useEffect(() => {
     const ac = new AbortController();
-    loadIssues(ac.signal);
+    const requestId = requestSeq.current + 1;
+    requestSeq.current = requestId;
+    listIssuesApi({ state: stateFilter, per_page: 50, signal: ac.signal })
+      .then((data) => {
+        if (ac.signal.aborted || requestSeq.current !== requestId) return;
+        setIssues(data.issues);
+      })
+      .catch((e) => {
+        if (ac.signal.aborted || requestSeq.current !== requestId || isAbortError(e)) return;
+        setError(getErrorMessage(e));
+      })
+      .finally(() => {
+        if (!ac.signal.aborted && requestSeq.current === requestId) {
+          setLoading(false);
+        }
+      });
     return () => ac.abort();
-  }, [loadIssues]);
+  }, [stateFilter, reloadKey]);
 
   return (
     <div className="flex flex-col h-full">
@@ -44,7 +64,7 @@ export default function IssueList({ onSelect, selectedIssue }: IssueListProps) {
         <div className="flex-1 flex bg-gray-900 rounded border border-gray-600 overflow-hidden text-xs">
           <button
             type="button"
-            onClick={() => setStateFilter("open")}
+            onClick={() => changeStateFilter("open")}
             className={`flex-1 px-2 py-1 transition-colors ${
               stateFilter === "open"
                 ? "bg-green-700/30 text-green-300"
@@ -56,7 +76,7 @@ export default function IssueList({ onSelect, selectedIssue }: IssueListProps) {
           </button>
           <button
             type="button"
-            onClick={() => setStateFilter("closed")}
+            onClick={() => changeStateFilter("closed")}
             className={`flex-1 px-2 py-1 transition-colors ${
               stateFilter === "closed"
                 ? "bg-purple-700/30 text-purple-300"
@@ -69,7 +89,7 @@ export default function IssueList({ onSelect, selectedIssue }: IssueListProps) {
         </div>
         <button
           type="button"
-          onClick={() => loadIssues()}
+          onClick={requestReload}
           className="shrink-0 p-1 rounded text-gray-400 hover:text-gray-200 hover:bg-gray-700 transition-colors"
           title="更新"
         >
@@ -85,7 +105,7 @@ export default function IssueList({ onSelect, selectedIssue }: IssueListProps) {
           </div>
         )}
 
-        {error && <InlineError message={error} onRetry={loadIssues} />}
+        {error && <InlineError message={error} onRetry={requestReload} />}
 
         {!loading && !error && issues.length === 0 && (
           <p className="text-xs text-gray-500 text-center py-4">

package/notes-app/vitest.config.ts

@@ -7,6 +7,7 @@ export default defineConfig({
   test: {
     environment: "jsdom",
     globals: true,
+    include: ["src/**/*.{test,spec}.{ts,tsx}"],
   },
   resolve: {
     alias: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ripla/godd-mcp",
-  "version": "1.0.1",
+  "version": "1.0.2-canary.2",
   "type": "module",
   "description": "GoDD (Governance-orchestrated Driven Development) MCP Server - Encrypted prompt distribution via Model Context Protocol",
   "main": "dist/index.js",

package/templates/agents/architect.hbs

@@ -51,10 +51,10 @@ In particular, understand and strictly follow the principles, guidelines, and re
 - .instruction/01_specialties/planning.md
 - .instruction/01_specialties/design.md
 - .instruction/01_specialties/consultation.md
-- docs/009_spec/README.md
-- docs/009_spec/api-template.md
-- docs/009_spec/ui-template.md
-- docs/009_spec/db-template.md
+- docs/003_requirements/spec/README.md
+- docs/003_requirements/api.template.md
+- docs/003_requirements/ui.template.md
+- docs/003_requirements/db.template.md
 
 ## Expertise
 

package/templates/agents/auto-documenter.hbs

@@ -14,10 +14,10 @@
 
 # Role (SSOT)
 
-- **Specifications (Spec)**: `docs/009_spec/` (.md)
-- **Operational templates**: `docs/010_templates/` (.md)
-- **Configuration descriptions**: `docs/011_config/README.md` (descriptions for yaml/json)
-- **Tech stack**: `docs/008_guides/tech-stack.md`
+- **Specifications (Spec)**: `docs/003_requirements/spec/` (.md)
+- **Operational templates**: `docs/006_development_workflow/` (.md)
+- **Configuration descriptions**: `docs/007_guides/mcp.md` (descriptions for yaml/json)
+- **Tech stack**: `docs/007_guides/tech-stack.md`
 - **Rules/Entry**: `AGENTS.md` / `docs/README.md`
 
 ## When to Use (Auto-Activation)

package/templates/agents/backend-developer.hbs

@@ -51,9 +51,9 @@ Before starting work, read and understand the `AGENTS.md` at the project root an
 - .instruction/02_project/architecture.md
 - .instruction/02_project/domain.md
 - .instruction/02_project/patterns.md
-- docs/009_spec/README.md
-- docs/009_spec/api-template.md
-- docs/009_spec/db-template.md
+- docs/003_requirements/spec/README.md
+- docs/003_requirements/api.template.md
+- docs/003_requirements/db.template.md
 
 Reference implementation: `{{backend.root_dir}}/**`
 

package/templates/agents/code-reviewer.hbs

@@ -14,7 +14,7 @@
 
 ## Review Criteria (SSOT)
 
-- **Spec alignment**: Does implementation match `docs/009_spec/`?
+- **Spec alignment**: Does implementation match `docs/003_requirements/spec/`?
 - **Boundaries**:
   - Backend: {{backend.dependency_direction}}
   - Front: UI and side effects separated (into hooks/services)
@@ -26,4 +26,4 @@
 ## Output Format
 
 - Issues are presented with **severity (Blocker/Important/Nice)**, reason, and specific fix proposals as a set
-- If additional Spec/templates are needed, include proposals to add to `docs/009_spec` or `docs/010_templates`
+- If additional Spec/templates are needed, include proposals to add to `docs/003_requirements/spec` or `docs/006_development_workflow`

package/templates/agents/database-developer.hbs

@@ -34,9 +34,9 @@ Before starting work, read and understand the `AGENTS.md` at the project root an
 - .instruction/02_project/architecture.md
 - .instruction/02_project/domain.md
 - .instruction/02_project/patterns.md
-- docs/009_spec/README.md
-- docs/009_spec/db-template.md
-- docs/009_spec/error-codes-template.md
+- docs/003_requirements/spec/README.md
+- docs/003_requirements/db.template.md
+- docs/003_requirements/error-codes.template.md
 
 ## DB Change Policy
 
@@ -47,6 +47,6 @@ Before starting work, read and understand the `AGENTS.md` at the project root an
 
 ## Deliverables (Minimum)
 
-- **DB Spec**: Satisfies `docs/009_spec/db-template.md` (DDL diffs, compatibility, migration/rollback, indexes, application steps)
+- **DB Spec**: Satisfies `docs/003_requirements/db.template.md` (DDL diffs, compatibility, migration/rollback, indexes, application steps)
 - **Migration**: Alembic revision and application steps (both Docker and local)
 - **Impact scope**: Impact on existing APIs/features (especially search, list, aggregation)

package/templates/agents/debug-specialist.hbs

@@ -25,8 +25,8 @@ Don't "fix by guessing" — converge reliably in order: reproduce→hypothesize
 
 - AGENTS.md
 - .instruction/01_specialties/investigation-debug.md
-- docs/010_templates/impact-analysis-template.md
-- docs/010_templates/test-plan-template.md
+- docs/006_development_workflow/impact-analysis.template.md
+- docs/006_development_workflow/test-plan.template.md
 
 ## Investigation Report (Minimum Format)
 

package/templates/agents/environment-setup.hbs

@@ -30,7 +30,7 @@ Agent responsible for **environment setup, reproducibility, and onboarding** for
 ## What to Do
 
 - Maintain the preflight script as the canonical entry point
-- Update `docs/012_setup/` and `docs/011_config/`, making procedures SSOT
+- Update `docs/007_guides/` and `docs/007_guides/`, making procedures SSOT
 - Ensure external tools can be launched according to configuration file declarations
 
 ## Output Format

package/templates/agents/frontend-developer.hbs

@@ -30,11 +30,11 @@ Screens focus on rendering; side effects (fetching/saving/IPC) are delegated to
 - .instruction/00_universal/quality.md
 - .instruction/00_universal/communication.md
 - .instruction/02_project/tech-stack.md
-- docs/009_spec/README.md
-- docs/009_spec/ui-template.md
-- docs/009_spec/api-template.md
-- docs/010_templates/impact-analysis-template.md
-- docs/010_templates/test-plan-template.md
+- docs/003_requirements/spec/README.md
+- docs/003_requirements/ui.template.md
+- docs/003_requirements/api.template.md
+- docs/006_development_workflow/impact-analysis.template.md
+- docs/006_development_workflow/test-plan.template.md
 
 ## Implementation Guide (Frontend)
 

package/templates/agents/integration-qa.hbs

@@ -19,7 +19,7 @@
 
 ## Verification Template (Required)
 
-Based on `docs/010_templates/test-plan-template.md`, fill in at minimum:
+Based on `docs/006_development_workflow/test-plan.template.md`, fill in at minimum:
 - Target features/modules
 - Normal/Error/Boundary cases
 - Manual verification steps and expected results

package/templates/agents/pr-writer.hbs

@@ -35,7 +35,7 @@ Retrieve the following via **Git MCP / git commands** and build the body from fa
 ## Generation Rules (PR Optimization)
 
 - **Title**: ~50 chars, change subject/purpose is unambiguous
-- **Body**: Fully compliant with `docs/010_templates/pr-template.md`
+- **Body**: Fully compliant with `docs/006_development_workflow/pr.template.md`
 - **Changes**:
   - Write **"why"** (background/purpose) briefly before "what"
   - Change points in **bullet lists** at review-friendly granularity

package/templates/agents/quality-lead.hbs

@@ -14,9 +14,9 @@
 
 ## Quality Gate (Minimum)
 
-- **Spec**: Sufficient specifications exist in `docs/009_spec/` and match implementation
-- **Impact scope**: `docs/010_templates/impact-analysis-template.md` is filled
-- **Test plan**: `docs/010_templates/test-plan-template.md` is filled
+- **Spec**: Sufficient specifications exist in `docs/003_requirements/spec/` and match implementation
+- **Impact scope**: `docs/006_development_workflow/impact-analysis.template.md` is filled
+- **Test plan**: `docs/006_development_workflow/test-plan.template.md` is filled
 - **Compatibility/Migration**: If breaking changes exist, migration/rollback are documented
 {{#if frontend.build_command}}- **Frontend changes**: `{{frontend.build_command}}` passes{{/if}}
 

package/templates/agents/requirements-analyst.hbs

@@ -14,7 +14,7 @@
 
 ## Success Criteria
 
-- Purpose/completion criteria are measurably defined and distilled into **implementable-granularity Spec** (`docs/009_spec/`)
+- Purpose/completion criteria are measurably defined and distilled into **implementable-granularity Spec** (`docs/003_requirements/spec/`)
 - If breaking changes/migration/rollback are needed, decision-making materials are prepared upfront
 
 ## Output (Minimum)
@@ -23,4 +23,4 @@
 - Current understanding (assumptions)
 - Unclear points (questions)
 - Options (standard/conservative/bold) with recommendation
-- Draft based on `docs/009_spec/*-template.md` (API/UI/DB/Feature/Usecase)
+- Draft based on `docs/003_requirements/spec/*-template.md` (API/UI/DB/Feature/Usecase)

package/templates/agents/security-analyst.hbs

@@ -18,4 +18,4 @@
 - Authentication/Authorization (policy when needed)
 - Information leakage (logs/error messages/screen display)
 - External I/O (file/OS/network) failure behavior
-- Error code design (`docs/009_spec/error-codes-template.md`)
+- Error code design (`docs/003_requirements/error-codes.template.md`)

package/templates/agents/ssot-updater.hbs

@@ -15,7 +15,7 @@
 # Role
 
 This Agent's **sole responsibility is SSOT updates**.
-It receives the "latest Spec (input)" and updates `docs/009_spec/`.
+It receives the "latest Spec (input)" and updates `docs/003_requirements/spec/`.
 
 ## Input (Required)
 
@@ -25,7 +25,7 @@ It receives the "latest Spec (input)" and updates `docs/009_spec/`.
 
 ## Acceptance Criteria (MUST)
 
-- **Traceability (Spec→Implementation→Test)** is added/updated in `docs/009_spec/index.md`
+- **Traceability (Spec→Implementation→Test)** is added/updated in `docs/003_requirements/spec/index.md`
 - Added/updated links point to existing files (file paths exist)
 - If test commands don't exist/aren't ready, **document the fact** and alternative verification
 - If ambiguity remains in Spec (terminology/completion criteria/exceptions), formalize as questions
@@ -33,7 +33,7 @@ It receives the "latest Spec (input)" and updates `docs/009_spec/`.
 ## Work Procedure (Standard)
 
 1. Read input Spec, determine category (Feature/API/UI/Usecase/DB/Error)
-2. Append to relevant section in `docs/009_spec/index.md` (create if missing)
+2. Append to relevant section in `docs/003_requirements/spec/index.md` (create if missing)
 3. List referenced implementation files/test commands and verify existence
 4. Fill in Spec template's "Implementation Reference" and "Test Reference" (mark missing as TODO)
 5. Check for contradictions between added/updated Specs (same terminology/completion criteria)

package/templates/agents/technical-writer.hbs

@@ -18,11 +18,11 @@ Maintain the SSOT for Spec-Driven Development, preparing "implementable-granular
 
 ## References (SSOT)
 
-- Spec: `docs/009_spec/`
-- Templates: `docs/010_templates/`
+- Spec: `docs/003_requirements/spec/`
+- Templates: `docs/006_development_workflow/`
 - Core guidelines: `AGENTS.md`
 
 ## Deliverables
 
 - Spec additions/updates (API/UI/DB/Feature/Usecase/Error Codes)
-- Impact analysis/Test plans/ADR/PR/Release notes (`docs/010_templates` format)
+- Impact analysis/Test plans/ADR/PR/Release notes (`docs/006_development_workflow` format)

package/templates/agents/unit-test-engineer.hbs

@@ -16,4 +16,4 @@
 
 - Bug fixes follow **reproduction test → fix → re-run** as the standard
 - Cover at the appropriate nearby layer (Backend: Domain/Usecase, Front: hooks/pure functions)
-- For large changes, fix perspectives first using `docs/010_templates/test-plan-template.md`
+- For large changes, fix perspectives first using `docs/006_development_workflow/test-plan.template.md`

package/templates/prompts/agent-dev-workflow.hbs

@@ -24,7 +24,7 @@ Enable developers to complete the full cycle — from environment setup to imple
 - Humans review **only via GitHub PR diffs**
 
 ## Canonical References
-- Spec: `docs/009_spec/`
+- Spec: `docs/003_requirements/spec/`
 {{#if frontend}}- Frontend quality gate: `{{frontend.build_command}}`
 {{/if}}{{#if backend}}- Backend quality gate: `{{quality_gate.backend}}`
 {{/if}}

package/templates/prompts/docs-init.hbs

@@ -14,52 +14,49 @@ ripla Notes（テキストノート / テーブルノート / drawio）で閲覧
 
 ```
 docs/
-├── README.md                          # docs 全体の入口・構成説明
+├── README.md                              # docs 全体の入口・構成説明
 ├── 001_project/
-│   ├── README.md                      # プロジェクト概要（背景・目的・MVP・用語）
-│   ├── tasks.csv                      # タスク管理（テーブルノート）
-│   ├── features.csv                   # 機能要件一覧（テーブルノート）
-│   ├── screens.csv                    # 画面要件一覧（テーブルノート）
-│   └── template_README.md
+│   ├── README.md                          # プロジェクト概要（背景・目的・プロダクト・システム構成・用語）
+│   ├── pages.csv                          # 各プロダクトの画面一覧（テーブルノート）と各画面の概要
+│   ├── features.csv                       # 画面ごとの機能一覧（テーブルノート）と各機能の概要
+│   └── tasks.csv                          # 開発チームからの質問リストと要件定義チームからの要望一覧
 ├── 002_business_flow/
-│   ├── README.md                      # ビジネスフロー概要（Mermaid 含む）
-│   └── flow-overview.drawio
+│   ├── README.md                          # ビジネスフロー概要、フォルダ内で整理するビジネスフロー一覧
+│   ├── business_flow_name.template.md     # 特定業務のビジネスフローを解説
+│   └── business_flow_name.template.drawio # 特定業務のビジネスフローを図示
 ├── 003_requirements/
-│   ├── README.md                      # 要件概要
-│   ├── requirements-list.csv          # 要件一覧（テーブルノート）
-│   └── template_requirements.md
-├── 004_non_functional_requirements/
-│   ├── README.md
-│   └── nfr-list.csv
-├── 005_pages/
-│   ├── README.md
-│   ├── page-definitions.csv
-│   └── template_page.md
-├── 006_designs/
-│   ├── README.md
-│   ├── api/api.md
-│   ├── db/db.md
-│   ├── db/tables.csv
-│   ├── infra/infra.md
-│   └── features/README.md
-├── 007_development/
-│   ├── README.md
-│   ├── structure.md
-│   ├── workflow.md
-│   ├── stacks.md
-│   └── git.md
-├── 008_guides/
-│   ├── README.md                      # 運用・利用ガイド集
-│   └── guide-user.md                  # ユーザー向けガイド
-├── 009_spec/
-│   ├── README.md                      # 仕様 SSOT
-│   └── api-spec.md                    # API 仕様
-├── 010_templates/
-│   └── README.md                      # テンプレート集（影響分析/テスト計画/ADR 等）
-├── 011_config/
-│   └── README.md                      # 設定説明（環境変数・デプロイ設定等）
-└── 012_setup/
-    └── README.md                      # セットアップ・デプロイ手順
+│   ├── README.md                          # フォルダの説明、フォルダ内で整理するrequirements一覧
+│   ├── requirements.template.md           # 概要、背景、ユーザーストーリー、画面要件、機能要件、機能詳細、非機能要件、備考
+│   ├── <Product Name>/                    # 管理画面、ユーザー向け画面などプロダクトごとにフォルダ作成
+│   │   └── <feature_name>.md              # 機能別の要件定義
+│   └── spec/                              # 仕様 SSOT（API仕様、インフラ仕様、言語仕様等）
+├── 004_pages/                             # 画面設計
+│   ├── README.md                          # フォルダの説明
+│   └── app/                               # 画面のURLパスを整理するため、Reactの app/ ディレクトリを配置
+│       ├── admin/
+│       │   └── corporations/
+│       │       └── requirements.md        # 画面ごとの画面要件を記載
+│       └── users/
+├── 005_architecture/                      # 開発をするにあたっての実際の設計（インフラ、DB、API、各機能の設計）
+│   ├── README.md                          # フォルダの説明
+│   ├── stacks/                            # 技術スタック
+│   ├── api/                               # APIのSwaggerなど
+│   ├── db/                                # DB設計（ER図など）
+│   ├── infra/                             # インフラアーキテクチャの設計
+│   └── features/                          # 各機能の設計
+│       └── feature.template.md            # 機能設計書、データフロー、DB設計などを記載
+├── 006_development_workflow/              # 開発のルールやワークフローなどについて
+│   ├── README.md                          # フォルダの説明
+│   ├── git.md                             # Gitルール
+│   └── workflow.md                        # 開発ワークフロー
+└── 007_guides/                            # ガイド集
+    ├── README.md                          # フォルダの説明
+    ├── godd_notes_usage.md                # GoDD Notesの利用方法
+    ├── godd_usage.md                      # GoDD のコマンド一覧、ツール一覧、利用方法
+    ├── setup_godd.md                      # GoDD の始め方
+    ├── setup_godd_notes.md                # GoDD Notesの構築方法
+    ├── setup_infra.md                     # インフラのCI/CDの構築ガイド
+    └── setup_local_environment.md         # ローカル環境構築ガイド
 ```
 
 ## ルール
@@ -82,26 +79,11 @@ id,type,product,category,subject,detail,created_by,created_at,priority,deadline,
 機能ID,機能名,概要,phase,優先度,ステータス
 ```
 
-### screens.csv
+### pages.csv
 ```
 画面ID,画面名,概要,提供フェーズ,関連機能ID,ステータス
 ```
 
-### requirements-list.csv
-```
-要件ID,要件名,概要,優先度,ステータス
-```
-
-### nfr-list.csv
-```
-NFR-ID,カテゴリ,要件,基準,優先度
-```
-
-### page-definitions.csv
-```
-画面ID,画面名,URL,認証要否,概要
-```
-
 ### tables.csv
 ```
 テーブル名,カラム名,型,制約,説明

package/templates/prompts/docs-update.hbs

@@ -15,10 +15,10 @@ docs/
 ├── 001_project/     # プロジェクト概要、機能要件、画面要件
 ├── 002_business_flow/ # ビジネスフロー
 ├── 003_requirements/  # 要件定義
-├── 004_non_functional_requirements/ # 非機能要件
-├── 005_pages/        # 画面設計
-├── 006_designs/      # 詳細設計（API/DB/機能別）
-└── 007_development/  # 設計思想・アーキテクチャ & 開発ガイド
+├── 004_pages/        # 画面設計
+├── 005_architecture/ # 詳細設計（インフラ/DB/API/機能別）
+├── 006_development_workflow/ # 開発ルール・ワークフロー
+└── 007_guides/       # 利用・構築・運用ガイド
 ```
 
 ## ルール
@@ -35,12 +35,12 @@ docs/
 | コード変更種別 | 影響するセクション |
 |---|---|
 | 新機能追加 | 001 (features.csv), 003 (requirements), 006 (features/) |
-| API 変更 | 006 (api/), 003 (requirements) |
-| DB スキーマ変更 | 006 (db/) |
-| 画面追加/変更 | 001 (screens.csv), 005 (pages/) |
-| インフラ変更 | 007 (infra.md) |
-| アーキテクチャ変更 | 007 (architecture.md) |
-| 開発フロー変更 | 007 (workflow.md, git.md) |
+| API 変更 | 005 (api/), 003 (requirements) |
+| DB スキーマ変更 | 005 (db/) |
+| 画面追加/変更 | 001 (pages.csv), 004 (app/) |
+| インフラ変更 | 005 (infra/) |
+| アーキテクチャ変更 | 005 (architecture.md) |
+| 開発フロー変更 | 006 (workflow.md, git.md) |
 | ビジネスフロー変更 | 002 (business_flow/) |
 
 ## 出力

package/templates/prompts/notes-deploy.hbs

@@ -23,7 +23,7 @@ notes-app (React + Vite)  ──proxy──▶  notes-api (FastAPI)  ──▶
 | ローカルで試す / 開発環境 | `godd notes compose --auto` |
 | 設定をカスタマイズしたい | `godd notes compose --config <path>` |
 | AWS にデプロイ | `godd notes deploy -y` |
-| インフラを新規構築 | `godd notes infra` |
+| インフラとアプリ雛形を新規構築 | `godd notes infra` |
 
 ### A. ローカルデプロイ（最も簡単）
 
@@ -79,6 +79,7 @@ godd notes compose --config notes-config.json
 **前提**: 
 - AWS CLI でログイン済み（`aws sts get-caller-identity` が成功すること）
 - `godd notes infra` でインフラ構築済み
+- `notes-api/` と `notes-app/` がデプロイ対象ルートに存在すること
 - `.godd-notes-infra.json` が存在すること
 
 ```bash

package/templates/prompts/pr-create.hbs

@@ -11,7 +11,7 @@
 {{> project-context }}
 
 ## Purpose
-Create a **Pull Request** on GitHub with a well-structured body following the PR template (`docs/010_templates/pr-template.md`). The Agent analyzes changes, generates PR content, and creates the PR.
+Create a **Pull Request** on GitHub with a well-structured body following the PR template (`docs/006_development_workflow/pr.template.md`). The Agent analyzes changes, generates PR content, and creates the PR.
 
 ## Auto-confirm Mode
 {{#if auto_confirm}}
@@ -27,7 +27,7 @@ Create a **Pull Request** on GitHub with a well-structured body following the PR
 **draft is DISABLED (default)** — Create the PR as a regular (ready for review) PR.
 {{/if}}
 
-## PR Template (SSOT: `docs/010_templates/pr-template.md`)
+## PR Template (SSOT: `docs/006_development_workflow/pr.template.md`)
 The PR body MUST follow this structure:
 
 ### TL;DR (3-7 lines)

package/templates/prompts/push-execute.hbs

@@ -32,7 +32,7 @@ Execute **pre-submission checks** and then **push to remote** (`git push`). The
    - **If no unpushed commits**: Report "No commits to push" and exit
 
 ### Step 2: Pre-submission Checks (Quality Gate)
-1. **Spec reflection**: Check if `docs/009_spec/` needs updates for the changes
+1. **Spec reflection**: Check if `docs/003_requirements/spec/` needs updates for the changes
 2. **Quality gate**: Run the project's quality gate commands:
    - If available: `pnpm quality-gate` (or equivalent from project config)
    - Fallback: lint + typecheck + test for changed areas
@@ -47,7 +47,7 @@ Execute **pre-submission checks** and then **push to remote** (`git push`). The
    ```
    Pre-submission Check Results:
    ✅ Quality gate: Passed
-   ✅ Spec reflection: No updates needed (or: Updated docs/009_spec/xxx.md)
+   ✅ Spec reflection: No updates needed (or: Updated docs/003_requirements/spec/xxx.md)
    ✅ Secret check: No secrets detected
    ✅ Breaking changes: None (or: Migration documented)
    

package/templates/prompts/push.hbs

@@ -15,7 +15,7 @@ Organize everything that needs to be done before push/submission — ensuring no
 
 ## Output (Checklist)
 - Local verification (required commands/results)
-- Spec (`docs/009_spec`) reflection status
+- Spec (`docs/003_requirements/spec`) reflection status
 - Template (impact analysis/test plan/PR body) creation status
 - Documentation of breaking changes/migration/rollback
 - Secret information leakage check (logs/config/screenshots/etc.)

package/templates/prompts/requirements-to-business-flow.hbs

@@ -26,4 +26,4 @@ Transform requirements (natural language) into business flows (As-Is / To-Be) an
 
 ### Spec Mapping
 - List the required Spec templates (UI/API/DB/Feature/Usecase/Error Codes) and recommend which to create
-- Specs are placed under `docs/009_spec/`
+- Specs are placed under `docs/003_requirements/spec/`

package/templates/prompts/specification-to-tickets.hbs

@@ -11,7 +11,7 @@
 {{> project-context }}
 
 ## Purpose
-Transform Specs (`docs/009_spec/`) into an implementable task list.
+Transform Specs (`docs/003_requirements/spec/`) into an implementable task list.
 
 ## Input
 - Target Spec (API/UI/DB/Feature/Usecase/Error Codes)

package/templates/prompts/submit.hbs

@@ -43,7 +43,7 @@ Execute the **complete submission workflow**: pre-submission checks → git push
    - If remote branch does not exist yet, run `git log --oneline -10` instead
 3. Execute pre-submission checks:
    - **Quality gate**: Run project's quality gate commands
-   - **Spec reflection**: Check if `docs/009_spec/` needs updates
+   - **Spec reflection**: Check if `docs/003_requirements/spec/` needs updates
    - **Secret check**: Scan for potential secrets in committed content
    - **Breaking changes**: Verify migration docs if breaking changes exist
 4. Present check results
@@ -78,7 +78,7 @@ Execute the **complete submission workflow**: pre-submission checks → git push
    - `git diff origin/<base>...HEAD --stat` for change summary
 2. Generate PR content:
    - **Title**: Use user-provided title, or derive from branch name and changes
-   - **Body**: Follow PR template (`docs/010_templates/pr-template.md`) — fill ALL sections
+   - **Body**: Follow PR template (`docs/006_development_workflow/pr.template.md`) — fill ALL sections
 3. Present PR title and body for review
 
 {{#if auto_confirm}}

package/templates/prompts/sync.hbs

@@ -42,7 +42,7 @@ Sync the current working branch with the latest changes from the default branch
 1. List conflicted files with `git diff --name-only --diff-filter=U`
 2. Read each conflicted file and identify conflict markers (`<<<<<<<` / `=======` / `>>>>>>>`)
 3. **Resolution policy (priority order)**:
-   1. **Keep the SSOT-compliant side**: If one side adheres to SSOT (`docs/009_spec/`, `.github/agents/user-clone.agent.md`, etc.) and the other diverges, **adopt the compliant side**
+   1. **Keep the SSOT-compliant side**: If one side adheres to SSOT (`docs/003_requirements/spec/`, `.github/agents/user-clone.agent.md`, etc.) and the other diverges, **adopt the compliant side**
    2. **Both SSOT-compliant and integrable**: If both sides comply with SSOT and can be functionally integrated, **integrate both**
    3. **Both compliant but integration difficult / uncertain**: If safe integration is not possible, **ask the user** (never guess)
 4. After resolving all conflicts: