source-command-gsd-join-discord
Join the GSD Discord community
Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Join the GSD Discord community
Reapply local modifications after a GSD update
Uses probing questions to draft STAR responses, distinguish individual actions from team actions, and require a metric. Produces versions suitable for 30-second and two-minute delivery.
Wait N seconds (default 20) via a blocking Node.js timer, for testing
Uses authoritative evidence when framework, library, runtime, platform, or API decisions depend on current documented behavior. Covers version-specific conventions and official best practices rather than framework-independent logic.
Ground framework-specific implementation in official documentation — detect stack versions, fetch authoritative docs, implement cited patterns, cite sources. Load when building with a library or framework where API correctness matters, when the user wants verified or documented code, or before writing framework code from memory. Also triggers on "source driven development", "cite the docs", "check…
Places, deduplicates, migrates, and validates Spark engineering knowledge across AGENTS, Notes, Roles, Skills, and Workflows.
Turn vague intent into a precise, executable spec in five phases. (gstack)
Hard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for consistency, traceability, and unresolved ambiguity. Returns PASS or FAIL with specific findings. Load when the spec-driven-development orchestrator routes /analyze, when the user asks to cross-check spec vs plan, audit traceability, verify spec readiness, gate-check before implement…
Full lifecycle spec-driven development methodology across three gated phases - Requirements (EARS-format acceptance criteria), Design (architecture, data models, edge cases), and Tasks (phased implementation plan).
Orchestrator for spec-driven development (SDD) — the discipline of writing executable specs before code, with a constitution above them and a hard cross-check gate before implementation. Mirrors GitHub Spec Kit / AWS Kiro slash-command shape. Routes /constitution, /specify, /clarify, /plan, /tasks, /analyze, /implement to the right leaf skill. Load when the user says "spec-driven development", "SD…
Write a Gherkin story file to docs/stories/ for a feature. The story IS the spec. No intermediate PROBLEM/SPEC/PLAN/TASKS artifacts.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name