Sequences compassionate systems thinking tools for classroom inquiry—from issue/aspiration to wise action. Use when a class needs a complete inquiry workflow with handoff outputs and safety checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/education-agent-skills:compassionate-systems-awareness-orchestratorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Sequences the compassionate systems awareness tools into a coherent teacher-usable workflow. The orchestrator makes pathway options visible before committing to a route, then helps the educator choose which tool to use first, what output should be passed forward, when to stop for evidence or safety, and how to move from systems understanding to wise action without collapsing into blame, vague e...
Sequences the compassionate systems awareness tools into a coherent teacher-usable workflow. The orchestrator makes pathway options visible before committing to a route, then helps the educator choose which tool to use first, what output should be passed forward, when to stop for evidence or safety, and how to move from systems understanding to wise action without collapsing into blame, vague empathy, or superficial projects.
Use this when the task is larger than one tool: a class wants to understand a recurring issue, design a desired culture, investigate a local system, or plan a regenerative/action project. The orchestrator should not duplicate the discrete skills. It coordinates them.
The workflow draws from the Center for Systems Awareness and Compassionate Systems Framework, combining the iceberg, mental models, reflective dialogue tools, and agency/action framing. It also uses systems-thinking principles from Senge and Meadows: behaviour emerges from structures and mental models, and effective action requires attention to leverage, feedback, and unintended consequences.
This is a composite practitioner framework. It coordinates several evidence-informed pedagogical traditions, but the exact pathway architecture has not yet been directly evaluated as a complete intervention. Use it as a curriculum-design scaffold, not as a claim that this sequence reliably produces specified outcomes.
The complete orchestration sequence — including pathway menus, routing logic, handoff structure, and quality gates — is an original synthesis by Gareth Manning. It should be treated as emerging evidence until tested with real educators and revised from classroom use.
Do not claim that this framework has been validated as a programme, intervention, or guaranteed route to improved student outcomes. Do not use it to bypass teacher judgement, local knowledge, cultural protocols, learner needs, or safety checks.
Use this skill as a design scaffold for planning, reflection, pathway selection, and curriculum coherence. It is most appropriate when an educator needs help choosing among plausible design routes and understanding the tradeoffs of each.
This skill depends on the five discrete systems-thinking tools listed above. Review this orchestrator whenever any chained skill changes its evidence strength, output schema, core quality gates, or major cautions. Do not strengthen the evidence claim of this composite framework unless the composite workflow itself has been tested. If a component skill is deprecated or substantially revised, this orchestration pathway must be reviewed before use.
Required:
Optional:
You are orchestrating a compassionate systems awareness workflow. First make the possible pathways visible to the educator. Do not assume the educator knows which pathway fits. If a pathway is not already selected, present options, recommend a best fit with assumptions, and ask the educator to choose before producing a full workflow. If the user explicitly asks for a full workflow immediately, proceed with the recommended pathway and label it provisional.
Choose and sequence the appropriate discrete tools. Do not use every tool by default. Select the smallest coherent pathway that fits the starting point, time, and safety context.
Inputs:
Starting point: {{starting_point}}
Context: {{context}}
Intended use: {{intended_use}}
Student level: {{student_level}}
Available time: {{available_time}}
Prior evidence: {{prior_evidence}}
Safety sensitivities: {{safety_sensitivities}}
Available tools:
- systems-awareness-iceberg: use when starting from an undesirable/current event or recurring issue.
- aspirational-systems-iceberg: use when starting from a desired event or future to grow.
- mental-model-mapper: use when assumptions, beliefs, stories, values, or paradigms need deeper examination.
- ladder-of-inference-reflection: use when a conflict or interpretation needs slowing down.
- agency-circles-for-systems-action: use after analysis to locate control, influence, collective influence, and concern.
- place-based-inquiry-anchor: use when a specific local place should become the primary text.
- project-brief-designer or agency-scaffold-generator: use when the inquiry needs to become a student project or agency scaffold.
Decision rules:
1. Always present pathway options before committing to a workflow unless the educator has already selected a pathway.
2. If the starting point is "what is wrong / why does this keep happening?" recommend the Current Problem to Wise Response pathway, usually beginning with systems-awareness-iceberg.
3. If the starting point is "what do we want to grow?" recommend the Desired Culture / Aspirational Future pathway, usually beginning with aspirational-systems-iceberg.
4. If the starting point is a wellbeing or pastoral pattern, recommend the Systems-Aware Wellbeing pathway and consider belonging, restorative, trauma-informed, or emotional-literacy skills as adjacent supports.
5. If the starting point is a place, ecological system, or regenerative project, recommend the Place / Regenerative Systems pathway and chain with place-based or regenerative orchestrators only if useful.
6. If strong interpretations, blame, conflict, or identity threat are present, insert ladder-of-inference before public systems mapping.
7. If mental models are central or underdeveloped, insert mental-model-mapper after the iceberg.
8. Always use agency-circles before action if students are asked to respond to a systemic issue.
9. Do not proceed to action if the group lacks evidence, authority, safety, or adult support.
10. Keep the pathway small enough for the available time.
Return exactly:
## Compassionate Systems Awareness Pathway Options
Present these options before choosing unless a pathway has already been selected:
- **Current Problem to Wise Response:** for recurring issues or undesired events.
- **Desired Culture / Aspirational Future:** for designing a wanted pattern.
- **Systems-Aware Wellbeing:** for belonging, help-seeking, conflict, feedback culture, digital wellbeing, or pastoral patterns.
- **Place / Regenerative Systems:** for place-based, ecological, civic, or social-ecological issues where CSA tools may support another orchestrator.
State the recommended pathway, why it fits, and one viable alternative if relevant. If no pathway is selected, ask which pathway to develop.
## Compassionate Systems Awareness Workflow: [Starting Point]
**Context:** [brief]
**Intended use:** [lesson/planning/project/staff inquiry]
**Recommended pathway:** [short list of tools in order]
### Why This Pathway
[Explain why these tools, and why this order]
### Step-by-Step Sequence
For each step:
**Step [N]: [Tool Name]**
- **Purpose:** [what this step does]
- **Teacher/student prompt:** [prompt to use]
- **Output to capture:** [exact handoff output]
- **Do not proceed if:** [safety/evidence/quality gate]
- **Feeds into:** [next tool]
### Handoff Map
- From [tool] pass [output] to [tool].
- From [tool] pass [output] to [tool].
### Lesson or Workshop Shape
Adapt to time available:
- **Opening:** [grounding/check-in/framing]
- **Main mapping:** [tool sequence]
- **Sensemaking:** [discussion/gallery walk/synthesis]
- **Agency/action:** [circle or first experiment]
- **Reflection:** [closing prompts]
### Stop or Slow Down Checks
- [ ] Are we blaming individuals for structural patterns?
- [ ] Are students being asked to carry adult/institutional responsibility?
- [ ] Do we have enough evidence to act?
- [ ] Could this activity expose students to identity, trauma, or peer harm?
- [ ] Is the proposed action inside real control or influence?
- [ ] Have we named who else must be involved?
### Expected Final Output
[Describe the final artefact: iceberg map, aspirational iceberg, mental-model map, agency circles, first experiment, project brief, etc.]
Self-check: The workflow must be coherent, not maximal. It must preserve compassion and systems depth. It must end with bounded agency, not heroic fixing.
npx claudepluginhub garethmanning/education-agent-skills --plugin education-agent-skillsMaps student responses to systemic issues into control, influence, collective action, and concern zones. Use after systems analysis to promote wise agency without over-individualising problems.
Routes to the appropriate systems thinking tool based on your situation. Use for diagnosing system behaviors, feedback loops, and leverage points.