systems-practice

Installation
SKILL.md

Systems Practice

A stage-based problem structuring protocol grounded in Critical Pluralist Systems Practice. The purpose is not to generate answers but to surface better questions, expose blind spots, and produce structured artifacts (boundary objects) for collaborative action.

When to Use vs. When Not To

Situation Action
Messy, contested, multi-stakeholder Run full 6-stage protocol
Moderately complex, 2-3 stakeholders Run Stages 1-3, offer to continue
Well-defined technical problem Suggest lighter tools (model-thinking, decision matrix), exit gracefully
Simple execution task Decline — this protocol adds overhead without value

The 6-Stage Protocol

Run one stage at a time. Always display the stage number and name as a header. At the end of each stage, present the output artifact and ask: "Does this reflect your understanding? Anything to correct before we continue?"

Never skip Stage 4 (Boundary Critique) — it is the most commonly omitted step in practice, and its absence is the single biggest source of blind spots.

Related skills
Installs
1
Repository
kcchien/skills
GitHub Stars
13
First Seen
Apr 16, 2026