skills.rest
zxyycom
zxyycomCOMMUNITY
Explore all skills by this author →
GitHub

source-driven-development

Detect stack dependencies from manifest files and lockfiles, then assemble citation-backed decision plans.

Updated Jun 4, 2026
Search Tags:#documentation#verification#citation#conflict-resolution#dependency-check#version-detection#source-driven
One-click install
npx skills add https://github.com/zxyycom/docnav --skill source-driven-development-zxyycom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/zxyycom/docnav/tree/main/.codex/skills/source-driven-development
Command: npx skills add https://github.com/zxyycom/docnav --skill source-driven-development-zxyycom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces evidence-based decision making by requiring official sources and citations for technical decisions across frameworks, libraries, APIs, and correctness-sensitive implementations.

Core Features & Use Cases

  • Systematically detects the dependency stack from manifest and lockfiles.
  • Prioritizes primary sources (official documentation, migration guides, web standards, and compatibility data) and surfaces precise citations.
  • Handles source conflicts and flags unverified claims to maintain transparency and auditability.
  • Ideal for engineering teams working on critical integrations and API correctness where traceability is essential.

Quick Start

Analyze the given project, fetch official sources for each decision, and produce a cited implementation plan.

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 dependency versions and API signatures using official documentation?▼

To verify dependency versions, this skill detects the stack from manifest files and lockfiles, then extracts API signatures, version constraints, and deprecations from official documentation to produce cited implementation plans.

What is the best way to resolve conflicts between different technical sources during implementation?▼

Source conflict resolution involves prioritizing primary sources like official documentation and migration guides, flagging unverified claims, and maintaining transparency to ensure decisions remain auditable and traceable.

How do I generate a citation-backed decision plan for critical API integrations?▼

Generating a citation-backed decision plan requires analyzing the project manifests, fetching authoritative sources for detected technologies, and assembling precise citations for frameworks, libraries, and APIs.

Why do I need official sources for framework migration and dependency checks?▼

You need official sources for framework migration and dependency checks to enforce evidence-based decision making, ensuring correctness-sensitive implementations rely on verified web standards and compatibility data.

Does this approach work with existing manifest and lockfiles in my project?▼

Yes, this approach systematically detects the dependency stack directly from your existing project manifest and lockfiles to identify detected technologies and extract relevant migration notes.

When should I not use source-driven development for technical decisions?▼

You should avoid source-driven development when traceability and auditability are not required, as it enforces evidence-based decisions by requiring official sources and citations for technical implementations.

Related Skills

Explore More Software Engineering Skills→
Z-M-HuangZ-M-Huang
14

vcp-dependency-check

Validate project dependencies against VCP dependency-management standards.

Community
Advanced
dobrinz123dobrinz123

gsd-analyze-dependencies

Analyze phase graphs to detect dependency conflicts and update ROADMAP.md.

Community
Intermediate
a35506322a35506322

microsoft-code-reference

Verify Microsoft SDK and .NET API signatures against official documentation.

Community
Intermediate
hamzaPixlhamzaPixl
2

security-scan

Scan code repositories and container images for secrets, OWASP Top 10 vulnerabilities, dependency CVEs, and RBAC misconfigurations.

Community
Intermediate