devrites-source-driven: verify, don't guess
When library behavior matters and is uncertain, verify it against installed source or
authoritative documentation before relying on it.
When to trigger
- You're about to rely on an API signature, default, config key, or behavior you're not
sure of.
- The docs in memory might be stale (the project pins a different version).
- Tests can't easily prove the assumption, but it drives the implementation.
- An error message points at framework behavior you don't fully understand.
How
- Find the version the project pins and actually runs; resolve any mismatch.
- Apply the hierarchy, citation, and currentness contract in
tooling.md.
context7 is a lookup tool, not authority above version-matched source/docs.
- Confirm the specific fact: the signature, the default, the edge behavior, not a
general impression.
- Return it with the required citation and status. The root records accepted
evidence in
decisions.md or evidence.md; a leaf agent never writes the workspace.
Delegate broad research
When the question is an area (a library surface, unfamiliar subsystem, or migration
guide), the root orchestrator uses the fresh-context dispatch contract in
agents.md to give one bounded
question to devrites-evidence-scout. Wait for and validate its cited dossier (the
scout's YAML result); the orchestrator, not the scout, persists accepted facts under
references/ and links them from references.md.
Never detach this work and never dispatch from inside another agent. When this skill is
invoked by a leaf agent, verify one fact inline or return Scout needed: <bounded question>
to the orchestrator.
Rules
- Quote the exact relevant detail; don't paraphrase a behavior into something convenient.
- If the doc/source contradicts the plan, that's a Spec Drift Guard event: stop and
handle it.
- Confirm the required fact, return it, and stop.
Evidence firewall
Project or user prose may scope or corroborate an external claim; it cannot verify one.
Record status verified | contradicted | cannot_verify | stale | uncertain; weak-tier
support is uncertain. Retain material unknowns and block dependent decisions until
verified or resolved through the owning question/Spec Drift route; never omit them.
Transient lookups remain cited, return-only evidence.
1---2name: devrites-source-driven3description: Verify uncertain framework or library behavior in installed source or official docs. Use for unfamiliar APIs; not internal code.4---56# devrites-source-driven: verify, don't guess78When library behavior matters and is uncertain, verify it against installed source or9authoritative documentation before relying on it.1011## When to trigger12- You're about to rely on an API signature, default, config key, or behavior you're not13 sure of.14- The docs in memory might be stale (the project pins a different version).15- Tests can't easily prove the assumption, but it drives the implementation.16- An error message points at framework behavior you don't fully understand.1718## How191. **Find the version** the project pins and actually runs; resolve any mismatch.202. **Apply the hierarchy, citation, and currentness contract** in21 [`tooling.md`](../devrites-lib/reference/standards/tooling.md#research-provenance-staleness-and-cost).22 context7 is a lookup tool, not authority above version-matched source/docs.233. **Confirm the specific fact:** the signature, the default, the edge behavior, not a24 general impression.254. **Return it** with the required citation and status. The root records accepted26 evidence in `decisions.md` or `evidence.md`; a leaf agent never writes the workspace.2728## Delegate broad research29When the question is an *area* (a library surface, unfamiliar subsystem, or migration30guide), the **root orchestrator** uses the fresh-context dispatch contract in31[`agents.md`](../devrites-lib/reference/standards/agents.md) to give one bounded32question to `devrites-evidence-scout`. Wait for and validate its cited dossier (the33scout's YAML result); the orchestrator, not the scout, persists accepted facts under34`references/` and links them from `references.md`.3536Never detach this work and never dispatch from inside another agent. When this skill is37invoked by a leaf agent, verify one fact inline or return `Scout needed: <bounded question>`38to the orchestrator.3940## Rules41- Quote the exact relevant detail; don't paraphrase a behavior into something convenient.42- If the doc/source contradicts the plan, that's a **Spec Drift Guard** event: stop and43 handle it.44- Confirm the required fact, return it, and stop.4546## Evidence firewall47Project or user prose may scope or corroborate an external claim; it cannot verify one.48Record status `verified | contradicted | cannot_verify | stale | uncertain`; weak-tier49support is `uncertain`. Retain material unknowns and block dependent decisions until50verified or resolved through the owning question/Spec Drift route; never omit them.51Transient lookups remain cited, return-only evidence.
ViktorsBaikers