sp ec
sp ec installs a shared .sp/ working area and slash commands that guide a
coding agent from a constitution and feature specification through planning,
tasks, analysis, and implementation.
Install
Run from a repository root:
sp ec installThe installer detects supported coding agents from their project configuration. Choose one explicitly when detection is not possible:
sp ec install --agent claude
sp ec install --agent cursor
sp ec install --agent copilot
sp ec install --agent gemini
sp ec install --agent opencode
sp ec install --allThe installed repository contains:
.sp/
memory/constitution.md
scripts/
templates/Generated scripts, templates, and run state are added to .gitignore.
.sp/memory/constitution.md remains trackable and is never overwritten by
--force.
Commands
The coding-agent command directory receives:
| Command | Purpose |
|---|---|
/constitution |
Establish or amend the repository's governing principles |
/specify |
Turn a feature description into a specification |
/clarify |
Resolve important specification ambiguity |
/plan |
Produce the implementation plan and supporting design artifacts |
/tasks |
Break the plan into an executable task list |
/analyze |
Check consistency across the specification, plan, and tasks |
/implement |
Execute the task list and validate the result |
Workspaces and huddles
Point --dir at a folder of Git repositories to install each repository
independently:
sp ec install --dir path/to/workspaceEach detected repository gets its own .sp/ area and repo-scoped commands. The
workspace root gets /huddle, which coordinates one initiative across multiple
repositories while keeping each repository's specification, plan, and tasks in
that repository.
Huddles are Markdown documents under:
.sp/huddles/NNN-short-name/huddle.mdMarkdown is always the source of truth. Remote synchronization never prevents a local huddle from being written.
Diagnose integrations
sp ec doctorThe doctor reports:
- the configured huddle store;
- GitHub CLI authentication and access to the configured GitHub Project;
- whether a Linear MCP configuration or
LINEAR_API_KEYis visible; - an actionable setup command for each missing capability.
Configure work management
Run guided setup:
sp ec project setupOr configure it without prompts:
sp ec project setup \
--provider github \
--url https://github.com/orgs/example/projects/1
sp ec project setup \
--provider linear \
--url https://linear.app/example \
--team Engineering \
--transport mcpGitHub Projects can be checked and synchronized directly:
sp ec project status
sp ec project sync .sp/huddles/001-example/huddle.md --dry-run
sp ec project sync .sp/huddles/001-example/huddle.mdEach GitHub draft item carries a stable huddle-path marker. Repeated syncs
update the existing item instead of creating duplicates. /huddle prefers
available GitHub MCP project tools and falls back to the gh CLI sync command.
Linear setup records the workspace, team, and preferred transport. sp ec doctor
then tells the user whether the configured agent exposes Linear MCP or whether an
API key is available.
Install options
| Option | Purpose |
|---|---|
--dir PATH |
Repository or workspace root; defaults to the current directory |
--agent NAME |
Target one coding agent; repeatable |
--all |
Install commands for every supported coding agent |
--each |
Treat --dir as a workspace and install into each child repository |
--root |
Install only at --dir, even when it contains repositories |
--ignore PATH |
Exclude a repository or directory during workspace discovery |
--force |
Refresh generated commands and templates without replacing constitutions |