Help us improve
Share bugs, ideas, or general feedback.
From ax
Reconstructs the ordered skill workflow behind a shipped artifact from past sessions, using ax and commit or date anchors.
npx claudepluginhub necmttn/axHow this skill is triggered — by the user, by Claude, or both
Slash command
/ax:ax-extract-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Given a deliverable (a demo, a PR, a feature) the user wants to know:
Traces design decisions through CASS sessions, handoffs, git, and artifacts to understand how architectural decisions evolved.
Turns Entire-tracked sessions, checkpoints, or repeated workflows into reusable SKILL.md drafts by extracting durable patterns via entire search and session metadata. Presents drafts for approval before writing.
Detects repeated workflow patterns from AI sessions and suggests reusable skills to automate them. Use when optimizing workflows.
Share bugs, ideas, or general feedback.
Given a deliverable (a demo, a PR, a feature) the user wants to know: what skills, in what order, produced it? This skill resolves an anchor (date or sha), windows the relevant sessions, and narrates the ordered skill arcs in plain text. Eats its own dogfood: it is itself a framing skill.
Assumes ax (axctl) is on PATH and the local SurrealDB is running.
If ax sessions here fails with a connection error, tell the user
scripts/db-start.sh and stop.
ONLY on explicit reconstruction triggers:
Do NOT fire on generic "what did I do today" or "show recent activity".
That is ax sessions here territory, not this skill.
Decide one of three modes based on what the user gave you:
| User said | Mode | Action |
|---|---|---|
| commit sha (full or short) | sha | use it directly |
| date or date range (YYYY-MM-DD) | date | use ax sessions around <date> |
| topic / feature / artifact name | topic | ax recall "<topic>" --sources=commit --json to find candidate shas |
| "this repo, recently" | pwd | ax sessions here --days=14 |
For topic mode pick the most relevant sha and proceed in sha mode. If results are ambiguous, ask the user to pick one before continuing.
Pick the right command for the resolved anchor:
ax sessions near <sha> --jsonax sessions around <date> --days=3 --jsonax sessions here --days=14 --jsonPick the N most relevant sessions from the JSON (default N=5). Bias to sessions with the highest turn counts and that touch files related to the artifact.
For each picked session:
ax sessions show <id> --json
ax sessions show <id> --by-role # optional, see Step 4
Read the top_skills and agent_delegations arrays. If a subagent's
work looks central to the artifact, drill in:
ax sessions show <id> --expand=<subagent-uuid>
Produce two artifacts inline (no files written - keep the answer in chat).
Lead with the framing skill that opened the work (use --by-role output
if available - the framing group goes first). Then execution skills,
then verification. For each skill, name it and write one line on what
it produced.
Example:
1. brainstorming -> defined the workflow extraction problem
2. writing-plans -> turned 13 grilled questions into a plan
3. subagent-driven -> executed the plan as 17 typed-CLI tasks
4. code-review -> two-stage spec + quality review per task
5. test-driven-dev -> 100% green throughout
Pull 2-4 turn excerpts where the user steered the work. Use:
ax recall "<keyword>" --skill=<framing-skill> --limit=5 --json
Quote one line per decision; cite the session id.
A one-paragraph "to do this again, you would" summary - the skills, the order, and the key user inputs at the steering points.
If ax sessions show <id> --by-role returns many skills in the
(unclassified) group, the role-weighted output above will be noisy.
Suggest the user run ax skills classify once - it generates briefs
the user can fill in to seed roles. Don't block on it; the
artifact-reconstruction story still works without roles.
Write everything inline. Do not create files under .ax/tasks/ or
anywhere else. Do not modify the repo. This is a read-only,
reconstruction-focused skill.
If the user asks for a permanent recipe, recommend they paste your
output into docs/recipes/<name>.md themselves - ax intentionally has
no recipe save format yet (per the workflow-extraction-frictions plan).