mattgierhart/ghm-harvest
.claude/skills/ghm-harvest/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mattgierhart/PRD-driven-context-engineering ghm-harvestInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 11:13 AM5.3s4 files scanned
SKILL.md
- name:
- ghm-harvest
- description:
- >
- context:
- fork
Harvest
Extract durable insights from temporary files to Source of Truth during EPIC Phase E (Finish).
Workflow Overview
- Enumerate Temps → List all temp/ files from current EPIC
- Identify SoT-worthy → Determine what should persist
- Format Entries → Convert to proper SoT templates
- Archive → Move temps to archive, update manifest
Core Output Template
| 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 |
Harvest Decision Matrix
| 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 |
Step 1: Enumerate Temp Files
- Read EPIC Execution Plan for temp file references
- List all files in
temp/directory - Match temps to EPIC (by date or naming)
Checklist
- [ ] All EPIC-referenced temps identified
- [ ] Temp directory scanned
- [ ] Files categorized by content type
Step 2: Identify SoT-Worthy Content
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 | - |
Checklist
- [ ] Each temp file evaluated
- [ ] Extract/Archive/Discard decision made
- [ ] Decisions documented
Step 3: Format SoT Entries
For each extracted item:
- Generate appropriate ID using
ghm-id-register - Format per SoT template
- Add cross-references
- Insert into correct SoT file
Entry Template
### [ID]: [Title]
**Status**: Active
**Created**: YYYY-MM-DD
**Source**: temp/[filename].md (EPIC-XX)
**Cross-References**: [Related IDs]
[Extracted content, properly formatted]
Checklist
- [ ] All extracts have valid IDs
- [ ] Formatting matches SoT templates
- [ ] Cross-references verified
Step 4: Archive and Cleanup
- Create archive directory:
archive/YYYY-MM/ - Move processed temps to archive
- Generate manifest
- Update EPIC Phase E checklist
Archive Manifest Template
## 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 |
Quality Gates
Pass Checklist
- [ ] All temps processed (none orphaned)
- [ ] Extracted content has valid IDs
- [ ] Archive manifest is complete
- [ ] EPIC Phase E checklist updated
Testability Check
- [ ] SoT entries are findable by ID
- [ ] Archive manifest matches actual files
- [ ] Temp directory is clean
Anti-Patterns
| 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 |
Boundaries
DO:
- Extract durable insights
- Format per templates
- Create complete manifests
- Clean up temps
DON'T:
- Create new analysis
- Modify conclusions
- Skip the manifest
- Delete without review
Handoff
After harvest completes:
- SoT files updated with new entries
- Temps archived with manifest
- EPIC Phase E marked complete
- Ready to close EPIC
Related Skills
mattgierhart/prd-v05-technical-stack-selection
tools
VerifiedTrustedCommunity
Make technology decisions for every product capability by discovering existing assets, evaluating vendor-aligned options, and categorizing as Reuse/Extend/Build/Buy/Integrate/Research during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on "tech stack", "build or buy?", "what technologies?", "technical decisions", "what do we reuse?", "existing stack", "vendor constraint", "IBM-first", "what tools do we need?", "evaluate solutions", "select tech stack". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and cross-references. Feeds v0.6 Architecture Design.
28SKILL.mdUpdated Apr 16, 2026
mattgierhart/prd-v09-launch-metrics
development
VerifiedTrustedCommunity
Define success criteria and tracking setup for launch during PRD v0.9 Go-to-Market. Triggers on requests to define launch metrics, set up tracking, or when user asks "how do we measure launch success?", "launch KPIs", "tracking setup", "success criteria", "analytics", "launch goals". Outputs KPI- entries specialized for launch measurement.
28SKILL.mdUpdated Apr 16, 2026
mattgierhart/prd-v09-gtm-strategy
development
VerifiedTrustedCommunity
Define go-to-market strategy including launch plan, messaging, channels, and timing during PRD v0.9 Go-to-Market. Triggers on requests to plan launch, define GTM strategy, or when user asks "how do we launch?", "go-to-market", "launch plan", "marketing strategy", "messaging", "launch channels", "GTM". Outputs GTM- entries with launch plan components.
28SKILL.mdUpdated Apr 16, 2026
mattgierhart/prd-v09-feedback-loop-setup
development
VerifiedTrustedCommunity
Establish channels and processes for capturing and processing post-launch feedback during PRD v0.9 Go-to-Market. Triggers on requests to set up feedback systems, capture user input, or when user asks "how do we collect feedback?", "feedback loop", "user research", "post-launch feedback", "customer feedback", "NPS", "voice of customer". Outputs CFD- entries specialized for post-launch feedback capture.
28SKILL.mdUpdated Apr 16, 2026