trace
/trace
Śledzi, czy zmiana wymagań lub przypadku użycia wpływa na projekt i pilnuje zgodności projektu z dokumentacją planistyczną.
- Autor
- moonklabs ↗
- Repozytorium
- aiwf ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 08.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Śledzi, czy zmiana wymagań lub przypadku użycia wpływa na projekt i pilnuje zgodności projektu z dokumentacją planistyczną.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when a use case, requirement (FR/NFR/C) or acceptance criterion changed and design may be affected, when a design decision differs from the planning documents, when a new design unit (flow, screen, chat element) appears, or after design was applied to code — "기획 변경 반영", "traceability", "대응표", "기획 변경 대기".
Jak działa
- Who changes what
- How to edit a row
- When planning changed
- When design differs from planning
- After applying to code
- Check
Podgląd SKILL.md
--- name: trace description: Use when a use case, requirement (FR/NFR/C) or acceptance criterion changed and design may be affected, when a design decision differs from the planning documents, when a new design unit (flow, screen, chat element) appears, or after design was applied to code — "기획 변경 반영", "traceability", "대응표", "기획 변경 대기". --- # Planning ↔ design ↔ implementation trace Copyright 2026 moonklabs. Licensed under Apache-2.0; see the plugin LICENSE and NOTICE. `<specRoot>/traceability.md` is the only connection point. Planning documents and design documents never edit each other directly; they signal through the row states of this table. Paths come from `design-spec.config.json` (`specRoot`, `planning.*`; schema in the plugin README). `<skills>` is the folder that holds this skill's folder. ## Who changes what | File | Changed by | |---|---| | `planning.requirements` · `planning.useCases` · `planning.testCases` | Planning (aiwf-core skills) | | `traceability.md` rows | The side that caused the change | | `HANDOFF.md` waiting list | The side that caused the change, one line | | `decisions.md` · `figma/figma-map.md` · `memories/plans/` | The designer | ## How to edit a row - **상태** uses only words from the `## 상태 값` table. Join several with ` · `. Put an explanation in parentheses after the word. - **갱신** is the date the row was edited (today; check with `date +%F`). Change it whenever another column changed, even if the state stayed the same. - The UC/FR/NFR/C IDs in the **기획** column must exist. Write ranges like `FR-008~009`. - Overwrite the row. Do not accumulate past states inside it. ## When planning changed 1. Read the changed UC/FR source. If it is not on this branch, find out which branch or PR has it. Do not invent its wording. 2. Find every row containing the ID: `grep -n "UC-002\|FR-004" <specRoot>/traceability.md`. Also read rows whose range notation (`UC-001~003`) contains it. 3. Only rows whose design unit (screen, component) shows the changed flow are affected rows. Leave rows whose ID is merely inside a range without that flow. For an affected row, add `기획 변경 대기` to its state, write briefly in the 기획 column what changed, and set 갱신 to today. 4. Add one line to HANDOFF's `## 기획 변경 대기` section: `UC-002/FR-004 '<변경 요약>' → <디자인 단위> 재검토`. If the section does not exist, create it right above "아직 결정 안 된 것". The designer deletes the line once handled. 5. Do not touch `decisions.md`, Figma or `memories/plans/`. Design decisions belong to the designer. 6. When aiwf-spec:sync-docs is in use, list these rows in its report as well. ## When design differs from planning Set the row state to `기획 변경 필요` and add one line to HANDOFF's "아직 결정 안 된 것". When planning creates a new ID with aiwf-core, link it in the 기획 column and remove `기획 변경 필요`. A new design unit without a matching UC stays `기획 없음`. ## After applying to code Change only the implementation column and the state. Set `구현: 새 디자인` only after the gates for that change (`gates`, including the token check) have actually passed. Until then keep the previous state and name what is unverified in parentheses, for example `구현: 이전 디자인 (적용 중, 게이트 미실행)`. When a person confirms it in the real app, set `검증 완료` and add an evidence link. ## Check ```bash node <skills>/review/scripts/design_spec_lint.mjs ``` Fix `DS_TRACE_STATUS`, `DS_TRACE_DATE` and `DS_DANGLING_REF`. Copy the `DS_QUEUE_DESIGN` (rows for the designer) and `DS_QUEUE_PLANNING` (rows for planning to decide) lists into the report as they are.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · moonklabs/aiwf | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| r3dlex/oh-my-auggie | 100 | Apache-2.0 |
| zereight/gitlab-mcp | 100 | MIT |
| proxify-dev/agentic-kit | 100 | MIT |
| biliboss/skills | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| Soul-Brews-Studio/arra-oracle-skills-cli | 100 | MIT |
| ccplugins/awesome-claude-code-plugins | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki ab5bb0de2515 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100sdlc-srs-workflow
Redaguje lub audytuje SRS z identyfikatorami wymagań, kryteriami akceptacji, ograniczeniami, punktami NFR i śledzeniem. - 100traceability
Tworzy macierz pokrycia wymagań: każde kryterium akceptacji lub wymaganie łączy z testami, ich wynikami i otwartymi błędami. - 90traceability-audit
Sprawdza, czy każdy wymóg PRD ma powiązany przypadek testowy i implementację w kodzie. - 100change
Ocenia nowy pomysł lub zgłoszenie według zmiany wymagań i wpływu na projekt kodu, a potem zadaje pytania i aktualizuje dokumenty. - 90system-lifecycle
Prowadzi cały cykl SDLC od wymagań przez kod do testów z pełną śledzalnością, np. przy definicji ukończenia.