SKILL_TEMPLATE
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest.
$ npx -y skills add mattgierhart/PRD-driven-context-engineering --skill ghm-harvest --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ghm-harvestContext preview
The summary Claude sees to decide when to auto-load this skill.
Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest.
name: ghm-harvest description: > Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest. context: fork allowed-tools: - Read - Write - Edit - Glob - Grep
Extract durable insights from temporary files to Source of Truth during EPIC Phase E (Finish).
1. **Enumerate Temps** → List all temp/ files from current EPIC 2. **Identify SoT-worthy** → Determine what should persist 3. **Format Entries** → Convert to proper SoT templates 4. **Archive** → Move temps to archive, update manifest
| 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 |
1. Read EPIC Execution Plan for temp file references 2. List all files in `temp/` directory 3. Match temps to EPIC (by date or naming)
For 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:
1. Generate appropriate ID using `ghm-id-register` 2. Format per SoT template 3. Add cross-references 4. Insert into correct SoT file
### [ID]: [Title] **Status**: Active **Created**: YYYY-MM-DD **Source**: temp/[filename].md (EPIC-XX) **Cross-References**: [Related IDs] [Extracted content, properly formatted]
1. Create archive directory: `archive/YYYY-MM/` 2. Move processed temps to archive 3. Generate manifest 4. Update EPIC Phase E checklist
## 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:
PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD, typed IDs, markdown knowledge graph, Claude Code skills & hooks.
Repo: mattgierhart/PRD-driven-context-engineering
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS /…
Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT…
Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo.…
Creates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type,…
Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation.…