Strategy Guide
| ID | Korean Name | Description |
|---|---|---|
| operations-manual | Operations Manual | Work processes, operating regulations, workflow design |
| procurement-docs | Procurement Documents | Purchase requests, purchase orders, vendor evaluation |
| sop-writer | SOP Writing | Standard operating procedures, manuals, guidelines |
| meeting-strategist | Meeting Strategist | Meeting minutes preparation, agenda management, follow-up actions |
→ Reference file: references/{id}.md
Execution Rules
- Receive user request → identify the corresponding strategy guide
references/{id}.mdLoad → execute according to the strategy guide--deepthinkor complex process design → if sequential-thinking MCP is installed,mcp__sequential-thinking__sequentialthinkinguse it; otherwise,ultrathinkreplace with keyword-based deep reasoning or general step-by-step reasoning- After generating the deliverable, request user review
Trigger Keywords
Process, operations manual, work procedure, SOP, procurement, purchasing, ordering, meeting minutes, agenda, workflow
Usage Examples
- "Create an onboarding SOP for new employees"
- "Create an IT equipment purchase request form"
- "Summarize today's meeting content into minutes"
- "Design a monthly operations manual for the sales team"
- "Create a vendor evaluation form for software purchasing"
Standalone Workflow
You can proceed to the next steps even without a strategy guide file:
- Identify the request: Confirm the document type (SOP/minutes/procurement/manual) and target work
- Design the structure: Draft the purpose, scope, responsible parties, and step-by-step procedures
- Write the content: Describe each procedure as specific action units (specify responsible parties, tools, and deliverables)
- Present review points: Check whether legal compliance requirements, approval lines, and emergency response procedures are included
- Final confirmation: Provide the final version after user review
Electronic approval and approval line design
When including approval procedures in process documents (SOPs, proposals, purchase requests, etc.), design the approval line using the standard flow below.
기안(담당) → 검토(팀장/부서장) → 합의·협조(관련 부서) → 전결 또는 최종 결재(결재권자)
- Drafting: The person in charge creates the document and submits it for approval. The document number and effective date follow the format rules.
- Review: The direct supervisor (team leader or department head) checks the content and format.
- Agreement (Cooperation): For agenda items requiring confirmation from stakeholder departments such as budget, legal, and security, an agreement column is placed in the middle of the approval line. If an agreement department rejects the item, it is returned to the drafting stage.
- Delegated approval: For matters whose approval authority has been delegated under the delegated approval regulations, the delegated approval authority approves after marking "delegated approval," and no approval column is created for their superior. In the absence of the approval authority, the acting official approves after marking "acting approval." (Basis: Article 10 of the "Regulations on Administrative Efficiency and Promotion of Collaboration" — this is the standard for administrative agencies; companies follow their own delegated approval regulations.)
Delegated Approval Regulation Design Guide: Define the delegated approval authority in a table by case type (expenditure, contract, personnel, public relations) and amount bracket. Since the amount brackets and the placement of delegated approval authorities differ by organization, do not arbitrarily fix default values and instead confirm the user organization's regulations (confirmation needed). For organizations without regulations, present a customary starting point such as "small recurring expenditures are approved by the department head, and new contracts and non-budgeted expenditures are approved by the CEO" as a draft and request review.
The actual forms for the approval column and delegated approval in official documents, draft documents, and approval requests are moai-officer:doc-hwp의 references/kr-official-forms.md(Korean-style form SSOT).
Troubleshooting
| Situation | Solution |
|---|---|
| Insufficient approval line information | If you provide the organizational chart or the scope of approval authority, we can create a customized version |
| Unable to confirm procurement regulations | We recommend drafting based on general internal purchasing standards and having the responsible department review it |
| Conflict with existing processes | If you share the current procedure document, we will draft an improvement plan |
| Industry/domain-specific requirements | Please also provide the relevant industry regulations or compliance standards |
Related skills (post-processing chain)
SOPs, operations manuals, meeting minutes, procurement documents, etc. Narrative deliverablesare finalized with the following chain.
collab-process → moai-coworker:ai-slop-reviewer → moai-writer:korean-humanize → 최종 검수
moai-coworker:ai-slop-reviewer— Reviews and revises AI-style patterns in the document body.moai-writer:korean-humanize— Polishes the reviewed body into a natural Korean business writing style.
When not to use this skill
- Drafting legally binding contracts → Requires review by a legal expert. Use moai-lawyer:legal-contract-review together
- Actual order processing or system entry → Requires direct access to the ERP or procurement system
- HR and labor-related procedures → The moai-recruiter:hr-operations skill is more suitable
- Finance and budget approval procedures → Use the moai-coworker skill
References
| File | Load condition |
|---|---|
| references/operations-manual.md | When writing operations manuals (analyze existing documents/code → generate business processes, step-by-step manuals, FAQs, and training materials) |
| references/procurement-docs.md | When preparing procurement documents — from the ordering party's perspective (requirements definition → supplier comparison → evaluation criteria → contract review → acceptance criteria). From the bidder's perspective, the Nara Marketplace guide is moai-coworker:collab-proposal의 references/nara-jangteo.md |
| references/sop-writer.md | When preparing a standard operating procedure (SOP) (process analysis → procedure design → documentation → verification) |
| references/meeting-strategist.md | When establishing a meeting strategy (setting meeting objectives → composing attendees → developing the agenda → planning the proceedings) |