Practices Pipeline

Practices Pipeline

Continuous improvement system for dotforge configuration.

Lifecycle

inbox/ → evaluating/ → active/ → deprecated/

Input Sources

Source	Command	Description
Manual	/forge capture "text" or /cap	Record insights during work; no args → auto-detect mode (analyzes session context, proposes insight, Y/n/edit confirmation)
Auto-detect	Hook detect-claude-changes.sh	Detects .claude/ changes at session end
Upstream	/forge watch	Fetches Anthropic docs for changes
Community	/forge scout	Reviews curated repos in sources.yml
Analysis	/forge insights	Top findings from session analysis
Audit	/forge audit	Detected gaps auto-generate practices

Processing

/forge update

Three phases:

1. Evaluate — classify inbox: accept / reject / postpone
2. Incorporate — apply changes to dotforge template, bump version
3. Propagate — list projects needing sync (informational only, never auto-propagates)

Effectiveness Tracking

practices/metrics.yml tracks each practice with a binary recurrence model:

• Practice activated → status: monitoring
• Each audit checks CLAUDE_ERRORS.md for error recurrence
• 5 checks without recurrence → status: validated
• Error recurs → status: failed (practice needs revision)

Practice File Format

---
id: practice-YYYY-MM-DD-slug
title: Short title
source: url or "experience"
source_type: web | changelog | community | experience
discovered: YYYY-MM-DD
status: inbox | evaluating | active | deprecated
tags: [hooks, security, ...]
tested_in: null | project-name
incorporated_in: [] | [template/rules/file.md, ...]
effectiveness: validated | monitoring | failed | not-applicable
error_type: null | syntax | logic | integration | config | security
---

Monitoring

/forge inbox      # list pending
/forge pipeline   # count by status