Assimilation Report: [System Name] — Development agent for Claude Code

When given an external system path:

1. Deploy exploration subagent to map the structure
2. Identify: skills, agents, commands, hooks, workflows, conventions
3. Document the external system's architecture patterns
4. Note any dependencies (API keys, MCP servers, tools)

Phase 1.5: INFRASTRUCTURE COMPATIBILITY CHECK

Before proceeding with gap analysis, verify infrastructure compatibility:

1. **List all dependencies** identified in Phase 1:

   • API keys required
   • MCP servers needed
   • CLI tools expected
   • External services referenced

2. **Check against your local infrastructure:**

   Build a table like this for the target system:

   Service	Available	Verification
   [API/Service]	?/?	[how to check]

   Check environment variables, running services, and CLI tools.

3. **For each MISSING dependency:**

   • SUBSTITUTE: Find local equivalent (e.g., one LLM provider -> another)
   • REQUIRES_SETUP: Flag for user to add before using
   • CANNOT_ASSIMILATE: No equivalent, skip feature

4. **Output compatibility report:**

   INFRASTRUCTURE CHECK:
   ? [dep] - available
   ?? [dep] - MISSING, substitute with [alt]
   ? [dep] - MISSING, no equivalent - will skip

**CRITICAL**: Do NOT proceed if critical dependencies cannot be resolved.

Phase 2: GAP ANALYSIS

Compare against your local system's capabilities:

1. List features that exist in external system but NOT in your local system
2. Score each feature: CRITICAL / HIGH / MEDIUM / LOW value
3. Identify adaptation requirements (naming, paths, dependencies)
4. Flag any conflicts with existing local artifacts
5. Check for overlap with existing local implementations

Phase 2.5: ITERATE OR ASSIMILATE DECISION

Before proceeding with full assimilation, determine the right approach:

**FULL ASSIMILATE** when:

• Capability is genuinely new to your system
• No existing agents/skills cover this domain
• External implementation is clearly super