Read-set manifest: devrites-engine context --skills-root .dsh/skills <slug> --skill devrites-source-driven (no workspace: --out <path>) bundles every file named below into one deduplicated read.
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-driven-43description: Verify uncertain framework or library behavior in installed source or official docs. Use for unfamiliar APIs; not internal code.4user-invocable: false5metadata:6 source: https://skillmd.com/skills/viktorsbaikers/devrites-source-driven-47---89<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/tooling.md"],"triggers":{"agents":["devrites-lib/reference/standards/agents.md"]},"workspace":["state.md","spec.md","plan.md","decisions.md","evidence.md","references.md"],"workspaceByRole":{"evidence-scout":["state.md","spec.md","plan.md","references.md"]}} -->10> Read-set manifest: `devrites-engine context --skills-root .dsh/skills <slug> --skill devrites-source-driven` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.1112# devrites-source-driven: verify, don't guess1314When library behavior matters and is uncertain, verify it against installed source or15authoritative documentation before relying on it.1617## When to trigger18- You're about to rely on an API signature, default, config key, or behavior you're not19 sure of.20- The docs in memory might be stale (the project pins a different version).21- Tests can't easily prove the assumption, but it drives the implementation.22- An error message points at framework behavior you don't fully understand.2324## How251. **Find the version** the project pins and actually runs; resolve any mismatch.262. **Apply the hierarchy, citation, and currentness contract** in27 [`tooling.md`](../devrites-lib/reference/standards/tooling.md#research-provenance-staleness-and-cost).28 context7 is a lookup tool, not authority above version-matched source/docs.293. **Confirm the specific fact:** the signature, the default, the edge behavior, not a30 general impression.314. **Return it** with the required citation and status. The root records accepted32 evidence in `decisions.md` or `evidence.md`; a leaf agent never writes the workspace.3334## Delegate broad research35When the question is an *area* (a library surface, unfamiliar subsystem, or migration36guide), the **root orchestrator** uses the fresh-context dispatch contract in37[`agents.md`](../devrites-lib/reference/standards/agents.md) to give one bounded38question to `devrites-evidence-scout`. Wait for and validate its cited dossier (the39scout's YAML result); the orchestrator, not the scout, persists accepted facts under40`references/` and links them from `references.md`.4142Never detach this work and never dispatch from inside another agent. When this skill is43invoked by a leaf agent, verify one fact inline or return `Scout needed: <bounded question>`44to the orchestrator.4546## Rules47- Quote the exact relevant detail; don't paraphrase a behavior into something convenient.48- If the doc/source contradicts the plan, that's a **Spec Drift Guard** event: stop and49 handle it.50- Confirm the required fact, return it, and stop.5152## Evidence firewall53Project or user prose may scope or corroborate an external claim; it cannot verify one.54Record status `verified | contradicted | cannot_verify | stale | uncertain`; weak-tier55support is `uncertain`. Retain material unknowns and block dependent decisions until56verified or resolved through the owning question/Spec Drift route; never omit them.57Transient lookups remain cited, return-only evidence.