Drewdresser Ai Dev Settings
drewdresser ai-dev-settings is a Claude Code plugin for the Build phase that connects strategic planning, user stories, and OKRs to rapid vision-to-code execution and review.
Install drewdresser ai-dev-settings when you want OKRs, user stories, and strategic plans to flow directly into rapid Claude Code execution and review on your main branch.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install drewdresser-ai-dev-settings@drewdresser/ai-dev-settingsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:drewdresser/ai-dev-settings") and the paste-ready config with skillselion.get_install_config("plugin:drewdresser/ai-dev-settings").
What it does
drewdresser-ai-dev-settings is a Claude Code plugin built for solo builders who refuse to treat planning and coding as separate worlds. It packages strategic planning habits—think objectives, user stories, and structured intent—with the speed of agent-driven implementation and review. Instead of dumping a generic rules file, it targets a vision-to-code loop: clarify what matters, break work into builder-sized stories, execute with Claude Code commands, and keep quality aligned through code-review oriented flows and main-branch discipline. The repo ships one focused plugin rather than a large marketplace, which makes it easier to adopt when you are mid-build and need PM rigor without hiring a PM. It pairs naturally with agents and skills you already run locally or in CI-minded main-branch workflows. Intermediate users get the most value: you should be comfortable defining OKRs or story backlogs yourself, then letting the plugin steer how the agent interprets them. Skillselion tags it under Build / PM because that is where planning artifacts first become executable scope, even though the same settings can inform validate-and-ship checkpoints later in the week.
Highlights
- Single-plugin pack: strategic planning meets rapid execution in Claude Code
- OKRs and user-story oriented workflow automation from vision to code
- Built-in code-review and dev commands aligned with main-branch delivery
- Skills and agents configuration for consistent development settings
- Workflow automation bridging planning artifacts and implementation
Why builders use it
Plans and OKRs live in docs while Claude Code improvises features that drift from the story you actually approved.
After install, your agent follows a vision-to-code workflow with planning commands, execution skills, and code-review aligned to main-branch delivery.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is drewdresser-ai-dev-settings for?
Indie developers using Claude Code who want strategic planning, user stories, and OKRs to stay attached to coding and review commands.
When should I use drewdresser-ai-dev-settings?
When you are in Build and need to turn a validated vision into sequenced stories and fast agent execution on your main branch.
How do I add drewdresser-ai-dev-settings to my agent?
Add the drewdresser/ai-dev-settings repository as a Claude Code plugin marketplace entry and enable its single workflow plugin in your dev settings.
Comments
Share how you use drewdresser-ai-dev-settings, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.