ssm-analysis
Skill28 starsChanged 8 months agoMITView on GitHub
In this repository105 other files it gives its agents.
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- business-rule-extractorSkill
- catwoe-root-definitionSkill
- constraint-detectorSkill
- critical-thinking-bias-checkSkill
- definition-of-done-drafterSkill
- deliverable-consistency-checkSkill
- edge-case-elicitorSkill
- evidence-gap-reviewSkill
- functional-vs-nonfunctional-splitterSkill
- interview-designSkill
- moscow-prioritisationSkill
- observation-study-planSkill
- pestle-analysisSkill
- porters-five-forcesSkill
- power-interest-gridSkill
- probe-question-generatorSkill
- problem-statement-refinerSkill
- process-modelling-and-improvementSkill
- process-model-specSkill
- proto-requirements-normalizerSkill
- prototype-elicitationSkill
- pyramid-funnel-diamond-interviewerSkill
- questionnaire-designSkill
- questionnaire-pilot-checkerSkill
- raci-matrixSkill
- raci-rasci-builderSkill
- requirements-conflict-checkerSkill
- requirements-elicitationSkill
- requirements-gap-auditorSkill
- requirements-interrogatorSkill
- requirements-packagerSkill
- requirements-prioritizerSkill
- requirements-quality-checkSkill
- requirements-traceability-starterSkill
- see-i-clarifierSkill
- stakeholder-analysisSkill
- stakeholder-communication-plannerSkill
- stakeholder-registerSkill
- strategy-analysisSkill
- swot-prioritisationSkill
- to-be-process-designerSkill
- use-case-specificationSkill
- value-proposition-analysisSkill
- workshop-designSkill
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Prefer evidence-backed conclusions over polished speculation.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Purpose
Apply Soft Systems Methodology for ambiguous, multi-perspective, sociotechnical problems.
Use when
- the situation is messy and contested
- conventional requirements framing is too narrow
- worldview, ownership, and environmental constraints matter heavily
Inputs
- project or problem context
- goals and constraints
- known stakeholders, systems, and documents
- level of formality required
Procedure
- Describe the messy situation without forcing premature structure.
- Produce a rich-picture-oriented summary or prompt.
- Identify relevant purposeful activity systems.
- Perform CATWOE for the most relevant systems.
- Write root definitions.
- Produce conceptual activity models.
- Compare conceptual models to the real world.
- Recommend feasible, desirable changes and open tensions.
Outputs
- messy-situation summary
- rich picture prompt/spec
- CATWOE tables
- root definitions
- conceptual activity model notes
- intervention options
Guardrails
- Explicitly separate fact, inference, and assumption.
- Prefer evidence-backed conclusions over polished speculation.
- Where conflict exists, record it rather than smoothing it away.
- Produce artifacts that can be inspected, edited, and reused.
Completion criteria
- deliverable pack exists
- tradeoffs are explicit
- unknowns are logged
- next decisions are obvious
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

