ntanh1402/sdlc-skills

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 appro…

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/ntanh1402/sdlc-skills --skill sdlc-ask-wiki

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Ask the wiki

Read-only. Never create, edit, delete or commit a wiki file, and never start a draft. Route a request to change the wiki to the skill that does it: sdlc-write-spec (requirements), sdlc-write-stories (user stories), sdlc-design-arch (architecture), sdlc-plan-tasks (tasks), sdlc-design-story-tests and sdlc-design-feature-tests (test design), sdlc-import (existing code, documents or tests to bring into the wiki, or to compare with it), sdlc-close-task (a Task whose code is merged), sdlc-edit-wiki (a typo, the glossary or conventions, a Feature marked released, a ticket link on a Task or a user story), sdlc-setup-wiki (the wiki itself, or a new Application). A request to write a Task's code goes to sdlc-build-task, and one to review a code change to sdlc-review-code.

Read references/read-protocol.md in this skill's folder and follow it: it finds the wiki, says how to read the default branch, and where the schema pages are. Read the schema page of a type before relying on its headings or statuses.

How to answer

  1. Ask only for what is genuinely missing: an Application when there are

several and the question does not say which, or a Feature when several match.

  1. Search cheaply first (indexes, grep -rl), then read only the files the

answer needs.

  1. Answer the question first, then cite the paths you read. Separate what the

wiki says from what you infer. When nothing is found, say what you searched.

  1. Do not paste whole files when a short interpreted answer does.

Recipe: list features

For one Application (ask which if there are several), read wiki/<app>/features/index.md and each Feature's overview.md. Report one row per Feature:

ColumnFrom
Key and titlefrontmatter
Statusstatus (the values are on the Feature schema page)
Versionversion and versionDate
Owner, priorityownerTeam, priority
Designed# Architecture is not None; "from v<n>" with designBasedOn, marked outdated when it is older than version
Not livenumber of Design concepts whose # Pending changes links this Feature
Open changesChangeRequests listed in its # Change history whose status is in pending.open_requests of .wiki-llm/schema/schema.json

Explain an empty list. Offer "show the architecture of FEAT-x" for detail.

Recipe: show a feature's architecture

For exactly one Feature:

  1. Summary: title, status, version, owner, and the design state: not

designed yet, designed from version designBasedOn (outdated when that is older than version), or Approved. A Feature that is designed but not Approved has Requirements that are a draft or a design that is behind; say which.

  1. Requirements: key, priority and one line each.
  2. The stored diagrams from ## High-level architecture and

## Runtime sequences, as they are.

  1. Frontends (only when ## Frontends exists): each one's status, its routes

or screens, and the Endpoints and Operations under its # Calls.

  1. Services: each one's status, its Endpoints and Subscriptions, the channels

it publishes, the tables and stores it uses, and the externals it calls.

  1. Decisions under ## Decisions, with their consequences.
  2. ## Traceability, Requirement by Requirement.
  3. References the Feature links under # References, with their notes.
  4. Not live: every concept with a # Pending changes entry for this Feature or

one of its ChangeRequests, with the entry's text; and the open ChangeRequests.

  1. Outdated: $T outdated --feature <key> lists the design, stories, Tasks

and TestGroups written from an older version, with the skill that rewrites each (sdlc-design-arch, sdlc-write-stories, sdlc-plan-tasks, sdlc-design-story-tests or sdlc-design-feature-tests). Leave this out when it is empty.

  1. Gaps found while reading: links that do not resolve, Requirements missing

from Traceability, differences between the wiki and code you also read (sdlc-import on that code compares them file by file).

A Feature with # Architecture None is not an error: say it is not designed yet and that sdlc-design-arch can design it now, even while its Requirements are a draft.

Recipe: what is outdated

"What must be redone since the spec changed?" Run $T outdated --feature <key> (or --change <key>). Report the target's version and date, then one row per file it lists: the path, what it is, the version it was written from, and the skill that rewrites it. A person may instead confirm that a file is still current with sdlc-edit-wiki.

Recipe: show an endpoint or a consumer

For exactly one Endpoint or Subscription:

  1. Summary: title, status, its Service, and method and path, or the

channel it consumes.

  1. Input: # Request, or the channel's payload linked from # Consumes.
  2. Output: # Response with ## Status codes, or the side effects named in

# Handler.

  1. # Validations, as stored.
  2. # Behavior or # Handler.
  3. The stored # Flowchart and # Sequence diagram, as they are.
  4. # Pending changes, when present, with each entry's text.

Recipe: show a user story

Stories are STORY-*.md files in a Feature's or ChangeRequest's folder (user-story.md). For one story, give its sentence, its criteria, the Requirements it lists, the Tasks whose # Stories link it, and its # Changed by entries: a Feature story describes the Feature as first delivered, and the ChangeRequest stories listed there describe later changes.

For "the paste-ready copy", "give me the story for the tracker" or similar, print each story asked for as references/paste-format.md shows, and nothing else.

Free-form questions

  • "What uses X?": open X and read its tool-written reverse section

(# Used by, # Publishers, # Subscribers, a Reference's # Referenced by), else grep -rl "<KEY>" wiki/.

  • "What should I read about X?", "is there an example of Y?": the References

in wiki/<app>/references/index.md whose title or description matches, and those the concepts about X link under # References. Give each one's description, status and resource, and say when it is Deprecated or past its stale_after.

  • "What is not live?": grep -rl "^# Pending changes" wiki/, then read the

entries.

  • "What is not tested, not planned or has no story?": coverage tests,

coverage tasks and coverage stories (read-protocol section 3). coverage stories reporting every Functional Requirement means the Feature has no stories, which is allowed.

  • "Why is it like this?": the decisions in wiki/<app>/decisions/, the

concept's log.md, then git log -p on its folder.

  • "Who confirmed it?": the verified stamps; a file without one is

unconfirmed.

  • "How far is this Task?": a Task is Todo until its code is merged, then

Done. Say that progress in between is in the Tracker, and give the Task's trackerKey and resource when it has them.

dallo stesso repository

Altri Skills

Tutti gli Skills
ntanh1402
Community

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

Installazioni / 1h
2
GitHub Stars
1
Aggiornato
13 nov
ntanh1402
Community

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. Use after a Task's pull request is merged, when a developer asks to close, finish or complete a Task in the wiki. Not for closing a ticket in a tracker, for merging or reviewing code, for marking a Feature released, or for any other change of s

Installazioni / 1h
2
GitHub Stars
1
Aggiornato
13 nov
ntanh1402
Community

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.

Installazioni / 1h
2
GitHub Stars
1
Aggiornato
13 nov
ntanh1402
Community

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

Installazioni / 1h
2
GitHub Stars
1
Aggiornato
13 nov