jiantw83
f38d1f3087
現行紀錄只記「被叫用」，沒有成敗也沒有結束碼。跑完整輪的技能與開場就 中止的技能，在紀錄裡長得一模一樣。 start 由技能用量 hook 順手發，不必改技能文件。end 只能由技能自己在收尾 步驟寫——hook 接在技能工具呼叫上，而實際工作發生在之後的模型輪次，它在 原理上看不到成敗。有 start 沒有配對的 end，就是那一輪中止了。 status 五選一，每支技能各自寫明什麼情況選哪一個。找不到回報腳本就安靜 跳過，回報失敗一律不改變技能自己的結論。
18 KiB
name, description
| name | description |
|---|---|
| plan | SDLC planning stage. Gate on capability tags enforced in code by sdlc-gate (plan requires reasoning-max, verified against the transcript's actual model id), pick or create a plan from PLAN_CONTENTS, which sits in the separate CONTENTS wiki repo, then run a decision tree until goal, scope, and feasibility reach consensus. Produce user stories into wiki page PLAN_{HASH} in the PLAN wiki repo, upsert the directory row through jsc-gitea/tools/wiki-contents.sh with an absolute wiki-url link, then close with tools/stage-report.sh - model tag verdict, worklog link, every wiki link written. Logic only - never write code or modify files. Use when the user wants to start or refine a plan; not for analysis or implementation. |
plan
Goal: create or extend the wiki plan page PLAN_{HASH}.
This skill is a logic-only stage: never output code, and never modify any file.
{HASH} = the shared wiki hash for {owner}/{repo} used to build the PLAN_{HASH} page name, computed by jsc-gitea/tools/hash-id (see jsc-gitea:wiki). It prints the full 40-character uppercase SHA-1 of its input — no truncation to 8 characters, no prefix rewrite. Never shorten it by hand: a shortened name points at a page nobody else writes to.
The two pages this stage touches live in two different wiki repos. The content page PLAN_{HASH} sits in the repo jsc-gitea/tools/gitea.sh wiki-repo PLAN resolves. The directory page PLAN_CONTENTS sits in the repo gitea.sh wiki-repo CONTENTS resolves — JSC_WIKI_REPO_CONTENTS first, JSC_WIKI_REPO second, exit 3 when neither is set; it never falls back to JSC_WIKI_REPO_PLAN. The directory row links the plan page by the absolute URL from gitea.sh wiki-url {PLAN repo} PLAN_{HASH}, written as [{text}]({url}) — one link syntax, whichever wiki the two pages sit in. The syntax and the check that runs before every write: "Every link is checked before it reaches a page" below.
All wiki reads and writes go through jsc-gitea:wiki. A failed wiki read or write stops this stage: report which page and which operation failed, never carry on against a page you could not read, and never report a page as saved when the write failed. Steps 8 and 9 still run after such a stop.
Steps
-
Model gate and stage lock — run
jsc-cli/tools/model-tags.sh sync, thenjsc-hooks/hooks/sdlc-gate.sh lock plan. This stage requires thereasoning-maxcapability tag. Rules:references/model-gate.md. Completion condition: the script exited 0, and you have reported the stage, the required tag, the actual model id it read from the transcript, and the verdict. -
Read
PLAN_CONTENTSviajsc-gitea:wiki, out of the CONTENTS wiki repo (gitea.sh wiki-repo CONTENTS, never the PLAN one), and list the plans whose status is the literal 「未分析」 (not analyzed), with names and HASH. Completion condition: you have listed every 未分析 plan with its name and HASH, or reported that none exists. -
Let the user choose per
jsc-ask:askrules: extend an existing plan (list the not-analyzed plans as options) or create a new plan. State the impact scope on every option. Completion condition: the user has picked one option explicitly, and you have named thePLAN_{HASH}page this run writes to. -
Keep questioning until consensus — rules in
references/consensus.md, which is the single authority for both planning and analysis. Cover all three items:- Goal: the problem to solve and the criteria for success.
- Scope: what is included, what is excluded, which repositories are involved.
- Feasibility: whether the system architecture and data sources support the goal.
One round is never enough: every answer must produce the next question, derived from what that answer just exposed. Never fill a gap with your own assumption, and never move on to user stories while any item is still open.
Completion condition: all three items are settled under both conditions of
references/consensus.md— no remaining unknown that would change the output, and the user's explicit confirmation of the summary you read back. -
Turn the consensus into user stories (the zh-TW pattern 「身為⋯⋯我想要⋯⋯以便⋯⋯」), one per line. Completion condition: every consensus item is covered by at least one user story in that pattern, and no user story rests on an unanswered question.
-
Apply
templates/plan-page.mdto create or update the plan page in the PLAN wiki repo, and write it back viajsc-gitea:wiki. The page content is Traditional Chinese, exactly as the template dictates. Every link on that page is written as[{文字}]({連結})and passesjsc-gitea/tools/link-check.shbefore the write — see "Every link is checked before it reaches a page" below. Completion condition: the page is saved on the wiki and carries every section the template dictates — goal, scope, feasibility, user stories and the consensus summary — with no placeholder left unfilled, and the page holds no link that the check did not clear. -
Upsert this plan's row in
PLAN_CONTENTSwithjsc-gitea/tools/wiki-contents.sh; never hand-edit the directory page. Take the plan page's absolute link fromgitea.sh wiki-url {PLAN repo} PLAN_{HASH}first, and branch on that command's exit code before the row is built — the same branchingjsc-log:worklogruns over this call:Exit What this step does 0 use the URL it printed, verbatim 4 the page is not on the wiki, so the step 6 write has not landed — go back to step 6 and come here again only once the page is saved 5 the page exists but carries no html_url— stop and report it, and never assemble the URL by hand; a hand-built path is not the one Gitea serves7 the key is invalid or lacks permission (HTTP 401/403) — stop and report the key problem. Never read this as exit 4: the plan page is alive, and treating it as absent records a live page as one that was never written 8 any other API failure — stop and report that status, and do not retry the same call unchanged Never let an empty string stand in for the URL: a row whose link cell is empty is a directory entry that points nowhere, and the next run overwrites it as if it were correct. Then check that URL with
jsc-gitea/tools/link-check.shand build the row only on exit 0 — see "Every link is checked before it reaches a page" below; a link that does not answer never goes into a directory everyone else reads. Then build one file holding the single row fromtemplates/plan-contents.md— the plan name, that absolute link written as[{文字}]({連結}), the code repository, the HASH, the literal 「未分析」 and the creation date; produce that file per Hard limits, with a Bash heredoc ormktemp, never withWriteorEdit. Then runjsc-gitea/tools/wiki-contents.sh upsert PLAN 4 {HASH} {row file} templates/plan-contents.md. The key is the HASH column, column 4, written exactly as the row file writes it; a key typed by hand appends a second row for the same plan. Branch on the exit code per "Contents pages are appended, never overwritten" below. Completion condition:wiki-urlreturned 0 and its URL is the one in the row,link-check.shreturned 0 over that URL, the upsert exited 0,PLAN_CONTENTSshows this plan's row with the literal 「未分析」 and that absolute plan-page link, and you have reported all three exit codes plus whether the script printedupdatedoradded. -
Stage report — the last thing this stage does, including every early stop (the model gate blocked, no plan was selectable, a wiki read or write failed). Run
tools/stage-report.sh planwith one--page TYPE:{page}per wiki page this run wrote —--page PLAN:PLAN_{HASH}for the content page and--page CONTENTS:PLAN_CONTENTSfor the directory page, because the script resolves each page's repo from the TYPE you pass and the two pages no longer share one — plus--worklogand--worklog-headingwhen a work log entry exists. No work log yet: write this stage's log content to a file — with a Bash heredoc ormktempper Hard limits, never withWriteorEdit— and pass--pending-file {file} --log-hash {HASH}so it is held for the nextjsc-log:worklogrun. Rules and exit codes:references/stage-report.md. Exit 1 is a warning, never a block. Completion condition: the script's output is reported to the user verbatim, and every wiki page this run wrote appears in it. -
Write this run's
skill-endstatus event — the very last thing this stage does, right after step 8, on every path including every early stop. Runjsc-hooks/tools/report-status.sh skill-end jsc-sdlc:plan {status} {exit} [detail], naming the script the way this stage already namesjsc-hooks/hooks/sdlc-gate.shin step 1. The matchingskill-startevent is written by jsc-hooks on its own, so this step owes only theend: a hook fires on the skill tool call and this stage's work happens in the model turns after it, so no hook can see how this run ended. Astartwith noendis what an aborted run looks like in the record, and this step is the only thing that keeps a finished run from looking like one.{status}is one of five words, never a sixth:Status When planreports itokEvery step's completion condition is met: the gate passed, all three consensus items were confirmed by the user, PLAN_{HASH}is saved with no placeholder left, thePLAN_CONTENTSrow carries the literal 「未分析」 and a checked absolute link, andtools/stage-report.shexited 0blockedStep 1's model gate stopped the run: sdlc-gate.sh lock planexited non-zero because the model running this stage carries noreasoning-maxtag. Nothing was planned, so this is neverfailed— the gate stopping an underpowered model is the gate working, and recording it as a failure sends the next reader hunting for a defect that is not therefailedThe run got past the gate and then a write did not land: the PLAN_{HASH}write failed,wiki-urlreturned 5, 7 or 8,link-check.shreturned 1 so the page was never written, orwiki-contents.shreturned 1, 7 or 8 while the plan page is also unsaveddegradedThe plan page is saved but the directory did not follow it: wiki-contents.shreturned 1, 3, 7 or 8 overPLAN_CONTENTS, ortools/stage-report.shexited 1 (no work log, or a link in its list does not answer). The plan exists; what is missing is the directory row that lets anyone find itabortedThe user stopped the run, or the run stopped itself because its premise did not hold — no plan was selectable and the user wanted no new one, or the consensus rounds ended with no agreement, so no user story was written {exit}is the exit code of the script whose verdict decided the status — the gate's code forblocked, the failing script's code forfailedanddegraded— and0when nothing exited non-zero,okandabortedincluded.[detail]is optional and Traditional Chinese per the STE100 rule: one line, no line break, naming what decided the status (for example 「模型能力標籤不符」 or 「目錄頁未更新」). The script truncates it at 200 characters, so put the short reason there and nothing else.A failure in this step never changes this stage's verdict. The script is not found (jsc-hooks is not installed on this machine, or this CLI's layout puts it somewhere else) → skip the event quietly and carry on; nothing is reported to the user and no step is re-run. The three recording sub-commands are built to exit 0 even when the write fails, so a non-zero code here means only that the call itself was malformed (exit 2, a usage error) — fix the arguments once and, either way, never turn a finished stage into a failed one because the record of it failed. Completion condition: one
skill-endevent has been written for this run, or the script could not be found and that skip is the reason no event exists.
Every link is checked before it reaches a page
One syntax. Every link this stage writes — on PLAN_{HASH}, in the PLAN_CONTENTS row, in the stage report — is written as [{文字}]({連結}). The {連結} is the absolute URL jsc-gitea/tools/gitea.sh wiki-url {repo} {page} printed, used verbatim: never assemble a wiki path by hand, and never write a link as [[頁名]] or [[顯示文字|頁名]]. That form resolves only inside the wiki it sits in, and it fails without an error — the reader sees plain text or a dead link, so a wrong link is neither noticed nor fixable.
Checked before it is written. Collect every link the page is about to carry, hand them all to jsc-gitea/tools/link-check.sh in one run — link-check.sh {網址}..., or the same URLs on stdin, one per line — and write the page only when that run exits 0. It prints one {OK|DEAD|SKIP}<TAB>{網址}<TAB>{說明} line per URL. The check goes through the API, never a web status code: a private repository's web URL answers 404 to a request carrying no key, so a status-code check marks live pages dead.
| Exit | What this stage does |
|---|---|
| 0 | every link answers — write the page |
| 1 | at least one link is dead — write nothing, and report the DEAD lines to the user |
| 2 | usage error: not one URL was passed — pass the links and run it again |
| 3 | the list holds a Gitea URL but GITEA_HOST is unset — report it as a setting to fix and run it again, and never skip the check instead |
| 7 | Gitea authentication failed (401/403) — stop and report the key problem. Never read this as exit 1: an expired key makes live pages look absent, and a page rewritten on that reading loses the links that were fine |
Completion condition: every page this stage wrote was cleared by a link-check.sh run that exited 0, and every non-zero code was branched on as this table says.
Contents pages are appended, never overwritten
PLAN_CONTENTS is a shared directory in the CONTENTS wiki repo: every row on it belongs to somebody's plan, and this run reads none of those rows from anywhere else. So the write is an upsert of one row on top of the content just read — never a whole-page overwrite, and never a row that belongs to another plan. jsc-gitea/tools/wiki-contents.sh upsert is the one way this stage does it: it resolves the CONTENTS repo, reads the whole page, replaces the row whose key column matches and appends when none matches, then writes the page back.
Branch on its exit code:
| Exit | What this step does |
|---|---|
| 0 | the row is in place — carry the updated or added word it printed into the stage report |
| 1 | the write failed, or the page holds no markdown table — report it as a failed write and go to step 8 as a failure |
| 2 | an argument was rejected (unknown type, key column, missing row file) — fix the argument and run it again; nothing was written |
| 3 | no CONTENTS wiki repo is configured — stop and report JSC_WIKI_REPO_CONTENTS and JSC_WIKI_REPO as the two variables to set. The plan page itself is saved and stays saved |
| 4 | the directory page is absent and no template was passed. Step 7 always passes templates/plan-contents.md, so this code does not come out of this skill's call — a wrong template path is rejected as 2, not as 4. Seeing it anyway means the template file is not where the plugin puts it: confirm the plugin installation is complete and run it again. Never answer it by dropping the template argument |
| 7 | the key is invalid or lacks permission — stop and report the key problem; the script wrote nothing, which is what keeps the other plans' rows alive |
| 8 | any other API failure — stop and report that status, and do not retry the same call unchanged |
Why 7 and 8 abort: both mean the old content is unknown, not that the page is missing. Reading either as "not there yet" would write a fresh template over a live directory, and every other plan's row is gone — the write carries no merge and no backup. PLAN_{HASH} is the opposite case: it is a content page belonging to this one plan and living in the PLAN repo, so step 6 rewriting it whole is correct. The distinction is the page, not the write.
Completion condition: the PLAN_CONTENTS write names the wiki-contents.sh exit code it branched on, and no directory page was created on any code other than 4.
Hard limits
- Never output a code snippet.
- Never modify any file in the working directory. This limit is enforced in code where the CLI allows it:
jsc-hooks/hooks/write-guard.shinstagemode runs as aPreToolUsehook and blocksWrite,EditandMultiEditwhile this stage's lock exists — the same lock statejsc-hooks/hooks/sdlc-gate.sh lock planwrites in step 1. Only claude hasPreToolUse. Codex, copilot, antigravity and kiro never reach that hook, so on those four CLIs this line is the only thing holding the limit. - The row file of step 7 and the pending-file of step 8 are produced with a Bash heredoc or
mktemp, in a temporary directory — never with theWriteorEdittool. That gate blocks on the stage lock alone and never looks at the path, so aWriteof either file is blocked by this stage's own lock and the stage cannot finish: the directory row never gets written and this stage's log content is never parked. Both files are scratch input to a script, they live outside the working directory, and writing them this way keeps the limit above intact — nothing in the working directory is touched. - Never skip the decision tree and assume requirements.
- Never stop questioning after one round; consensus is reached only under
references/consensus.md, and the user says so.
What the work package gate no longer stops here
jsc-hooks/hooks/sdlc-gate.sh wp-check used to block this skill outright while the repository still held an unsettled work package PR. For plan it is now a reminder that prints and lets the run through. The protection given up is the work-in-progress cap: nothing stops a new plan from starting while packages from the last one are still open, so plans can pile up faster than they are implemented. The reminder still names the unsettled package, and the same gate still blocks analyze and maintain, so the cap holds one stage later. implement was always waved through — that is the path that settles the open PR, and a gate that blocked it would lock itself.