
Programmer Workflow Playbook for Lean Teams
Programmer playbook
Think of this as hiring Pedro to handle your programming this week.
Use a structured coding workflow for specs, refactors, test scaffolding, and debugging while keeping final technical ownership.
Start here
Time to first useful output: 20-30 minutes
Tip: set your profile once in Business Profile and it will be injected into prompts automatically.
- Define one target feature or bug with acceptance criteria.
- Gather stack traces, code snippets, and constraints.
- Run starter prompt to generate plan before writing code.
First win: An implementation plan with tests and risk checkpoints.
Starting rules
- Always define acceptance criteria first.
- Generate tests before or alongside code.
- Prefer minimal safe patches over rewrites.
- Call out unknowns and required assumptions.
- Explain rollback path for risky changes.
Starting prompt
Act as a senior software engineer. Given this issue/spec, return: architecture approach, implementation steps, edge cases, test plan, and rollback strategy. Keep assumptions explicit.ChatGPT and Claude setup examples
ChatGPT · GPT-4.1
Best for: Rapid implementation planning and code sketching.
- Paste failing code and expected behavior.
- Ask for smallest safe change first.
- Request tests and edge cases before patch.
ChatGPT starter
Plan a minimal safe fix for this bug and provide regression tests.Claude · Claude Sonnet
Best for: Longer codebase reasoning and refactor design notes.
- Share architecture context and constraints.
- Ask for tradeoff table between approaches.
- Request final recommendation with risks.
Claude starter
Design two implementation options for this feature and compare complexity, risk, and maintainability.Prompt library
Copy a proven prompt, run it, then iterate with your context.
Feature implementation plan
Ship with fewer surprises.
Library prompt
Create an implementation plan for this feature including architecture options, selected approach, edge cases, and tests.Bug triage and patch
Reduce time-to-fix.
Library prompt
Debug this issue and provide root-cause hypotheses, repro steps, patch, and regression tests.Refactor design
Improve maintainability safely.
Library prompt
Propose a refactor plan for this module with migration sequence and risk controls.Code review lens
Catch bugs before merge.
Library prompt
Review this PR diff for defects, regressions, missing tests, and reliability risks.Workflow Partner
Automate recurring work and speed up decisions
AutomaticWork gives your team structured AI workflows for repeat tasks, approvals, and handoffs, so decisions happen faster and less work gets stuck.
What to hand off first
- Shorter implementation cycles
- Better bug triage and reproducibility
- Improved consistency in code patterns
Examples you can run this week
Feature spec to implementation plan
- Provide constraints, APIs, and acceptance criteria.
- Generate implementation plan with risk checkpoints.
- Produce test cases before writing production code.
Example prompt
I need an implementation plan for this feature. Include architecture choices, edge cases, tests, and rollout strategy.Bug fix fast lane
- Share stack trace, failing behavior, and expected output.
- Generate probable root causes and isolation steps.
- Propose minimal patch and regression tests.
Example prompt
Debug this issue. Give me likely root causes ordered by probability, exact reproduction steps, and the safest patch.Get this role's customized prompt library
Fill one short setup form and get prompts customized to your business across this role and every other StaffUp playbook.