pageel/para-workspace/logs

Skill: Logs Audit Extensions

Sidecar Skill for the /logs workflow. Contains audit extension templates

that the Agent loads only when the session used a specialized plan template

(e.g., TDD plan → load TDD Compliance template).

Pattern: Workflow = Logic → Sidecar Skill = Data Router.

The /logs workflow instructs the Agent to read this skill at audit extension time.

When to Load

• /logs --deep → Step 3: After base audit sections, check if session used a TDD plan → load references/tdd-compliance.md
• /logs (fast glance) → NOT needed (no extensions)

Detection Logic

IF active_plan exists in project.md:
  Read the plan file → check for "Methodology: Strict TDD" or plan filename contains "-tdd"
  OR check if plan template used TDD Cycle markers (🔴 RED / 🟢 GREEN)
  → IF match: load references/tdd-compliance.md and append to audit report
ELSE:
  Skip TDD compliance section

References

Usage: Transcript Parser

When executing /logs --deep or verifying TDD/Drift compliance, the Agent can run this Python utility locally to extract structured statistics without flooding the token context window:

# Resolve and run from workspace root
python3 .agents/skills/logs/scripts/parse-transcript.py [path_to_transcript_or_directory]

Convention: Data files live in references/ (not templates/).

This follows the Sidecar Skill convention formalized in v1.7.6.3.

Extensibility

Future audit extensions can be added here following the same pattern: