verify-primary-sources

What problem does it solve?

It prevents confident-but-wrong migrations, designs, and security/API decisions caused by relying on secondary summaries that omit critical scope like version, configuration, or migration path.

Core Features & Use Cases

• Secondary sources as leads: Treat agent claims, blog posts, and paraphrased “docs say” statements as pointers that must be validated against the primary material.
• Primary source verification: Fetch the vendor/project’s official documentation, changelog/release notes/migration guide, spec/RFC, or relevant source code to confirm the claim in context.
• Scope-preserving conclusions: Ensure the final recommendation carries the correct qualifiers (which version/mode/API surface/migration path) rather than using an unscoped interpretation.
• First-pass correction: Forces verification on the first research cycle so the next step is not “go fetch the primary source” after a mismatch is discovered.

Quick Start

When you are about to make a design, migration, or security-related decision from a cited claim, ask me to verify it by fetching and reading the primary source and summarizing what it actually supports in the correct scope.