From PRD-Driven Context Engineering
Extracts durable insights from temp/ files to Source of Truth during EPIC Phase E. Triggers at EPIC completion or explicit /ghm-harvest invocation. Outputs new SoT entries and archive manifest.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prd-ce:ghm-harvestThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Extract durable insights from temporary files to Source of Truth during EPIC Phase E (Finish).
Extract durable insights from temporary files to Source of Truth during EPIC Phase E (Finish).
| Element | Definition | Evidence |
|---|---|---|
| Temp Files | Files processed | List with paths |
| New SoT Entries | IDs created | BR-XXX, UJ-XXX, etc. |
| Archive Manifest | What was archived | Paths and dates |
| Discarded | What was not kept | Reason for each |
| Content Type | Action | Destination |
|---|---|---|
| Business rule discovered | Extract | SoT/SoT.BUSINESS_RULES.md |
| User flow documented | Extract | SoT/SoT.USER_JOURNEYS.md |
| API design finalized | Extract | SoT/SoT.API_CONTRACTS.md |
| Customer feedback captured | Extract | SoT/SoT.customer_feedback.md |
| Session notes | Archive only | archive/YYYY-MM/ |
| Scratch work | Discard | Delete after review |
temp/ directoryFor each temp file, evaluate:
| Question | If Yes | If No |
|---|---|---|
| Is this a business rule? | Extract as BR-XXX | Continue |
| Is this a user flow? | Extract as UJ-XXX | Continue |
| Is this an API design? | Extract as API-XXX | Continue |
| Is this customer evidence? | Extract as CFD-XXX | Continue |
| Is this useful context? | Archive | Continue |
| Is this scratch work? | Discard | - |
For each extracted item:
ghm-id-register### [ID]: [Title]
**Status**: Active
**Created**: YYYY-MM-DD
**Source**: temp/[filename].md (EPIC-XX)
**Cross-References**: [Related IDs]
[Extracted content, properly formatted]
archive/YYYY-MM/## Archive Manifest: EPIC-XX
**Date**: YYYY-MM-DD
**Archived To**: archive/YYYY-MM/
### Extracted to SoT
| Temp File | New ID | SoT File |
|-----------|--------|----------|
| temp/file.md | BR-XXX | SoT.BUSINESS_RULES.md |
### Archived Only
| Temp File | Reason |
|-----------|--------|
| temp/notes.md | Session context |
### Discarded
| Temp File | Reason |
|-----------|--------|
| temp/scratch.md | No durable value |
| Pattern | Example | Fix |
|---|---|---|
| Orphan temps | Temps not in manifest | → Process all files |
| Lost context | Archive without manifest | → Always create manifest |
| Over-extraction | Everything becomes SoT | → Apply decision matrix |
| Under-extraction | Valuable insights lost | → Review before discard |
DO:
DON'T:
After harvest completes:
npx claudepluginhub mattgierhart/prd-driven-context-engineering --plugin prd-ceCreates new Source of Truth (SoT) files when existing templates don't fit. Guides schema design, template drafting, and registration for durable project artifacts.
Bulk imports knowledge from files, directories, or URLs into structured backlogs, or captures a single document with a 5-section template (claims, worth-keeping, contested, action, reaction).
Merges REPORT.md and ANALYSIS.md artifacts into permanent docs following markdown conventions, then deletes sources. Use to clean git status before PRs.