wmasfoe/md-editor / .agents/skills/best-practice-research
best-practice-research
Verified[OMX] Bounded best-practice research wrapper using official/upstream evidence first
Best-Practice Research
Use this skill when a task depends on current external best practices, version-aware guidance, standards, official recommendations, or upstream behavior. This is a workflow wrapper: it routes evidence gathering and synthesis; it is not a new research authority and it does not replace researcher.
Purpose
Produce a cited, reusable best-practice answer or handoff that separates current external evidence from repo-local facts and dependency-selection decisions. For pre-planning investigation, this is the ordinary first research wrapper: gather official/upstream evidence, then hand it to $ralplan or the caller as planning input. Do not present $best-practice-research as a final architecture component or as a validator-gated research loop.
Activate When
- The user asks for best practices, recommended approach, current guidance, official recommendations, standards, or version-aware external behavior.
$ralplan,$deep-interview,$team, or another workflow needs current external evidence before planning or execution can be correct.- The task involves an already chosen technology and needs authoritative usage guidance, migration notes, API behavior, lifecycle rules, or current safety guidance.
Do Not Activate When
- The answer is fully repo-local; use
explorefor codebase facts. - The main question is whether to adopt, replace, upgrade, or compare dependencies; use
dependency-expert. - The user only needs implementation against already-grounded requirements; use
executor,$ralph, or$teamas appropriate. - The task can be answered from stable local project conventions without current external lookup.
Specialist Routing
- Use
explorefirst for brownfield facts: current code usage, local constraints, versions, config, and integration points. - Use
researcherfor official/upstream docs, release notes, standards, migration guides, source-backed examples, and current best-practice evidence for an already chosen technology. - Use
dependency-expertonly for adoption/upgrade/replacement/comparison decisions. - Return to the caller with explicit evidence, uncertainty, and any implementation handoff constraints.
Source-Quality Rules
- Prefer official documentation, upstream source, release notes, changelogs, standards, and maintainer guidance.
- Include source URLs for material claims.
- State date/version context for current best-practice claims.
- Label third-party summaries as supplemental; do not use them before official/upstream sources.
- Flag stale, conflicting, undocumented, or version-mismatched evidence.
- Do not over-fetch: gather the smallest evidence set that can support the decision.
Workflow
- Classify the question: conceptual best practice, implementation guidance, migration/version guidance, standards/compliance guidance, or mixed local + external guidance.
- Gather repo-local facts with
explorewhen local usage or constraints affect the answer. - Gather external evidence with
researcherwhen current or version-aware practice affects correctness. - Synthesize a concise answer with source quality, version/date context, caveats, and an implementation or planning handoff.
- Stop when the answer is grounded enough for the caller; otherwise report the exact blocker or specialist handoff needed.
Output Contract
## Best-Practice Research: <question>
### Direct Recommendation
<actionable guidance or decision support>
### Evidence Used
- Official/upstream: <source URL> — <what it establishes>
- Supplemental, if any: <source URL> — <why it is secondary>
### Version / Date Context
<versions, dates, release channels, or unknowns>
### Repo-Local Context
<facts from explore, or "not needed">
### Boundaries / Non-goals
<what this research does not decide>
### Handoff
<planning/execution/test implications>
Stop Rules
- Stop after a source-backed recommendation is reusable by the caller.
- Stop and route upward if the task becomes dependency comparison, broad architecture, or implementation.
- Do not continue researching when remaining work would only polish wording rather than change the recommendation.
Task: {{ARGUMENTS}}
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 |