systematic-theology

$npx mdskill add Tibsfox/gsd-skill-creator/systematic-theology

Organizes doctrine into coherent structures across theological traditions.

  • Answers queries about specific doctrines and their historical development.
  • Relies on creedal texts, historical sources, and comparative theology.
  • Determines doctrine's place in a tradition's conceptual architecture.
  • Returns structured explanations of doctrine and its systematic context.

SKILL.md

.github/skills/systematic-theologyView on GitHub ↗
---
name: systematic-theology
description: Systematic theology as a method — the organization of doctrine into a coherent structure with defined loci (God, creation, humanity, sin, Christ or analogous figure, salvation, church, last things, where applicable to tradition). Covers creedal formation, the history of doctrine, the distinction between dogmatic and systematic work, and the comparative shape of systematics across Western Christian, Eastern Christian, Jewish, and Islamic traditions. Use when a query asks about a specific doctrine, its historical development, or its place in a tradition's overall conceptual architecture.
type: skill
category: theology
status: stable
origin: tibsfox
modified: false
first_seen: 2026-04-12
first_path: examples/skills/theology/systematic-theology/SKILL.md
superseded_by: null
---
# Systematic Theology

Systematic theology is the attempt to organize what a tradition affirms into a coherent structure, so that each doctrine can be related to every other and the whole can be taught, defended, and revised. This is a methodological claim, not a devotional one. A secular reader can follow the moves of a systematic theologian exactly as a secular reader can follow the moves of a legal scholar arguing from precedent — the internal logic of the system is accessible once the starting premises are laid out.

**Agent affinity:** aquinas (scholastic method, *Summa Theologiae* architecture), augustine (patristic doctrinal framing)

**Concept IDs:** theology-doctrine, theology-historical-context, theology-philosophical-foundations

## 1. Systematic vs. dogmatic vs. biblical theology

These three terms overlap and are sometimes used interchangeably. They are distinct disciplines.

| Discipline | Primary question | Canonical example |
|---|---|---|
| Biblical theology | What do the scriptures themselves teach, read in their historical and literary context? | Von Rad, *Old Testament Theology* |
| Dogmatic theology | What does this specific tradition hold as authoritative doctrine? | Barth, *Church Dogmatics* |
| Systematic theology | How does the whole of doctrine fit together as a coherent conceptual system? | Aquinas, *Summa Theologiae*; Schleiermacher, *The Christian Faith* |

A given theologian may do all three, and they are rarely cleanly separated. But the questions differ. A biblical theologian may resist imposing a later system. A dogmatic theologian may resist philosophical reorganization. A systematic theologian owes an account of how the whole hangs together.

## 2. The standard Christian loci

Western Christian systematic theology, from the high Middle Ages through the twentieth century, typically organizes itself around a set of loci (places, topics). The list varies but this sequence is conventional:

| Locus | Subject |
|---|---|
| Prolegomena | What is theology, what are its sources, what is its method? |
| Theology proper | God — existence, attributes, Trinity |
| Creation | God as source of the world, the created order |
| Anthropology | The human person, the image of God, freedom, the soul |
| Hamartiology | Sin — its origin, nature, and transmission |
| Christology | The person and work of Christ |
| Pneumatology | The Holy Spirit |
| Soteriology | Salvation — how the work of Christ reaches persons |
| Ecclesiology | The church — its nature, marks, ministries, sacraments |
| Eschatology | Last things — death, judgment, resurrection, consummation |

Not every tradition organizes itself this way. Eastern Orthodox theology tends to resist the scholastic locus structure in favor of a more liturgical and apophatic presentation. Anabaptist traditions often foreground ethics and ecclesiology. Liberation theology reorders the sequence to begin with concrete social conditions rather than prolegomena.

## 3. Comparative systematics

Other traditions organize their theological thinking differently.

### Jewish theology

Judaism traditionally prioritizes halakhah (law and practice) over theoretical theology. Systematic doctrinal treatises are rare. Maimonides's *Mishneh Torah* is organized as law; his *Guide of the Perplexed* is organized as philosophy. The Thirteen Principles of Faith, also by Maimonides, are a summary that functioned for later Jewish piety much as a creed functions in Christianity, but the principles were contested from their first promulgation and are not treated as binding in the way a Christian creed is. The "systematic question" in Jewish theology is often "what do you need to assent to in order to be a faithful member of the covenant people?" rather than "what is the coherent architecture of divine being?"

### Islamic theology (*kalam*)

*Kalam* is the Arabic term for theology as dialectical discipline. Classical Islamic theology developed major schools — Mu'tazila, Ash'ari, Maturidi — that argued about the relation of God's attributes to God's essence, the status of the Qur'an (created or uncreated), free will and predestination, and the possibility of seeing God in the next world. These are recognizably systematic questions and generated a literature comparable in sophistication to Christian scholasticism. *Kalam* is distinguished within Islamic learning from *falsafa* (philosophy) and from Sufism (mystical theology); the three sometimes cooperate and sometimes clash.

### Chinese traditions

Confucian and Daoist traditions develop doctrine but not usually as "systematic theology" in the Western sense. The characteristic shape is commentary on a root text — the *Analects*, the *Mencius*, the *Daodejing*, the *Zhuangzi* — through which successive thinkers work out positions. Neo-Confucianism under Zhu Xi and Wang Yangming is as architecturally complex as anything in European scholasticism, and it addresses the same questions (the relation of mind and nature, the status of principle, the grounds of moral action). It just enters the questions through commentary rather than through locus-organized treatise.

## 4. Creedal formation

A creed is a short, authoritative summary of doctrine, typically produced to settle a dispute. The key Christian creeds are:

- **Old Roman Creed** (c. 2nd century) — early baptismal formula that is the ancestor of the Apostles' Creed.
- **Nicene Creed** (325, revised 381) — produced at the Council of Nicaea to settle the Arian controversy (is the Son of the same substance as the Father?), revised at Constantinople to clarify the status of the Holy Spirit.
- **Chalcedonian Definition** (451) — produced at the Council of Chalcedon to settle the question of how the divine and human natures are united in Christ.
- **Athanasian Creed** (5th–6th century) — a Western summary of Trinitarian and Christological orthodoxy.

Reading a creed requires reading the argument it settles. The phrase "of one substance (*homoousios*) with the Father" in the Nicene Creed is doing specific work — it rules out the Arian proposal that the Son is the highest created being and not God in the same sense as the Father. The Chalcedonian definition ("in two natures, without confusion, without change, without division, without separation") is doing specific work — it rules out both the Nestorian account (which separates the natures too much) and the monophysite account (which blends them).

Creeds are therefore the dense midpoint between scripture and systematic theology. They show which distinctions the tradition takes to be settled and which are open.

## 5. The history of doctrine as a discipline

Systematic theology depends on the history of doctrine — the descriptive study of how doctrines have developed over time. Adolf von Harnack's *History of Dogma* (1886–1890) framed the development of Christian doctrine as an increasing Hellenization of a simple original gospel; this "Hellenization thesis" has been much debated and largely qualified but started the discipline in its modern form. Jaroslav Pelikan's *The Christian Tradition* (1971–1989) is the standard five-volume reference work.

For a theology student, the history of doctrine is where the systematic claims are tested against the documentary record. When a contemporary theologian says "the church has always held X," the historian's job is to check. Sometimes the answer is yes. Sometimes it is "it held X from the fourth century on, after a contested earlier period." Sometimes it is "not really."

## 6. The shape of a doctrinal argument

A systematic theologian defending a doctrinal claim typically marshals four kinds of evidence, weighted differently by tradition:

1. **Scripture.** What does the relevant scripture teach, read in its canonical and hermeneutic context?
2. **Tradition.** How has the community of faith understood the claim historically — in creeds, councils, liturgy, and authoritative writers?
3. **Reason.** Is the claim internally coherent and consonant with what else we know?
4. **Experience.** Does the claim fit the lived experience of the community, including its moral and contemplative life?

The Anglican tradition famously names three of these (scripture, tradition, reason) as a triad sometimes called the "Wesleyan quadrilateral" after John Wesley added experience as the fourth. Catholic teaching emphasizes scripture and tradition as two streams of a single deposit, with reason (especially philosophical reason) as a servant and the sensus fidelium (sense of the faithful) as a form of experiential witness. Reformed theology traditionally foregrounds scripture and constrains the others accordingly. Eastern Orthodox theology foregrounds tradition as liturgical and patristic living memory.

None of this is neutral, and a student should notice which weighting the argument they are reading assumes before evaluating it.

## 7. Common mistakes

| Mistake | Why it fails | Fix |
|---|---|---|
| Confusing systematic with biblical theology | The disciplines ask different questions | Specify which mode the argument is in |
| Treating one tradition's system as universal | Doctrinal architecture varies | Name the tradition |
| Ignoring creedal context | Creeds were produced to settle specific disputes | Read the controversy the creed addresses |
| Reading "development" as "improvement" | Development is descriptive, not evaluative | Ask what was lost as well as what was gained |
| Conflating doctrine with devotion | A claim can be doctrinally held without being devotionally central | Separate the two |
| Using contemporary categories anachronistically | The Fathers were not early modern theists | Use the categories the period used |

## 8. Cross-references

- **augustine agent:** Patristic framing of sin, grace, Trinity, and the earthly city.
- **aquinas agent:** Scholastic architecture, analogy, the relation of faith and reason.
- **maimonides agent:** Jewish systematic reflection in the *Guide* and the *Mishneh Torah*.
- **huston-smith agent:** Cross-tradition comparison of doctrinal shapes.
- **philosophical-theology skill:** Natural-theology arguments and metaphysical commitments.
- **scripture-and-interpretation skill:** The exegetical base on which systematic claims rest.
- **ethics-and-practice skill:** The moral and liturgical downstream of systematic commitments.

## 9. References

- Aquinas, T. (c. 1265–1274). *Summa Theologiae*. Multiple modern editions.
- Pelikan, J. (1971–1989). *The Christian Tradition: A History of the Development of Doctrine*. 5 volumes. University of Chicago Press.
- Harnack, A. (1886–1890). *History of Dogma*. 7 volumes.
- Schleiermacher, F. (1830). *The Christian Faith*. 2nd edition.
- Barth, K. (1932–1967). *Church Dogmatics*. T&T Clark.
- Watt, W. M. (1973). *The Formative Period of Islamic Thought*. Edinburgh University Press.
- Maimonides, M. (c. 1180). *Mishneh Torah*.
- Fackenheim, E. (1968). *Quest for Past and Future: Essays in Jewish Theology*. Indiana University Press.

More from Tibsfox/gsd-skill-creator

SkillDescription
3d-interaction-designDesign heuristics for three-dimensional interaction — input modalities (6DoF controllers, gaze, gesture, voice), selection and manipulation techniques (ray-cast, virtual hand, go-go, world-in-miniature), navigation (teleport, continuous, redirected walking), and feedback loops (haptic, audio, visual). Covers Fitts' law in 3D, discoverability vs affordance, safe-zone design, and comfort/simulator sickness mitigation. Use when designing VR/AR interactions, immersive walkthroughs, or any input system where the user's body is the controller.
accessibility-patternsProvides web accessibility best practices for semantic HTML, ARIA, keyboard navigation, color contrast, and screen reader patterns. Use when building UI components, reviewing accessibility, or when user mentions 'a11y', 'accessibility', 'ARIA', 'screen reader', 'keyboard navigation', 'WCAG'.
active-listeningActive listening techniques for effective communication. Covers attending behaviors, paraphrasing, reflective listening, clarifying questions, empathic response, barriers to listening, listening in conflict, and cross-cultural listening. Use when building listening skills, improving understanding in conversation, mediating disputes, or analyzing communication breakdowns.
adversarial-pr-reviewAdversarial spec-compliance PR review — cross-references diffs against approved specs, verifies runtime claims against source, detects competing PRs, audits scope/convention compliance. Use before merging.
agile-methodsAgile and Lean software development methodologies for iterative, adaptive project execution. Covers Scrum (roles, ceremonies, artifacts), Kanban (WIP limits, flow metrics), XP (TDD, pair programming, CI), SAFe overview, Lean Software Development (Poppendieck's 7 principles), user stories (INVEST criteria), estimation via story points and velocity, and the Agile Manifesto's values and principles. Includes Cynefin framework for methodology selection and GSD's relationship to Agile as a structured Lean variant.
algebraic-reasoningSymbolic manipulation, equation solving, and algebraic structures for mathematical reasoning. Covers distributive law, factoring, completing the square, linear through polynomial equation solving, systems of equations (substitution, elimination, Gaussian elimination, matrix methods), algebraic structures (groups, rings, fields), modular arithmetic, polynomial theory, and inequalities. Use when solving equations, simplifying expressions, working with algebraic structures, or performing symbolic manipulation.
algorithmic-awarenessUnderstanding how algorithmic systems shape what users see, know, and do -- from recommendation feeds to search ranking to credit scoring to hiring software. Covers the mechanics of recommendation systems, algorithmic bias and its sources, personalization's effects on information diets, opacity and accountability, AI limitations (hallucination, confident wrongness), and the human-in-the-loop question. Use when a learner needs to think critically about why particular content reached them.
algorithms-data-structuresAlgorithms and data structures from first principles through advanced analysis. Covers sorting (bubble, insertion, selection, merge, quick, heap, radix), searching (linear, binary, BFS, DFS, Dijkstra, A*), fundamental data structures (arrays, linked lists, stacks, queues, hash tables, trees, heaps, graphs, tries), complexity analysis (Big-O, Big-Omega, Big-Theta, amortized), recurrence relations, and algorithm design paradigms (divide-and-conquer, greedy, dynamic programming, backtracking). Use when analyzing, selecting, implementing, or comparing algorithms and data structures.
aminet-browserAminet search and browse: full-text search, category tree navigation, architecture filtering, package detail, and curated collections. Use when searching, browsing, or managing package collections.
aminet-emulatorFS-UAE emulator configuration and launch: hardware profiles, ROM management, WHDLoad integration, config generation, and state snapshots. Use when configuring emulation, managing ROMs, or launching Amiga software.