methodology-pattern-extractorlisted

Extract recurring collaboration patterns from accumulated meeting logs (optionally session JSONL) and record them in docs/methodology.md with evidence of where each was sighted. Use when the user asks to update methodology, extract recurring patterns across the meeting logs, or consolidate recurring collaboration flows; or when five or more meeting logs have accumulated while §Patterns is still empty. Not for writing the meeting logs themselves (session-to-meeting-log) or for parking one-off ideas (backlog-routing-by-topic). Takes no arguments — the fork scans all of `meetings/*.md`.
wei18/apple-dev-skills · ★ 18 · Data & Documents · score 81

Install: claude install-skill wei18/apple-dev-skills

# Methodology Pattern Extractor Runs via [`context: fork`](https://code.claude.com/docs/en/skills#run-skills-in-a-subagent) — the fork has no memory of the invoking conversation, so it rescans `meetings/*.md` fresh each time. ## When to invoke - The user says "update methodology", "extract a pattern", "I feel this flow has happened several times now". - ≥ 5 meeting logs have accumulated but methodology.md §Patterns is still empty. - After hitting an important milestone (end of spec phase, v1 release, major refactor close-out). ## Inputs - All `meetings/*.md` - Corresponding session JSONL (optional, for filling in details) — see `session-to-meeting-log`'s "Locating the session file" for finding the `.jsonl` by id (`ls ~/.claude/projects/*/<sessionId>.jsonl`) rather than computing the project directory; this skill has no `[session-id]` argument, so treat it as best-effort and skip it if the file isn't already known. [Create custom subagents](https://code.claude.com/docs/en/sub-agents) only documents this transcript location for subagent transcripts specifically — treat the general-conversation case as unconfirmed. - The existing `docs/methodology.md` (to avoid duplicate entries) ## Rule: ≥ 3 sightings or it's not a pattern **Don't** turn a one-off behaviour into a pattern. Criteria: - The same triggering situation appears in **≥ 3 different meeting logs** - The response action each time is consistent or convergent - There is an observable outcome Items with