docs(dev): stack-close names the next link of a chain (#205)
CI / verify (push) Successful in 7m45s
CI / pwsh (push) Successful in 2m28s

Files changed:
- docs/dev/development.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-10 09:09:03 +02:00
1 parent 3c80262a05
commit 88788d6663
1 file changed
+3 -2
+3 -2
View File
@@ -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 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 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 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 run, `stack-close` checks the body's final state and stale `docs/` and contract prose, closes
the issue. The handover goes through the state in the tracker, not through a session's context: 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 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 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 (`/stack-build #N`, `/stack-close`) - exactly where the choice falls whether to continue in the