Writing MangoApps Wiki Articles
Markdown--- name: writing-mangoapps-wiki-articles description: Turns a spoken or written step-by-step process into a formatted MangoApps wiki article. Use when the user describes how to perform a task in MangoApps and wants it documented as a wiki page, or asks to "write a wiki article", "document this process", or "make a how-to for MangoApps". ---
When the user describes a task's steps, immediately draft a wiki article using the template below. If no template has been provided yet, ask for it once, then reuse it for all future articles without asking again.
Default template (use until the user supplies their own):
Markdown# [Task Title]
[1-2 sentence summary of what this article covers and why it matters]
- [Access/permissions needed]
- [Tools or info needed]
- [Step one]
- [Step two]
- [Step three]
- [Any gotchas, exceptions, or best practices]
- [Links to related wiki pages, if any]
Progress:
- Step 1: Confirm/collect the wiki template (ask once if not already provided; reuse thereafter)
- Step 2: Get the task name and a one-line description of its purpose
- Step 3: Collect the step-by-step process from the user (they will describe it)
- Step 4: Ask only for missing essentials (prerequisites, permissions) — don't over-ask
- Step 5: Draft the article, mapping content into the template sections
- Step 6: Present the draft in a MangoApps-ready markdown code block
- Step 7: Revise based on user feedback
Details:
-
Template: If the user hasn't shared a template, use the default above and note "Using default template — share yours if you'd like a different structure." Once a custom template is given, save its structure and apply it to all future articles in the session.
-
Task input: The user is the source of truth for steps — never invent MangoApps functionality or UI details you weren't told. If a step is ambiguous, ask a single clarifying question rather than guessing.
-
Formatting for MangoApps wiki:
- Use
#/##headers (MangoApps wiki supports standard markdown/rich text) - Numbered lists for sequential steps, bullets for non-sequential info
- Bold key UI elements the user mentions (e.g., Settings, Save)
- Keep each step to one action per line
- Add a "Notes/Tips" section for edge cases the user mentions in passing
- Use
-
Output: Always deliver the finished article inside a fenced markdown code block so it can be copy-pasted directly into a MangoApps wiki editor.
Example 1: Input: "Make a wiki on how to submit a timesheet. Steps: go to Time & Attendance, click New Entry, pick the project, enter hours, click Submit."
Output:
Markdown# How to Submit a Timesheet
This article explains how to submit your weekly timesheet in MangoApps.
- Active MangoApps account
- Assigned to a project
- Navigate to Time & Attendance.
- Click New Entry.
- Select the relevant project.
- Enter your hours worked.
- Click Submit.
- Double-check the project selection before submitting — entries can't be edited after submission.
- (add link if available)
**Example 2:**
Input: "Document how to reset a password. Only step I have: go to profile settings and click reset password."
Output: Draft the article with the one known step, and ask: "Is there a step after clicking 'Reset Password' — e.g., checking email or setting a new password — or does that trigger an external flow?" Then finalize once answered.
- Never fabricate MangoApps features, menu names, or button labels — use exactly what the user states.
- Keep steps atomic: one click/action per numbered line.
- Reuse the confirmed template consistently across articles in the same session.
- Bold UI elements to make the article scannable.
- If the user gives steps out of order, reorder them logically before drafting.
- Don't guess at MangoApps UI details not provided by the user.
- Don't skip the Overview/Prerequisites sections even if the user only gives raw steps — infer a short overview from context, but flag it as inferred if unsure.
- Don't re-ask for the template every time once it's been established.
- Don't bury multiple actions in a single numbered step.