Complete the business document in the order of 결정 또는 행동 정의 → 근거 정리 → 구조 작성 → 초안 → 실행 가능성 검토 → 문체 검사 .
1. Define the document's success conditions
Confirm the following or infer them from context.
- The reader and final decision-maker
- The decision or action the document requests
- Decision deadline
- Facts already confirmed and content that is still a proposal
- Alternatives to compare, costs, risks, and constraints
- Execution owners and schedule
Ask questions only when the decision or request is unclear and the document's direction would change. Select the document type from references/formats.md.
2. Distinguish evidence and status
- Preserve facts, figures, dates, quotations, and proper nouns exactly as in the source.
- Do not turn plans into completed results.
- Distinguish proposed, under review, approved, and completed through wording.
- Do not invent unverified budgets, performance, or customer reactions.
- If information is missing, reveal the gap as in
미정,확인 필요,담당자 지정 필요.
3. Write conclusion-first
Place the conclusion, request, and key evidence within the first screen. Do not delay the decision with background explanation.
- Write the needed decision or key status first.
- Follow with only the evidence needed for judgment.
- If there are alternatives, compare them by the same criteria.
- Present risks together with mitigation measures.
- End with owners, deadlines, and next actions.
For detailed format, apply references/formats.md; for completion judgment, apply references/quality-gate.md. If a file output is needed, use assets/business-document-template.mdreduced to fit the purpose.
4. Check style and structure
CORE_SKILL_DIRInterpret natural-korean as the directory in the same parent folder as this skill.
uv run "$CORE_SKILL_DIR/scripts/lint.py" path/to/document.md --genre business
uv run "$CORE_SKILL_DIR/scripts/outline.py" path/to/document.md
uv run "$CORE_SKILL_DIR/scripts/terms.py" path/to/document.md
If there is no common inspection skill, manually review with references/quality-gate.mdand briefly state that fact in the result. Treat lint findings not as errors but as review candidates.
5. Final delivery
Present the completed document first. If undecided items, assumptions, or risks remain that the decision-maker must check, briefly list them separately after the document. Do not leave internal drafting notes or inspection JSON unless requested.