gsd-preflight

Use when GSD commands are failing or .planning/ artifacts look inconsistent. Run before any GSD execute-phase or verify-work attempt to catch cross-artifact mismatches early.

Aller à l'installation Vérifier les fichiers

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: 70
Forks: 10

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 un assistant IA

Copiez ce prompt dans l’assistant IA que vous utilisez.

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

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-preflight

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.

Explorateur de fichiers

3 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

name: gsd-preflight
description: Use when GSD commands are failing or .planning/ artifacts look inconsistent. Run before any GSD execute-phase or verify-work attempt to catch cross-artifact mismatches early.
description-frequency: on-demand
type: skill
category: gsd
status: stable
origin: tibsfox
modified: false
first_seen: 2026-02-07T00:00:00.000Z
first_path: examples/gsd-preflight/SKILL.md
superseded_by: null

# GSD Preflight Validator Pre-flight checks on `.planning/` artifacts to catch issues before workflows fail. ## Core Artifact Checks **PROJECT.md** — Sections: What This Is, Requirements, Constraints, Key Decisions **ROADMAP.md** — Sequential phase numbers, each with Goal/Deliverables/Success Criteria **STATE.md** — Current Position matches ROADMAP status, reasonable progress % **config.json** — Valid JSON, valid enum values (mode, model_profile, depth) ## Cross-Artifact Consistency - STATE.md phase exists in ROADMAP.md - Completed phases have matching SUMMARY files for each PLAN - Phase directories exist for all ROADMAP phases - No orphaned files (PLAN without phase, SUMMARY without PLAN) ## Severity | Level | Definition | Action | |-------|------------|--------| | BLOCKER | Will cause workflow failure | Must fix first | | WARNING | May cause confusion | Should fix | | INFO | Informational | No action needed | ## Common Fixes - **STATE/ROADMAP out of sync:** Run /gsd:progress - **Missing SUMMARY for completed plan:** Re-execute or mark incomplete - **Invalid config.json:** Check for trailing commas, invalid values - **Orphaned directories:** Add to ROADMAP or remove

Voir sur GitHub

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

gsd-preflight

Informations de source

Options d'installation

Installer avec un assistant IA

Vérifiez les fichiers source

Plus depuis ce dépôt

Installer avec un assistant IA

Plus depuis ce dépôt