write
$
npx mdskill add jongwony/epistemic-protocols/writeDrafts multi-perspective blog posts from session insights.
- Converts analytical sessions into structured publishable content.
- Depends on anamnesis, prothesis, and syneidesis tools.
- Uses iterative refinement and gap detection for quality.
- Delivers finalized drafts ready for publication.
SKILL.md
.github/skills/writeView on GitHub ↗
---
name: write
description: Write blog posts from session insights with material recall and multi-perspective analysis.
skills:
- anamnesis:recollect
- prothesis:frame
- syneidesis:gap
---
# Write Skill
Transform session insights and conceptual explorations into structured, publishable content through multi-perspective analysis and iterative refinement.
Invoke directly with `/write` when the user wants blog drafting from session insights.
## When to Use
Invoke this skill when:
- Converting framework development or analytical sessions into blog posts
- Writing about conceptual topics requiring multi-perspective review
- Structured iterative refinement anticipated
Skip when:
- Technical tutorials with code (standard writing)
- Documentation updates (direct Edit)
- Single-pass content without review need
## Workflow Overview
```
RECOLLECT → PROTHESIS(Context→Perspective→Inquiry→Synthesis) → FORMAT → DRAFT → REFINE → VALIDATE → FINALIZE
```
| Phase | Tool | Decision Point |
|-------|------|----------------|
| Recollect | /recollect protocol | Prior session material recognition |
| Prothesis | /frame protocol | Context-derived perspectives, parallel inquiry |
| Format | AskUserQuestion | Output type, language |
| Draft | Write | — |
| Refine | Edit (loop) | User feedback |
| Validate | /gap | Gap detection |
| Finalize | Edit | — |
## Phase Execution
### 0. Material Recall (/recollect)
Invoke `/recollect` to surface prior session material relevant to the drafting topic — terminology coined in earlier sessions, prior decisions referenced, framings already established. The recalled context enriches the Phase 1-3 context acquisition (`G(U) → C`), improving perspective selection in the multi-perspective analysis.
This phase is conditional: skip silently when the drafting topic has no prior session footprint (e.g., entirely new domain). Anamnesis's internal Phase 0 scan determines applicability.
### 1-3. Prothesis Protocol (Multi-Perspective Analysis)
Apply the Prothesis protocol (/frame) for epistemic analysis:
```
Phase 0: G(U) → C -- Context acquisition from session/topic
Phase 1: C → {P₁...Pₙ}(C) → Pₛ -- Perspectives derived FROM context (not predefined)
Phase 2: Pₛ → ∥I(Pₛ) → R -- Parallel inquiry with Horizon Limits
Phase 3: R → Syn(R) → L -- Synthesis: convergence, divergence, assessment
```
**Key differences from standalone /frame**:
- Continues automatically to Format phase after Synthesis
- Lens L becomes input for content generation
Reference: `prothesis/skills/frame/SKILL.md`
### 4. Format Decision
Present output options:
- Blog Post (Korean/English)
- Essay
- Newsletter
- Thread
### 5. Draft Generation
Write initial draft to `~/.claude/.write/` directory:
- Filename: `YYYY-MM-DD-{topic-slug}.md`
- Structure: Hook → Context → Framework → Application → Implications
### 6. Iterative Refinement
Loop on user feedback:
- Incremental changes → Edit directly
- Structural changes → Generate option versions (A, B, C)
Exit conditions:
- User approval
- Explicit "finalize" command
### 7. Gap Detection
Invoke /gap for final validation:
- Procedural gaps
- Consideration gaps
- Duplicate content
**Composition note**: When /write output is downstream-reviewed by /comment-review, this Phase 7 internal /gap and /comment-review's Scan Step 2 /gap address distinct scopes (internal draft quality here vs. fixation-event decision quality downstream). Both invocations are intentional; the scope distinction preserves the /gap invariant.
### 8. Finalization
Apply final edits. Optionally clean intermediate versions.
## Quality Criteria
| Metric | Limit |
|--------|-------|
| Concepts per section | ≤3 |
| Framework components | ≤5 |
| Abstraction layers | ≤2 |
## Content Transformation
### What Becomes Content
| Session Element | Blog Element |
|-----------------|--------------|
| Problem context | Opening hook |
| Multi-perspective analysis | Framework structure |
| Convergence points | Core thesis |
| Divergence points | Discussion sections |
| Resolution approach | Actionable methodology |
### What Gets Filtered
- Tool invocations, command outputs
- Trial-and-error debugging steps
- Redundant restatements
- Context-specific details (paths, configs)
## Integration
This skill integrates with:
- **/recollect** — Material recall (Phase 0)
- **/frame** — Multi-perspective analysis (Phases 1-3)
- **/gap** — Gap detection (Phase 7)
## Additional Resources
For detailed workflow steps and content transformation rules:
- **`references/workflow.md`** — Complete phase descriptions
More from jongwony/epistemic-protocols
- attendRoute upstream epistemic deficits and evaluate execution-time risks during AI operations. Scans for unresolved upstream protocol needs, materializes intent into tasks, classifies each for risk signals, delegates low-risk tasks to executor, and surfaces elevated-risk findings for user judgment. Type: (ExecutionBlind, User, EVALUATE, ExecutionContext) → SituatedExecution. Alias: Prosoche(προσοχή).
- audit-deltaPeriodic progress-tracking re-run of the c059212d epistemic-protocols audit. Surveys state of audit-derived GitHub issues (#237-#241) and Deterministic Queue items (DQ1-DQ8) via gh CLI, traces commit activity in audit scope files (Track Alpha + Track Beta), scans for emergent audit targets in newly opened issues, and produces a progress report at docs/audit-delta-YYYY-MM-DD.md. Invoke this skill whenever you want to check 'how much of the previous epistemic audit is resolved', 'track audit issue status', 'see what changed in the audit scope since the last run', 'find new audit items', or run /audit-delta. Invoke on demand for weekly-to-monthly audit progress checks. This is a lightweight delta tracker, not a fresh ensemble re-audit.
- boundDefine epistemic boundaries per decision. Produces BoundaryMap classifying domains as user-supplies, AI-proposes, or AI-autonomous when boundary ownership is undefined. Type: (BoundaryUndefined, AI, DEFINE, TaskScope) → DefinedBoundary. Alias: Horismos(ὁρισμός).
- catalogProtocol handbook — instant reference for when to use each epistemic protocol.
- clarify[Deprecated — use /elicit (Euporia) for axis-emergent reverse induction] Clarify intent-expression gaps. Extracts clarified intent when what you mean differs from what you said. Type: (IntentMisarticulated, Hybrid, EXTRACT, Expression) → ClarifiedIntent. Alias: Hermeneia(ἑρμηνεία).
- comment-reviewReview markdown artifacts before fixation (publish/commit/deposit/merge) via /inquire × /gap × /contextualize through a channel-first browser preview loop. User-invoked via /comment-review.
- composeProtocol composition authoring assistant — build composition SKILL.md files from protocol Lego blocks. Validates chains against graph.json, analyzes gate dispositions via the Constitution/Extension classification model, and generates pipeline templates. Use when the user asks to 'compose protocols', 'create composition skill', 'build protocol chain', 'combine protocols', or wants to author a composition workflow like /review.
- contextualizeDetect application-context mismatch after execution. Verifies applicability when correct output may not fit the actual context, producing contextualized execution. Type: (ApplicationDecontextualized, AI, CONTEXTUALIZE, Result) → ContextualizedExecution. Alias: Epharmoge(ἐφαρμογή).
- cursesDiscover the structural costs hidden in your strengths through behavioral dimension analysis, strength-shadow extraction, and attitude recommendations.
- dispatchDelegated parallel issue resolution via /dispatch. User sets a minimal delegation contract (or accepts profile-derived defaults); AI categorizes open issues by project mission/direction (read from the project guide) and evidence-accumulation status (whether substrate-cited locks are satisfied), fans out per-category sub-branches with per-category PRs, then loads review feedback and inscribes rejection traces to the linked issues so a fresh-context next session can re-enter without re-deriving the rejection. Reads the project's profile rule and editing conventions for personalization. Use when the user asks to 'resolve as many open issues as possible', 'process the open backlog', 'work through pending issues', or invokes /dispatch.