ntanh1402/sdlc-skills

sdlc-close-task

Record in the project wiki that the code of one wiki Task is merged - set the Task Done with its merge commit, remove the pending entries of the Design files it covered and mark them live, and move its Feature to InDev or its ChangeRequest to Implemented.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/ntanh1402/sdlc-skills --skill sdlc-close-task

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Close a Task

This skill records that a Task's code is merged. Its input is a Task key and the one code folder the Task was built in. Its output is one draft, wiki/close-<Task key>, that changes:

  • the Task: status: Done, mergeCommitSha, mergedAt (its basedOn stays

at the version it was built from);

  • each Design file the Task covered: its pending entry removed and, when no

entry is left, its status set to live;

  • the parent: a Feature Approved becomes InDev; an Approved

ChangeRequest whose Tasks are now all Done becomes Implemented.

The last two change only when the parent is approved; section 1 says what changes while it is not.

One Task per run. Section 6 lists what it never does.

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 "<the line in RELEASE>"
statusDo
currentGo on
olderStop: "The wiki's tool is older than this skill. Run sdlc-setup-wiki to upgrade the wiki."
newerStop: "The wiki was set up by a newer release. Update your installed sdlc-skills."
editedStop: "The wiki's tool copy was edited by hand. Run sdlc-setup-wiki to restore it."

Then read the schema pages schema.md ("Pending changes"), task.md, feature.md, change-request.md and the page of each Design type in the Task's scope, in the wiki's .wiki-llm/schema/.

Other requests go elsewhere; say so and stop:

RequestAnswer
Close, move or comment a ticket in a TrackerNo skill does: a person follows the ticket by hand. Offer to record the merge in the wiki instead, and write nothing until asked
Write or fix the Task's codesdlc-build-task
Review the code before the mergesdlc-review-code
Mark a Feature released or deprecated; add a ticket link to a Task or a user storysdlc-edit-wiki
The merged code differs from the designsdlc-import on the code folder compares and corrects; a ChangeRequest with sdlc-write-spec when the design should change
Push, merge, or open a pull requestThe person does that

The gates

A gate is a stop for the person's explicit approval: first the combined Intent and Design gate (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 close 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. Look up

The Task. Find it on the wiki's default branch: git ls-tree -r --name-only "$DEFAULT" -- wiki | grep '/TASK-<name>.md$'. Refuse, as a refusal and not a question, when:

CaseSay
The Task is DoneIt is already closed; name its mergeCommitSha when it has one
The Task is not on the default branchName the draft that holds it and ask to merge it first
The parent is closed: a Feature that is Released or Deprecated, or a ChangeRequest that is Implemented or RejectedThe parent is already closed

When the user gave no code folder, ask for it once. Never guess it; "this folder" is an answer.

The merged commit. In the code folder, read the default branch of the remote, never a local branch that may hold unmerged work:

bash
SRC=<the code folder>
git -C "$SRC" fetch --quiet origin
BASE=$(git -C "$SRC" symbolic-ref --quiet --short refs/remotes/origin/HEAD \
  || { git -C "$SRC" show-ref --verify --quiet refs/remotes/origin/main && echo origin/main; } \
  || { git -C "$SRC" show-ref --verify --quiet refs/remotes/origin/master && echo origin/master; })
git -C "$SRC" log "$BASE" --grep='^Task: <Task key>$' --format='%H %cI %s'

When the fetch fails or BASE is empty, refuse: the folder has no remote this skill can read, and a commit that is only local is not merged.

  • One or more lines: the Task's code is merged. The first line is the newest

commit: its hash is mergeCommitSha and its committer date is mergedAt.

  • No line: a squash merge dropped the trailer, or the code was written by

hand. Ask for the commit, then check it is merged: git -C "$SRC" merge-base --is-ancestor <commit> "$BASE". A commit that is not on BASE is not merged: refuse, and say the Task is closed after the merge. Read its hash and date with git -C "$SRC" show -s --format='%H %cI %s' <commit>.

Never call a hosting service, and never compare the code with the Design files: that is a review.

The wiki changes. Read the Task's # Planned scope, each Design file it links, the parent's overview.md, and every other Task file in the parent's folder.

While the parent is not approved (a Feature Draft or ReqApproved, a ChangeRequest Proposed or ReqApproved), only the Task file and the parent folder's log.md change. The parent's status and the Design files' # Pending changes entries stay as they are: sdlc-design-arch removes the entries when it approves the parent.

When the parent is Approved (or a Feature InDev), its Tasks are all at its current version: an approved parent never has an outdated Task (basis.approved-task). Work out, for each concept in the scope:

The conceptChange
Another Todo Task of the same parent links it in its # Planned scopeNothing: the entry stays until that Task is closed
No other Todo Task of the parent covers itRemove the parent's entry from # Pending changes
It has no entry leftRemove the # Pending changes section. Status Active; or Deprecated when it was Removing. The file of a removed concept stays, because this Task and its parent link it
It still has an entry of another Feature or ChangeRequestKeep the section and the status

and for the parent:

The parentChange
A Feature that is ApprovedInDev
A Feature that is InDevNothing, even when this was its last Task: code merged is not code deployed
An Approved ChangeRequest whose Tasks are now all DoneImplemented
An Approved ChangeRequest with another Todo TaskNothing

Another close in progress. git -C "$WIKI" branch -a --list 'wiki/close-TASK-*' 'remotes/origin/wiki/close-TASK-*' lists the close drafts that are not merged. The table above reads the other Tasks' status on the default branch, so two closes open at once can each keep an entry the other one should have removed. When such a draft closes a Task of the same parent that shares a Design file with this one, say so at the stop of section 3: name the draft and the shared files, and go on. Do not stop for it. validate reports an entry left behind as pending.leftover once both are merged.

2. The question

Show the commit or commits found and ask one question: "Was this change reviewed?"

AnswerDo
YesGo on
NoSay that sdlc-review-code checks a change against the wiki, and ask: review first, or close anyway? "Review first" ends the run with nothing written. "Close anyway" goes on

3. One stop: the Intent and the Design gate

Show the planned wiki changes, file by file, with the commit, and ask for approval:

text
Close TASK-coupon-api: merged as 3f2a91c "Add the apply-coupon endpoint" on origin/main.
  TASK-coupon-api.md     status Todo → Done; mergeCommitSha 3f2a91c…; mergedAt 2026-10-12T09:14:00+07:00
  EP-apply-coupon.md     pending entry for FEAT-coupons removed; Planned → Active
  TBL-coupons.md         pending entry kept: TASK-coupon-admin still covers it
  FEAT-coupons/overview  Approved → InDev
Approve?

An edit here is shown again before anything is written.

4. Write, finish and commit

Read references/write-protocol.md now.

Start the draft close-<Task key> as write-protocol.md section 2 says. The input paths are the Task file, the other Task files of the parent, the parent's overview.md and each Design file in the scope.

Write exactly the changes approved in section 3:

  • the Task's frontmatter: status: Done, mergeCommitSha (the full hash)

and mergedAt (the committer date, with its offset);

  • the Design files and the parent, as the tables of section 1 say;
  • an entry in the log.md of every concept folder you changed, naming the

Task and the commit, for example * **Close**: TASK-coupon-api is Done; its code is merged as 3f2a91c. EP-apply-coupon is live. Written by an AI model with sdlc-close-task.

Change nothing else in those files, and write no 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: close(<Task key>): <the Task's title>.

5. The build worktree, then the summary

sdlc-build-task builds a Task in <code folder>/.worktrees/<Task name without TASK->/. When that folder exists, ask whether to remove it. Remove it only on a yes and only when it has no uncommitted change (git -C "<the worktree>" status --porcelain prints nothing): git -C "$SRC" worktree remove "<the worktree>". Otherwise leave it and say so. Never delete its branch.

End with the summary, "Done" and "Next":

text
Done: wiki/close-TASK-coupon-api, 4 files, pushed. Open the pull request.
Next: TASK-coupon-admin is the last Todo Task of FEAT-coupons.

When the close leaves every Task of an InDev Feature Done, "Next" says that sdlc-edit-wiki sets the Feature Released when it ships. When the parent is not approved yet, "Next" says that sdlc-design-arch removes the pending entries when it approves the parent. When the Task's basedOn is older than the parent's current version, "Next" also says that sdlc-plan-tasks checks the Task against the new version, adds a Task for any difference and updates its basedOn, which the parent needs before it can be approved.

6. What this skill never does

  • It never compares the code with the Design files, and never edits code.
  • It never sets a Feature Released or Deprecated.
  • It never touches a TestCase or a TestSuite.
  • It never writes trackerKey, resource or prUrl, and never calls a

hosting service or a Tracker.

  • It never deletes a concept's file, and never closes two Tasks in one run.

Done when

  • The merged commit was found by its trailer, or given by the person and

checked to be on the remote's default branch.

  • The person answered whether the change was reviewed.
  • The parent was open, and the Design files and the parent changed only when

the parent was approved.

  • The wiki changes were approved file by file before the draft was started.
  • draft finish was ok, the change set was approved, and draft commit

reported the branch.

  • A build worktree was removed only after a yes and only when it was clean.
do mesmo repositório

Mais Skills

Todos os Skills
ntanh1402
Comunidade

sdlc-ask-wiki

Answer questions from the project wiki without changing it - list an application's Features with status, spec version, owner, priority, design readiness and open ChangeRequests; list what was written from an older version of a spec; show one Feature's approved architecture with its diagrams, services, frontends, contracts, decisions, traceability and what is not built yet; show one Endpoint or consumer with its input, output, validations and diagrams; show a user story or print its paste-ready c

Instalações / 1h
2
GitHub Stars
1
Atualizado
13 de nov.
ntanh1402
Comunidade

sdlc-build-task

Write the code and unit tests of one wiki Task in one code repository, against the project wiki - read the Task's acceptance and planned scope, the contracts of the Design files it covers and the Application's conventions, plan the files, write them in a git worktree on a branch of their own, check them against the wiki and commit with a Task trailer, without pushing. Use when a developer asks to build, implement or code a Task of the project wiki. Not for coding without a wiki Task, for changin

Instalações / 1h
2
GitHub Stars
1
Atualizado
13 de nov.
ntanh1402
Comunidade

sdlc-convert-doc

Convert local documents into Markdown by routing text-bearing files through Microsoft MarkItDown and OCR-heavy inputs through Datalab Marker. Use when asked to convert PDFs, scanned PDFs, images, Word, PowerPoint, Excel, HTML, EPUB, email, archives, or other document files to Markdown, especially when OCR, tables, equations, layout preservation, or extraction-quality fallback is needed.

Instalações / 1h
2
GitHub Stars
1
Atualizado
13 de nov.
ntanh1402
Comunidade

sdlc-design-arch

Design and approve the target architecture of a Feature or ChangeRequest in the project wiki, while its requirements are a draft or once they are agreed - the services, frontends, endpoints, events, data and externals it needs, their contracts, Mermaid diagrams, traceability and architecture decisions - and mark what is not built yet. Use when requirements need technical design, impact mapping, interface contracts or ADRs, when a spec changed after its design, or to approve a ChangeRequest whose

Instalações / 1h
2
GitHub Stars
1
Atualizado
13 de nov.