Enforce an Evidence-Loop Development workflow with Sense/Model/Predict/Change/Ground/Record phases.
npx skills add https://github.com/CAPHTECH/claude-marketplace --skill eld
Please help me install this Agent Skill. Skill: eld Source: https://github.com/CAPHTECH/claude-marketplace/tree/main/caphtech-plugin/skills/eld Command: npx skills add https://github.com/CAPHTECH/claude-marketplace --skill eld
Evidence-Loop Development (ELD) unifies code understanding as an interconnected graph of meaning, enabling minimal, verifiable changes guided by Law/Term constraints.
Use this Skill to begin an ELD loop on a new feature: "Implement new auth flow with ELD guidance."
High-intent search queries and answers about installing and using this skill.
Evidence-Loop Development structures code changes through interconnected phases—Sense, Model, Predict, Change, Ground, Record—that collect and validate evidence from code, tests, and telemetry. Each phase produces artifacts like Issue Contracts, Law/Term Cards, and Evidence Packs that enforce constraints and create auditable decision trails for minimal, verifiable changes.
Law/Term Cards map domain concepts to enforceable constraints during development. They define vocabulary boundaries, invariants, and pre/post conditions that guide feature work and refactors. Cards link directly to code evidence, creating a structured knowledge memory that prevents constraint violations across changes.
Yes. ELD applies to feature implementations, bug fixes, and refactors across software projects. It governs the full workflow—from sensing the problem through grounding changes in test and telemetry evidence—ensuring all modifications satisfy functional requirements and maintain invariants regardless of task type.
ELD enforces minimal-change and pure/IO separation principles by requiring changes to be grounded in collected evidence and validated against Law/Term constraints before recording. The Change phase produces only modifications necessary to satisfy verified requirements, reducing unintended side effects.
An ELD cycle produces Issue Contracts defining requirements, Law/Term Cards encoding constraints, Link Maps connecting evidence sources, Grounding Plans specifying test and telemetry validation, and Evidence Packs documenting the complete decision trail for audit and review.
No. Evidence-Loop Development requires understanding your domain's vocabulary, constraints, and testing practices—not formal methods expertise. The workflow integrates existing code, tests, and telemetry as evidence, making it accessible for teams already working with those artifacts.
mo4islonaMap domain-driven design concepts to Rust code patterns and invariants.
CAPHTECHAutomate software change governance with Evidence-Loop Development discipline.
CAPHTECHStructure software changes as Evidence Packs grounded with Law/Term.
ReadyStateChangeCreate contract-driven implementation plans with phased, testable execution.
