bmad-agent-texas

Orchestrate source extraction, validation, and fallback resolution across providers.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill bmad-agent-texas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-texas
Source: https://github.com/jlenrique/course-DEV-IDE-with-AGENTS/tree/main/skills/bmad-agent-texas
Command: npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill bmad-agent-texas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, python-docx, requests, notion, PyYAML, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Source Wrangler guarantees production runs begin with complete, verified source material by orchestrating extraction, validation, and fallback resolution across multiple providers and reference assets.

Core Features & Use Cases

  • Schematic orchestration: dispatches to retrieval adapters, runs deterministic extraction, and applies immediate quality checks.
  • Cross-reference validation: compares extractions against reference assets to certify completeness or justify fallbacks.
  • Session governance: updates sanctum memory, logs, and provenance to support reproducibility and curation.

Quick Start

Run the Texas wrangling workflow on your directive to ensure every source is complete and validated before production.

Frequently Asked Questions about bmad-agent-texas

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

FAQPage Schema
How do I validate extracted text from PDF and Notion sources before a production run?

Source validation is handled by running cross-reference checks against reference assets, verifying extraction completeness, and applying deterministic fallbacks to ensure production runs begin with complete, verified material.

What's the best way to automate cross-validation for data extraction workflows?

Automated cross-validation compares extracted content directly against reference assets, certifying completeness or justifying deterministic fallbacks while logging provenance to support reproducibility and curation.

How do I extract and standardize outputs from local files, URLs, and Notion pages?

Schematic orchestration dispatches retrieval adapters across local files, URLs, and Notion pages, running deterministic extraction to produce standardized outputs including extracted.md, metadata.json, and extraction-report.yaml.

Does this source wrangling workflow support reproducibility and provenance tracking?

Provenance tracking and reproducibility are supported through session governance, which updates sanctum memory, logs, and provenance records alongside a result envelope for every validated extraction.

When should I use deterministic fallbacks during source material validation?

Deterministic fallbacks are selected when cross-validation against references fails to certify completeness, ensuring the production run continues with verified, standardized source material rather than halting.

Can I use python-docx and pypdf for extracting references across multiple providers?

Yes, the workflow uses pypdf, pdfplumber, and python-docx dependencies to orchestrate extraction across local files, URLs, and Notion pages, dispatching to retrieval adapters for each provider.