Hey, dude
Start a work session with a tight resume: establish only the context needed
to take the next useful action. Then act. This skill is the start-of-session
partner to later-dude.
1. Establish the work boundary
- Use the project, branch, issue, handoff, or task the user named.
- If no project is identifiable from the conversation or current directory, ask
one concise question rather than scanning the machine.
- Treat a user statement that something was already selected, checked, or done
as current context. Seek only new evidence needed for the next action.
Completion criterion: there is one selected work area and one stated outcome.
2. Read the smallest authoritative context
Inspect, in this order when they exist:
- Applicable project instructions such as
AGENTS.md, CLAUDE.md, or a
contributor guide.
- The current handoff, issue, task list, or status document.
- The working-tree and branch state, preserving unrelated changes.
- The implementation, tests, logs, or live state directly relevant to the
user's request.
Prefer current repository or runtime evidence over an old handoff. Treat a
handoff as a starting hypothesis, not a substitute for checking the seam it
describes. Do not read personal memory stores, credentials, or unrelated
projects unless the user explicitly places them in scope.
Completion criterion: the next action is grounded in current evidence, and any
stale or contradictory context is called out briefly.
3. Turn context into motion
Return a compact resume note only when it helps:
- Current state: the relevant verified facts.
- Next action: one runnable, in-scope step.
- Blocker: only if no safe next step exists.
Immediately perform the requested work when it is authorized. Do not stop at a
status summary if a safe, useful action remains. For a broad or dependent task,
make a short execution plan and keep it current as work completes.
Completion criterion: the requested work has begun, or the user has the exact
missing decision or authority needed to begin.
Safety boundaries
- Never treat session-start language as authorization to change external state.
- Preserve uncommitted work that is outside the selected task.
- Do not create, send, publish, deploy, merge, or delete merely because past
context mentions it.
- If the project has its own instructions, follow them unless the user gives a
direct, applicable override.
Example
User: “Hey dude, pick up the settings-panel bug.”
The agent identifies the relevant project, reads its instructions and handoff,
checks the current branch and the settings-panel seam, then begins the approved
diagnosis or fix. It does not inventory every repository on the computer.
1---2name: hey-dude3description: Use when the user begins or resumes a work session and wants a focused catch-up before continuing: hey dude, pick this back up, where were we, resume, or what is the next step. Establishes current project truth from the selected workspace, handoff, and working tree, then proceeds with the requested work. Do not use for a general project audit or to scan unrelated directories.4license: See LICENSE.txt5---67# Hey, dude89Start a work session with a **tight resume**: establish only the context needed10to take the next useful action. Then act. This skill is the start-of-session11partner to `later-dude`.1213## 1. Establish the work boundary1415- Use the project, branch, issue, handoff, or task the user named.16- If no project is identifiable from the conversation or current directory, ask17 one concise question rather than scanning the machine.18- Treat a user statement that something was already selected, checked, or done19 as current context. Seek only new evidence needed for the next action.2021Completion criterion: there is one selected work area and one stated outcome.2223## 2. Read the smallest authoritative context2425Inspect, in this order when they exist:26271. Applicable project instructions such as `AGENTS.md`, `CLAUDE.md`, or a28 contributor guide.292. The current handoff, issue, task list, or status document.303. The working-tree and branch state, preserving unrelated changes.314. The implementation, tests, logs, or live state directly relevant to the32 user's request.3334Prefer current repository or runtime evidence over an old handoff. Treat a35handoff as a starting hypothesis, not a substitute for checking the seam it36describes. Do not read personal memory stores, credentials, or unrelated37projects unless the user explicitly places them in scope.3839Completion criterion: the next action is grounded in current evidence, and any40stale or contradictory context is called out briefly.4142## 3. Turn context into motion4344Return a compact resume note only when it helps:4546- **Current state:** the relevant verified facts.47- **Next action:** one runnable, in-scope step.48- **Blocker:** only if no safe next step exists.4950Immediately perform the requested work when it is authorized. Do not stop at a51status summary if a safe, useful action remains. For a broad or dependent task,52make a short execution plan and keep it current as work completes.5354Completion criterion: the requested work has begun, or the user has the exact55missing decision or authority needed to begin.5657## Safety boundaries5859- Never treat session-start language as authorization to change external state.60- Preserve uncommitted work that is outside the selected task.61- Do not create, send, publish, deploy, merge, or delete merely because past62 context mentions it.63- If the project has its own instructions, follow them unless the user gives a64 direct, applicable override.6566## Example6768> User: “Hey dude, pick up the settings-panel bug.”6970The agent identifies the relevant project, reads its instructions and handoff,71checks the current branch and the settings-panel seam, then begins the approved72diagnosis or fix. It does not inventory every repository on the computer.
wretcher207