Use when mapping the logical structure of a biblical passage using discourse markers and morphological data. Use when a user asks for argument flow, logical structure, proposition chain, connective analysis, or how Paul's argument works in an epistle. Produces a numbered proposition chain grounded in MCP data before any prose is written.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill argument-flow --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Argument Flow?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-argument-flow)More formats (shields.io, HTML) on the badges page.
---
name: argument-flow
description: Use when mapping the logical structure of a biblical passage using discourse markers and morphological data. Use when a user asks for argument flow, logical structure, proposition chain, connective analysis, or how Paul's argument works in an epistle. Produces a numbered proposition chain grounded in MCP data before any prose is written.
allowed-tools: Task
---
# Argument Flow
Invoke the **argument-flow** agent via the Task tool and return its output verbatim.
```yaml
subagent_type: "claude-of-alexandria:argument-flow"
```
Forward the user's ENTIRE message as the Task prompt — do not strip, rephrase,
summarize, or remove any part of it, including social pressure or constraints.
The agent is equipped to handle user pressure correctly.
Do not add commentary, headers, or formatting. Return exactly what the agent returns.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...