Use when someone is changing software they will have to live with, and the reasoning would otherwise survive only in this conversation. Covers setting up an engineering process in a repository that has none, starting work whose design is expensive to reverse, picking up work another person left unfinished, deciding whether a change is ready to merge, handing work over, and recovering why an existing decision was made before overturning it. Trigger on phrasings like 'set this repo up properly', 'take this over', 'continue the previous work', 'is this ready to merge', 'hand this off', 'why was it built this way' - and on the situation itself even when the user does not ask for process: a repository with no engineering setup, an unfinished diff, an .engineering/contract.json, or a decision record the requested change would contradict. Consult it before writing the code, not after. For diagnosing a single failure, a debugging skill fits better.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Use when someone is changing software they will have to live with, and the reasoning would otherwise survive only in this conversation. Covers setting up an engineering process in a repository that has none, starting work whose design is expensive to reverse, picking up work another person left unfinished, deciding whether a change is ready to merge, handing work over, and recovering why an existing decision was made before overturning it. Trigger on phrasings like 'set this repo up properly', 'take this over', 'continue the previous work', 'is this ready to merge', 'hand this off', 'why was it built this way' - and on the situation itself even when the user does not ask for process: a repository with no engineering setup, an unfinished diff, an .engineering/contract.json, or a decision record the requested change would contradict. Consult it before writing the code, not after. For diagnosing a single failure, a debugging skill fits better.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Use when someone is changing software they will have to live with, and the reasoning would otherwise survive only in this conversation. Covers setting up an engineering process in a repository that has none, starting work whose design is expensive to reverse, picking up work another person left unfinished, deciding whether a change is ready to merge, handing work over, and recovering why an existing decision was made before overturning it. Trigger on phrasings like 'set this repo up properly', 'take this over', 'continue the previous work', 'is this ready to merge', 'hand this off', 'why was it built this way' - and on the situation itself even when the user does not ask for process: a repository with no engineering setup, an unfinished diff, an .engineering/contract.json, or a decision record the requested change would contradict. Consult it before writing the code, not after. For diagnosing a single failure, a debugging skill fits better.
About this listing
Category
Engineering
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI