new_harae

Verify business rules for correctness and generate a harae.md issue tracking file.

10|1|Updated Jun 10, 2026

Search Tags:#verification #issue tracking #business rules #rule management #harae.md

Ready to run

npx skills add https://github.com/studyplus/miko --skill new-harae

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: new_harae
Source: https://github.com/studyplus/miko/tree/main/skills/miko.new_harae
Command: npx skills add https://github.com/studyplus/miko --skill new-harae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill performs an aggressive initial verification of business rules to ensure their correctness, generating a new harae.md file for managing issues and statuses.

Core Features & Use Cases

Aggressive Rule Verification: Checks for any potential flaws in the business rule definitions.
harae.md Generation: Creates a new harae.md file to track and manage identified issues.
Use Case: After defining new business rules with /miko.new_cap, use this Skill to perform an initial round of verification to identify any weaknesses in the rules.

Quick Start

Run the /miko.new_harae order_management command to initiate the verification process for the 'order_management' capability.

Frequently Asked Questions about new_harae

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

FAQPage Schema

How do I verify business rules for correctness after defining them?▼

You can verify business rules for correctness by running an aggressive initial verification process that analyzes rule definitions for potential flaws and outputs a harae.md file for issue tracking.

What is aggressive initial verification in business rule management?▼

Aggressive initial verification is a business rule management process that proactively checks newly defined rules to identify weaknesses and ensure correctness before production.

How do I create an issue tracking document for business rule flaws?▼

To create an issue tracking document for business rule flaws, run a verification process that automatically generates a new harae.md file from scratch to manage the identified issues.

When do I need to use an aggressive verification approach for business rules?▼

You need an aggressive verification approach for business rules immediately after defining new capabilities, ensuring an initial verification round identifies any weaknesses in the rule definitions.

Does business rule verification require any specific dependencies or components?▼

Business rule verification requires no external dependencies, operating independently through internal scripts to analyze rules and generate the harae.md issue tracking document.