engagement-scoping SKILL.md skillA
engagement-scoping from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/engagement-scoping@git:20260303.508e8a6Pins git:20260303.508e8a6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/consultant/engagement-scoping/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260303.508e8a6, committed Mar 3, 2026
- Size
- 8,553 bytes
- Repository stars
- 21
- License
- MIT
Define the scope, success criteria, roles, and boundaries for a consulting engagement. Use when a consultant says "help me scope this engagement", "I need to define what's in and out", "the client keeps adding things", "scope is getting fuzzy", "we need a contracting conversation", "I'm not sure what we actually agreed to", "help me set boundaries with a client", or "what should be in a kickoff". Also trigger when describing an engagement that feels like it is expanding without agreement, or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Overview Based on **"Flawless Consulting"** by Peter Block. The contracting phase is the most important and most skipped phase of a consulting engagement. Vague contracting creates resentment, scope creep, and failed engagements - not bad execution. A well-contracted engagement defines what success looks like, who does what, what happens when things go wrong, and what is explicitly not in scope. Do it in writing, at the start. ## Workflow ### Step 1: Clarify the Business Problem Before scoping anything, confirm you are solving the right problem. Block warns against solving the presenting problem when the real problem is different. Ask: - "What is the specific business problem this engagement is solving?" (Not the symptom - the root cause) - "What would we see differently in 6 months if this engagement succeeds?" - "Who is most affected by this problem and how?" - "What has already been tried?" Document: a 2-3 sentence problem statement in business language. Share it with the client and confirm alignment before proceeding. If they revise it significantly, you were not scoping the right problem. ### Step 2: Define Success Criteria …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/engagement-scoping@sha256:300fd7fa5db2d67aThe line at the top of this page pins the label git:20260303.508e8a6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7su6i5pyug7cr3x7)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8553 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7su6i5pyug7cr3x7 GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/engagement-scoping GET https://markdownregistry.com/api/v1/blob/300fd7fa5db2d67a4bb50b18c2dd3fbdebbf232b6c0a62f2d0fa9b8ae6698895
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from qa-aman/claude-skills
Every file in qa-aman/claude-skills