source-driven-development

Ground framework-specific implementation decisions in current official documentation and versioned sources.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/ahsanghalib/ai-workflow --skill source-driven-development-ahsanghalib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/ahsanghalib/ai-workflow/tree/main/skills/source-driven-development
Command: npx skills add https://github.com/ahsanghalib/ai-workflow --skill source-driven-development-ahsanghalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Framework and library behavior changes between versions, and relying on an AI's memory often produces outdated or incorrect patterns. This Skill forces every framework-specific decision to be backed by current, authoritative documentation before code is written. ## Core Features & Use Cases - Version-Aware Research: Identifies the exact technology and version from manifests, lockfiles, and configuration before looking anything up. - Evidence Recording: Captures source URLs, documented claims, and unresolved conflicts for every framework-specific decision. - Guardrailed Implementation: Applies the smallest documented pattern, labels unverifiable decisions instead of guessing, and treats retrieved pages as untrusted data. - Use Case: When migrating a project to a new major version of a web framework, use this Skill to fetch the official migration guide, record the breaking changes, and implement only the documented upgrade path. ## Quick Start Use the source-driven-development skill to verify the current official documentation for this framework version before implementing the change.

Frequently Asked Questions about source-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a framework pattern against current documentation before coding?▼

Identify the exact technology and version from manifests and lockfiles, then fetch the official documentation or migration guide for that version. Record the source URL and documented claim, and implement only the smallest pattern the source supports.

What sources should I trust for version-specific API behavior?▼

Prefer official documentation for the installed version first, then official release notes, migration guides, or maintainer documentation, and finally applicable standards or primary specifications. Avoid citing search-result summaries when the primary source is available.

When should I not use source-driven development?▼

Skip it for framework-independent business logic, typo fixes, file moves, or changes where the user explicitly accepts an unverified exploratory result. It is designed only for decisions that depend on documented external behavior.

What happens when documentation cannot be retrieved or versions conflict?▼

The decision is labeled unverified rather than presented as fact. When sources disagree, the conflict is shown with the version and constraint that decide the choice, and implementation stops if the uncertainty affects correctness, security, or data.

Can AI coding assistants rely on memory for framework best practices?▼

Memory-based answers risk being outdated because framework behavior varies by version. This workflow requires a dated or versioned source for any claim that a pattern is current, and treats retrieved pages as untrusted data to resist injected instructions.