How do I install the Consult Gates skill?

Run npx skillmds@latest add timelnapp/consult-gates in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Consult Gates safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Consult Gates?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Consult Gates free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Consult Gates?

Timelnapp (@timelnapp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Consult Gates by timelnapp — Agent Skill

Name: Consult Gates
Author: Timelnapp

Consult Gates

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).

Timelnapp e4f5f12 2.3 KB Updated Sep 17, 2026

File contents

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 -- confirm if 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-plan conflicts with consult-arc, prefer consult-arc for 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

---name: consult-gatesdescription: 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).license: MIT---# Consult Gates -- Stage Gate TableBreak 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 |## Workflow1. Name **3-5 phases** max (merge weak phases). Order is linear unless source needs parallel -- if parallel, split rows and note dependency.2. 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 -- confirm` if missing.3. 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-plan` conflicts with `consult-arc`, prefer `consult-arc` for 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 |

Frequently asked questions