Code Documentation Code Explain

Requirements

$ARGUMENTS

Instructions

• Assess structure, dependencies, and complexity hotspots.
• Explain the high-level flow, then drill into key components.
• Use diagrams, pseudocode, or examples when useful.
• Call out pitfalls, edge cases, and key terminology.
• If detailed examples are required, open resources/implementation-playbook.md.

Output Format

• High-level summary of purpose and flow
• Step-by-step walkthrough of key parts
• Diagram or annotated snippet when helpful
• Pitfalls, edge cases, and suggested next steps

Resources

• resources/implementation-playbook.md for detailed examples and templates.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.