Report the true state of the work to the founder — failures plainly, no cheerleading, bad news before good. Load in every session with a founder; apply to every status report.
EnglishStructured diagnosis for bugs — no guess-and-patch. Use when something is broken, throwing, failing, or slow and the cause isn't already proven.
EnglishRoute decisions correctly between a non-technical founder and their AI engineering lead. Load at the start of any working session with a non-technical founder, or whenever unsure whether to ask the founder or decide yourself.
EnglishCost and quality discipline for dispatching sub-agents, background workers, or multi-agent workflows. Use before launching any agent fleet or long-running autonomous task, and whenever someone mentions burning through quota or budget.
EnglishInterview a non-technical founder to sharpen a fuzzy product idea before any code is written. Use when the founder gives a vague feature request ("add a login page", "make it feel warmer"), or before starting any feature worth more than an hour of work.
EnglishWrite a self-contained handoff when work moves to a new session, a different AI tool, or another person. Use when context is about to be lost — quota exhausted, switching tools, ending a session mid-project.
EnglishWrite an exit-condition contract before letting any AI run unattended — a background agent, a scheduled loop, a "keep going until it works" task. Use whenever work is handed off to run without a human watching.
EnglishAssign the right model tier to each job — expensive brains plan and judge, cheap hands search and grind. Use when dispatching any sub-agent, configuring a multi-agent workflow, or when quota pressure appears.
EnglishWrite the failing test before the fix or feature — never trust a green light you didn't first see red. Use when building any feature or fixing any bug.
EnglishReview finished work on two separate axes — craft quality and faithfulness to what was asked — and never let one axis excuse the other. Use before merging any meaningful change.
EnglishSlice work into thin end-to-end feature tickets, never into technical layers. Use when breaking any plan, spec, or feature request into workable units.
English
AGENT SKILLS ATLASIncludes Bad News First, Bug Autopsy, Decision Wiring, and other workflows.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Bad News First
Report the true state of the work to the founder — failures plainly, no cheerleading, bad news before good. Load in every session with a founder; apply to every status report.
Bug Autopsy
Structured diagnosis for bugs — no guess-and-patch. Use when something is broken, throwing, failing, or slow and the cause isn't already proven.
Decision Wiring
Route decisions correctly between a non-technical founder and their AI engineering lead. Load at the start of any working session with a non-technical founder, or whenever unsure whether to ask the founder or decide yourself.
Dispatch Economics
Cost and quality discipline for dispatching sub-agents, background workers, or multi-agent workflows. Use before launching any agent fleet or long-running autonomous task, and whenever someone mentions burning through quota or budget.
Grill Founder
Interview a non-technical founder to sharpen a fuzzy product idea before any code is written. Use when the founder gives a vague feature request ("add a login page", "make it feel warmer"), or before starting any feature worth more than an hour of work.
Handoff Contract
Write a self-contained handoff when work moves to a new session, a different AI tool, or another person. Use when context is about to be lost — quota exhausted, switching tools, ending a session mid-project.
Loop Contract
Write an exit-condition contract before letting any AI run unattended — a background agent, a scheduled loop, a "keep going until it works" task. Use whenever work is handed off to run without a human watching.
Model Tiering
Assign the right model tier to each job — expensive brains plan and judge, cheap hands search and grind. Use when dispatching any sub-agent, configuring a multi-agent workflow, or when quota pressure appears.
Red Light First
Write the failing test before the fix or feature — never trust a green light you didn't first see red. Use when building any feature or fixing any bug.
Two Axis Review
Review finished work on two separate axes — craft quality and faithfulness to what was asked — and never let one axis excuse the other. Use before merging any meaningful change.
Vertical Tickets
Slice work into thin end-to-end feature tickets, never into technical layers. Use when breaking any plan, spec, or feature request into workable units.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Bad News First skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.