From 88788d6663cb6b4adee907053d5232b80441f329 Mon Sep 17 00:00:00 2001 From: Torben Nehmer Date: Sat, 10 Oct 2026 09:09:03 +0200 Subject: [PATCH] docs(dev): stack-close names the next link of a chain (#205) Files changed: - docs/dev/development.md Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2 --- docs/dev/development.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/dev/development.md b/docs/dev/development.md index a128437..11d2041 100644 --- a/docs/dev/development.md +++ b/docs/dev/development.md @@ -279,8 +279,9 @@ low, and three kinds have to be told apart before any of it turns into work: Three skills (`instructions/dev/`, present only in this origin repository) carry a session that works on the stack itself rather than on wiki content through three phases: `stack-dev` works the issue out until its body is "ready", `stack-build` builds, publishes and waits for a green CI -run, `stack-close` checks the body's final state and stale `docs/` and contract prose, and closes -the issue. The handover goes through the state in the tracker, not through a session's context: +run, `stack-close` checks the body's final state and stale `docs/` and contract prose, closes +the issue and, where the body carries a `## Kette` section, names the next link of that chain +with the slash command that starts it. The handover goes through the state in the tracker, not through a session's context: every phase change works in the same session or after `/clear`. `stack-dev` triggers automatically; `stack-build` and `stack-close` are started only by the operator, by slash command (`/stack-build #N`, `/stack-close`) - exactly where the choice falls whether to continue in the