Help us improve
Share bugs, ideas, or general feedback.
From spec-team
Initialize SpecTeam: set up collaborator identity, normalize source design docs into .spec/, create core files, and establish Git diff baseline. Use this when starting the SpecTeam workflow for the first time or onboarding a new collaborator.
npx claudepluginhub surebeli/specteam --plugin spec-teamHow this skill is triggered — by the user, by Claude, or both
Slash command
/spec-team:spec-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Initialize the SpecTeam workflow state for the current collaborator.
Provides 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.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Initialize the SpecTeam workflow state for the current collaborator.
$ARGUMENTS: Optional repo mode flag (--branch=spec-docs or --submodule). Default: Mode A (dedicated branch spec-docs).Check whether .spec/ directory already exists:
{is_founder} = false.Run git branch --show-current and capture the output as {main_branch}.
Run git config --local spec.main-branch {main_branch} to persist it locally.
This branch becomes the protected SpecTeam branch — all other skills will refuse to execute on any other branch.
{main_branch} into COLLABORATORS.md header (see Step 7).Main Branch field from existing COLLABORATORS.md and run git config --local spec.main-branch {main_branch} to sync to local machine.Run git config user.name and capture the output as {git_name}.
Output the following block verbatim (substituting {git_name}), then stop and wait for the user to reply:
[SpecTeam init — Step 1]
Please provide your member code (nickname / collaborator ID, e.g. alice, bob, dev-007).
This code identifies your documents across the shared workflow.
(Press Enter to use your Git username automatically: {git_name})
After the user replies:
{git_name} (from git config user.name) as the member code.git config user.name is also empty, fall back to the output of git config user.email, stripping the @... domain part.-, keep only [a-z0-9_-].git config --local spec.member-code {code} to save the member code into .git/config. This is machine-local and not committed to the repo, so each collaborator's clone has their own identity.Only if {is_founder} = true(.spec/ does not exist), output the following block verbatim, then stop and wait:
[SpecTeam init — Step 2: Set project goal]
You are the first to initialize SpecTeam on this project. Please briefly describe the shared project goal / mission (1–3 sentences). This will be written to THESIS.md as the North Star — all future collaborators will align to it.
Example:
Save the user's reply as {project_goal}.
If {is_founder} = false (join mode), skip this step. The existing THESIS.md already contains the project goal.
Output the following block verbatim, then stop and wait:
[SpecTeam init — Step 3: Specify document directories]
Please provide the local design document directories (comma-separated for multiple).
Example: ./design, ./docs/alice-proposal, ./superpowers-output
These can be plan-generated, superpowers plugin output, or spec-driven-dev rule output.
Only if {is_founder} = false, read .spec/THESIS.md and .spec/DIVERGENCES.md (if exists), then display:
[Project Goal Review]
Current project North Star (set by {founder_code}):
{THESIS.md North Star content}
[Current Divergence State]
{If DIVERGENCES.md exists:}
{If DIVERGENCES.md does not exist:} (No divergence records yet)
Please confirm you have reviewed the project goal and current workflow state. Your documents will be aligned to this baseline.
(This is informational — no need to wait for confirmation, proceed immediately.)
git status and display the result..spec/ directory if it doesn't exist..spec/COLLABORATORS.md with:
Main Branch metadata header.spec/design/{code}/ mapping# SpecTeam Collaborators
**Main Branch**: {main_branch}
## Members
| Code | Source Directories | Spec Path | Joined |
|------|-------------------|--------------|--------|
| {code} | {dirs} | .spec/design/{code}/ | {date} |
Main Branch from existing COLLABORATORS.md → run git config --local spec.main-branch {main_branch} to sync the protected branch to the local machine..md files into .spec/design/{code}/ (preserve relative paths, max 2 levels):
<!-- Spec Normalized Document --> header to each file.spec/THESIS.md:
{project_goal} as the North Star section.spec/RULES.md — Code conventions (create if not exists).spec/SIGNALS.md — Runtime status (create if not exists)git add .spec/ and commit:
"[SpecTeam] init — {code} created project and normalized design documents""[SpecTeam] init — {code} joined workflow and normalized design documents"/spec-parse (execute the parse skill inline)."Initialization complete! You are the project founder. Project goal written to THESIS.md, documents normalized to .spec/design/{code}/, Git diff baseline established.""Initialization complete! You have joined the workflow. Identity recorded as {code}, documents normalized to .spec/design/{code}/. See THESIS.md for the project goal."⚠️ [Branch Protection]
SpecTeam data (DIVERGENCES.md, decisions/, last-*.json, etc.) is branch-specific.
Follow these rules to prevent divergence state corruption:
✅ Recommended: Run all SpecTeam skills only on the main branch (or spec-docs dedicated branch)
✅ Safe: Make code-only changes on feature branches without running any spec-* commands
❌ Dangerous: Running any skill on a feature branch (commits .spec/); switching back to main will cause state inconsistency
Main branch locked to: {main_branch}
Operations on any other branch will be rejected by the branch guard.