Consult acceptance
Skill Timelnapp/skills/skills/consulting-os/consult-acceptance
6 SKILLs to improve Claude Code memory, derived from Timeln's second brain capability to remember everything.
npx -y skills add Timelnapp/skills --skill consult-acceptanceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Trigger on "acceptance criteria", "consult acceptance", "success criteria", "signoff matrix", "deliverables per phase", "primary path fallback", "definition of done". Per-phase deliverables, measurable criteria (tech + business/ops), owner, primary path + fallback. NOT commercial terms (use consult-commercial), NOT gate questions (use consult-gates).
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.3 KB, 476 tokens by cl100k_base, as published. Nobody here has run it
Consult Acceptance -- Acceptance Matrix
Map each gate phase to deliverables, measurable success, sign-off, and fallbacks under uncertainty.
Inputs
| Input | Required |
|---|---|
Gate table from consult-gates | yes |
Optional: timeln-warned -- fold real past failures into fallback rows only when sourced; otherwise unknown -- workshop.
Workflow
- For each phase row in the gate table, add:
- Deliverables -- nouns (artifacts, systems states, tests passed), not tasks.
- Technical success -- measurable or binary checks.
- Business / ops success -- how the business knows value landed.
- Sign-off owner -- named role; align with gate owner or explain delta.
- Primary path -- default path if no surprises.
- Fallback -- what you do if the primary path fails technical or data reality; must stay inside scope of the phase.
- Flag missing measurability with
TBD metric -- propose in workshop. - If a phase has no plausible fallback, write none -- escalate / stop instead of soft language.
Output -- exactly this shape
## Acceptance -- <client or "TBD"> -- <YYYY-MM-DD>
| Phase | Deliverables | Technical success | Business/ops success | Sign-off | Primary path | Fallback |
|---|---|---|---|---|---|---|
| ... | | | | | | |
**Global gaps**
- <rows needing client input>
Rules
- Every phase from
consult-gatesgets exactly one matrix row unless merged explicitly in gates. - Do not promise numbers the source did not provide -- use
TBDwith how you will derive them. - Fallback is not scope expansion -- it is a scoped pivot.
Common failure modes
| Mistake | Fix |
|---|---|
| Success = "complete phase 2" | Replace with checks a third party could verify |
| One generic sign-off for all | Per-phase owners or explicit "same as gate owner" |
| Fallback = "add more people" | Tie fallback to data, scope trim, or alternate design inside phase |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.