ReddRadar
Agent skill
dialogue-verify-logging-compliance
Verify that required logging occurred during a process execution. Use before presenting work for approval to ensure decisions and observations were captured. Triggers on "verify logging", "check compliance", "validate logs".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/dialogue-verify-logging-compliance
SKILL.md
Dialogue: Verify Logging Compliance
Validate that required decision and observation logging occurred during process execution.
When to Use
Use this skill:
- Before presenting work for human approval
- As a validation step in capability flows
- When auditing whether dialogue protocol was followed
What It Checks
The verification checks for:
| Log Type | Minimum Expected | Purpose |
|---|---|---|
| Decisions | ≥1 per significant choice | Ensures rationale is captured |
| Observations | ≥1 for context elicitation | Ensures inputs are recorded |
How to Verify
Option 1: Quick Check (Manual)
Review the logs directly:
# Count decisions with a specific context/tag (per-file structure)
grep -l "<process-identifier>" ${CLAUDE_PROJECT_DIR}/.dialogue/logs/decisions/*.yaml | wc -l
# Count observations with a specific context/tag (per-file structure)
grep -l "<process-identifier>" ${CLAUDE_PROJECT_DIR}/.dialogue/logs/observations/*.yaml | wc -l
Option 2: Script-Based Verification
Execute the verification script:
${CLAUDE_PLUGIN_ROOT}/skills/dialogue-verify-logging-compliance/scripts/verify-logging.sh <process-identifier> <min-decisions> <min-observations>
Parameters
| Parameter | Description | Example |
|---|---|---|
process-identifier |
String to search for in context/tags | "Process Architect v2" |
min-decisions |
Minimum decision entries expected | 5 |
min-observations |
Minimum observation entries expected | 2 |
Example
${CLAUDE_PLUGIN_ROOT}/skills/dialogue-verify-logging-compliance/scripts/verify-logging.sh "Process Architect v2 simulation" 5 2
Output
The script returns:
- PASS if minimums are met, with counts
- FAIL if any minimum not met, with details
Example output:
Verifying logging compliance for: Process Architect v2 simulation
---
Decisions found: 5 (minimum: 5) ✓
Observations found: 2 (minimum: 2) ✓
---
PASS: Logging compliance verified
Escalation
If verification fails:
- Identify which log type is deficient
- Return to the relevant process step to add missing entries
- Re-run verification before proceeding
Integration with Process Flows
Add a verification step before approval gates:
Step X: Verify Logging Compliance
├── Capability: Validate
├── Pattern: AI-Only
├── AI role: Run verification script; report results
├── Escalation triggers: Verification fails (missing entries)
├── Completion criteria: All minimums met
└── Validation: Script returns PASS
Part of the Dialogue Framework
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?