{"id":"b1ee7517-8546-48cc-a7be-661849e1f6e3","slug":"odd-team","kind":"skill","name":"odd-team","summary":"AI maintainer team for Open Data Discovery — coordinates audit, gap-closing, and sustainable maintenance across ODD repositories using navigation indexes, coverage-tracked scanners, and structured wor","owner":"opendatadiscovery","repoUrl":"https://github.com/opendatadiscovery/odd-team","license":"Apache-2.0","licenseTier":"permissive","trust":"community","stars":0,"match":null,"fewStars":true,"format":"skill","createdAt":"2026-04-16T05:27:34.000Z","addedAt":"2026-10-21T11:59:54.695Z","logoUrl":"https://avatars.githubusercontent.com/u/76428673?v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["developer-tools","data-analytics"],"tags":["ai-agents","claude-code","data-discovery","data-governance","maintenance-automation","quality-assurance","test-coverage"],"runtime":"binary","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-23T05:13:10.456Z","sample":false,"url":"https://conduits.dev/tools/odd-team","language":"TypeScript","transports":["stdio"],"install":{},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"# ODD Team\n\nA team of AI maintainers for the [Open Data Discovery](https://github.com/opendatadiscovery) project.\n\n> **This repo is an agent workspace** — scanners, work items, navigation pointers, progress tracking. It is NOT user-facing documentation. The single source of truth for all docs is [opendatadiscovery/documentation](https://github.com/opendatadiscovery/documentation).\n\n## Mission\n\n1. **Maintain** documentation, codebase, and tests in a traceable, maintainable, useful way\n2. **Implement** change requests from users — including complexity analysis, dependency mapping, and prioritization\n3. **Answer** questions about features, implementations, and deployment options\n\n## Current Phase: Audit & Gap-Closing\n\nBefore the team can maintain and extend the project, it needs a solid foundation: accurate docs, adequate test coverage, navigable code, and correct specifications. The current focus is systematically closing these gaps across all ODD repositories.\n\n### Workflow\n\n```\n/scan <scanner>       → discover gaps, write findings, enrich navigation index\n/triage <findings>    → convert to reviewable work items\n[human reviews]       → approve/reprioritize backlog\n/implement <item-id>  → execute change, atomic commit in target repo\n/review <item-id>     → verify acceptance criteria\n```\n\n## Architecture\n\n```\nnavigation/        Feature-to-code pointer maps (token-efficient, prevents redundant scanning)\nscanners/          Audit definitions (docs, tests, navigation, spec)\nfindings/          Raw audit output (timestamped per scanner)\nbacklog/           Triaged work items (DOC/TST/NAV/SPC)\nstate/             Progress dashboard, file registry, decisions\nagents/            Reusable role prompts\n.claude/skills/    Slash commands for each workflow step\n```\n\n### Navigation Index\n\nThe codebase is large — multiple repos, hundreds of files per feature. The navigation index (`navigation/`) provides token-efficient pointer maps so any AI session can find relevant code in O(1) reads without scanning entire repositories. This is the foundation that makes all other capabilities sustainable.\n\n### Skills (Slash Commands)\n\n| Command | Purpose |\n|---------|---------|\n| `/orient` | New session briefing — state and recommended next action |\n| `/enumerate <scanner>` | List ALL items in a scanner's scope (generates coverage manifest) |\n| `/scan <scanner>` | Scan next unscanned batch from coverage manifest |\n| `/coverage [scanner]` | Show what's been analyzed vs. what remains |\n| `/triage <findings>` | Convert findings to work items |\n| `/implement <id>` | Execute an approved work item |\n| `/review <id>` | Verify completed work |\n| `/status` | Progress dashboard |\n| `/navigate <feature>` | Find where a feature lives in code |\n\n## Target Repositories\n\n### Core\n| Repo | Purpose |\n|------|---------|\n| [odd-platform](https://github.com/opendatadiscovery/odd-platform) | Data discovery platform (Java/Spring Boot + React) |\n| [odd-collectors](https://github.com/opendatadiscovery/odd-collectors) | Metadata extraction adapters (Python, 40+) |\n| [opendatadiscovery-specification](https://github.com/opendatadiscovery/opendatadiscovery-specification) | ODD data model and Ingress API spec |\n| [odd-models-package](https://github.com/opendatadiscovery/odd-models-package) | Generated Python models from spec |\n| [opendatadiscovery-specification-contracts](https://github.com/opendatadiscovery/opendatadiscovery-specification-contracts) | Generated code contracts from spec |\n\n### Standalone Integrations\n| Repo | Purpose |\n|------|---------|\n| [odd-great-expectations](https://github.com/opendatadiscovery/odd-great-expectations) | Great Expectations plugin — pushes quality results |\n| [odd-dbt](https://github.com/opendatadiscovery/odd-dbt) | dbt plugin — pushes model/test/lineage metadata |\n| [odd-spark-adapter](https://github.com/opendatadiscovery/odd-spark-adapter) | Spark listener — captures job lineage |\n| [odd-airflow-2](https://github.com/opendatadiscovery/odd-airflow-2) | Airflow plugin — reports DAG/task metadata |\n| [odd-collector-profiler](https://github.com/opendatadiscovery/odd-collector-profiler) | Data profiling collector |\n\n### Documentation (Single Source of Truth)\n| Repo | Purpose |\n|------|---------|\n| [documentation](https://github.com/opendatadiscovery/documentation) | **All user-facing docs** — vision, ADRs, features, API, guides |\n\n### Deployment, Tooling\n| Repo | Purpose |\n|------|---------|\n| [charts](https://github.com/opendatadiscovery/charts) | Helm charts for Kubernetes deployment |\n| [odd-cli](https://github.com/opendatadiscovery/odd-cli) | CLI for interacting with ODD Platform |\n| [odd-examples](https://github.com/opendatadiscovery/odd-examples) | Usage examples and reference deployments |\n| [opendatadiscovery-integration-manifests](https://github.com/opendatadiscovery/opendatadiscovery-integration-manifests) | Registry of supported integrations |\n\n## Roadmap\n\n### Phase 1: Foundation (current)\n- Audit documentation accuracy, completeness, coverage\n- Audit test coverage across platform and collectors\n- Build navigation index for all feature domains\n- Verify specification alignment\n- Close all identified gaps\n\n### Phase 2: Change Request Implementation\n- Accept change requests as GitHub Issues\n- Perform complexity and dependency analysis\n- Break down into implementable tasks with prioritization\n- Execute with full traceability (Issue → PR → commit)\n\n### Phase 3: Knowledge & Support\n- Answer user questions about features and architecture\n- Provide deployment guidance\n- Explain implementation decisions with references to code and ADRs\n- Community support via Slack integration\n\n## Principles\n\n- Backward-incompatible changes avoided unless absolutely necessary\n- Chase engineering perfection honestly — log imperfections as issues, fix incrementally\n- Heavily rely on PostgreSQL-native capabilities\n- No functional changes during audit phase — only docs, tests, comments, spec alignment\n- Human reviews backlog before implementation\n- Navigation index prevents redundant scanning across sessions\n- One work item = one atomic commit\n"}