Draft the public document in the following order: 공식 근거 확인 → 시민 행동 정의 → 대상·조건 구조화 → 쉬운 초안 → 정확성·접근성 검토 → 문체 검사 .
1. Confirm the institution and legal effect
- Sending institution and responsible department
- Document type and legal and administrative effect
- Official basis and reference date
- Target, region, period, and exceptions
- Actions citizens must take and deadlines
- Application channels, required documents, costs, and contact points
Verify statutes, ordinances, support conditions, dates, and contact information against the provided materials or official sources. If recency cannot be verified, do not create definitive wording and mark it as 확인 필요. If the institution has required forms and approval formats, prioritize those formats.
2. Put what citizens need to know first
Answer the following quickly at the beginning.
- What is changing or being provided?
- Who is eligible?
- What must be done by when?
- Where and how is it handled?
- Where should one contact for help?
Do not list legal bases at length before citizen actions. However, do not arbitrarily abbreviate wording needed to determine effect and eligibility.
Select the document type from references/formats.md.
3. Write plainly and accurately
- Use active voice to distinguish what the institution does from what citizens must do.
- Write dates as absolute dates including the year, and specify times, amounts, and units.
- Spell out abbreviations and technical terms when they first appear.
해당,상기,제반,통하여,실시한다Review whether it can be changed into specific targets and actions.- Do not hide exclusions from application, conditions under which selection is not guaranteed, or disadvantages.
- Cross-check web addresses, phone numbers, attachment names, and reception channels against the original text.
If a file output is needed, use assets/public-document-template.mdshortened to fit the document type. Before completion, apply references/quality-gate.md.
4. Check style and structure
CORE_SKILL_DIRis interpreted as the natural-korean directory in the same parent folder.
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
Do not change statute names, official notice wording, or required administrative terms because of lint. If there is no common inspection skill, review manually as a quality gate and state that the inspection was not run.
5. Final delivery
After the completed document, list separately the dates, legal bases, contact points, or institution-specific forms that require official confirmation. If any unverified items remain, do not call it a publishable final version.