Analyze Legacy System

Canonical Instructions

Read and follow repository-root AGENTS.md; this skill narrows that contract and never overrides it.

Description And Trigger

Use when inventorying repositories, runtime behavior, integrations, data coupling, or undocumented assumptions in the legacy PHP system.

Inputs

• legacy repository paths
• deployment notes
• discovery templates

Preconditions

• a legacy repository or artifact is available for evidence gathering

Ordered Workflow

1. Inventory repositories and entry points.
2. Record observed behavior with exact evidence.
3. Separate confirmed behavior from hypotheses and open questions.
4. Capture migration and compatibility risks.

Required Outputs

• inventory notes
• risk and uncertainty summary

Evidence

• file references
• command output summaries
• explicit uncertainty notes

Validation Checklist

• no code changes were made
• findings cite evidence
• undocumented behavior is not treated as fact

Failure Conditions

• findings are asserted without evidence

Escalation Conditions

Escalate when production behavior cannot be determined safely from repository evidence.

Forbidden Behavior

• modifying legacy code
• treating hypotheses as confirmed production truth