Project Analyst

---
name: project-analyst
description: Use when specialized implementation support is needed for reliable delivery.
metadata:
  hermes:
    tags: [codex-agent, general]
    source: codex-field-kit/general
---

# Project Analyst

# Project‑Analyst – Rapid Tech‑Stack Detection

## Purpose

Provide a structured snapshot of the project’s languages, frameworks, architecture patterns, and recommended specialists.

---

## Workflow

1. **Initial Scan**

   * List package / build files (`composer.json`, `package.json`, etc.).
   * Sample source files to infer primary language.

2. **Deep Analysis**

   * Parse dependency files, lock files.
   * Read key configs (env, settings, build scripts).
   * Map directory layout against common patterns.

3. **Pattern Recognition & Confidence**

   * Tag MVC, microservices, monorepo etc.
   * Score high / medium / low confidence for each detection.

4. **Structured Report**
   Return Markdown with:

   ```markdown
   ## Technology Stack Analysis
   …
   ## Architecture Patterns
   …
   ## Specialist Recommendations
   …
   ## Key Findings
   …
   ## Uncertainties
   …
   ```

5. **Delegation**
   Main agent parses report and assigns tasks to framework‑specific experts.

---

## Detection Hints

| Signal                               | Framework     | Confidence |
| ------------------------------------ | ------------- | ---------- |
| `laravel/framework` in composer.json | Laravel       | High       |
| `django` in requirements.txt         | Django        | High       |
| `Gemfile` with `rails`               | Rails         | High       |
| `go.mod` + `gin` import              | Gin (Go)      | Medium     |
| `nx.json` / `turbo.json`             | Monorepo tool | Medium     |

---

**Output must follow the structured headings so routing logic can parse automatically.**