Skill
auto
Run a SpecWeave increment unattended until every task is done, then verify and close. Use for "auto mode", "run until done", "ship this while I sleep".
@anton-abyzovView 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".
Install
$ npx -y skills add anton-abyzov/specweave --skill sw-project --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/sw-project
Context preview
The summary Claude sees to decide when to auto-load this skill.
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".
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]"
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]" 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.
Ships withspecweave
Spec-first AI development: describe a feature → AI creates spec + plan + tasks, builds autonomously, syncs to GitHub/JIRA. Domain-expert skills for PM, Architect, Frontend, QA learn your patterns permanently. Claude Code, Codex, Cursor, Copilot & more.
Get the whole plugin
Stats
164
Stars
21
Forks
Active
Maintenance
TypeScript
Language
MIT
License
11h ago
Last commit
11mo ago
Created
Repo: anton-abyzov/specweave
In this plugin
See everything inside Other skills on specweave.
@anton-abyzovView SkillSkill
brainstorm
Widen the options before committing - framed options compared on stated criteria, ending in a pick that becomes an increment. Use for "brainstorm", "ideate",…
@anton-abyzovView SkillSkill
do
Work a SpecWeave increment task by task - claim, implement inside the task's Files, test, commit, done with evidence - then verify and close. Use for…
@anton-abyzovView SkillSkill
done
Close a SpecWeave increment - every task done or skipped, specweave verify green, a fresh-context review, then specweave complete. Use for "close it", "we are…
@anton-abyzovView SkillSkill
handoff
Hand work to another tool, account or machine and pick it up there, in two words. Use when the user says "hand off", "out of tokens", "switching accounts",…
@anton-abyzovView SkillSkill
increment
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use for "plan a feature", "new…
@anton-abyzovView Skill