refactor: separate outline.yaml and fields.yaml

- Output to {topic}/ directory structure
- fields.yaml now independent file for field definitions
- outline.yaml contains items + execution config
- Deep research agents read fields.yaml independently (hard constraint)
- Update README with new directory structure

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

README.md

@@ -36,14 +36,15 @@ cp -r skills/* ~/.claude/skills/
 ```
 - Uses model knowledge + web search
 - Asks for existing field definitions
-- Outputs `{topic}_outline.yaml` in current directory
+- Creates `{topic}/` directory with separated files
 
 ### Phase 2: Deep Research
 ```
 /research/deep
 ```
-- Reads outline automatically from current directory
+- Reads outline and fields automatically from current directory
 - Launches parallel agents (5 per batch)
+- Agents read fields.yaml independently (not passed in prompt)
 - Outputs structured JSON per item
 - Supports resume from checkpoint
 
@@ -55,21 +56,32 @@ cp -r skills/* ~/.claude/skills/
 
 ## Output Format
 
-### Outline (YAML)
+### Directory Structure
+```
+{topic}/
+  ├── outline.yaml    # items + execution config
+  ├── fields.yaml     # field definitions
+  └── results/        # deep research outputs
+```
+
+### outline.yaml
 ```yaml
 topic: "your topic"
 items:
   - name: "Item1"
     source: "source info"
-fields:
-  basic_info:
-    - name: "field_name"
-      description: "field description"
-      detail_level: "detailed|brief"
 execution:
   batch_size: 5
 ```
 
+### fields.yaml
+```yaml
+basic_info:
+  - name: "field_name"
+    description: "field description"
+    detail_level: "detailed|brief"
+```
+
 ### Research Result (JSON)
 Each item outputs a structured JSON file with all defined fields.