walk-through-work-history
v1.1.0Explain how work progressed — PR, branch, or project — one page at a time.
By JT SternbergLicense: MIT5 GitHub starsUpdated 2 days ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 21, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install walk-through-work-history for Codex and Claude Code
codex plugin marketplace add jtsternberg/claude-plugins
codex plugin marketplace upgrade jtsternberg
codex plugin add walk-through-work-history@jtsternbergPaste and run these commands in a terminal with Codex. They add and refresh the jtsternberg catalog, then install this plugin.
Compatibility: the page URL and API slug “walk-through-work-history” remain stable.
- Codex:
walk-through-work-history@agent-plugin-marketplace→walk-through-work-history@jtsternberg
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/jtsternberg/claude-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/pr-workflow/walk-through-work-history/.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json└── skills/walk-through-work-history/SKILL.md
Included Skills1
Research and explain how work progressed as an interactive, one-page-at-a-time walkthrough. Use when the user asks for the history, evolution, review progression, revisions, decisions, false starts, or outcome of a GitHub pull request (the primary use case), issue, branch, project, incident, document, ticket, or other chronological work record—including a Google Doc's revision history and comment threads—especially when they ask for a paginated, ADHD-friendly, story-like, or "turn the page" explanation.
Plugin manifests2
{
"name": "walk-through-work-history",
"version": "1.1.0",
"description": "Explain how work progressed — PR, branch, or project — one page at a time.",
"author": {
"name": "JT Sternberg",
"url": "https://github.com/jtsternberg"
},
"repository": "https://github.com/jtsternberg/claude-plugins",
"license": "MIT",
"keywords": [
"github",
"pull-requests",
"code-review",
"google-docs"
],
"skills": "./skills/",
"interface": {
"displayName": "Walk Through Work History",
"shortDescription": "Explain how work progressed — PR, branch, or project — one page at a time.",
"developerName": "JT Sternberg",
"category": "Developer Tools",
"capabilities": [
"Interactive",
"Read",
"Write"
],
"websiteURL": "https://github.com/jtsternberg/claude-plugins",
"defaultPrompt": [
"Use $walk-through-work-history:walk-through-work-history to explain how work progressed one page at a time."
]
}
}{
"name": "walk-through-work-history",
"description": "Explain how work progressed — PR, branch, or project — one page at a time.",
"version": "1.1.0",
"author": {
"name": "JT Sternberg",
"url": "https://github.com/jtsternberg"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[walk-through-work-history on Agent Plugins Marketplace](https://pluginsmp.com/plugins/walk-through-work-history)