are-we-done
[Adam''s Skills] Deterministic close-out gate for a session or work tree. Sweeps a fixed set of sources — the todo list, this session''s own promises, git…
[Adam''s Skills] Alias for the ttp skill. Shape user-facing output to be brief and direct — lead with the substance, keep the default answer short, and expand only when the user asks for detail. Leaves the user in control: Claude settles small, reversible, or already-decided
$ npx -y skills add adamlinscott/claude-skills --skill to-the-point --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/to-the-pointContext preview
The summary Claude sees to decide when to auto-load this skill.
[Adam''s Skills] Alias for the ttp skill. Shape user-facing output to be brief and direct — lead with the substance, keep the default answer short, and expand only when the user asks for detail. Leaves the user in control: Claude settles small, reversible, or already-decided
name: to-the-point description: '[Adam''s Skills] Alias for the ttp skill. Shape user-facing output to be brief and direct — lead with the substance, keep the default answer short, and expand only when the user asks for detail. Leaves the user in control: Claude settles small, reversible, or already-decided points and proceeds, but routes high-impact calls (ADR-worthy, production, project shape, which features get built, infrastructure) to the user with enough context to decide. Only shapes prose written for the user to read; Claude''s own reasoning, tool use, code, and planning are untouched. Triggers on the user naming it, with or without a slash: "ttp", "/ttp", "to the point", "/to-the-point", "be to the point" — a bare "ttp" on its own line is a request to turn this on. Do not load it for a general "be brief"; the user has to name it. Stays on until "stop ttp", "ttp off", or "normal mode".'
This is an alias so that both `/ttp` and `/to-the-point` work — and so that either name, typed bare with no slash, still reaches the skill.
Read `skills/ttp/SKILL.md` — resolve it relative to this file's parent directory (`../ttp/SKILL.md`), or at `~/.claude/skills/ttp/SKILL.md` when installed — and follow it in full. Pass through any flags the user gave.
Do not duplicate the rules here. One source of truth: a divergent copy drifts, and then the two names behave differently.
Each skill lives under skills//SKILL.md and is the single source of truth; an install script links them into the global skills directory (~/.claude/skills/) so Claude loads them in every session, on every machine.
Repo: adamlinscott/claude-skills
[Adam''s Skills] Deterministic close-out gate for a session or work tree. Sweeps a fixed set of sources — the todo list, this session''s own promises, git…
[Adam''s Skills] DEPRECATED — superseded by /build-it. Do not use for new work. Surfaced the load-bearing assumptions behind a task before a long run — goal,…
[Adam''s Skills] Print a plain-English re-entry briefing for a user who has lost the thread of a long-running session — after a distraction, overnight, or over…
[Adam''s Skills] Build a piece of work, from wherever it is written down — a ticket number or URL, a plan or spec file, the plan agreed in the conversation…
[Adam''s Skills] Check whether the installed copy of this skills collection is behind its remote, and offer to update it. Runs a script that resolves the clone…
[Adam''s Skills] Audits a repository''s Claude context-injection setup — CLAUDE.md, CONTEXT.md, docs/, .claude/agents/, and the per-project memory directory.…