From sextant
Raise, resolve, or list carry-forward concerns — feature-global unknowns that outlive the tranche that found them and must be consumed by a later tranche. Blocks finalize until resolved.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sextant:tranche-concernThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manage **carry-forward concerns**: open unknowns or risks discovered in one
Manage carry-forward concerns: open unknowns or risks discovered in one
tranche that cannot be closed there and must be carried into a later tranche of
the same feature. Unlike a tranche's in-doc open questions (which are
tranche-local), a carry-forward concern lives at the feature level in
.sextant/tranches.json and blocks finalize until it is resolved.
This is the escape valve at the end of the unknown escalation ladder:
grep finding ─▶ open question before implementation (resolve by READY — hard gate)
─▶ open question before ship (resolve in-flight — soft gate)
─▶ carry-forward concern (resolve in a LATER tranche — finalize gate)
Raise a concern (raised against the currently-active tranche):
node "${CLAUDE_PLUGIN_ROOT}/bin/tranches.mjs" concern add \
--text "<the concern>" [--target <tranche id>] --root "$PWD"
--target is an OPTIONAL surfacing hint (which later tranche likely owns it).
It is never a gate — a wrong target won't block anything. Accepts T4 or 4.Resolve a concern when a later tranche consumes it:
node "${CLAUDE_PLUGIN_ROOT}/bin/tranches.mjs" concern resolve \
--id <n> [--note "<how it was addressed>"] --root "$PWD"
List all concerns (open + resolved):
node "${CLAUDE_PLUGIN_ROOT}/bin/tranches.mjs" concern list --root "$PWD"
Marking a concern resolved asserts you addressed it — Sextant does not verify the
underlying work (same as bug-log / remember). The real enforcement is the
finalize hard-block: a feature cannot be finalized while any concern is open
(use finalize --force to abandon them, which prints them loudly first).
Open concerns appear in the SessionStart "Active tranche" block (flagging any
targeted at the now-active tranche) and in the first-turn reminder count. Use
/sextant:tranche-status to see the full list any time.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub kylesiwi/sextant --plugin sextant