Menu
Use when a plan with tasks exists and you need to execute implementation
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 | implement |
| description | Use when a plan with tasks exists and you need to execute implementation |
Execute tasks with death tests before unit tests.
Use update_plan and update_plan for progress tracking.
On entry, read index.yaml to analyze task dependencies.
Use agent named "samsara-implementer" for agent dispatch.
See dispatch-template.md for the Subagent dispatch: template.
After all tasks complete, use the $samsara-security-privacy-review skill skill.
