• agile-charter Use when asked to run an agile chartering session — collaboratively defining a project's vision, objectives, and working agreement with a diverse stakeholder group — as distinct from a formal project charter document (see project-charter), which is written and approved rather than co-created in a session.
  • agile-coaching Use when asked about the agile coach role — facilitating ceremonies, removing impediments, fostering psychological safety, and evolving from hands-on guidance to strategic coaching as a team matures — as distinct from a Scrum Master's more process-focused role or a traditional project manager (see project-management).
  • agile-delivery Use when asked to run the delivery track of dual-track agile — building, testing, and shipping validated work via a continuous delivery pipeline — as the track that runs alongside, not after, discovery (see agile-discovery), and grounded in continuous delivery's build/test/deploy/release pipeline.
  • agile-discovery Use when asked to run the discovery track of dual-track agile — validating what to build before building it, via problem identification, user personas, and prototyping — as the track that runs alongside, not before, delivery (see agile-delivery), and feeds product-management's broader discipline.
  • agile-liftoff Use when asked to run an agile project liftoff — aligning a team on vision, objectives, stakeholders, and initial plan at project start — as distinct from an agile chartering session's working-agreement focus (see agile-charter) or a formal project charter document (see project-charter).
  • agile-principles Use when asked what the Agile principles are, to check a team practice or process decision against them, or to explain the reasoning behind agile software delivery (as opposed to a specific framework like Scrum or Kanban, which implement these principles rather than being identical to them).
  • agile-reflection Use when asked to run a team reflection or retrospective in the spirit of the 12th Agile Manifesto principle — regular, honest process examination followed by actual behavior change — as distinct from a futurespective's forward-looking scenario exploration (see futurespective), which looks ahead rather than back.
  • agile-standup Use when asked to run a daily standup (daily scrum) — the three-question format, timeboxing, and common failure modes — including whether a team should even run one at all, as distinct from a broader agile-coaching engagement (see agile-coaching) that would help diagnose that question.
  • anomaly-analysis Use when asked to detect anomalies/outliers in data — statistical, machine-learning, and deep-learning detection methods, supervised vs. unsupervised approaches — as distinct from trend-analysis's focus on overall patterns over time rather than individual deviant points.
  • architecture-decision-record Use when a user wants to create, write, name, place, or organize an Architecture Decision Record (ADR) in a software project — e.g. "write an ADR for choosing a database", "document this architecture decision", "set up an adr/ or decisions/ directory", "which ADR template should I use", "supersede an old ADR". Covers picking a template, naming the file, filling in context/decision/consequences, and deciding whether a decision even needs an ADR.
  • brainstorming Use when asked to run a brainstorming session well — quantity-over-quality, non-judgmental atmosphere, timeboxing, and capture technique — the foundational technique within the broader creative-thinking toolkit (see creative-thinking).
  • budget-forecasting Use when asked to build or maintain a budget forecast — the ongoing, continuously updated projection of future income and expenses against actuals — as distinct from a budget itself, which is a fixed plan or target set for a period rather than a live projection.
  • business-continuity-plan Use when asked to write a business continuity plan (BCP) — an organization-wide plan for keeping critical operations running through a major disruption (facility loss, supplier failure, pandemic, natural disaster) — as distinct from disaster-recovery-testing (see below), which is the IT-systems-only slice of this.
  • capacity-planning Use when asked to determine whether available capacity — production, staffing, or infrastructure — will meet projected demand, and what to do about a gap or a surplus in either direction, as distinct from [[demand-forecasting]], which produces the demand projection capacity planning is measured against rather than deciding what to do about it.
  • cause-and-effect-diagram Use when asked to run a root-cause analysis session using a fishbone/Ishikawa-style diagram — the 6M cause categories (Manpower, Methods, Machines, Materials, Measurements, Mother Nature) — the same technique also called fishbone-diagram or ishikawa-diagram under alternate names.
  • change-request Use when asked to write or process a change request — a formal request to modify a specific system, process, or environment under IT/ITIL-style change control — as distinct from [[enterprise-change-management]], which governs organizational and people change (reorgs, new processes, culture shifts) rather than controlled technical or operational changes to a system.
  • changelog Use when asked to write or maintain a changelog — the complete, running, human-readable record of notable changes to a project across all versions — as distinct from [[release-notes]], which is the announcement for one specific release, narrower in scope and often more promotional in tone.
  • chaos-testing Use when asked to deliberately inject failure into a system to test resilience — chaos engineering, fault injection — as distinct from disaster-recovery testing (see disaster-recovery-testing), which validates a specific recovery procedure rather than exploring unknown failure modes.
  • compliance-testing Use when asked to test whether software adheres to regulatory or policy standards (HIPAA, PCI-DSS, GDPR, SOX) — as distinct from security testing broadly (see security-testing), which compliance testing draws on but is scoped specifically to named external requirements.
  • configuration-management Use when asked to set up or document configuration management — systematically tracking and controlling a system's settings, versions, and dependencies so its actual state is known and reproducible rather than drifting unrecorded — as distinct from a [[change-request]], which is the approval process for a specific proposed change rather than the ongoing record of a system's current configuration.
  • crisis-communication-plan Use when asked to write a crisis communication plan — how an organization communicates externally, to media, customers, or the public, during a crisis — as distinct from an [[incident-response-plan]], which covers the internal operational or technical response rather than the external-facing message.
  • data-governance Use when asked to define or document data governance — the policies, ownership, and processes for how an organization manages its data as an asset (who owns a dataset, how it's classified, how long it's retained, who can request access) — as distinct from [[data-quality]], which is the measurable property those policies aim to protect, not the framework itself.
  • data-pipeline Use when asked to design, document, or troubleshoot a data pipeline — an automated sequence that extracts data from a source, transforms it, and loads it into a destination on a schedule or trigger — as distinct from [[data-quality]], which measures whether the data moving through the pipeline is actually accurate and complete, not how it's moved.
  • data-quality Use when asked to define, measure, or improve data quality — whether data is accurate, complete, consistent, and fit for its actual use — as distinct from [[data-governance]], which is the policy and ownership framework around data, not the measurable property of the data itself.
  • decision-records Draft, review, and manage decision records (DRs) — short documents that capture one significant choice, its context, the options considered, the decision, and its consequences. Use when someone wants to write a decision record or ADR, decide whether a choice is significant enough to warrant one, pick between a lightweight and a comprehensive template, walk through drafting one step by step, find a worked example close to their own domain, or check a draft before publishing it for comment.
  • demand-analysis Use when asked to run or explain a demand analysis — estimating and understanding customer demand for a product or service (market size, price sensitivity, demand drivers) — as the market-feasibility input to a broader feasibility-analysis or business case.
  • demand-forecasting Use when asked to project future customer demand for operational planning — how much to produce, stock, or staff for — as distinct from [[demand-analysis]] (market-sizing and opportunity assessment for a business decision) which this is not; demand forecasting is the ongoing operational forecast that drives inventory and capacity decisions.
  • disaster-recovery-plan Use when asked to write a disaster recovery plan — the written plan for recovering IT systems and data after a major disruption, including recovery objectives, sequence, and backup strategy — as distinct from [[disaster-recovery-testing]] (verifying the plan actually works, rather than the plan itself) and narrower than a [[business-continuity-plan]] (org-wide continuity across people, facilities, and suppliers, not just IT systems and data).
  • disaster-recovery-testing Use when asked to test backup restoration, failover, and business-continuity recovery procedures — recovery time/point objectives (RTO/RPO) — as distinct from chaos testing (see chaos-testing), which explores unknown failure modes broadly rather than validating one defined recovery plan.
  • disciplined-agile Use when asked to choose or tailor a team's "way of working" (WoW) with Disciplined Agile (DA) — a goal-driven toolkit of decision points and options spanning multiple lifecycles, rather than one prescribed process — as distinct from adopting a single fixed framework like scrum, scaled-agile-framework, or large-scale-scrum outright.
  • dmaic Use when asked to run a Six Sigma DMAIC improvement project — Define, Measure, Analyze, Improve, Control — as a data-driven, project-scoped alternative to Kaizen's continuous, incremental cycle (see kaizen) or PDCA's general iterative loop (see plan-do-check-act).
  • enterprise-architecture Use when asked to align an organization's business processes, information systems, and technology infrastructure at the whole-enterprise level — business/information/technology/application architecture — as distinct from a single system's software-architecture.
  • enterprise-change-management Use when asked to plan or run change management for a large organizational change (merger, reorganization, major technology rollout) — planning/implementation/evaluation stages, stakeholder engagement, resistance — as ECM, distinct from the specific change-improvement techniques in dmaic, kaizen, and adkar.
  • evolutionary-architecture Use when asked to design a software architecture that supports incremental, guided change over time — architectural fitness functions, incremental change, appropriate coupling across multiple architectural dimensions — as distinct from a one-time upfront design, and the architectural counterpart to evolutionary-engineering's practice-level focus.
  • extreme-programming Use when asked to apply Extreme Programming (XP) — pair programming, test-driven development, continuous integration, refactoring, and sustainable pace as the specific engineering practices behind agile delivery — as distinct from scrum's process/role framework, which XP's practices are commonly run inside rather than as a competing alternative.
  • feature-prioritization Use when asked to rank competing feature or work candidates — via RICE, MoSCoW, value-vs-effort, or a similar framework — instead of prioritizing by whoever argues loudest or whichever request came in most recently.
  • fishbone-diagram Use when asked about a "fishbone diagram" for root-cause analysis — the same technique as a cause-and-effect diagram (see cause-and-effect-diagram), named for its fish-skeleton shape, also called an Ishikawa diagram (see ishikawa-diagram).
  • futurespective Use when asked to run a futurespective — a forward-looking group exercise imagining possible future scenarios to inform current decisions — as the forward-facing counterpart to a retrospective, drawing on scenario planning and SWOT analysis (see swot-analysis).
  • getting-feedback Use when asked how to seek out or receive feedback well — actively soliciting it, listening without immediately defending, separating the signal from delivery, and deciding what to act on — as the complement to giving-feedback.
  • incident-response-plan Use when asked to write or review an incident response plan — the pre-defined process for handling a security or operational incident while it's happening, including severity levels, roles, and escalation — as distinct from a [[postmortem]] (the after-the-fact analysis once the incident is over) and a [[business-continuity-plan]] (broader, org-wide continuity planning rather than tactical in-the-moment response).
  • itil-5 Use when asked to apply, explain, or adopt ITIL 5, the PeopleCert ITIL release that emphasizes digital product management and AI governance alongside service management. Distinct from [[iso-iec-20000]] (certifiable standard), [[verism]] (organization-wide approach), and [[product-management]] (general product practice).
  • kaizen Use when asked to apply Kaizen — continuous, incremental, all-employee process improvement built on the Plan-Do-Check-Act cycle (see plan-do-check-act) — as distinct from a project-scoped Six Sigma DMAIC effort (see dmaic), which is heavier-weight and typically team-led rather than everyone-participating.
  • kanban Use when asked to set up or run a Kanban board — columns, work-in-progress limits, continuous flow — as an alternative to Scrum's fixed sprints (see scrum), suited to continuous-flow work rather than timeboxed iterations.
  • key-risk-indicators Use when asked to define or choose a Key Risk Indicator (KRI) — an early-warning metric for organizational risk — as the risk-focused counterpart to key-performance-indicators's performance-focused metrics, typically used together for a full view of health.
  • large-scale-scrum Use when asked to scale scrum across many teams with LeSS (Large-Scale Scrum) — one Product Backlog, one Product Owner, and one Sprint shared across all teams, deliberately minimizing added roles and process — as distinct from scaled-agile-framework's more prescriptive, role-heavy approach to the same scaling problem.
  • legal-compliance-audit Use when asked to conduct a legal compliance audit — systematically checking an organization's actual practices against applicable laws and regulations — as an internal, ongoing counterpart to legal-due-diligence's transaction-specific investigation.
  • legal-data-privacy-compliance Use when asked about legal data privacy compliance — meeting obligations under data protection laws (such as GDPR, CCPA, and similar regimes) for collecting, using, and protecting personal data — as a specific, commonly audited compliance area.
  • load-testing Use when asked to test how an application performs under expected and peak user load — capacity limits, breaking points — as distinct from stress testing beyond normal capacity (see stress-testing) or sudden-spike testing (see peak-testing), which load testing's staged progression leads into.
  • machine-learning-model-card Use when asked to write or review a model card — a document accompanying a trained ML model that describes what it does, how it was trained and evaluated, and its known limitations — as distinct from [[mlops]], which covers the infrastructure for deploying and monitoring a model rather than documenting it for downstream users.
  • maturity-models Use when asked to design, apply, or explain a maturity model — level naming conventions, top-down vs bottom-up construction, or well-known examples (CMMI, DevOps, Agile maturity models) — grounded in joelparkerhenderson/maturity-models, including documented rebuttals.
  • mermaid-diagram Use when asked to write Mermaid.js diagram syntax — flowcharts, sequence diagrams, Gantt charts, class diagrams, state diagrams, pie charts — a browser-based, Markdown-like alternative to plantuml-diagram, and natively supported inside Markdown on many platforms (GitHub, GitLab, and this environment's own Artifacts).
  • mlops Use when asked about MLOps — the practices and infrastructure for deploying, monitoring, and maintaining ML models in production reliably — as distinct from the model-development and training work itself, and from [[machine-learning-model-card]], which documents a model for downstream users rather than operating it once it's live.
  • on-call-rotation Use when asked to set up or document an on-call rotation — the schedule and process for who's responsible for responding to alerts and incidents outside normal hours, and how that responsibility hands off between people — as distinct from an [[incident-response-plan]], which governs what happens once an incident is declared rather than who's watching for one in the first place.
  • performance-testing Use when asked to measure application responsiveness and resource use under workload — the umbrella covering load, stress, endurance, and spike testing (see load-testing, stress-testing) — to identify bottlenecks and confirm the system meets performance requirements.
  • portfolio-management Use when asked to prioritize an organization's whole set of projects/programs against strategy and capacity, write a portfolio review or investment case, or explain portfolio management concepts (strategic alignment, capacity-based sequencing) — as distinct from managing one project (see project-management) or one program of related projects (see program-management).
  • postmortem Use when asked to write or facilitate a postmortem — a blameless, after-the-fact analysis of an incident, its timeline, root cause, and follow-up actions — as distinct from an [[incident-response-plan]] (what happens during the incident, not after) and a routine [[agile-reflection]] (triggered by an incident, not run on a scheduled cadence).
  • product-roadmap Use when asked to build, review, or explain a product roadmap — the ongoing, product-wide plan of themes and rough timeframes communicated to stakeholders — distinct from a [[project-charter]], which is a single project's formal scope document with a defined start and end.
  • project-management-body-of-knowledge Use when asked about PMBOK (the Project Management Body of Knowledge, published by PMI) specifically — its knowledge areas and process groups — as distinct from the general project-management discipline and from a specific methodology like prince2.
  • prompt-engineering Use when asked to write, improve, or debug a prompt for a language model — getting reliable, intended behavior through specific instructions, examples, and context — as distinct from [[machine-learning-model-card]], which documents a trained model's capabilities and limits rather than shaping its behavior through the prompt.
  • raci-matrix Use when asked to build a RACI matrix specifically — the Responsible/Accountable/Consulted/Informed variant of responsibility-assignment-matrix — including the PARIS variant sometimes used instead.
  • release-notes Use when asked to write release notes — the announcement accompanying one specific release, aimed at users deciding whether and how it affects them — as distinct from a [[changelog]], which is the complete, cumulative running history across every version rather than one release's announcement.
  • risk-register Use when asked to create or maintain a risk register — a living table of identified risks with likelihood, impact, score, owner, mitigation, and status — as distinct from a full RAID log ([[risks-actions-issues-decisions]]), which also tracks actions, issues, and decisions, and from [[key-risk-indicators]], which are the metrics that signal a risk is materializing.
  • risks-actions-issues-decisions Use when asked to maintain a RAID log using the Risks/Actions/Issues/Decisions expansion of RAID — one of two common RAID acronym expansions in project management, the other being Risks/Assumptions/Issues/Dependencies (see project-management). Confirm which expansion a specific team means before assuming.
  • roi-analysis Use when asked to calculate or compare the return on investment (ROI) of a decision or initiative — net benefit relative to cost — as distinct from a [[budget-forecasting]] projection, which tracks overall income and expense over time rather than evaluating one specific investment decision.
  • root-cause-analysis Use when asked to investigate why a problem happened, rather than just its symptoms — the identify/gather-data/analyze/identify-cause/plan/implement steps of root cause analysis (RCA) — used across engineering, manufacturing, healthcare, software, and business management.
  • runbook Use when asked to write a runbook — a step-by-step operational procedure for a specific, recurring task or system situation, such as restarting a service, rotating a credential, or failing over a database — as distinct from an [[incident-response-plan]], which governs roles and communication during an incident rather than the precise technical steps for one specific action.
  • scaled-agile-framework Use when asked to scale agile delivery across many teams with SAFe (Scaled Agile Framework) — Agile Release Trains, PI Planning, and Portfolio/Large Solution/Essential configurations — as distinct from large-scale-scrum's deliberately minimal alternative for the same scaling problem, and from disciplined-agile's goal-driven toolkit approach rather than a single prescribed structure.
  • scrum Use when asked to set up or run Scrum — roles (Product Owner, Scrum Master, Development Team), artifacts (Product Backlog, Sprint Backlog, Increment), and events (sprint planning, daily scrum, review, retrospective) — as a fixed-sprint alternative to Kanban's continuous flow (see kanban).
  • scrum-of-scrums Use when asked to coordinate multiple scrum teams working on one product via a Scrum of Scrums meeting — a lightweight cross-team sync sending one ambassador per team — as distinct from adopting a full scaling framework like large-scale-scrum or scaled-agile-framework, which restructure roles and planning rather than just adding a coordination meeting.
  • scrumban Use when asked to run Scrumban — a hybrid blending scrum's planning structure with kanban's continuous-flow board and WIP limits, pulling work on demand rather than committing to a fixed sprint backlog — for a team that needs more structure than pure Kanban but finds Scrum's fixed sprint commitment a poor fit for their work's variability.
  • security-testing Use when asked to evaluate a system's security — vulnerability scanning, authentication/authorization testing, encryption verification, security configuration review — the umbrella discipline penetration testing (see penetration-testing) and compliance testing (see compliance-testing) both sit within.
  • service-catalog Use when asked to build or document a service catalog — a structured, discoverable list of the IT or business services an organization offers internally or externally, what each includes, and how to request it — as distinct from a [[service-level-agreement]], which defines the performance commitment for one specific service rather than listing what services exist at all.
  • service-integration-and-management Use when asked to apply Service Integration and Management (SIAM), a methodology for managing multiple service suppliers in a complex ecosystem, especially when an organization outsources parts of IT and must integrate vendors. Distinct from [[vendor-management]] (single-supplier relationships), [[itil-5]], and [[service-level-agreement]].
  • service-level-agreement Use when asked to draft or review a service level agreement (SLA) — defining expected service performance such as uptime, response time, or support tiers between a provider and customer — as distinct from a statement-of-work, which defines a project's specific deliverables and scope rather than ongoing performance standards; for general guidance only, not legal advice, so always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
  • service-management-guide-maintainer-skill Use when asked to write, review, or update a topic, glossary entry, skill link, or reference in the Service Management Guide monorepo and keep it consistent with spec/index.md — as distinct from reading or applying the guide (see service-management-guide-skill).
  • service-management-guide-skill Use when asked to find, explain, or apply content from the Service Management Guide — choosing topics for a role or problem, running a team conversation from a topic's discussion questions, or adapting one of its AI prompts to a team's own material — as distinct from maintaining or editing the guide (see service-management-guide-maintainer-skill).
  • shift-left-testing Use when asked to move testing earlier in the development lifecycle — code review, static analysis, and testing-as-you-write rather than testing-after-the-fact — the strategic principle underlying test-driven development (see test-driven-development) and CI-integrated quality gates broadly.
  • six-sigma Use when asked about the Six Sigma quality-management methodology as a whole — belt-level roles, sigma levels/defects-per-million, and choosing between DMAIC (improving an existing process, see dmaic) or DMADV/DFSS (designing a new one) — as distinct from running the DMAIC cycle itself, which this skill defers to for the step-by-step improvement procedure.
  • software-engineering-metrics Use when someone wants to apply this book's guidance to their own team or organization -- choosing a metric, naming its gaming vector and guardrail, applying the Flow Framework, SPACE, or DORA, filling in a metrics charter or dashboard spec, or running the maturity self-assessment. Not for editing the book's own chapters; use software-engineering-metrics-maintainer for that.
  • stakeholder-analysis Use when asked to run or explain a stakeholder analysis — identifying stakeholders and mapping their interest and influence (a power/interest grid) to plan engagement — as the analytical step that typically precedes formalizing responsibilities in a responsibility-assignment-matrix.
  • statistical-analysis Use when asked which statistical technique fits a data question — descriptive vs. inferential statistics, regression, time series, factor/cluster analysis, data mining — as the umbrella technique-selection layer above more specific methods like bayes-theorem-analysis, chi-square-analysis, and monte-carlo-analysis.
  • survey-design Use when asked to design a survey, questionnaire, or feedback form — writing questions and response scales that actually measure what they're meant to without leading or confusing respondents — as distinct from a [[user-interview-guide]], which is a qualitative, open-ended conversation rather than a standardized instrument.
  • swot-analysis Use when asked to run or explain a SWOT analysis — Strengths, Weaknesses, Opportunities, Threats — the internal-vs-external strategic planning framework, sourced from Wikipedia's SWOT analysis article, including its history and known limitations.
  • team-focus Use when asked to apply McKinsey's TEAM FOCUS framework — the interpersonal TEAM half (Talk, Evaluate, Assist, Motivate) and the analytical FOCUS half (Frame, Organize, Collect, Understand, Synthesize) — for structuring both team dynamics and a problem-solving process together.
  • test-driven-development Use when asked to write code test-driven — red/green/refactor, writing the failing test first, or explaining TDD's benefits and limits — as distinct from behavior-driven development's given/when/then framing (see behavior-driven-development) or writing tests after the fact.
  • training-needs-analysis Use when asked to identify the actual gap between current and needed skills or knowledge before building training — root cause, target audience, success measure — so training solves a real, specific gap rather than being commissioned on a generic assumption; distinct from [[curriculum-design]], which designs the program once a genuine training need is confirmed.
  • trend-analysis Use when asked to analyze data over time to identify patterns and forecast — regression, moving averages, exponential smoothing — as distinct from anomaly-analysis's focus on individual deviant points rather than the overall directional pattern.
  • two-way-door-decisions Use when asked to decide how much deliberation, evidence, and approval a decision deserves by classifying it as reversible (a two-way door, decide fast and adjust) or hard to reverse (a one-way door, slow down and verify), and to find ways to turn one-way doors into two-way ones — as distinct from a [[weighted-decision-matrix]] (choosing among options), a [[premortem]] (stress-testing a chosen plan), and [[architecture-decision-record]] (documenting a decision made).
  • user-story Use when asked to write or review a user story — a short, structured statement of a specific end-user need ("As a [role], I want [goal], so that [benefit]") that drives a feature — typically one of several components inside a larger [[product-requirements-document]].
  • value-stream-map Use when asked to build a value stream map — a lean process-analysis diagram tracing material and information flow through a process, distinguishing value-adding steps from waste and quantifying time — as distinct from a plain swimlane-diagram (see below), which shows who does what without that waste analysis.
  • vendor-management Use when asked to set up or run ongoing vendor management — the practice of overseeing an external vendor relationship after a contract is signed — as distinct from the earlier selection stage covered by [[request-for-proposal]] and [[contract-review]].
  • workflow-analysis Use when asked to examine how work actually flows through a process or organization — workflow mapping, time analysis, data-flow analysis, roles/responsibilities, decisions, controls — as the process-level counterpart to task-analysis's single-task focus.