aminet-browser
Aminet search and browse: full-text search, category tree navigation, architecture filtering, package detail, and curated…
@tibsfoxInstall 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.
Claude Code
$ npx -y skills add Tibsfox/gsd-skill-creator --skill gsd-trace --agent claude-code
Codex
$ npx skills add Tibsfox/gsd-skill-creator --skill gsd-trace -a codex -y
Cursor
$ npx skills add Tibsfox/gsd-skill-creator --skill gsd-trace -a cursor -y
Gemini CLI
$ npx skills add Tibsfox/gsd-skill-creator --skill gsd-trace -a gemini-cli -y
GitHub Copilot
$ npx skills add Tibsfox/gsd-skill-creator --skill gsd-trace -a github-copilot -y
OpenCode
$ npx skills add Tibsfox/gsd-skill-creator --skill gsd-trace -a opencode -y
Windsurf
$ npx skills add Tibsfox/gsd-skill-creator --skill gsd-trace -a windsurf -y
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.
Stats
71
Stars
11
Forks
Maintained
Maintenance
TypeScript
Language
Last commit
Created
Ships withgsd-skill-creator
An adaptive learning and coprocessor architecture for Claude Code, built as an extension to GSD (open-gsd)
71102 skills61 agents1 MCP
Stars on GitHub
Momentum
- stars in total
- 71
Other skills on gsd-skill-creator.
@tibsfoxInstall Skillaminet-emulator
FS-UAE emulator configuration and launch: hardware profiles, ROM management, WHDLoad integration, config generation, and state…
@tibsfoxInstall Skillaminet-index
Manages Aminet INDEX infrastructure: fetch, parse, cache, and incremental update of ~84,000-entry package database. Use when…
@tibsfoxInstall Skillaminet-installer
Aminet package installation: LhA/LZX extraction, Amiga filesystem mapping, dependency detection, install tracking, and scan gate…
@tibsfoxInstall Skillaminet-mirror
Selective Aminet package mirroring: single-package fetch, integrity verification, mirror state tracking, bulk download, and sync…
@tibsfoxInstall Skillaminet-scanner
Multi-layer virus scanning for Aminet packages. Signature-based detection, heuristic hunk analysis, boot block scanning,…
@tibsfoxInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about gsd-trace.
- Which coding agents can use gsd-trace?
- gsd-trace installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.