compoundlisted

# Compound Capture problem solutions while context is fresh, creating structured documentation in `knowledge-base/project/learnings/` with YAML frontmatter for searchability. ## Usage Activate this skill after solving a non-trivial problem. If context about the problem is not already in the conversation, use `ask_user` to request a brief description. ## Phase 0: Setup Read project conventions from `GEMINI.md` if it exists. Apply conventions during documentation. **Branch safety check:** Run `run_shell_command` with `git branch --show-current`. If the result is `main` or `master`, abort with: "Error: compound cannot run on main/master. Checkout a feature branch first." ## Phase 0.5: Session Error Inventory Before writing any learning, enumerate ALL errors encountered in this session. Output a numbered list. This step cannot be skipped. Include: - Wrong file paths, directories, or branch confusion - Failed shell commands or unexpected exit codes - API errors or unexpected responses - Wrong assumptions that required backtracking If genuinely no errors occurred, output: "Session error inventory: none detected." ## Execution Strategy Analyze the session context to extract the learning. Unlike the Claude Code version which spawns 5 parallel subagents, this version runs sequentially within the conversation: ### 1. Context Analysis - Extract conversation history - Identify problem type, component, symptoms - Determine YAML frontmatter fields: title, date, category, tag