--- name: sdlc-edit-wiki description: Make a small edit to the project wiki that no lifecycle skill owns - fix a typo or wording, change the glossary or the conventions, mark a Feature released or deprecated, add a Reference (a page, a document or a code example to consult) or link one from any concept, mark a Reference deprecated, add a Task's or a user story's ticket link, add a Task's pull request link, record that a person confirmed a file, or record that a design, story, Task or TestGroup is still current for a new spec version. Use for small corrections of wording and for these status and link changes. Not for requirements, architecture, tasks, test design, corrections against code or documents, or closing a Task - those belong to the lifecycle skills, and this skill names the right one. --- # Edit the wiki This skill makes the small edits that no lifecycle skill owns, in one draft `wiki/edit-`. It refuses every other edit and names the skill that owns it. The list below is short on purpose: a wiki change that carries a decision goes through the skill that asks for that decision. ## Before you start Read, in this skill's folder, `references/read-protocol.md`. Find the wiki as the read protocol says, and check that it matches this skill. `RELEASE`, next to this file, holds one line such as `1.0.0`: ```bash cd "$WIKI" && $T copy check --release "" ``` | `status` | Do | |---|---| | `current` | Go on | | `older` | Stop: "The wiki's tool is older than this skill. Run sdlc-setup-wiki to upgrade the wiki." | | `newer` | Stop: "The wiki was set up by a newer release. Update your installed sdlc-skills." | | `edited` | Stop: "The wiki's tool copy was edited by hand. Run sdlc-setup-wiki to restore it." | Then read `schema.md` ("Corrections", "Pending changes") and the schema page of each type you will edit, in the wiki's `.wiki-llm/schema/`. ## The gates A gate is a stop for the person's explicit approval: first the combined Intent and Design gate (exact file-by-file changes, before any draft is started), then the Change-set gate (the diff and commit message, before committing). - Approval is an explicit yes to the gate's question. "Sounds good", silence or "whatever you think" is not approval. - An edit at a gate reopens that gate and every later one. - When you cannot ask the person (a run with no one to answer), or the person asks you to skip questions or approvals ("don't ask me, just write it"), stop before the first gate and start no draft. Return the open decisions and the gates the work still needs. Never assume approval. - When the person rejects the changes at section 3, stop and write nothing. When the person rejects at the Change-set gate, discard a draft this run started. - Being asked to run this skill does not approve anything it writes. - A refusal this file states is a refusal. Do not turn it into a question. ## 1. What this skill edits | Allowed | Rule | |---|---| | A typo or a wording fix in any file a person writes | The meaning of a contract, a Requirement or an acceptance item does not change, so a Feature's or ChangeRequest's `version` stays as it is | | The Application's `glossary.md` and `conventions.md` | Terms, roles and rules, added, changed or removed | | A Feature's status to `Released` or `Deprecated` | Only when none of its Tasks is `Todo` and no Design file has a pending entry for it; `Released` only from `InDev`, with `releasedAt` set to the time the person gives | | A Task's `trackerKey`, `resource` and `prUrl` | The ticket and the pull request a person followed by hand. Never its status | | A user story's `trackerKey` and `resource` | The ticket a person made from the story's paste-ready copy | | A `verified` stamp | The person says they read the file and it is right: `$T verify ` in the draft worktree | | Still current for a new spec version | The person says a file `$T outdated` lists needs no change for the new version. Set its record to the target's current version: `designBasedOn` on a Feature or ChangeRequest, `basedOn` on a Task, story or TestGroup, each `{ version, at }` copied from the target's `version` and `versionDate`. Add a log entry naming the person, for example `* **Still current**: TASK-refund-endpoint checked against version 3 by human:ana; no change.` Nothing else in the file changes. A Task's parent is never approved here: an approved parent has no outdated Task, so this happens before `sdlc-design-arch` approves it | | A new Reference | Material the person gives or points to: a page, a short document already in Markdown, a code location at a commit or tag. Section 2 says how | | A `# References` entry added to or removed from any concept | The entry links a Reference of the same Application, with a note on what to take from it. It changes no status | | A Reference's status to `Deprecated` | The person says it no longer applies. It is never deleted | | Refused | Say | |---|---| | A new or changed Requirement | `sdlc-write-spec` | | A new target design, a new Design concept, a changed contract | A ChangeRequest with `sdlc-write-spec`, then `sdlc-design-arch` | | A user story added, regrouped or deleted, or its criteria changed | `sdlc-write-stories` | | A Task added, or a Task's scope, acceptance or stories changed | `sdlc-plan-tasks` | | A TestCase, TestGroup or TestSuite | `sdlc-design-story-tests` for a story's group, `sdlc-design-feature-tests` for `GENERAL/`; `sdlc-import` for a correction | | A Task's status | `sdlc-close-task`, after its code is merged | | The wiki is wrong about what is built | `sdlc-import` on the code or the document: it compares and corrects | | A Feature's or ChangeRequest's status other than `Released` or `Deprecated` | The lifecycle skill of that step | | A question about the wiki | `sdlc-ask-wiki` | | A document to convert from PDF, Word or slides | `sdlc-convert-doc` first, then ask again | | A new version of a Reference's material, compared with the old one | `sdlc-import` (a reference source) | A refusal is not a question. Three rules decide the cases the tables do not name: - **Does the edit change what someone would build or test?** If a developer or a tester would do anything differently after the edit, it is not a wording fix. Refuse it and name the skill. - **A file that holds a target not built yet** (a `Planned`, `Modifying` or `Removing` Design file, a Feature before `Released`) is never edited in a way that changes that target. A typo there is still a typo. - **A request that mixes both** is split: do the allowed part, and list the rest under "For other skills" with the skill for each. ## 2. Look up, and ask only when needed Find the file or files on the default branch, and read them. Ask only what the request leaves undecided: which of two matching files, the exact new wording when the person gave only the fault, the release time. One question, with your proposal. For `Released` or `Deprecated`, read the Feature's Tasks, and find the Design files that still have a pending entry for it: `grep -rl "features//overview.md" "wiki/"`, then keep those whose `# Pending changes` section links it. `validate` refuses a `Released` or `Deprecated` Feature while such an entry exists (`pending.parent-open`), and this skill never removes an entry. So refuse when: - for `Released`, a Task is `Todo`: name the Tasks, and say each is closed with `sdlc-close-task` after its code is merged; - for `Deprecated`, a Task is `Todo` or an entry is left: name them. No skill withdraws an approved design; a person removes the entries, the `Planned` files and the `Todo` Tasks by hand, then asks again; - for `Released`, an entry is left with no `Todo` Task: name the files; a close that is not merged yet usually explains it. **A new Reference.** Read `.wiki-llm/schema/reference.md`, and look in `references/index.md` for one that already covers the material: when one does, propose linking it instead. Otherwise draft the folder `references/REF-/`, the key taken from the title: - `overview.md`: `type: Reference`, `status: Active`, a `description` that names the subject and when to consult it, `resource` when the material lives outside the wiki (code at a commit or tag, never a branch), and `stale_after` when it moves; a summary under the title, saying what to follow and what not to copy for a code example; `# Contents` listing the content files, or `None`; - the content files, when the person gave the material itself; - `log.md` with a **Creation** entry. Propose the concepts that should link it under `# References`, with the note for each. The person approves the whole folder at the stop below. ## 3. One stop: the Intent and the Design gate Show the exact changes, file by file, as the old text and the new text, and what is refused and where it goes. A new Reference is shown in full: its overview and every content file. Ask for approval. ```text Edit FEAT-catalog: features/FEAT-catalog/overview.md status InDev → Released; releasedAt 2026-10-04T00:00:00+07:00 features/FEAT-catalog/log.md a Released entry Not done here: "add a requirement for search filters" is sdlc-write-spec. Approve? ``` An edit here is shown again. ## 4. Write, finish and commit Read `references/write-protocol.md` now. The draft key is `edit-`: the key of the concept that holds the main file (`edit-FEAT-catalog`, `edit-TASK-sms-channel`, `edit-SVC-orders`, `edit-REF-cancel-flow-example`), or a short name for an Application file (`edit-glossary`, `edit-conventions`). Start it as `write-protocol.md` section 2 says. The input paths are the files you edit. Write exactly the approved changes. Add an entry to the `log.md` of each concept folder you changed, saying what changed and who asked: ```markdown * **Edit**: Reworded the summary; no contract changed. Written by an AI model with sdlc-edit-wiki. * **Released**: The Feature is live since 2026-10-04. Written by an AI model with sdlc-edit-wiki. * **References**: Linked REF-cancel-flow-example for the idempotency handling. Written by an AI model with sdlc-edit-wiki. ``` The Application's own files have no log; the commit message says what changed. Never write `generated`, a section the tool writes, or an `index.md`. Then follow `write-protocol.md` section 3, "At section 4": the input check, `draft finish`, the Change-set gate, `draft commit`. Commit message: `edit(): `, for example `edit(FEAT-catalog): released on 2026-10-04`. End with the summary: "Done" and "Next", and "For other skills" when part of the request was refused: ```text Done: wiki/edit-FEAT-catalog, 2 files, pushed. Open the pull request. For other skills: "add a requirement for search filters" (sdlc-write-spec) Next: Open and merge the pull request for wiki/edit-FEAT-catalog. ``` ## 5. What this skill never does - It never changes a Requirement, a contract, an acceptance item, a planned scope, a TestCase or a diagram's meaning. - It never changes a Task's status, and never a status other than a Feature's `Released` or `Deprecated` and a Reference's `Deprecated`. - It never adds a `# Pending changes` entry or removes one. - It never reads code to decide what the wiki should say. ## Done when - Every change made is in the "Allowed" table, and every refused part was named with its skill. - The exact changes were approved before the draft was started. - `draft finish` was `ok`, the change set was approved, and `draft commit` reported the branch.