assimilate-popular-workflows

# Assimilate Popular Workflows Search public GitHub repositories for SKILL.md files, classify each repo by archetype, and maintain structured research documents under `docs/reference-repos/[org]/[repo-name]/`. The goal is not to copy skills verbatim but to extract transferable value: processes for the babysitter process library, babysitter marketplace plugin ideas, and implicit procedural knowledge that can be codified into babysitter JS processes. ### Process Library Placement Rules Extracted processes go into the babysitter process library (`library/`). Placement depends on scope: | What it is | Where it goes | Examples | |------------|---------------|---------| | Full generic dev methodology (entire workflow paradigm) | `methodologies/<name>/` | agile, gsd, tdd, scrum, kanban, waterfall | | Common cross-domain pattern (reusable across many specializations) | `specializations/shared/` | audit-pipeline, expert-advisory, progressive-disclosure | | Domain-specific process | `specializations/<domain>/` | security-compliance, devops-sre-platform, data-science-ml | **Important**: Do NOT place domain-specific processes in `methodologies/`. Only full, generic development methodologies belong there. A "k8s security audit" is `specializations/security-compliance/`, not a methodology. A "deep research pipeline" is `specializations/shared/` (cross-domain). A "TDD agent workflow" is `methodologies/atdd-tdd/` (full dev methodology). ### Plugin Ideas = Babysitter Marketplace Plugins...