miko.catchup_system_hld

Check and update system_high_level_design.md against the current codebase.

10|1|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/studyplus/miko --skill miko-catchup-system-hld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: miko.catchup_system_hld
Source: https://github.com/studyplus/miko/tree/main/skills/miko.catchup_system_hld
Command: npx skills add https://github.com/studyplus/miko --skill miko-catchup-system-hld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the system_high_level_design.md document stays up-to-date with the current state of the codebase, minimizing discrepancies.

Core Features & Use Cases

  • Directory Structure Check: Verifies that all directories listed in system_high_level_design.md exist and are up-to-date.
  • API Structure Validation: Confirms that all documented API patterns match the current routing definitions.
  • Business Rule Alignment: Assesses if business rules documented in the system_high_level_design.md still apply and are correctly reflected in the code.
  • Use Case: Regularly run this Skill after major changes in the codebase to maintain the consistency between the design documentation and the actual code.

Quick Start

To update the system_high_level_design.md with the current codebase status, run /miko.catchup_system_hld.

Frequently Asked Questions about miko.catchup_system_hld

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep my high level design document in sync with the codebase?

To keep your high level design document in sync with the codebase, you can run a check that identifies discrepancies in directory structures, API patterns, and business rules, then proposes necessary updates to the documentation.

What is high level design document maintenance for software engineering?

High level design document maintenance is the process of verifying that documented directory structures, API patterns, and business rules still accurately reflect the current codebase implementation.

How do I validate API patterns against current routing definitions?

You validate API patterns against current routing definitions by running an API structure validation check that confirms all documented endpoints match the actual codebase routing implementation.

When should I update system design documentation after codebase changes?

You should update system design documentation regularly after major changes in the codebase to maintain consistency between the design documentation and the actual code.

Do I need codebase access to check business rule alignment?

Yes, you need codebase access and documentation files to check business rule alignment, as the process assesses if documented rules still apply and are correctly reflected in the code.