# Super Collect

Find problems in one project, verify each, write one findings doc and hand it to Matt...

- Repository: https://github.com/EricTechPro/super-board (577 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add EricTechPro/super-board --skill super-collect -g -a claude-code -y`
Codex: `npx skills add EricTechPro/super-board --skill super-collect -g -a codex -y`
Cursor: `npx skills add EricTechPro/super-board --skill super-collect -g -a cursor -y`
Gemini CLI: `npx skills add EricTechPro/super-board --skill super-collect -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add EricTechPro/super-board`

## Description

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".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# super-collect, find problems, hand them to the planning chain

One job: find problems and turn them into tickets. The flow:

1. Collect candidates from the sources.
2. One fresh verifier checks each candidate.
3. Write ONE findings doc that groups what survived: `docs/super-board/findings/collect-<YYYY-MM-DD>.md`.
4. `/to-spec` turns the findings doc into a spec.
5. `/to-tickets` turns the spec into tickets.
6. Build fork: **1, 5 tickets → `/implement-spec`** (one session, no QA lane). **6+ tickets →
   super-board**: each ticket goes to **Backlog**, then `/super-board lint` and `run`.

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](../../docs/super-board/routing.md).

## 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](references/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.

## Setup

The rest: https://github.com/EricTechPro/super-board/blob/HEAD/skills/super-collect/SKILL.md