One-Sentence XMind Feature Map Generator

Problem: Turning a Vague Scenario into Reviewable Features

When drafting product requirements, mapping business processes, or planning a system, the first hard step is often deciding how to break features into modules. A manual outline can miss edge cases, while a generic model answer may return shallow labels such as user management or order management. This skill targets that gap: take a scenario description, shape it into a layered feature tree, and produce an openable .xmind file.

How It Works: From Scenario to Deliverable

• Scope: identify the system name, key roles, and main business domains; use the system name as the root node. If the input is unclear, ask one focused question.
• Decomposition: choose a depth of 2 to 4 layers based on system complexity, with roughly 3 to 10 top-level modules. It prefers user journey, business domain, or system capability views.
• Node notes: each node should carry a note field. The root states positioning, first-level nodes state module responsibilities, and lower levels capture functions, rules, and operational boundaries.
• File generation: the structure is written to a temporary JSON file, then a built-in script generates a .xmind file compatible with XMind 8 and later.
• Delivery summary: the response includes the root node, first-level modules, child-feature counts, and total feature count for quick review.

Boundaries

It is useful for producing an initial feature map from product requirements, business workflows, or system plans. Output quality depends on the input scenario; detailed field lists, integration APIs, and permission matrices still need follow-up. If your team has fixed architecture rules, include those decomposition constraints in the prompt.