Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
Moodle
Defines source-backed Moodle course, role, plugin, integration, assessment, and data administration review, evidence handling, and action boundaries.
Read the fileOverview
Moodle overview
Use this bundle to prepare source-backed Moodle course, role, plugin, integration, assessment, and data administration review and a review-ready Moodle change brief.
Read the fileWorkflow
Moodle source-backed triage
1. State the requested decision or artifact. 2. Inventory evidence: site and Moodle version, environment, course, category, cohort, user, role, and capability; plugins, themes, dependencies.
Read the fileTemplate
Moodle change brief
Review-ready artifact for Moodle course, role, plugin, integration, assessment, and data administration review, evidence quality, verification, and controlled actions.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Moodle
- Teams working in Technology, Business operations
When to use it
- A proposed Moodle configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Prepare a Moodle change brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- Moodle change brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Moodle and produce Moodle change brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with moodledev.io — 5.1 / Apis, then confirm that the reference is current and applicable. Inspect Moodle before drafting.
Context path: bundles/tools/moodle
What the bundle includes
Tools
- Moodle
Frameworks
- source-evidence matrix
- Moodle course, role, plugin, integration, assessment, and data administration review matrix
- qualified-review gate
Evaluations
- Moodle source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Use the listed authoritative sources for general role or tool behavior; local configuration, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for site and Moodle version, environment, course, category, cohort, user, role, and capability; plugins, themes, dependencies, activities, resources, questions, grades, dates, enrollment, completion, web-service functions and tokens, privacy, retention, backup, restore, logs, tests, and approvals.
- Do not infer capability, enrollment, grade, completion, plugin compatibility, course visibility, integration behavior, or learner outcome.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that enroll or message users, change grades or course content, enable web services, issue tokens, install plugins, run upgrades, restore backups, or expose learner data.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.