Search archived tickets by keywords to find related historical context.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill discover-history --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Discover History?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-discover-history)More formats (shields.io, HTML) on the badges page.
---
name: discover-history
description: Search archived tickets by keywords to find related historical context.
allowed-tools: Bash
user-invocable: false
---
# Discover History
Search archived tickets to find related past work.
## Instructions
Run the bundled script with keywords extracted from the ticket request:
```bash
bash .claude/skills/discover-history/sh/search.sh <keyword1> [keyword2] ...
```
### Keyword Extraction
Extract 3-5 keywords from:
- Key file paths (e.g., `ticket.md`, `drive.md`)
- Domain terms (e.g., `branch`, `commit`, `archive`)
- Layer names (e.g., `Config`, `UX`)
### Output Format
The script returns matches sorted by relevance (match count):
```
5 .workaholic/tickets/archive/feat-xxx/ticket-a.md
3 .workaholic/tickets/archive/feat-yyy/ticket-b.md
```
### Interpreting Results
- Higher count = more keyword matches = more relevant
- Read top 5 tickets to understand context
- Extract: title, overview, key files, layer
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...