Consult gates
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-gatesAssembled 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 "lock phasing", "stage gates", "consult gates", "phase outcomes", "primary question per phase", "entry exit criteria", "gate table". Defines staged outcomes with one primary question per phase plus entry/exit. NOT acceptance metrics (use consult-acceptance), NOT personal save cascade (timeln-plan is parallel -- use its output as optional input only).
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, 477 tokens by cl100k_base, as published. Nobody here has run it
Consult Gates -- Stage Gate Table
Break work into stages; each stage answers one primary question; gates have entry and exit.
Inputs
| Input | Required | Notes |
|---|---|---|
Phasing hints from consult-arc | yes | Sequence + option (MVP/Pilot/Full) if chosen |
timeln-plan artifact or stage list | optional | Import stage names / bets as raw material only -- rewrite for client phases |
Workflow
- Name 3-5 phases max (merge weak phases). Order is linear unless source needs parallel -- if parallel, split rows and note dependency.
- For each phase write:
- Primary question -- exactly one yes/no or decidable question.
- Entry criteria -- what must be true to start.
- Exit / outcome -- what exists when the gate opens.
- Gate owner -- role who says the gate passed;
unknown -- confirmif missing.
- Add between-stage notes only where ordering is controversial (one line: what must not happen out of order).
Output -- exactly this shape
## Gates -- <client or "TBD"> -- <YYYY-MM-DD>
**Selected option:** MVP | Pilot | Full | mixed -- <note>
| Phase | Primary question | Entry | Exit / outcome | Gate owner |
|---|---|---|---|---|
| 1 ... | | | | |
| 2 ... | | | | |
**Sequencing locks**
- ...
Rules
- Primary question is not a task list -- it is what the phase decides.
- If input from
timeln-planconflicts withconsult-arc, preferconsult-arcfor naming; pull content from plan only when clearly the same engagement. - Do not add acceptance metrics here -- qualitative gate only; metrics go to
consult-acceptance.
Common failure modes
| Mistake | Fix |
|---|---|
| "Phase 2: build stuff" | Replace with the question phase 2 answers |
| Same owner for every gate | Split or name RACI per phase |
| More than one primary question in a row | Split phase or merge until one remains |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.