pce-memory-feedback-guide

Automate software change governance with Evidence-Loop Development discipline.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/CAPHTECH/claude-marketplace --skill pce-memory-feedback-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pce-memory-feedback-guide
Source: https://github.com/CAPHTECH/claude-marketplace/tree/main/caphtech-plugin/skills/eld-ground-memory-collector/references/feedback_guide.md
Command: npx skills add https://github.com/CAPHTECH/claude-marketplace --skill pce-memory-feedback-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standardizes feedback signals for claims (positive/negative/delete) with guidance on evidence and next steps.

Quick Start

Use feedback to rate claims and trigger follow-up actions in memory lifecycle.

Frequently Asked Questions about pce-memory-feedback-guide

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

FAQPage Schema
How do I structure and process feedback for claims in software governance?

Feedback for claims standardizes positive, negative, and delete signals with evidence guidance. Use the feedback lifecycle to rate claims, document supporting evidence, and trigger follow-up actions within your Evidence-Loop Development cycle to enforce governance discipline and produce auditable decisions.

What is the Evidence-Loop Development cycle and how does it apply to code changes?

The ELD cycle enforces Sense/Model/Predict/Change/Ground/Record discipline across new features, bug fixes, and refactors. It structures evidence and claims into grounding tests and telemetry, delivering issue contracts, link maps, and ADRs that create a reusable knowledge store through pce-memory integration.

How do I use memory feedback to automate governance of software changes?

Process memory feedback by structuring evidence, Law/Term cards, and grounding within the ELD cycle. The Skill produces Evidence Packs, ADRs, and pce-memory outputs that audit decisions and establish a knowledge store for reproducible change governance.

What outputs do I get from following this feedback and governance process?

Following the feedback and grounding discipline produces issue contracts, link maps, grounding tests, telemetry records, Evidence Packs, and Architecture Decision Records. These outputs create an auditable trail and reusable knowledge base for future changes.

Can I apply this feedback process to different types of code changes?

Yes. The feedback and Evidence-Loop Development approach applies to new features, bug fixes, and refactors across codebases. It standardizes governance across all change types by enforcing consistent evidence structuring and grounding discipline.