From Golden Hoop Spell
Archive completed sprints to clean up active project state. Only archives sprints with status 'completed'. For incomplete sprints, use /ghs:force-archive instead.
How this skill is triggered — by the user, by Claude, or both
Slash command
/golden-hoop-spell:ghs-archiveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Move completed sprints from the active `.ghs/features.json` to `.ghs/archived/`, keeping the project state clean for the next sprint.
Move completed sprints from the active .ghs/features.json to .ghs/archived/, keeping the project state clean for the next sprint.
Resolve the project directory:
python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/resolve_project_dir.py
python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/archive_sprint.py --list --project-dir "<PROJECT_DIR>"
Show the user which sprints are eligible for archiving (status: completed).
python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/archive_sprint.py --dry-run --project-dir "<PROJECT_DIR>"
python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/archive_sprint.py --project-dir "<PROJECT_DIR>"
This will:
.ghs/archived/<sprint-id>_<name>_<timestamp>/.ghs/features.json.ghs/progress.md to the default templateNo git commit needed — .ghs/ tracking files are local metadata (gitignored by ghs:init).
.ghs/archived/<folder>/features.json.ghs/archived/<folder>/progress.md.ghs/features.json.ghs/progress.md is reset to the default templateIf there are no completed sprints, tell the user. They may need to:
/ghs:force-archive if they want to archive regardless of statusnpx claudepluginhub wangdahoo/golden-hoop-spell --plugin golden-hoop-spellProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.