Skill
aminet-browser
Aminet search and browse: full-text search, category tree navigation, architecture filtering, package detail, and curated collections. Use when searching,…
@tibsfoxView SkillDevelopment
Skill
/gsd-trace
Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.
Install
$ npx -y skills add Tibsfox/gsd-skill-creator --skill gsd-trace --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/gsd-trace
Context preview
The summary Claude sees to decide when to auto-load this skill.
Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.
SKILL.md
gsd-trace.SKILL.mdname: 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-02
triggers:
- "user asks \"why did we"
updated: 2026-04-25
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.
Read more
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-02 triggers: - "user asks \"why did we" updated: 2026-04-25 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.
Ships withgsd-skill-creator
An adaptive learning and coprocessor architecture for Claude Code, built as an extension to GSD (open-gsd)
Get the whole plugin
Stats
69
Stars
9
Forks
Maintained
Maintenance
TypeScript
Language
1mo ago
Last commit
7mo ago
Created
Repo: Tibsfox/gsd-skill-creator
Other skills on gsd-skill-creator.
@tibsfoxView SkillSkill
aminet-emulator
FS-UAE emulator configuration and launch: hardware profiles, ROM management, WHDLoad integration, config generation, and state snapshots. Use when configuring…
@tibsfoxView SkillSkill
aminet-index
Manages Aminet INDEX infrastructure: fetch, parse, cache, and incremental update of ~84,000-entry package database. Use when managing INDEX data, checking…
@tibsfoxView SkillSkill
aminet-installer
Aminet package installation: LhA/LZX extraction, Amiga filesystem mapping, dependency detection, install tracking, and scan gate enforcement. Use when…
@tibsfoxView SkillSkill
aminet-mirror
Selective Aminet package mirroring: single-package fetch, integrity verification, mirror state tracking, bulk download, and sync detection. Use when…
@tibsfoxView SkillSkill
aminet-scanner
Multi-layer virus scanning for Aminet packages. Signature-based detection, heuristic hunk analysis, boot block scanning, quarantine management, and scan…
@tibsfoxView Skill