miko.propose

Transform unstructured human input into structured capability change proposals.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires miko, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill facilitates the transformation of unstructured human input into structured capability change proposals, streamlining the process of documenting and implementing changes.

Core Features & Use Cases

  • Input Parsing: Converts user-provided text into structured change proposals.
  • Dialogue-based Elaboration: Engages in a conversation to clarify and expand upon user input.
  • Proposal Generation: Outputs a comprehensive proposal with business rules, functional specifications, and potential impacts on other capabilities.

Quick Start

/miko.propose order_management トライアル終了時にメール通知を送りたい

Frequently Asked Questions about miko.propose

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

FAQPage Schema
How do I turn unstructured business requests into structured capability change proposals?

To generate capability change proposals, you input a business rule modification request as text. The system parses the input and uses dialogue-based elaboration to clarify ambiguity, outputting a structured proposal with functional specifications and impact analysis.

How does conversation AI handle ambiguity when creating feature specifications?

Conversation AI handles ambiguity by engaging in a dialogue-based elaboration process. It asks targeted questions to validate the human input against system guidelines, ensuring the resulting feature specifications are accurate and comprehensive.

What is the best way to document business rule modifications across different capabilities?

The best way to document business rule modifications is to use an AI-driven proposal generation process. It transforms human input into a comprehensive proposal, detailing business rules, functional specifications, and potential impacts on other capabilities.

Do I need to understand system architecture to generate change proposals?

Yes, understanding system architecture is required to generate change proposals effectively. The process involves impact analysis across different business capabilities, which relies on validating the proposed changes against existing architectural guidelines.

Can I use miko.propose to analyze the impact of a new feature on existing business capabilities?

Yes, you can use miko.propose to analyze feature impact. It transforms your feature specification input into a comprehensive proposal that explicitly details potential impacts on other business capabilities and existing business rules.

What are the limitations of using automated proposal generation for business rules?

Automated proposal generation requires clear human input and dialogue to handle ambiguity effectively. If the domain expert cannot provide accurate context for the system architecture, the resulting business rules and impact analysis may lack necessary validation.