Generate FAQ content for: $ARGUMENTS
$ARGUMENTS should include a pathway slug (reframation, metanoia, mdna, movement-intelligence, discipleship) and optionally specific questions to answer or a number of Q&A pairs to produce.
Step 1 — Load Context
- Read the voice spec:
/Users/joshuashepherd/Desktop/Dev/repos/docs/intelligence/leader-research/alan-hirsch/profile/voice-system/ALAN_HIRSCH_VOICE_AND_STYLE_PROMPT.md
- Read the existing pathway vision doc:
/Users/joshuashepherd/Desktop/Dev/repos/docs/pathways/[slug]/vision/ — check if FAQ content already exists
- Read the pathway's existing articles:
/Users/joshuashepherd/Desktop/Dev/repos/docs/pathways/[slug]/articles/
- Read existing QA eval sets if available:
/Users/joshuashepherd/Desktop/Dev/repos/docs/knowledge/evals/qa-sets/
Step 2 — Corpus Research
Book-to-Pathway Map
| Pathway |
Primary Books |
Key Chapters |
| Reframation |
reframation |
ch01–ch18 (especially ch03 Grey Town, ch07 Great Reframation) |
| Metanoia |
metanoia |
ch02 (Metanoi-eh), ch04 (Christo-logic), ch05 (Wholehearted), ch07 (Paradigm) |
| mDNA |
the-forgotten-ways, the-forgotten-ways-handbook |
TFW ch04–ch09 (six elements), Handbook ch01–ch07 |
| Movement Intelligence |
on-the-verge, fast-forward-to-mission |
OTV ch01–ch16 |
| Discipleship |
untamed, disciplism |
Untamed ch01–ch14, Disciplism all |
Books path: /Users/joshuashepherd/Desktop/Dev/repos/docs/books/english/[book-slug]/
Research process:
- Grep for the pathway's core concepts across primary books
- Read 3–5 most relevant chapters
- Extract: definitions, common objections Alan addresses, distinctions he makes, clarifications he offers
- Note direct quotes with citations:
Book Title — ch[N] "[Chapter Title]"
Also check content-library articles for existing definitions:
/Users/joshuashepherd/Desktop/Dev/repos/docs/intelligence/leader-research/alan-hirsch/content/articles/
/Users/joshuashepherd/Desktop/Dev/repos/docs/knowledge/core-content/concept-definitions/
Step 3 — Generate FAQ Content
Requirements
- Minimum 6 Q&A pairs, ideally 8–10
- FAQPage schema compatible — each Q&A must be self-contained and quotable
- GEO-optimized — these are the highest-value surface for AI citation
Question Categories (include at least one from each)
- Term clarification (2–3): "What does [term] actually mean?" / "Isn't [term] just another word for [common equivalent]?"
- Common objection (1–2): "Isn't this just [reductive comparison]?" / "How is this different from [related concept]?"
- Practical application (1–2): "How does [concept] work in a small church?" / "What does this look like in practice?"
- Distortion warning (1): "What does [concept] look like when it goes wrong?" — Alan always names the distortion
- Framework connection (1): "How does [concept] connect to [other Alan Hirsch framework]?"
- Attribution/origin (1): "Who developed [framework]?" / "Where does [term] come from?"
Question Phrasing
- Phrase as a reader would actually ask — natural language, not academic
- Mirror "People Also Ask" patterns from Google
- Include the primary keyword naturally
- Avoid yes/no questions — each should open into explanation
Answer Structure
- 60–150 words each — complete enough to stand alone as a cited answer
- Open with a direct answer in the first sentence
- Then expand with Alan's voice: theological depth, historical example, or framework connection
- Close with forward-building implication — never "as mentioned above"
- Include at least one book reference where the concept is developed further
Answer Ordering
Progress from most common/accessible → deepest/most challenging:
- Start with "What is…" / "What does… mean?"
- Then "How is this different from…" / "Isn't this just…"
- Then practical: "How do you apply…" / "What does this look like…"
- Then deep: "What about [edge case]…" / "What does it look like when it goes wrong?"
Step 4 — Voice
Five Markers (all required)
| Marker |
Weight |
In FAQ Context |
| Christocentric Anchoring |
30% |
Ground answers in Jesus/Kingdom — even definitional answers should connect to Christ |
| Prophetic Intensity |
25% |
Calibrated lower in FAQ — clarity over challenge, but still present in distortion/objection answers |
| Pastoral Warmth |
20% |
"We" language. Invitational. Meet the questioner where they are. |
| Narrative Imagery |
15% |
One story or metaphor per 2–3 answers — don't overload FAQ format |
| Theological Depth |
10% |
Brief but substantive. Etymology, historical notes, Scripture woven when it clarifies. |
Anti-Patterns
- Never "Not X, but Y" — use additive framing
- Never corporate consultant vocabulary
- Never vague: "some scholars suggest…" — be specific
- Never self-referential: "as discussed in the Overview section" — FAQ must stand alone
Output
---
pathway: [slug]
section: faq
qa_count: [number]
books_cited: [list]
voice_check: [pass/flag]
---
**Q1: [Question phrased naturally]**
[Answer — 60–150 words, self-contained, GEO-ready]
**Q2: [Question]**
[Answer]
...
Save to: /Users/joshuashepherd/Desktop/Dev/repos/docs/pathways/[slug]/faq.md
If FAQ content already exists in the vision doc, flag differences and ask before overwriting.
1---2name: pathway-faq3description: Generate FAQ and QA content for an Alan Hirsch pathway page. Produces 6–10 GEO-optimized Q&A pairs grounded in Alan's books, written in his voice, covering common confusions, objections, term clarifications, and distortion warnings. High SEO/GEO value — AI engines cite FAQ pages directly.4user-invocable: true5allowed-tools: Read, Write, Edit, Grep, Glob, Agent6metadata:7 source: https://skillmd.com/skills/joshuashepherd/pathway-faq8---910Generate FAQ content for: $ARGUMENTS1112$ARGUMENTS should include a pathway slug (`reframation`, `metanoia`, `mdna`, `movement-intelligence`, `discipleship`) and optionally specific questions to answer or a number of Q&A pairs to produce.1314---1516## Step 1 — Load Context17181. Read the voice spec: `/Users/joshuashepherd/Desktop/Dev/repos/docs/intelligence/leader-research/alan-hirsch/profile/voice-system/ALAN_HIRSCH_VOICE_AND_STYLE_PROMPT.md`192. Read the existing pathway vision doc: `/Users/joshuashepherd/Desktop/Dev/repos/docs/pathways/[slug]/vision/` — check if FAQ content already exists203. Read the pathway's existing articles: `/Users/joshuashepherd/Desktop/Dev/repos/docs/pathways/[slug]/articles/`214. Read existing QA eval sets if available: `/Users/joshuashepherd/Desktop/Dev/repos/docs/knowledge/evals/qa-sets/`2223---2425## Step 2 — Corpus Research2627### Book-to-Pathway Map2829| Pathway | Primary Books | Key Chapters |30|---------|--------------|--------------|31| **Reframation** | `reframation` | ch01–ch18 (especially ch03 Grey Town, ch07 Great Reframation) |32| **Metanoia** | `metanoia` | ch02 (Metanoi-eh), ch04 (Christo-logic), ch05 (Wholehearted), ch07 (Paradigm) |33| **mDNA** | `the-forgotten-ways`, `the-forgotten-ways-handbook` | TFW ch04–ch09 (six elements), Handbook ch01–ch07 |34| **Movement Intelligence** | `on-the-verge`, `fast-forward-to-mission` | OTV ch01–ch16 |35| **Discipleship** | `untamed`, `disciplism` | Untamed ch01–ch14, Disciplism all |3637Books path: `/Users/joshuashepherd/Desktop/Dev/repos/docs/books/english/[book-slug]/`3839**Research process:**401. Grep for the pathway's core concepts across primary books412. Read 3–5 most relevant chapters423. Extract: definitions, common objections Alan addresses, distinctions he makes, clarifications he offers434. Note direct quotes with citations: `Book Title — ch[N] "[Chapter Title]"`4445Also check content-library articles for existing definitions:46- `/Users/joshuashepherd/Desktop/Dev/repos/docs/intelligence/leader-research/alan-hirsch/content/articles/`47- `/Users/joshuashepherd/Desktop/Dev/repos/docs/knowledge/core-content/concept-definitions/`4849---5051## Step 3 — Generate FAQ Content5253### Requirements5455- **Minimum 6 Q&A pairs**, ideally 8–1056- **FAQPage schema compatible** — each Q&A must be self-contained and quotable57- **GEO-optimized** — these are the highest-value surface for AI citation5859### Question Categories (include at least one from each)60611. **Term clarification** (2–3): "What does [term] actually mean?" / "Isn't [term] just another word for [common equivalent]?"622. **Common objection** (1–2): "Isn't this just [reductive comparison]?" / "How is this different from [related concept]?"633. **Practical application** (1–2): "How does [concept] work in a small church?" / "What does this look like in practice?"644. **Distortion warning** (1): "What does [concept] look like when it goes wrong?" — Alan always names the distortion655. **Framework connection** (1): "How does [concept] connect to [other Alan Hirsch framework]?"666. **Attribution/origin** (1): "Who developed [framework]?" / "Where does [term] come from?"6768### Question Phrasing69- Phrase as a reader would actually ask — natural language, not academic70- Mirror "People Also Ask" patterns from Google71- Include the primary keyword naturally72- Avoid yes/no questions — each should open into explanation7374### Answer Structure75- **60–150 words each** — complete enough to stand alone as a cited answer76- Open with a direct answer in the first sentence77- Then expand with Alan's voice: theological depth, historical example, or framework connection78- Close with forward-building implication — never "as mentioned above"79- Include at least one book reference where the concept is developed further8081### Answer Ordering82Progress from most common/accessible → deepest/most challenging:831. Start with "What is…" / "What does… mean?"842. Then "How is this different from…" / "Isn't this just…"853. Then practical: "How do you apply…" / "What does this look like…"864. Then deep: "What about [edge case]…" / "What does it look like when it goes wrong?"8788---8990## Step 4 — Voice9192### Five Markers (all required)9394| Marker | Weight | In FAQ Context |95|--------|--------|----------------|96| **Christocentric Anchoring** | 30% | Ground answers in Jesus/Kingdom — even definitional answers should connect to Christ |97| **Prophetic Intensity** | 25% | Calibrated lower in FAQ — clarity over challenge, but still present in distortion/objection answers |98| **Pastoral Warmth** | 20% | "We" language. Invitational. Meet the questioner where they are. |99| **Narrative Imagery** | 15% | One story or metaphor per 2–3 answers — don't overload FAQ format |100| **Theological Depth** | 10% | Brief but substantive. Etymology, historical notes, Scripture woven when it clarifies. |101102### Anti-Patterns103- Never "Not X, but Y" — use additive framing104- Never corporate consultant vocabulary105- Never vague: "some scholars suggest…" — be specific106- Never self-referential: "as discussed in the Overview section" — FAQ must stand alone107108---109110## Output111112```113---114pathway: [slug]115section: faq116qa_count: [number]117books_cited: [list]118voice_check: [pass/flag]119---120121**Q1: [Question phrased naturally]**122[Answer — 60–150 words, self-contained, GEO-ready]123124**Q2: [Question]**125[Answer]126127...128```129130Save to: `/Users/joshuashepherd/Desktop/Dev/repos/docs/pathways/[slug]/faq.md`131132If FAQ content already exists in the vision doc, flag differences and ask before overwriting.