Menu
Analyze conversation for learnings and save to docs folder
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | learn |
| description | Analyze conversation for learnings and save to docs folder |
| argument-hint | ["optional topic hint"] |
| model | claude-opus-4-5-20251101 |
| allowed-tools | Read, Write, Edit, Glob, Grep, AskUserQuestion |
Analyze this conversation for insights worth preserving in the project's documentation.
If a topic hint was provided via $ARGUMENTS, focus on capturing that specific learning.
If no hint provided, analyze the full conversation for valuable insights.
Think deeply about what was learned in this conversation:
Only capture insights that are:
If nothing valuable was learned, say so and exit gracefully.
Read existing docs to find the best home. Look for a docs/ folder or similar documentation directory in the project.
If no existing doc fits, propose a new doc file with kebab-case naming.
Note: CLAUDE.md stays stable as the entry point. All detailed learnings go to /docs only.
Format the insight to match existing doc style:
Present your proposed changes:
Wait for explicit user approval before saving.
After approval, save the learning and confirm what was captured.
Facilitate interactive brainstorming sessions for feature ideas using structured questioning rounds. Use when asked to "brainstorm", "explore an idea", "flesh out a feature", "help me think through", or when the user presents a raw feature concept that needs refinement. Guides users through metrics, visualization, goals, implementation details, and scope to produce a complete feature spec.
Review current changes with parallel subagents
Check GitHub pipeline status and plan fixes if failing
Interview me about the plan
Open a pull request from the current branch
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
