name: specsync-setup description: > Set up specsync for this project. Creates .specsync.json with the server URL and verifies the server is reachable. Run this before using the specsync skill.
TRIGGER THIS SKILL when: - The user says "set up specsync", "configure specsync", "specsync setup" - The user wants to change the specsync server URL - The specsync skill reports that .specsync.json is missing
Specsync Setup
Configure specsync for this project by creating .specsync.json with the server URL.
Steps
Check for existing config. Read
.specsync.jsonin the project root. If it exists, show the currentserverUrland ask the user if they want to change it. If they don't, stop here.Ask the user for the server URL. Suggest
http://localhost:4000as the default. If the team has a shared server, they'll provide the URL (e.g.,https://specsync.myteam.com).Write
.specsync.jsonto the project root:
{
"serverUrl": "SERVER_URL_HERE"
}
- Verify the server is reachable. Hit the health endpoint:
curl -s --max-time 5 "SERVER_URL_HERE/health"
- If it responds, tell the user setup is complete.
- If it fails, tell the user the config was saved but the server is not reachable. They should start it with
npx @specsync/serveror check the URL.
Tell the user they're ready. They can now say "ask the team" or "submit for review" and the specsync skill will use the configured server.
Briefly mention what happens next so there are no surprises:
- "Ask the team" opens a Q&A form; share the printed URL.
- "Submit for review" opens a review document; share the printed URL and the 6-character join code. Reviewers enter their name and the code once in the browser. Q&A sessions don't need a code.