hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/research
research
VerifiedAnswer one cited question on code, history, claims or patterns. Use when: asked how it works, why it changed, if a claim or done/shipped report holds, or a pattern warrants a rule.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.4 KB |
| references/adoption-and-lineage.md | markdown | 2.4 KB |
| references/codebase-recon/codebase-recon.feature | other | 1.8 KB |
| references/codebase-recon/pack-contract.md | markdown | 3.3 KB |
| references/goals.md | markdown | 1.2 KB |
| references/pattern-mining/pack-contract.md | markdown | 2.2 KB |
| references/pattern-mining/pattern-mining.feature | other | 824 B |
| references/research.feature | other | 530 B |
| references/status.md | markdown | 2.0 KB |
| schemas/findings.json | config | 3.3 KB |
| schemas/reality-check-report.v1.schema.json | config | 1.5 KB |
| scripts/claim-audit/validate-output.shexecutable | script | 1.6 KB |
| scripts/codebase-recon/validate-output.shexecutable | script | 19.0 KB |
| scripts/pattern-mining/validate-output.shexecutable | script | 2.1 KB |
| scripts/validate.shexecutable | script | 2.9 KB |
references/adoption-and-lineage.md
View on GitHub# Adoption and decision lineage
Read this for an adoption question or a "why is it like this" question.
Research's [evidence rules](../SKILL.md#evidence-rules) still apply.
## Adoption questions
For "should we adopt, replace or keep X" or "does advisory Y reach us", the
answer needs both sides. Ours: the current tool and a cited place it is used,
or a searched absence plus where X would plug in, and any earlier decision on
the same question. Theirs: a current primary source for each external fact the
answer rests on. A strong side never covers a missing one; then answer "not yet
answerable" and list what to inspect. Keeping the current tool or doing nothing
is a real option. A claim made in the conversation is a lead to check, not
evidence. For a choice that is costly to undo, each decisive claim needs two
independent sources; a vendor page speaks for its own product and is not
independent support. Rank candidates for "what should we use for X" only when
the short list comes from current sources and the criteria are stated or
recoverable; otherwise return what was found and name what is missing.
When the question compares another tool's features with ours, tag each of its
capabilities by source: `code` (their source shows it; cite the `file:line`
you opened and say what the code does, often less than the claim), `docs`
(a README, page or announcement says it; unverified) or `hosted` (a service
you cannot inspect). Only a `code` capability can be recommended for adoption;
a `docs` or `hosted` one stays a gap to verify. Our side of each row cites our
file, or the search command and scope that found nothing. Recommend taking the
pattern in our own terms, not their runtime or storage engine, and hand a
choice that is costly to undo (an architecture fork, a storage or data
migration) to [Plan](../../plan/SKILL.md).
## Decision lineage
For "why is it like this" or "how did this idea change", trace one decision or
idea through commits, ADRs, issues, reviews and prior reports into dated, cited
buckets: first appearance, clearest statement, current form, reversals,
contradictions (two claims that cannot both hold) and abandoned variants. An
empty bucket says what was searched; a supersession is not a contradiction; do
not smooth messy history into a tidy story. Before presenting a past reason as
binding, check that its cause still holds in the current tree or record; if
not, report that as evidence for reopening, leaving the call to its owner or
the caller.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |