dw-solo-skills
Listeda persistent Solo Projects spec-to-ship workflow for Claude Code
Bundles
Everything this plugin ships — skills, agents, commands, hooks, and MCP servers it bundles.
Skills (11)
dw-check
A fast, optional quality gate over the change in progress: delegate to an outside reviewer when asked for one, else a quick two-axis self-review — correct? fits this repo? — findings at real file:line, fixed in-session after approval. Repeatable mid-build; writes no artifact. Use when the work so far deserves a look, or when someone says "review this", "check this", "quick QA". Prefer this over a multi-auditor review pipeline.
dw-doctor
Read-only environment diagnostic for a solo-lane repo: check whether the tools the hooks and skills assume are installed and whether the repo's guardrails will actually fire, then report each gap with a copy-paste fix. Mutates nothing. Use when setting up or inheriting a repo, or when someone asks "check my setup", "why aren't my hooks running", "diagnose the repo".
dw-git
One skill for every git operation in this project — commit, push, open PR, sync (rebase), branch, stash — applying the repo's own `## Git conventions` from `AGENTS.md` instead of generic defaults. Use for any git intent, however it's phrased.
dw-grill
Interview the user to sharpen a fuzzy idea into decisions before anything gets written — one question at a time, at most five, hardest-first, each with a recommended answer. Writes nothing; the shared understanding it reaches is the input to `dw-shape`. Use when an idea is still vague, when a request could be read two ways, or when someone says "grill me", "interview me", "poke holes in this", "help me think this through". Prefer this over guessing at intent.
dw-handoff
Compact the live session into `.ai/work/<slug>/HANDOFF.md`: how far into the current task you are, what is applied but uncommitted, and which dead ends are already ruled out — so the next context window resumes mid-task instead of re-deriving it. Explicit-invoke only — you are the one who can see the session is about to end.
dw-init
Scaffold a private/solo repo for the solo loop — `.ai/` (work / backlog / archive), `docs/decisions/`, `CONTEXT.md`, a tracked `AGENTS.md` with a Task Router and a size budget, the guardrail hooks, settings with a derived allow-list, and an optional pre-commit. For a repo where you are the only reader. Explicit-invoke only — scaffolding a repo is your call, never the model's.
dw-land
Close out a change: one thin verdict over the diff — correct, fits the repo, blast radius, ticked boxes actually proven — then, on approval, promote the durable residue to `docs/decisions/`, `CONTEXT.md`, `## Gotchas` and the backlog, and archive the change doc. Use when a change is finished, or when someone says "land this", "wrap this up", "is this ready to merge", "close this out". Prefer this over merging and letting the change doc rot.
dw-next
The solo lane's build step and its resume point in one skill. Bare, it reports where the active `.ai/work/<slug>/CHANGE.md` stands and what the next unchecked task is — read from disk, so it survives a `/clear`. With `go` it builds that task and commits. Use when picking work back up or moving it forward, or when someone says "what's next", "where were we", "build the next task", "keep going". Prefer this over re-deriving state from scrollback.
dw-shape
Turn a request or a finished `dw-grill` conversation into a durable `CHANGE.md` under `.ai/work/` — goal, decisions taken, a task checklist, anchors in real files; one per independently shippable scope. Depth scales with size: a small change gets two checkboxes, not a spec. Read back by `dw-next` after a `/clear`. Use when starting work on a private project, or when someone says "shape this", "write this up", "let's plan this out". Prefer this over a multi-file spec-and-plan ceremony.
dw-ship
Ship the landed change: push — straight to the default branch when that's where you are, else PR → squash-merge — then tear down the worktree and branch and pull. Runs the closing pass first when the change doc is still there. Explicit-invoke only — merging is your call, never the model's.
dw-start
Open a shaped change for building: create its worktree and branch, enter it, and claim the change by writing the branch into its `CHANGE.md`. Bare lists what's unclaimed. Explicit-invoke only — creating branch topology is your call, never the model's.
Hooks (8)
Quality Score: 53/100
Details
- Author
- dominikwozniak
- Repository
- dominikwozniak/dw-solo-skills
- Created
- 2 weeks ago
- Last Updated
- today
- Language
- Shell
- License
- MIT