gsd-trace

Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.

설치로 이동 파일 검토

저장소: Tibsfox/gsd-skill-creator
최근 소스 활동: 2026년 4월 25일 21:14
감지된 SKILL.md 언어: 영어
스타: 70
포크: 10

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

AI 어시스턴트로 설치

이 프롬프트를 복사해 사용 중인 AI 어시스턴트에 입력하세요.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/Tibsfox/gsd-skill-creator/tree/main/project-claude/skills/gsd-trace.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill gsd-trace

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md

소스 지침 · 읽기 전용 미리보기

name: gsd-trace
description: Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.
version: 1.0.0
format: 2025-10-02T00:00:00.000Z
triggers: ["user asks \"why did we"]
updated: 2026-04-25T00:00:00.000Z
status: ACTIVE

# GSD Decision Archaeology Excavate GSD artifact timeline to reconstruct decision chains, requirement evolution, and phase rationale. ## Sources (authority order) 1. PROJECT.md Key Decisions 2. STATE.md Session Continuity 3. ROADMAP.md phase goals/criteria 4. Phase CONTEXT.md / RESEARCH.md 5. Plan SUMMARY.md outcomes 6. Git commit messages 7. Archived milestone docs ## Trace Process 1. **Identify query type** — decision rationale, requirement status, phase outcome, impact analysis 2. **Search sources** — start with highest authority, cross-reference downward 3. **Build timeline** — chronological events from artifacts 4. **Trace causality** — link decisions to requirements to implementation 5. **Answer directly** — cite specific sources and dates ## Query Types | Type | Primary Sources | |------|----------------| | Why decision X? | PROJECT.md Key Decisions, RESEARCH.md | | What happened to req Y? | REQUIREMENTS.md, STATE.md, milestones/ | | Phase N outcome? | ROADMAP.md, SUMMARY files, git commits | | What depends on X? | PLAN files, git history, code search | | What was tried/abandoned? | RESEARCH.md, STATE.md | ## Limitations Can only trace what GSD documented. Undocumented decisions, verbal discussions, and vague commit messages are untraceable.

GitHub에서 보기

검색으로 돌아가기 설치로 돌아가기

goal-ambiguity-gate

Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.

2026-07-19

memory-hubness-gate

Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.

2026-07-19

memory-use-warrant

Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.

2026-07-19

이 저장소의 모든 Skills 보기

gsd-trace

소스 정보

설치 방법

AI 어시스턴트로 설치

소스 파일 검토

이 저장소의 다른 Skills

AI 어시스턴트로 설치

이 저장소의 다른 Skills