gsd-trace

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

Aller à l'installation

Dépôt: Tibsfox/gsd-skill-creator
Dernière activité de la source: 14 avril 2026 à 07:57
Langue détectée de SKILL.md: anglais
Étoiles: 69
Forks: 9

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

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

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’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

Tout voir dans ce dépôt

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.
type	skill
category	gsd
status	stable
origin	tibsfox
modified	false
first_seen	"2026-02-07T00:00:00.000Z"
first_path	examples/gsd-trace/SKILL.md
superseded_by	null

GSD Decision Archaeology

Excavate GSD artifact timeline to reconstruct decision chains, requirement evolution, and phase rationale.

Sources (authority order)

PROJECT.md Key Decisions
STATE.md Session Continuity
ROADMAP.md phase goals/criteria
Phase CONTEXT.md / RESEARCH.md
Plan SUMMARY.md outcomes
Git commit messages
Archived milestone docs

Trace Process

Identify query type — decision rationale, requirement status, phase outcome, impact analysis
Search sources — start with highest authority, cross-reference downward
Build timeline — chronological events from artifacts
Trace causality — link decisions to requirements to implementation
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.

gsd-trace

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

GSD Decision Archaeology

Sources (authority order)

Trace Process

Query Types

Limitations

GSD Decision Archaeology

Sources (authority order)

Trace Process

Query Types

Limitations