Ln 640 Pattern Evolution Auditor

What it does

The Ln 640 Pattern Evolution Auditor analyzes architectural patterns within a project to identify evolutionary changes and ensure compliance with current best practices. It acts as an L2 Coordinator, orchestrating a series of specialized worker tools (ln-641 through ln-647) to perform audits and research related to pattern implementation. The skill ultimately generates a comprehensive audit report detailing findings and recommendations.

When to use it

• To assess the adherence of existing architectural patterns to current best practices.
• When tracking changes in complex data sequences within a project.
• Before making significant modifications or refactoring efforts involving architectural patterns.
• As part of a regular audit process for software projects utilizing "ln 640" patterns.
• To identify potential gaps and areas for improvement in pattern implementation.

Key capabilities

• Pattern Analysis: Evaluates implemented architectural patterns against current best practices.
• Coordination: Manages the execution of worker tools (ln-641 - ln-647) including ln-641-pattern-analyzer, ln-642-layer-boundary-auditor and others.
• Research Integration: Requires research to be conducted before pattern scoring, leveraging official documentation, MCP references, and web best practices.
• Boundary Audits: Performs boundary audits prior to pattern scoring.
• Report Generation: Aggregates findings from worker tools into a final audit report.

Example prompts

• "Run the Ln 640 Pattern Evolution Auditor on this project's codebase."
• "Analyze the 'payment processing' pattern for compliance with current best practices using the Ln 640 Pattern Evolution Auditor."
• "Initiate an audit of the 'user authentication' architecture, utilizing the Ln 640 Pattern Evolution Auditor and its associated worker tools."

Tips & gotchas

• Mandatory Reads: Before using this skill, ensure you review the referenced documents: evaluation_coordinator_runtime_contract.md, evaluation_summary_contract.md, evaluation_research_contract.md and research_tool_fallback.md.
• Workflow Dependency: The skill follows a specific phase order (CONFIG, DISCOVERY, RESEARCH, BOUNDARY AUDITS, PATTERN ANALYSIS, AGGREGATE, REPORT, SELF-CHECK) – research must be completed before pattern scoring.
• Skill Tool Usage: Worker logic should not be inlined; use the Skill tool to delegate tasks to the worker tools (ln-641 through ln-647).