Menu
Use when starting new feature work or investigating a problem before pre-thinking and planning
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
Use when entering a new project for the first time, or when the codebase has changed significantly — generates a yin-side codebase map with structural analysis and silent failure surface assessment
Use when the user describes a small, low-risk change — bug fix with known cause, config change, dependency update, or small refactor under 100 lines
Use when a plan with tasks exists and you need to execute implementation — requires index.yaml and tasks/ directory
Use when implement is complete and feature-level scar items need review — aggregates remaining scars across tasks, triages cross-task patterns, and fixes system-level rot before validate-and-ship
Use when research/kickoff is complete and you need to create an implementation plan with specs, tasks, and acceptance criteria
Use when research output is complete and planning would otherwise need to assume design, task-shape, structural boundaries, or evaluation details before implementation planning
| name | research |
| description | Use when starting new feature work or investigating a problem before pre-thinking and planning |
The starting point for any new work. Before building, interrogate the problem.
Use the file reading (via exec_command with cat/nl) to read the current codebase context. Use the exec_command to run discovery commands. Use the exec_command with rg to search for patterns.
After completing research outputs, use the $samsara-pre-thinking skill skill.
