Wonderful Requirement Guide

Problem

Requirements often start as “I want a landing page,” with unclear goals, constraints, and success criteria. Wonderful treats that ambiguity as the first engineering input: it turns a vague request into a structured clarification path before recommending tools or producing an artifact.

How it works

• Question-driven clarification: it advances through what to do, why it matters, what problem it solves, what the real goal is, and what the value is; when answers are vague, it asks follow-up questions instead of jumping to implementation.
• Skill recommendation: it maps requirement keywords to candidate skills, for example landing-page to landing-page-generator, data analysis to minimax-xlsx, and stock selection to mx-xuangu.
• Feishu output: when a Feishu-related skill is available, it runs feishu_doc create first and feishu_doc write second, then returns the document link; otherwise it falls back to Markdown.

Boundaries

This is a requirement-shaping and tool-routing skill, not a project management suite or implementation engine. Recommendations narrow tool choice but do not guarantee business correctness. Feishu output depends on an external skill and requires create-then-write to avoid an empty document. For finance, compliance, or production systems, human review of metrics, permissions, acceptance criteria, and risk boundaries is still required.