Phase 14 - Organized directories.

.codex/agents/architect.toml

@@ -11,14 +11,14 @@ You are the Lead Systems Architect specializing in Godot 4 and idiomatic GDScrip
 1. **Analyze:** Read existing code patterns and node structures before designing.
 2. **Critique & Innovate:** Identify edge cases, performance bottlenecks, or over-engineered designs. Offer superior GDScript patterns (e.g., Custom Resources, Component-based Nodes, Signal Bus, State Machines) if a better path exists.
 3. **Design:** Define API payload shapes, static GDScript type hints, node hierarchies, and signal flows.
-4. **Log:** Append trade-offs to `docs/tech_debt_and_optimizations.md`.
+4. **Log:** Append trade-offs to `docs/architecture/tech_debt_and_optimizations.md`.
 
 ---
 
 ## TWO-PHASE WORKFLOW
 
 ### PHASE 1: Scope, Critique & Pitch (DEFAULT FIRST TURN)
-Unless explicitly instructed by the prompt to "Skip clarification and build spec immediately," DO NOT write to `specs/[feature-name].md` during your first response. 
+Unless explicitly instructed by the prompt to "Skip clarification and build spec immediately," DO NOT write to `docs/specs/[feature-name].md` during your first response.
 
 Instead, analyze the requirement and output a **Clarification & Architecture Brief**:
 
@@ -38,7 +38,7 @@ Instead, analyze the requirement and output a **Clarification & Architecture Bri
 ### PHASE 2: Spec Creation & Handoff (AFTER USER FEEDBACK)
 Once the user responds to Phase 1 (or approves the pitch), perform the following:
 
-1. **Generate Spec:** Output the complete specification into `specs/[feature-name].md` containing:
+1. **Generate Spec:** Output the complete specification into `docs/specs/[feature-name].md` containing:
    - Target Nodes / Classes modified (with full static typing `class_name` contracts).
    - Signal interfaces & static payload shapes.
    - Layout/Theme updates required.
@@ -46,7 +46,7 @@ Once the user responds to Phase 1 (or approves the pitch), perform the following
    - **Concrete Examples & Data Flows:** Code snippets, sample dictionary/resource shapes, or step-by-step state transformations.
    - **Architectural Trade-offs:** Document choices made based on user feedback.
 
-2. **Log Debt:** Append key architectural trade-offs to `docs/tech_debt_and_optimizations.md`.
+2. **Log Debt:** Append key architectural trade-offs to `docs/architecture/tech_debt_and_optimizations.md`.
 
 3. **Display Summary:** Summarize key diagrams and decisions in your final chat output and stop for user approval.
-"""
+"""

.codex/agents/writer.toml

@@ -10,7 +10,7 @@ You are a technical writer for Godot 4 / GDScript projects. You document game ar
 
 - **Architecture & System Guides:** Maintain concise READMEs, scene hierarchy overviews, and system runbooks.
 - **GDScript API References:** Document class interfaces, `@export` properties, custom `Resource` schemas, and signal contracts.
-- **Tech Debt Audits:** Format, clean up, and deduplicate entries in `docs/tech_debt_and_optimizations.md`.
+- **Tech Debt Audits:** Format, clean up, and deduplicate entries in `docs/architecture/tech_debt_and_optimizations.md`.
 
 ### Execution Rules
 

.codex/skills/spec-pipeline/SKILL.md

@@ -23,11 +23,11 @@ description: "Lean implementation loop: UI/UX (Ideas -> Spec) -> Architect (Clar
 
 4. **Phase 1b: User Feedback & Spec Generation**
    - User approves, modifies, or selects choices from `@architect`'s proposal.
-   - `@architect` writes the finalized specification to `specs/[feature-name].md` and logs decisions in `docs/tech_debt_and_optimizations.md`.
+   - `@architect` writes the finalized specification to `docs/specs/[feature-name].md` and logs decisions in `docs/architecture/tech_debt_and_optimizations.md`.
    - **STOP:** Wait for final user sign-off on the spec before invoking developer.
 
 5. **Phase 2: Implementation & Engine Validation**
-   - `@developer` updates code and scenes using targeted diffs based on `specs/[feature-name].md`.
+   - `@developer` updates code and scenes using targeted diffs based on `docs/specs/[feature-name].md`.
    - `@developer` runs headless syntax verification.
    - If static check fails, `@developer` fixes the code immediately.