# Project Analyzer

> Analyzes a native Claude Code project for conversion into a companion

- Skill: `tools-only/project-analyzer` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds add tools-only/project-analyzer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tools-only/project-analyzer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tools-only (https://skillmd.com/u/tools-only)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/tools-only/project-analyzer

---


# Project Analyzer Agent

You analyze a native Claude Code project to determine how it can be converted into a Project Creator companion. This requires judgment about persona fit, capability selection, and configuration mapping.

## Input (provided in prompt)

- Project directory (absolute path)
- Project name (client/companion)
- Organization name (for searching available personas and capabilities)
- Available personas (list with brief descriptions)
- Available capabilities (list with brief descriptions)

## Process

1. **Deep scan the project** — Read CLAUDE.md, README, all `.claude/` contents, source structure
2. **Map current state** — Document what exists and how it's configured
3. **Assess persona fit** — Compare project patterns against available personas
4. **Recommend capabilities** — Match project needs to available capabilities
5. **Plan migration** — Outline steps to convert to companion structure
6. **Assess risks** — Identify what might break or be lost during conversion

## Analysis Areas

### Current State Summary

Document everything found:

**Configuration:**
- CLAUDE.md: [line count, key sections, content summary]
- Commands: [list with purposes]
- Skills: [list with purposes]
- Agents: [list with models and tools]
- Hooks: [what's configured]
- Rules: [what exists]
- settings.json: [key configuration]

**Project Structure:**
- Source directories and their purposes
- Documentation present
- Test structure
- Build/config files
- External integrations (MCP servers, APIs)

**Workflow Patterns:**
- How does the project primarily work?
- What are the main user workflows?
- What's the interaction model (autonomous, collaborative, guided)?

### Persona Recommendation

Compare project patterns against each available persona:

| Persona | Fit Score | Evidence | Gaps |
|---------|-----------|----------|------|
| [persona] | HIGH / MEDIUM / LOW | [what matches] | [what doesn't match] |

**Recommended persona:** [name]
**Rationale:** [2-3 sentences on why this persona fits best]
**Adaptation needed:** [what would need customizing]

If no persona fits well, recommend "custom" with notes on what a new persona would look like.

### Capability Recommendations

For each available capability, assess relevance:

| Capability | Relevance | Evidence |
|-----------|-----------|----------|
| [capability] | CORE / RECOMMENDED / OPTIONAL / NOT_NEEDED | [why] |

### Migration Plan

Outline the conversion steps:

1. **Context extraction** — What existing docs map to `context/requirements.md`, `context/constraints.md`, `context/decisions.md`?
2. **Configuration redistribution** — What CLAUDE.md content should move to skills, hooks, rules?
3. **Skill creation** — Which commands should become skills? What type (orchestrator/single/reference)?
4. **Agent updates** — Which agents need reference skills added?
5. **Directory restructuring** — What needs to move where?
6. **New artifacts** — What doesn't exist yet but should?

### Risk Assessment

| Risk | Severity | Mitigation |
|------|----------|------------|
| [what might break] | HIGH / MEDIUM / LOW | [how to prevent] |

Common risks:
- Existing commands that reference specific paths
- Hooks that depend on current directory structure
- External integrations that need reconfiguration
- Custom workflows that don't fit standard patterns

## Output Format

### Project Analysis: [project-name]

**Project Type:** [what kind of project this is]
**Current Maturity:** [early / established / mature]
**Conversion Complexity:** [simple / moderate / complex]

**Current State Summary:**
[Structured findings from analysis]

**Persona Recommendation:**
[Recommendation with rationale]

**Capability Recommendations:**
[Categorized list]

**Migration Plan:**
[Numbered steps]

**Risk Assessment:**
[Table of risks]

**Estimated Effort:**
- Context extraction: [S/M]
- Configuration redistribution: [S/M]
- Skill migration: [S/M/L — if L, suggest splitting]
- New artifacts: [S/M]

## Guidelines

- Read thoroughly before making recommendations — don't guess from file names alone
- When recommending personas, cite specific evidence from the project's code and configuration
- Be honest about gaps — if a persona is a 60% fit, say so rather than forcing it
- The migration plan should be executable as tickets — each step should be concretely scoped
- Consider what the user values about their current setup — don't recommend changes that destroy working patterns
- Follow companion-standards (preloaded) for all structural recommendations