Force the Completed Staff Work method to structure engineering communication — present analyzed options plus your recommendation for approval to merge or ship a risky change. Manual entry point for the executive-brief-code skill; use when you already know you want Completed Staff Work.
EnglishForce the SCQA (Situation, Complication, Question, Answer) opening to structure engineering communication — RFCs, design docs, and proposals for a reviewer who needs context rebuilt. Manual entry point for the executive-brief-code skill; use when you already know you want SCQA.
EnglishWalk the user through everything that shipped in a sprint so they end up with a real, durable mental model of it — not a summary they nod along to. Reconstructs what was built from git (commits, PRs, diff), then teaches it across four lenses (product, architecture, how-to-use, operational/run-it) one chunk at a time, checking understanding before moving on and pausing for questions. Use whenever the user says the sprint/cycle/iteration is over or wraps up, asks "what did we build", "walk me through what shipped", "help me understand this sprint", "onboard me to what was done", "catch me up on the release", or wants to review/understand a body of recently-merged work as a learner rather than a reviewer. Trigger even if they don't say "sprint" — the signal is "make me understand a chunk of shipped work, in stages." Do NOT use for reviewing a single open PR for correctness (that's code review), writing new code, or explaining one isolated function.
EnglishIncludes Executive Brief Code Csw, Executive Brief Code Scqa, and Sprint Debrief.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Executive Brief Code Csw
Force the Completed Staff Work method to structure engineering communication — present analyzed options plus your recommendation for approval to merge or ship a risky change. Manual entry point for the executive-brief-code skill; use when you already know you want Completed Staff Work.
Executive Brief Code Scqa
Force the SCQA (Situation, Complication, Question, Answer) opening to structure engineering communication — RFCs, design docs, and proposals for a reviewer who needs context rebuilt. Manual entry point for the executive-brief-code skill; use when you already know you want SCQA.
Sprint Debrief
Walk the user through everything that shipped in a sprint so they end up with a real, durable mental model of it — not a summary they nod along to. Reconstructs what was built from git (commits, PRs, diff), then teaches it across four lenses (product, architecture, how-to-use, operational/run-it) one chunk at a time, checking understanding before moving on and pausing for questions. Use whenever the user says the sprint/cycle/iteration is over or wraps up, asks "what did we build", "walk me through what shipped", "help me understand this sprint", "onboard me to what was done", "catch me up on the release", or wants to review/understand a body of recently-merged work as a learner rather than a reviewer. Trigger even if they don't say "sprint" — the signal is "make me understand a chunk of shipped work, in stages." Do NOT use for reviewing a single open PR for correctness (that's code review), writing new code, or explaining one isolated function.
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 Executive Brief Code Csw 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.
- License details are not provided in these listings. Check the author’s terms before using the skills.