Skip to content
Back to skills

Pathway Organizer

ASecurity

Organize discovered pathway/portal/theme content into the docs repo structure. Copies new files, resolves duplicates, updates the README, and ensures each portal directory has complete coverage. Run after pathway-collector to consolidate content.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 26, 2026
documentationgobash

Security analysis

A100/100

Scanned October 26, 2026

npx -y skills add JoshuaShepherd/my-skills --skill pathway-organizer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pathway Organizer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pathway Organizer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/joshuashepherd-pathway-organizer/badge)](https://www.skillsdirectory.com/skills/joshuashepherd-pathway-organizer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pathway-organizer
description: Organize discovered pathway/portal/theme content into the docs repo structure. Copies new files, resolves duplicates, updates the README, and ensures each portal directory has complete coverage. Run after pathway-collector to consolidate content.
user-invocable: true
allowed-tools: Read, Grep, Glob, Bash, Write, Edit, Agent
---

Organize pathway content into the docs repo: $ARGUMENTS

$ARGUMENTS can specify:
- A portal slug to focus on (reframation, metanoia, mdna, movement-intelligence, forgotten-ways, discipleship)
- A source repo to pull from (e.g., "from movemental-ai")
- "all" to do a full organization pass

If no arguments, perform a full organization across all portals.

---

## Docs Repo Location

`~/Desktop/Dev/repos/docs/`

---

## Target Directory Structure

```
docs/
├── pathways/
│   ├── {portal-slug}/
│   │   ├── vision/          # Strategic/conceptual vision documents
│   │   ├── articles/        # Written content pieces
│   │   ├── case-studies/    # Real-world examples
│   │   └── html-templates/  # HTML/CSS/JS prototypes
│   └── _shared/             # Cross-portal resources
│       ├── christocentric-spine/
│       ├── glossary/
│       └── architecture/
├── knowledge/        # Research, mappings, inventories
│   ├── portal-mappings/
│   ├── inventories/
│   ├── core-content/
│   └── evals/
├── pastoral-warm/           # Pastoral-Warm themed portal content
│   ├── apest/
│   ├── christocentric/
│   ├── disciple-making/
│   ├── formation/
│   ├── kingdom-mission/
│   └── missional-church/
└── reference/               # Design specs, skills, prototypes
    ├── design/
    ├── skills/
    └── stitch-prototypes/
```

---

## Step 1 — Read Current State

1. Read `~/Desktop/Dev/repos/docs/INVENTORY.md` if it exists (produced by `pathway-collector`)
2. Glob the current docs repo to understand what's already organized
3. Identify what's missing or needs updating

---

## Step 2 — Source Mapping

Map content from source repos to docs directory:

| Source Location | Docs Destination |
|----------------|------------------|
| `alan-hirsch/_docs/pathways/*-vision.md` | `pathways/{slug}/vision/` |
| `alan-hirsch/_docs/portal/*.md` | `pathways/_shared/` |
| `alan-hirsch/_docs/PORTAL_MAP_AND_CHRISTOCENTRIC_SPINE.md` | `pathways/_shared/christocentric-spine/` |
| `alan-hirsch/public/html/pathway-templates/*` | `pathways/{slug}/html-templates/` |
| `alan-hirsch/public/html/pathways/*` | `reference/stitch-prototypes/` |
| `alan-hirsch/public/html/site/portals.json` | `pathways/_shared/` |
| `alan-hirsch/_docs/design/PATHWAYS_DESIGN_ALIGNMENT.md` | `reference/design/` |
| `alan-hirsch/_docs/current-ui-overviews/03-pathways.md` | `reference/` |
| `alan-hirsch/.claude/skills/pathway-*` | `reference/skills/` |
| `movemental-ai/_docs/themes-content/knowledge/*` | `knowledge/` |
| `movemental-ai/_docs/themes-content/articles/{theme}/*` | `pathways/{slug}/articles/` |
| `movemental-ai/_docs/themes-content/pastoral-warm/*` | `pastoral-warm/` |
| `adam-seiz/.claude/skills/pathway-*` | `reference/skills/` |

### Article Theme-to-Portal Mapping

| Article Theme Directory | Portal Slug |
|------------------------|-------------|
| `reframation/` | `reframation` |
| `metanoia/` | `metanoia` |
| `forgotten-ways/` | `forgotten-ways` |
| `movement-intelligence/` | `movement-intelligence` |
| `discipleship-disciple-making/` | `discipleship` |
| `apest-fivefold-ministry/` | `mdna` |
| `jesus-is-lord-mdna/` | `mdna` |
| `apest-culture/` | `mdna` |
| `liminality-communitas/` | `forgotten-ways` |
| `missional-incarnational-impulse/` | `movement-intelligence` |
| `organic-systems/` | `movement-intelligence` |

---

## Step 3 — Copy New Content

For each source file:
1. Check if it already exists in the docs repo (by filename)
2. If not, copy it to the correct destination directory
3. If it exists, compare modification dates — keep the newer version
4. Never overwrite without checking

Use `cp` via Bash for file operations. Create directories as needed with `mkdir -p`.

---

## Step 4 — Deduplicate

Some content exists in multiple repos (e.g., pathway-audit skill in both alan-hirsch and adam-seiz). When duplicates are found:
1. Compare content — if identical, keep one and note the duplicate
2. If different versions, keep both with a suffix indicating source (e.g., `pathway-audit-alan-hirsch.md`, `pathway-audit-adam-seiz.md`)
3. Log deduplication decisions

---

## Step 5 — Update README

After organizing, update `~/Desktop/Dev/repos/docs/README.md`:
1. Verify the directory structure section matches reality
2. Update the source repositories table with any new sources
3. Add file counts per section

---

## Step 6 — Generate Per-Portal Index

For each portal, create or update `pathways/{slug}/INDEX.md`:

```markdown
# {Portal Title} — Content Index

## Vision
- [filename](vision/filename.md) — brief description

## Articles (N files)
- [filename](articles/filename.md) — brief description
...

## Case Studies
...

## HTML Templates
...

## Completeness (vs 12-section architecture)
- [x] Overview
- [ ] The Model
- [x] Quotes
...
```

---

## Step 7 — Report

Print a summary of what was organized:
- Files added
- Files updated
- Duplicates resolved
- Gaps remaining per portal

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.