Source Grounding

Source Grounding

Use sources when correctness depends on current or version-specific behavior. Local code is the primary source for this repo; official docs are the primary source for external APIs and frameworks.

Process

1. Detect the version and surface:

• package lock, config, imports, CLI output, SDK version
• runtime, framework, database, provider, or protocol

1. Choose source tier:

• repo source and tests for local behavior
• official docs or API reference for external behavior
• release notes or migration guides for version changes
• source code/types when docs are incomplete

1. Record a source note:

• claim
• source path or URL
• version/date if available
• confidence
• what remains unverified

1. Apply the finding narrowly:

• update the plan, phase brief, implementation, or review package
• do not paste long docs into artifacts
• mark any unsourced assumption explicitly

Source Note

## Source Grounding

Claim: {behavior or API decision}
Source: {repo path, official docs URL, type definition, release note}
Version: {detected version or unknown}
Confidence: {high | medium | low}
Unverified: {none or remaining uncertainty}

Red Flags

• Using remembered API syntax for a library version not checked locally.
• Treating blog posts or examples as authoritative over official docs.
• Ignoring local wrappers or project conventions.
• Updating code from docs without checking installed version.
• "Probably works" appears in a plan, review, or completion claim.

Verification

• [ ] Version or local source was checked when relevant.
• [ ] External claims use official or primary sources.
• [ ] Unverified assumptions are labeled.
• [ ] The final artifact cites the source note briefly.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: danielleit241
• Source: danielleit241/forge
• License: ISC

Install and usage instructions live in the source repository linked above.