starting-the-task
Starting the Task
Use this checklist any time you begin work on a bd issue (or whenever the user says “start working on …”). It ensures the effort is grounded, observable, and reversible.
-
Understand the Task
- Read the bd issue (and any linked discoveries or docs) end-to-end.
- Confirm acceptance criteria, dependencies, and blockers. Ask clarifying questions before touching code.
-
Environment Readiness
- Run
cargo test(or the project’s canonical smoke suite) onmainto ensure the baseline is green before you diverge. - If tests fail, stop and coordinate—don’t start stacking new work on a broken branch.
- Run
-
Branch & Tracking
- Create a fresh branch for the effort, even if you expect a small change.
git checkout -b <short-task-name> bd update <id> --status in_progress --notes "Starting work"so the tracker reflects the new ownership/status.- If multiple repos are involved, repeat for each.
- Create a fresh branch for the effort, even if you expect a small change.
More from lambdamechanic/skills
dumbwaiter-mcp
Provider-agnostic wait-for-change skill that uses the Dumbwaiter MCP server to wait on PR events (GitHub first) via wait.start/status/cancel/await, with progress notifications and durable state.
60rust-guidelines
Pragmatic Rust conventions to keep code readable, testable, and performant for this project.
9landing-the-plane
Checklist for finishing work, pushing a branch, and opening a ready-for-review PR with tests and tracker updates.
8python
Default Python stack for Lambda: uv + Astral tools, typed code, schemas, and Hypothesis.
6typescript
Default TypeScript stack for Lambda: pnpm workspaces + Turbo, strict TS, and sensible DX helpers.
6galahad
how to approach tests, types and coverage
5