Skip to main content
command CX Codex

history — Claude Code command: explore past attempts

history — a command to research historical attempts at solving a task: what was tried before, what worked, what mistakes to avoid. Helps prevent repeating errors and apply lessons from experience.

MIT ★ 1,988 updated 2026-04-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources
Open on GitHub

What history does

The history command surfaces what Claude has tackled in the past—internal projects and external examples. It asks clarifying questions: which history to search (industry attempts, internal projects, academic research), how far back (1–2 years, 3–5 years, longer), what to focus on (why things failed, what succeeded, what's changed).

Once scoped, it researches past attempts and documents each one: what was tried, what worked, what broke and why. It identifies patterns in success and failure, then explains what's different now. The output is saved to artifacts/research/ with a date and topic name.

It comes with structured templates: strategic summary, list of attempts with cause analysis, shared patterns, what to do and avoid, unresolved questions. Each point is concrete, not vague.

What it helps with

  • find what past projects have already tried to solve this task
  • understand why previous approaches failed
  • identify which methods worked and should be repeated
  • determine what has changed since then and whether it applies now

Example prompts for the agent

  • What attempts have been made at real-time data sync in our history?
  • Research our company's past migration from monolith to microservices
  • What OAuth approaches did we try before and why were they dropped?

How to install history

1Plugin marketplace

/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources

2Manually: put the files in place

.claude/commands/history.md

Call it with /history. For all projects use ~/.claude/commands/

Questions about history

How do I install history in Claude Code?

Run /plugin marketplace add glittercowboy/taches-cc-resources, then /plugin install taches-cc-resources@taches-cc-resources. The command will be available via .claude/commands/history.md.

What does history do?

It researches historical attempts at solving a task or approach. It asks about scope, time depth, and focus, then finds past examples, analyzes what succeeded and failed, and extracts lessons for your current work.

Where does history save results?

To the artifacts/research/ directory with a filename like YYYY-MM-DD-[topic]-history.md. If the directory does not exist, it creates it.

Source text

history.md · MIT
---
description: Research what's been tried before - past attempts, lessons learned
argument-hint: [problem/approach or leave blank for current context]
---

<objective>
Research historical attempts at $ARGUMENTS (or the current topic if no arguments provided).

Find what's been tried before - internally and externally - and extract lessons to avoid repeating mistakes.
</objective>

<intake_gate>

<context_analysis>
First, analyze $ARGUMENTS to extract what's already provided:
- The problem/approach to investigate
- Known past attempts
- How far back to look
- Internal vs external focus

Only ask about genuine gaps - don't re-ask what's already stated.
</context_analysis>

<initial_questions>
Use AskUserQuestion to ask 2-4 questions based on actual gaps:

**If scope unclear:**
- "What kind of history?" with options: Industry attempts, Internal past projects, Academic/research, All of the above, Other

**If timeframe unclear:**
- "How far back?" with options: Recent (1-2 years), Medium (3-5 years), Long (5+ years), All time, Other

**If focus unclear:**
- "What do you want to learn?" with options: Why things failed, Success patterns, What's changed since then, All of the above, Other

**If context unclear:**
- "Any known past attempts?" with options: Yes (I'll list them), No (find them), Some internal knowledge, Other

Skip questions where $ARGUMENTS already provides the answer.
</initial_questions>

<decision_gate>
After receiving answers, use AskUserQuestion:

Question: "Ready to research history, or would you like me to ask more questions?"

Options:
1. **Start research** - I have enough context
2. **Ask more questions** - There are details to clarify
3. **Let me add context** - I want to provide additional information

If "Ask more questions" → generate 2-3 contextual follow-ups, then present decision gate again
If "Let me add context" → receive input, then present decision gate again
If "Start research" → proceed to research
</decision_gate>

</intake_gate>

<process>
After intake complete:

1. Define what problem/approach we're investigating
2. Find past attempts (internal projects, industry examples, academic)
3. For each attempt, document:
   - What they tried
   - What worked
   - What failed and why
   - What's different now
4. Extract patterns and lessons
5. Identify what to adopt and what to avoid
</process>

<output_format>
## History Research: [Problem/Approach]

### Strategic Summary
[2-3 sentences: key historical pattern, main lesson, what's different now]

### What we're investigating
[The problem or approach we want to learn from]

### Past Attempts

**[Attempt 1: Name/Company/Project]**
- **When:** [Timeframe]
- **What they tried:** [Approach]
- **What worked:** [Successes]
- **What failed:** [Failures and root causes]
- **Why:** [Analysis of success/failure factors]

**[Attempt 2: Name/Company/Project]**
[Same structure...]

**[Attempt 3: Name/Company/Project]**
[Same structure...]

### Patterns

**Common success factors:**
- [Factor that correlates with success]
- [Factor that correlates with success]

**Common failure modes:**
- [Why things typically fail]
- [Why things typically fail]

### What's Different Now
- [Technology/market/context change]: [implication]
- [Technology/market/context change]: [implication]

### Lessons to Apply
**Do:**
- [Lesson to adopt]
- [Lesson to adopt]

**Don't:**
- [Mistake to avoid]
- [Mistake to avoid]

**Open question:**
[What we still don't know from history]

### Implementation Context
<claude_context>
<adopt>
- patterns: [successful patterns to follow]
- approaches: [technical approaches that worked]
- validations: [things to validate early based on past failures]
</adopt>
<avoid>
- antipatterns: [approaches that failed repeatedly]
- assumptions: [false assumptions that caused failures]
- shortcuts: [shortcuts that backfired]
</avoid>
<changed>
- now_possible: [things that are feasible now but weren't before]
- still_hard: [things that remain challenging]
- new_risks: [new risks that didn't exist before]
</changed>
</claude_context>

**Next Action:** Apply lessons to planning, research specific aspect deeper, or validate key assumptions

### Sources
- [Source name]: [URL] - [date accessed]
- [Source name]: [URL] - [date accessed]
</output_format>

<artifact_output>
Save the research to a file:

1. Create directory structure if it doesn't exist:
   - `[current-working-directory]/artifacts/research/`

2. Generate filename from topic:
   - Get current date in YYYY-MM-DD format
   - Slugify the topic (lowercase, hyphens for spaces)
   - Format: `YYYY-MM-DD-[topic]-history.md`
   - Example: `2025-01-15-real-time-sync-history.md`

3. Write the complete research to the file

4. Report to user: "Saved to `artifacts/research/[filename]`"
</artifact_output>

<success_criteria>
- Past attempts are relevant (similar problem/context)
- Failure analysis goes to root cause (not surface)
- Lessons are actionable (not just "be careful")
- Acknowledges what's changed since then
- Implementation context gives Claude specific patterns to adopt/avoid
- Informs current approach concretely
- Output saved to artifacts/research/ directory
</success_criteria>

© Lex Christopherson · MIT · glittercowboy/taches-cc-resources

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set48

The whole set →
build-macos-apps build-macos-apps is a Claude Code skill for building native macOS apps with SwiftUI and AppKit. It routes work on new apps, bugs, tests, performance, and releases to a matching workflow. CX Codex +1 ★ 1,988repo stars options A command to evaluate multiple options side-by-side: tools, approaches, architectures. It asks clarifying questions, builds a comparison matrix, and recommends the best choice with reasoning. CX Codex +1 ★ 1,988repo stars competitive competitive researches competitors for any feature or product, maps market gaps, and saves a markdown report to your project. CX Codex +1 ★ 1,988repo stars deep-dive deep-dive — a slash command that investigates a topic from several angles and writes a structured report into artifacts/research/ inside your project. CX Codex +1 ★ 1,988repo stars technical Researches technical implementation options, evaluates libraries and tradeoffs, and saves a ready architecture brief into Markdown. CX Codex +1 ★ 1,988repo stars feasibility feasibility is a command that assesses whether a project can meet its constraints and recommends whether to proceed, revise terms, or stop. CX Codex +1 ★ 1,988repo stars landscape Maps a domain landscape: identifies key players, available tools, trends and gaps. Takes a domain name or works in current context without arguments. CX Codex +1 ★ 1,988repo stars build-iphone-apps build-iphone-apps builds native iPhone apps in Swift using SwiftUI and UIKit via terminal commands without opening the Xcode IDE. Handles everything from code to App Store shipping. CX Codex +1 ★ 1,988repo stars

Project sponsors

Companies that keep this analytics open