dw-create-pr
01Command Claude Code
Push branch and open a pull request with issue linkage.
not rated 0 1mo ago A 0 tokens
0Stars on the repository
21Mods indexed here, across every type
1mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied
dw-implement
02Command Claude Code
Start work on a GitHub Issue — create branch, implement, and track progress.
not rated 0 1mo ago A 0 tokens
dw-merge
03Command Claude Code
Merge an approved pull request and clean up.
not rated 0 1mo ago A 0 tokens
dw-plan
04Command Claude Code
Research a story and write the plan — the agreed approach — as ONE GitHub plan issue, then stop for human review.
not rated 0 1mo ago A 0 tokens
Command Claude Code
Review the changes an issue was implemented with — do they deliver the issue, and do they stay surgical rather than sprawling beyond it?
not rated 0 1mo ago A 0 tokens
Command Claude Code
Review a story for completeness and ensure it stays a goal document, not a spec.
not rated 0 1mo ago A 0 tokens
Command Claude Code
Review the GitHub issues a story was broken into — do they cover the story, and does each stay a lean goal rather than a frozen spec?
not rated 0 1mo ago A 0 tokens
dw-story
08Command Claude Code
Create a user story file from user input.
not rated 0 1mo ago A 0 tokens
dw-tasks
09Command Claude Code
Break a reviewed plan (or a story) into GitHub task issues, each linked back to it.
not rated 0 1mo ago A 0 tokens
Command Claude Code
Research best practices, study the project, and write its README — diagrams and all.
not rated 0 1mo ago A 0 tokens
Command Claude Code
Check a README delivers for its reader, reads and looks right, and is true to the code.
not rated 0 1mo ago A 0 tokens
qw-cases
12Command Claude Code
Turn a reviewed test plan into readable test docs in docs/tests/ — reusing vetted steps where a reuse index is available, instead of re-inventing them.
not rated 0 1mo ago A 0 tokens
qw-plan
13Command Claude Code
Derive the scenarios that verify a story (or an on-request target) — the "what to test", before any test doc is written.
not rated 0 1mo ago A 0 tokens
Command Claude Code
Check each test doc does one clear job, has observable steps, and traces back to its story — before it is bound and run.
not rated 0 1mo ago A 0 tokens
Command Claude Code
Check the proposed scenarios cover the story — and stay coverage, not a frozen step-by-step spec.
not rated 0 1mo ago A 0 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: