auto
Run a SpecWeave increment unattended until every task is done, then verify and close - the Unattended section of sw-do. Use for…
@anton-abyzovInstall SkillDevelopment
Skill
/sw-project
Keep a project's goal, decisions, work items, artifacts and briefs portable across AI tools and accounts. Use for project coordination, "project brief", "what is this project about".
Claude Code
$ npx -y skills add anton-abyzov/specweave --skill sw-project --agent claude-code
Codex
$ npx skills add anton-abyzov/specweave --skill sw-project -a codex -y
Cursor
$ npx skills add anton-abyzov/specweave --skill sw-project -a cursor -y
Gemini CLI
$ npx skills add anton-abyzov/specweave --skill sw-project -a gemini-cli -y
GitHub Copilot
$ npx skills add anton-abyzov/specweave --skill sw-project -a github-copilot -y
OpenCode
$ npx skills add anton-abyzov/specweave --skill sw-project -a opencode -y
Windsurf
$ npx skills add anton-abyzov/specweave --skill sw-project -a windsurf -y
SKILL.md
sw-project.SKILL.mddescription: Keep a project's goal, decisions, work items, artifacts and briefs portable across AI tools and accounts. Use for project coordination, "project brief", "what is this project about".
argument-hint: "[show|init|set|brief|work-add|artifact-add|routine-add]"
metadata:
version: "3.0.0"
sw-project: shared intent across tools
Your tool runs the work; SpecWeave keeps what every tool and account must share, in the repository: the goal (`.specweave/project/hub.json`), durable decisions (`.specweave/memory/`), work items, artifacts and routine definitions.
Steps
1. Read AGENTS.md and `.specweave/memory/MEMORY.md`, then `specweave project show --json`. No project yet: `specweave project init --name "Name" --goal "Goal"` (works without Git). 2. Keep the goal and shared context current with `specweave project set --revision N --goal "..."` or `--context-file ctx.md`. Read the latest revision first; a stale write fails instead of overwriting another session. 3. Decisions that must outlive this session: one file per fact in `.specweave/memory/` and one line for it in `MEMORY.md`. Never store secrets or a copy of the conversation. 4. One work item per outcome: `specweave project work-add --title "Outcome" --summary "Scope and expected evidence"`, reusing existing items. Engineering work links an increment with `--increment 0042`; its ledger and `specweave verify` stay authoritative. 5. A fresh assignment for another tool: `specweave project brief --intent ID --harness codex` (or `claude`, `generic`). It is a snapshot, not proof anything started. 6. Record who ran it when known: `specweave project work-record --intent ID --revision N --harness codex --session ID`. Omit model and effort when unknown. 7. Deliverables: `specweave project artifact-add --revision N --title "Report" --location reports/report.md --intent ID` (files stay in place; HTTPS links work). `specweave project work-update --intent ID --revision N --state review` marks review readiness; it is not verification. 8. Routines are definitions: `specweave project routine-add --revision N --title "Weekly review" --cadence "Mondays 09:00" --instructions-file routine.md`. Only configure a real scheduler when the user has authorized recurring runs.
Follow your tool's own task and subagent rules and the user's authorization; never invent a task or session id. `specweave dashboard` shows the hub, work board and sessions.
Manual path (no CLI)
Keep the goal and decisions as files in `.specweave/memory/` with the `MEMORY.md` index, commit them, and write briefs by hand from those files.
Read more
description: Keep a project's goal, decisions, work items, artifacts and briefs portable across AI tools and accounts. Use for project coordination, "project brief", "what is this project about". argument-hint: "[show|init|set|brief|work-add|artifact-add|routine-add]" metadata: version: "3.0.0"
sw-project: shared intent across tools
Your tool runs the work; SpecWeave keeps what every tool and account must share, in the repository: the goal (`.specweave/project/hub.json`), durable decisions (`.specweave/memory/`), work items, artifacts and routine definitions.
Steps
1. Read AGENTS.md and `.specweave/memory/MEMORY.md`, then `specweave project show --json`. No project yet: `specweave project init --name "Name" --goal "Goal"` (works without Git). 2. Keep the goal and shared context current with `specweave project set --revision N --goal "..."` or `--context-file ctx.md`. Read the latest revision first; a stale write fails instead of overwriting another session. 3. Decisions that must outlive this session: one file per fact in `.specweave/memory/` and one line for it in `MEMORY.md`. Never store secrets or a copy of the conversation. 4. One work item per outcome: `specweave project work-add --title "Outcome" --summary "Scope and expected evidence"`, reusing existing items. Engineering work links an increment with `--increment 0042`; its ledger and `specweave verify` stay authoritative. 5. A fresh assignment for another tool: `specweave project brief --intent ID --harness codex` (or `claude`, `generic`). It is a snapshot, not proof anything started. 6. Record who ran it when known: `specweave project work-record --intent ID --revision N --harness codex --session ID`. Omit model and effort when unknown. 7. Deliverables: `specweave project artifact-add --revision N --title "Report" --location reports/report.md --intent ID` (files stay in place; HTTPS links work). `specweave project work-update --intent ID --revision N --state review` marks review readiness; it is not verification. 8. Routines are definitions: `specweave project routine-add --revision N --title "Weekly review" --cadence "Mondays 09:00" --instructions-file routine.md`. Only configure a real scheduler when the user has authorized recurring runs.
Follow your tool's own task and subagent rules and the user's authorization; never invent a task or session id. `specweave dashboard` shows the hub, work board and sessions.
Manual path (no CLI)
Keep the goal and decisions as files in `.specweave/memory/` with the `MEMORY.md` index, commit them, and write briefs by hand from those files.
Stats
170
Stars
20
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withspecweave
Open-source spec CLI: the spec, tasks and proof of done live in git, so any AI coding agent (Claude Code, Codex, Cursor, Copilot) can pick up where another stopped. Powers SpecWithCode: specwithcode.com
17018 skills1 agent
Stars on GitHub
Momentum
- stars in total
- 170
Other skills on specweave.
@anton-abyzovInstall Skilldo
Work a SpecWeave increment task by task - claim, implement inside its Files, test, commit, done with evidence - alone, unattended…
@anton-abyzovInstall Skilldone
Close a SpecWeave increment - every task done or skipped, specweave verify green, a fresh-context review, then specweave…
@anton-abyzovInstall Skillgrill-me
Interview the user relentlessly, in rounds, until every decision in a plan is settled; facts are your job, decisions are theirs.…
@anton-abyzovInstall Skillhandoff
Hand work to another tool, account or machine and pick it up there, in two words. Use when the user says "hand off", "hand off…
@anton-abyzovInstall Skillincrement
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use…
@anton-abyzovInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about sw-project.
- Which coding agents can use sw-project?
- sw-project installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.