Structured Markdown Document Generator

Problem

Market research, competitor analysis, business analysis, SOPs, and briefs often fail not because content is missing, but because the structure is unstable: raw notes, tables, and open items are scattered, while direct generation may produce inconsistent headings, overly generic sections, or mixed process and conclusion content. @user_d82fedf3/document-engine constrains the output to a Markdown document, first identifying the document type and then organizing sections, lists, and process steps to reduce manual reformatting work.

How It Works

This skill is focused on structured Markdown document generation, turning loose material into readable deliverables. It supports:
- Market research reports: organizing target market, users, opportunities, and risks
- Competitor analysis: breaking features, pricing, channels, and strengths into comparable dimensions
- Business analysis: separating context, assumptions, conclusions, and action items
- SOP documents: structuring steps, owners, inputs, outputs, and precautions
- Brief proposals: clarifying objectives, scope, deliverables, and constraints

A practical workflow is to provide the topic, audience, source material, and target document type. The skill then generates ## headings, lists, and field-style content that is easy to edit. Because the provided material does not specify a rendering engine or external dependencies, treat it as a draft generator and manually verify facts, data, and accountability.

Boundaries

It is most useful when the topic and base material are already defined, such as converting meeting notes, interview points, or competitor tables into reports or SOPs. It should not replace real-time data validation, legal or compliance review, or complex workflow orchestration. Output should remain renderable Markdown and avoid introducing undocumented proprietary formats.