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.

Ir a la instalación Revisar archivos

Repositorio: Tibsfox/gsd-skill-creator
Última actividad en el origen: 25 de abril de 2026 a las 21:14
Idioma detectado de SKILL.md: inglés
Estrellas: 70
Forks: 10

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

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

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

3 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

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
version: 1.0.0
format: 2025-10-02T00:00:00.000Z
triggers: ["GSD commands are failing or"]
updated: 2026-04-25T00:00:00.000Z
status: ACTIVE

# 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

Ver en GitHub

Volver a la búsqueda Volver a la instalación

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

Ver todos los de este repositorio

gsd-preflight

Datos de origen

Opciones de instalación

Instalar con un asistente de IA

Revisa los archivos de origen

Más de este repositorio

Instalar con un asistente de IA

Más de este repositorio