Super Collect
Find problems in one project, verify each, write one findings doc and hand it to Matt...
Install
npx skills add EricTechPro/super-board --skill super-collect -g -a claude-code -y- Repository
- EricTechPro/super-board577
- Category
- AI and agents
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Find problems in one project, verify each, write one findings doc and hand it to Matt Pocock's /to-spec then /to-tickets; 1, 5 tickets go to /implement-spec, 6+ to the super-board Backlog (no /to-spec or /to-tickets installed → files straight into Backlog). Source plug-ins - sentry (app errors), posthog (exceptions, rage/dead clicks, failure events, web vitals, tracking gaps), github (issues not on the board), prs (recurring problems in merged PRs and their review comments), architecture (refactor findings), plus any custom source added in onboard (an MCP server, HTTP API, CLI command or app). Each candidate is checked by one fresh verifier first. Dry-run by default. Use when the user says "super-collect", "/super-collect", "/super-collect sentry", "collect tickets", "triage errors onto the board", "what keeps breaking", or "find refactors".
super-collect, find problems, hand them to the planning chain
One job: find problems and turn them into tickets. The flow:
- Collect candidates from the sources.
- One fresh verifier checks each candidate.
- Write ONE findings doc that groups what survived:
docs/super-board/findings/collect-<YYYY-MM-DD>.md. /to-specturns the findings doc into a spec./to-ticketsturns the spec into tickets.- Build fork: 1, 5 tickets →
/implement-spec(one session, no QA lane). 6+ tickets → super-board: each ticket goes to Backlog, then/super-board lintandrun.
No /to-spec or /to-tickets in this project → file each finding straight into Backlog
(today's path, "Filing" below) and print why. super-collect never edits app code and never
moves a card to Ready. Per project only: it reads the active project's super-board config and
files onto that project's board. The whole rule in plain words:
routing.
Invocation
| Command | Does |
|---|---|
/super-collect | every source enabled in collect.sources |
/super-collect <source> [<source>…] | just those: sentry, posthog, github, prs, architecture, or a custom source's name |
--since 30d / --since 2026-09-01 | window; default collect.window_days, else 14 days |
--yes | write and file without the confirm step (never skips verify or dedupe) |
--direct | skip the planning chain: file each finding straight into Backlog |
Default is dry-run: show the findings doc and the route, write nothing, go on only on confirm.
Scheduler integration
For periodic intake, use scheduled-intake.md: let the owner's scheduler invoke this existing skill, retain source verification and holding-column-only filing, and notify only on meaningful changes or failures. No job, cadence or scheduler is created by this skill.
