| name | pragmatic-programmer-workflow |
| description | Apply Pragmatic Programmer (Hunt & Thomas, 2019 edition) advice to software tasks and code reviews; use when the user asks to apply pragmatic tips, asks how to approach a task, or when performing a code review to map relevant chapters/tips to the current context. |
Pragmatic Programmer Guide
Quick start
- Load
references/index.md and references/foundations.md.
- Ask the user which mode they want (guided workflow):
- Quick checklist (short, actionable)
- Chapter scan (pick relevant chapters, then synthesize)
- Tip-by-tip (list tips that apply, with concrete actions)
- Working agreement (define "how we'll work" for this task/project)
- Identify context: task type, stage (kickoff vs review), constraints, and risk level.
Chapter selection (fast map)
Use this to decide which chapter files to load:
- Chapter 1 (Philosophy): quality, culture, responsibility, communication, docs.
- Chapter 2 (Approach): duplication, coupling, prototypes, estimates, reversibility.
- Chapter 3 (Tools): automation, shell/text tooling, reproducibility, version control.
- Chapter 4 (Paranoia): contracts, error handling, defensive design, small steps.
- Chapter 5 (Bend, or Break): modularity, data flow, state management, architecture.
- Chapter 6 (Concurrency): workflow, shared state, coordination patterns.
- Chapter 7 (While You Are Coding): refactoring, complexity, testability, security, naming.
- Chapter 8 (Before the Project): requirements, users, glossary, constraints, policy.
- Chapter 9 (Pragmatic Projects): testing practice, automation, documentation, ownership.
Output structure
- Start with a short "context summary" based on the task.
- Provide only relevant tips (with titles) and paraphrased guidance.
- For each tip: include "Why it applies," "How to apply now," and "What to watch for."
- If in code review, tie guidance to the diff or files under review.
- If at task start, propose a first slice (tracer bullet/prototype) and a checklist.
Behavioral rules
- Always apply Foundations (tips 1-2) implicitly.
- If no tips are relevant, say so and explain why.
- Paraphrase guidance; avoid long quotes. Tip titles are ok.
- Keep recommendations optional and invite the user's preference.
References
references/index.md for the full tip list and chapter mapping.references/signals-to-tips.md for a fast signals to tips crosswalk.references/foundations.md for tips 1-2.- Chapter files:
references/chapter-1-philosophy.md through references/chapter-9-projects.md.
