ecosystem-intake

You can triage ecosystem signals into an actionable backlog by automating the classification of curated sources, upstream repos, and release notes into adopt, adapt, or reject candidates. The process applies structured scoring guardrails to generate ready-to-action backlog outputs.

Automated backlog triage for upstream repositories is the process of reading ecosystem inputs via GitHub MCP and applying decision criteria to score them. It categorizes new commands, hooks, or skills into structured adopt, adapt, or reject backlog candidates for project management.

You can track triage decisions and candidate scores using SQL by storing the structured intake passes in a SQL-backed tracking system. This enables you to monitor candidates, review scoring data, and maintain a persistent record of adopt, adapt, or reject decisions across multiple triage passes.

Yes, you can use GitHub MCP to read and triage upstream release notes. The tool leverages GitHub-native intake through MCP and web fetch capabilities to read the upstream state of repositories, enabling a read-and-triage workflow for monitoring new ecosystem updates.

No, automated ecosystem intake does not require external dependencies to run. The skill operates independently to apply structured intake, scoring, and backlog generation requirements with built-in guardrails and clear decision criteria for evaluating ecosystem inputs.