Run any Skill in Manus with one click

end-phase

Stars35

Forks2

UpdatedJuly 1, 2026 at 20:19

Explicitly end a tale-mode build phase by clearing the phase marker(s) under <project>/.claude/, which stops the Stop-hook's committed-gate enforcement for this repo. Invoke ONLY when the user explicitly asks to end the phase, stop or disarm the tale-mode phase loop, or clean up phase markers — never proactively, and never as a way to escape a failing gate.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

alicicek

alicicek/tale-mode

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	end-phase
description	Explicitly end a tale-mode build phase by clearing the phase marker(s) under <project>/.claude/, which stops the Stop-hook's committed-gate enforcement for this repo. Invoke ONLY when the user explicitly asks to end the phase, stop or disarm the tale-mode phase loop, or clean up phase markers — never proactively, and never as a way to escape a failing gate.

End a phase

A /tale-mode:kickoff-phase (or the kickoff-phase skill) arms committed-gate enforcement by writing a session-scoped marker <project>/.claude/tale-mode.phase.<session-id>.json. Normally you never need this skill — the marker dies with the session (/clear orphans it and a ~24h reap removes strays), and hitting max_rounds disarms it. This skill is the explicit, immediate off-switch: the user has decided the phase is over (shipped, abandoned, or being re-scoped) and wants enforcement gone now, mid-session.

Guardrail first: if a committed gate is currently RED and the user hasn't clearly said to stop the phase, do NOT reach for this skill — driving the gate to green (or pausing via needs_user in the marker) is the designed path. Ending a phase to silence a failing gate is the exact band-aid tale-mode exists to prevent; confirm intent before clearing.

To end the phase, from the project root:

ls .claude/tale-mode.phase.*.json 2>/dev/null   # see what's armed (may be none)
rm -f .claude/tale-mode.phase.*.json            # clear it/them

Notes, so you report accurately:

You can't know your own session id, so clear all markers matching the glob. That's safe: any non-current markers belong to crashed/old sessions (each session only ever reads its own), and a marker only enables enforcement of gates the user already content-hash-trusted — clearing markers just returns every session in this repo to normal, un-enforced behavior.
This also removes a not-yet-adopted .claude/tale-mode.phase.pending.json (the cross-platform kickoff arming file), un-arming a kickoff that hasn't had its first Stop event yet.
This does not touch an ad-hoc goal-file (.claude/active-goal*.json) — that's the separate agent-armed loop. Mention it if one exists; only delete it when the user asks for that too (and explain why, per the goal-loop's own rules).
No markers found → say so; nothing was armed, nothing to end.
Confirm the result to the user: what was removed, and that the committed gates are now inert until the next kickoff.

More from this repository

same repository

kickoff-phase

alicicek/tale-mode

Build ONE scoped phase of an existing multi-phase plan in a fresh session — re-verify the plan against the live code, interview the user sharply on real forks, then implement only that phase behind plan-mode approval with runnable verification and a fresh-eyes review. Invoke explicitly when starting a phase (the cross-platform form of /tale-mode:kickoff-phase; on Codex, name the plan-file + phase in your prompt). On Claude Code, use the /tale-mode:kickoff-phase command instead of this skill.

2026-07-0335

plan-phase

alicicek/tale-mode

Plan a large, multi-phase feature to a high bar — verify against the code, receipts on every decision, an adversarial fresh-eyes review, and runnable verification gates, decomposed into independently-shippable phases. Invoke explicitly when starting a big multi-session build (the cross-platform form of the /tale-mode:plan-phase command; on Codex, name the task in your prompt). On Claude Code, use the /tale-mode:plan-phase command instead of this skill.

2026-07-0335

tale-mode

alicicek/tale-mode

Make Claude work rigorously on complex or high-stakes tasks instead of one-shotting them. Triggers: "tale mode", "tale on" — or self-activates on hard multi-step work. Enforces staged planning, decisions-with-receipts, verifying claims against the real source (not memory), parallel delegation, an independent adversarial review for high-stakes output, and durable progress notes. Right-sizes itself so trivial work stays fast.

2026-07-0235

seed-gates

alicicek/tale-mode

Scan a repo's package.json scripts, CI workflows, and equivalent manifests, then SUGGEST a committed .claude/tale-mode.json gate list for tale-mode's Stop-hook loop — suggestions only; this skill never writes the config unasked, never trusts it, and never arms anything. Invoke ONLY when the user explicitly asks to seed, suggest, or set up tale-mode gates for a repo.

2026-07-0135

trust

alicicek/tale-mode

Reference for tale-mode's two user-only opt-in files — the committed-gate trust store (~/.claude/tale-mode-trust) and the Codex cwd-root opt-in (~/.tale-mode-allow-cwd-root) — and their security model. Invoke ONLY when the user explicitly asks how to trust a repo's committed tale-mode gates, about the "content-hash is NOT trusted" notice, or how to enable the autonomous loop on Codex. Do NOT load this proactively, and NEVER write either file yourself — both grants are manual, user-only actions.

2026-07-0135

name	end-phase
description	Explicitly end a tale-mode build phase by clearing the phase marker(s) under <project>/.claude/, which stops the Stop-hook's committed-gate enforcement for this repo. Invoke ONLY when the user explicitly asks to end the phase, stop or disarm the tale-mode phase loop, or clean up phase markers — never proactively, and never as a way to escape a failing gate.

End a phase

To end the phase, from the project root:

ls .claude/tale-mode.phase.*.json 2>/dev/null   # see what's armed (may be none)
rm -f .claude/tale-mode.phase.*.json            # clear it/them

Notes, so you report accurately:

You can't know your own session id, so clear all markers matching the glob. That's safe: any non-current markers belong to crashed/old sessions (each session only ever reads its own), and a marker only enables enforcement of gates the user already content-hash-trusted — clearing markers just returns every session in this repo to normal, un-enforced behavior.
This also removes a not-yet-adopted .claude/tale-mode.phase.pending.json (the cross-platform kickoff arming file), un-arming a kickoff that hasn't had its first Stop event yet.
This does not touch an ad-hoc goal-file (.claude/active-goal*.json) — that's the separate agent-armed loop. Mention it if one exists; only delete it when the user asks for that too (and explain why, per the goal-loop's own rules).
No markers found → say so; nothing was armed, nothing to end.
Confirm the result to the user: what was removed, and that the committed gates are now inert until the next kickoff.