methodology-pattern-extractorlisted

# Methodology Pattern Extractor ## 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) - 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 fewer than 3 sightings can go into methodology.md §Backlog as "candidate patterns", annotated with the sighting count. ## Output format One entry per pattern, four lines: ```markdown ### <Pattern name> - **Trigger**: <what context activates this pattern> - **Action**: <the observed response action> - **Outcome**: <the resulting outcome> - **Next-time adjust**: <what you'd improve next time, may be empty> - **Sightings**: <meeting log dates ×N, comma-separated> ``` Example: ```markdown ### Section-by-section approval - **Trigger**: User asks Leader to draft a document section (design.md / foundations.md / plan.md) - **Action**: Leader advances one section at a time, waits for OK before moving