gsd-trace

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

Zur Installation springen Dateien prüfen

Repository: Tibsfox/gsd-skill-creator
Letzte Quellaktivität: 25. April 2026 um 21:14
Erkannte Sprache von SKILL.md: Englisch
Sterne: 70
Forks: 10

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit einem KI-Assistenten installieren

Diesen Prompt kopieren und in den verwendeten KI-Assistenten einfügen.

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.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

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

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

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.

Auf GitHub ansehen

Zurück zur Suche Zurück zur Installation

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

Alle aus diesem Repository ansehen

gsd-trace

Quellinformationen

Installationsoptionen

Mit einem KI-Assistenten installieren

Quelldateien prüfen

Mehr aus diesem Repository

Mit einem KI-Assistenten installieren

Mehr aus diesem Repository