AIで既存アプリをリバースエンジニアリングする実験：Model Weaveで設計地図を作ってみた

Proceed with one-shot Model Weave reverse engineering for NaviMovie-Maker.

Goal:
Generate a first-pass Model Weave model set for NaviMovie-Maker from the provided source code and provided Model Weave documentation only.

This is an experiment to evaluate whether an AI with no prior project knowledge can visualize a small application using only:
- target application source code
- target application README / release docs
- Model Weave format documentation
- Model Weave dogfood guidance notes
- this prompt

Do not use previous chat context.
Do not use external knowledge.
Do not use web search.
Do not infer product intent beyond the source, README, release docs, and provided documentation.

Workspace root:
navimovie-maker-reverse-root

Actual workspace structure:
navimovie-maker-reverse-root/
├─docs/
│  └─docs/
│      ├─99_notes/
│      └─formats/
└─navimovie-maker/
    ├─NaviMovieMaker.App/
    │  ├─Assets/
    │  ├─Models/
    │  └─Services/
    └─release-docs/

Target application source:
- navimovie-maker/
- navimovie-maker/NaviMovieMaker.App/
- navimovie-maker/release-docs/

Model Weave documentation and guidance:
- docs/docs/formats/
- docs/docs/99_notes/

Allowed information sources:
- navimovie-maker/**
- docs/docs/formats/**
- docs/docs/99_notes/**
- this prompt

Strictly forbidden:
- Do not use web search.
- Do not run git commands.
- Do not create commits.
- Do not push.
- Do not edit NaviMovie-Maker source code.
- Do not edit files under docs/.
- Do not edit README or release docs.
- Do not modify build outputs.
- Do not create temporary helper scripts or scratch files.
- Do not run destructive commands.
- Do not invent behavior not supported by source, README, or release docs.
- Do not model future/planned behavior unless it is explicitly described in source, README, or release docs.
- Do not create generated Model Weave files inside navimovie-maker/.
- Do not create generated Model Weave files inside docs/.

Allowed actions:
- Read files.
- List directories.
- Search source code with grep/rg or equivalent.
- Create directories and files only under model/.

Before generating any model files:
1. Locate the target application source under navimovie-maker/.
2. Locate Model Weave format docs under docs/docs/formats/.
3. Locate dogfood guidance notes under docs/docs/99_notes/.
4. Read and follow the required guide files if present:
   - docs/docs/99_notes/GUIDE-MW-AI-GENERATION-RULES.md
   - docs/docs/99_notes/GUIDE-MW-FRONTMATTER-SAFE-WIKILINK.md
   - docs/docs/99_notes/GUIDE-MW-MARKDOWN-TABLE-SAFE-CELL.md
   - docs/docs/99_notes/REPORT-MW-SOURCE-DRIVEN-DOGFOOD-FINDINGS.md
   - docs/docs/99_notes/STATUS-MW-IMPLEMENTATION-COVERAGE.md
5. Read the current format documents before creating model files:
   - docs/docs/formats/FORMAT-dfd_diagram.md
   - docs/docs/formats/FORMAT-dfd_object.md
   - docs/docs/formats/FORMAT-data_object.md
   - docs/docs/formats/FORMAT-app_process.md
   - docs/docs/formats/FORMAT-screen.md
6. Do not assume table schemas from memory. Use the provided format docs.

Output directory:
Create all generated Model Weave files under:
model/

Use this structure:
model/
  01_dfd/
    diagrams/
    objects/
  03_data/
  04_process/
  09_screen/
  99_notes/

Language rules:
- User-facing model prose must be Japanese.
- Source symbols, class names, method names, file paths, and model IDs may remain English.
- Keep explanations concise.
- Prefer source-backed facts over speculation.

Markdown table safety rules:
- Follow GUIDE-MW-MARKDOWN-TABLE-SAFE-CELL.md.
- Keep table cells short.
- Do not use C# / TypeScript array notation such as Foo[] or Array<Foo> in tables.
- Use Foo list or list of Foo instead.
- Do not use Wikilink aliases such as [[target|label]] inside tables.
- Avoid raw pipe characters inside table cells.
- Put long explanations in ## Notes instead of table cells.
- Do not leave empty placeholder rows.

Frontmatter / Wikilink rules:
- Follow GUIDE-MW-FRONTMATTER-SAFE-WIKILINK.md.
- Avoid Wikilinks in frontmatter unless the format explicitly supports them safely.
- Prefer plain IDs in frontmatter fields.
- Use Wikilinks in body tables only where Model Weave format examples support them.

Model ID rules:
- Use prefix NMM for NaviMovie-Maker.
- Use stable IDs.
- Do not use spaces in IDs.

Examples:
- DFD-NMM-CORE-L0
- DFD-NMM-OBJ-UI
- DFD-NMM-OBJ-CONVERSION
- DATA-NMM-CONVERSION-JOB
- PROC-NMM-CONVERT-LOCAL-FILE
- SCR-NMM-MAIN-WINDOW

Reverse engineering scope:
Process the whole small application in one pass.

Inspect at minimum:
- navimovie-maker/README.md if present
- navimovie-maker/release-docs/**
- project files such as .csproj
- WPF XAML files
- ViewModels if present
- Models
- Services
- Settings / configuration code
- queue / job handling code
- download logic
- conversion logic
- preset logic
- external tool integration
- ffmpeg / yt-dlp integration if present

Ignore:
- .git/
- bin/
- obj/
- generated build outputs
- IDE metadata
- package/cache directories

Required generated models:

1. Core DFD

Create:
model/01_dfd/diagrams/DFD-NMM-CORE-L0.md

Purpose:
Represent the main runtime boundaries and data flows of NaviMovie-Maker.

Include boundaries only if source-backed:
- User
- Main Window / UI
- ViewModel / application controller
- Queue / job manager
- Download service
- Conversion service
- Preset / settings service
- External tools
- File system

Use current FORMAT-dfd_diagram.md.
Do not assume DFD table schemas from memory.

2. DFD objects

Create small DFD object files for source-backed boundaries.

Likely candidates:
- model/01_dfd/objects/DFD-NMM-OBJ-USER.md
- model/01_dfd/objects/DFD-NMM-OBJ-UI.md
- model/01_dfd/objects/DFD-NMM-OBJ-APP-CONTROLLER.md
- model/01_dfd/objects/DFD-NMM-OBJ-QUEUE.md
- model/01_dfd/objects/DFD-NMM-OBJ-DOWNLOAD.md
- model/01_dfd/objects/DFD-NMM-OBJ-CONVERSION.md
- model/01_dfd/objects/DFD-NMM-OBJ-SETTINGS.md
- model/01_dfd/objects/DFD-NMM-OBJ-EXTERNAL-TOOLS.md
- model/01_dfd/objects/DFD-NMM-OBJ-FILE-SYSTEM.md

Create only objects supported by source, README, or release docs.

3. DATA models

Create concise DATA models for important runtime data.

Likely candidates:
- model/03_data/DATA-NMM-APP-SETTINGS.md
- model/03_data/DATA-NMM-CONVERSION-JOB.md
- model/03_data/DATA-NMM-QUEUE-ITEM.md
- model/03_data/DATA-NMM-CONVERSION-PRESET.md
- model/03_data/DATA-NMM-DOWNLOAD-REQUEST.md
- model/03_data/DATA-NMM-OUTPUT-FILE.md
- model/03_data/DATA-NMM-EXTERNAL-TOOL.md

Use source-backed field names where possible.
Do not model every minor property if it does not help understanding.

For data_object files, use this section order:
1. ## Summary
2. ## Fields
3. ## Notes
4. ## Source Links

Do not place ## Source Links immediately after ## Fields.

4. Process / Business Flow models

Create structured app_process models with table-based ## Steps and ## Flows.

Preferred workflows:
- model/04_process/PROC-NMM-ADD-FILE-TO-QUEUE.md
- model/04_process/PROC-NMM-DOWNLOAD-AND-CONVERT.md
- model/04_process/PROC-NMM-CONVERT-LOCAL-FILE.md
- model/04_process/PROC-NMM-COPY-ONLY.md
- model/04_process/PROC-NMM-APPLY-PRESET.md
- model/04_process/PROC-NMM-RESOLVE-EXTERNAL-TOOLS.md
- model/04_process/PROC-NMM-SAVE-SETTINGS.md

Create only workflows that are clearly source-backed.
If a workflow is unclear, omit it and mention it in the findings note.

Business Flow requirements:
- Use type: app_process.
- Use current FORMAT-app_process.md.
- Every Flows.from and Flows.to must match a local Steps.id.
- Do not use external model IDs as Flows.from or Flows.to.
- Use compact branch conditions only when source-backed.
- Keep diagrams readable.

5. Screen model

Create:
model/09_screen/SCR-NMM-MAIN-WINDOW.md

Purpose:
Represent the main UI structure from WPF/XAML and ViewModel behavior.

Include if source-backed:
- main fields
- buttons
- mode selection
- queue display
- preset selection
- output path / file selection
- progress / status display
- main user actions mapped to process models

Do not model pixel-level layout.

6. Findings note

Create:
model/99_notes/REPORT-NMM-REVERSE-ENGINEERING-FINDINGS.md

Include:
- source files inspected
- generated model coverage
- architecture summary
- implemented workflows found
- uncertain or deferred areas
- suspected missing source evidence
- recommended next improvements
- whether Model Weave was effective for this app

Source Links:
For generated files, include ## Source Links where useful.
Use parser-supported tables from the provided guidance.
Prefer actual source paths and symbols.

Validation checklist:
After creating files, inspect the generated Markdown and report:
- frontmatter type/schema is correct
- table headers match provided Model Weave format docs
- no C# / TypeScript array notation like Foo[] in tables
- no Wikilink aliases in tables
- no empty placeholder rows
- DFD flow schemas match FORMAT-dfd_diagram.md
- app_process flow schemas match FORMAT-app_process.md
- every app_process flow endpoint exists as a local step id
- data_object files use ## Notes before ## Source Links
- Japanese prose remains Japanese
- source symbols and file paths are accurate
- no files outside model/ were changed
- no source files were changed
- no git commands were run

Return:

## Generated files
List every created file with one-line purpose.

## Source evidence summary
List the main source files used and what each contributed.

## Architecture summary
Summarize NaviMovie-Maker boundaries and data flow.

## Main workflows modeled
List created process models and what each visualizes.

## Uncertain or deferred areas
List anything not modeled because source evidence was weak.

## Validation result
Report:
- DFD files created: count
- DATA files created: count
- Process files created: count
- Screen files created: count
- Notes files created: count
- table schemas checked: yes/no
- app_process flow endpoints checked: yes/no
- data_object section order checked: yes/no
- no files outside model/ changed: yes/no
- no source files changed: yes/no
- no git commands run: yes/no

End with:
No source files were changed.
No git commands were run.