Reorganise as a marketplace with multiple focused plugins: - claude/code: Core development (hooks, scripts, data collection) - claude/review: Code review automation - claude/verify: Work verification - claude/qa: Quality assurance loops - claude/ci: CI/CD integration Structure: - .claude-plugin/marketplace.json lists all plugins - Each plugin has its own .claude-plugin/plugin.json - Commands namespaced: /code:*, /review:*, /qa:*, etc. Install individual plugins or all via marketplace: claude plugin add host-uk/core-agent claude plugin add host-uk/core-agent/claude/code Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Lessons Learned: {{PROJECT_NAME}} ({{SYMBOL}})
Excavation Date: {{DATE}} Post-Mortem By: {{EXCAVATOR}}
Project Timeline
| Date | Event |
|---|---|
| {{GENESIS}} | Genesis block |
| {{DEATH_YEAR}} | Project effectively dead |
What Killed It?
Primary Cause
The main reason this project failed
Contributing Factors
The Final Straw
What was the last event before abandonment?
Warning Signs We Saw
Signs that appeared before death (in order):
What Could Have Saved It?
| Problem | Potential Solution | Why It Didn't Happen |
|---|---|---|
Patterns to Watch For
Red flags that Lethean should monitor in itself:
What They Did Right
Not everything was a failure. Worth preserving:
Community Sentiment
At Peak
How did the community feel when things were good?
At Decline
How did sentiment shift?
At Death
Final community state
Quotes Worth Remembering
"Quote from team or community" — Source, Date
Key Takeaways for Lethean
Post-mortem generated by project-archaeology