Quiver
Install a composable Claude Code lifecycle—brainstorm, plan, execute, review, and hand over—from idea through merged PR.
Overview
quiver is a plugin marketplace for the Build phase that provides a composable Claude Code lifecycle from brainstorm through review and handover to a merged PR.
What is this marketplace?
- Single MIT-licensed quiver plugin: brainstorm → plan → execute → review → handover
- Session management and context handover hooks for multi-day solo shipping
- Git commit and PR-oriented workflow tags built into marketplace metadata
- Composable lifecycle from idea to merged pull request
- 1 plugin in marketplace: quiver (MIT license)
Community signal: 9 GitHub stars.
What problem does it solve?
Solo agent sessions lose intent between brainstorm and merge, so plans fragment and PRs ship without consistent review or handover notes.
Who is it for?
One-person teams using Claude Code who want a lightweight product-management rhythm tied to git and session handover.
Skip if: Large teams with Jira-driven process or builders who only need isolated code-generation skills.
What do I get? / Deliverables
You run a repeatable brainstorm-plan-execute-review-handover chain with session and git-aware context so work lands as reviewed, merge-ready changes.
- Structured session artifacts across brainstorm, plan, execute, and review
- Handover notes and git-linked commits suitable for opening or updating a PR
- Repeatable solo shipping ritual inside Claude Code
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Build + PM is the canonical shelf because Quiver orchestrates how work moves through implementation and review even though it starts earlier in discovery. PM captures phased commands, handover, and git-linked session flow rather than a single frontend or backend generator.
How it compares
Lifecycle and session workflow marketplace, not an MCP server or a single REST integration skill.
Common Questions / FAQ
Who is Quiver for?
Solo developers who use Claude Code end-to-end and want structured phases from ideation through merged pull requests.
When should I use Quiver?
Use it when you start features in chat, lose context between sessions, or want explicit review and handover before merging.
How do I add Quiver to my agent?
Add the Quiver marketplace plugin in Claude Code from the published repository, then invoke its brainstorm, plan, execute, review, and handover commands or hooks as your default shipping loop.