Edwinhu Workflows
edwinhu-workflows is a Claude Code plugin for the Build phase that provides unified, GSD-style workflows with handoff rules and validation for development, data science, and writing.
by edwinhu · github.com/edwinhu/workflows
Install unified GSD-style Claude Code workflows that enforce output-first rules, session handoffs, and validation across development, data science, and writing tasks.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install edwinhu-workflows@edwinhu/workflowsBuilt 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:edwinhu/workflows") and the paste-ready config with skillselion.get_install_config("plugin:edwinhu/workflows").
What it does
edwinhu-workflows is a Claude Code plugin marketplace that ships one consolidated workflow pack for builders who split time between software, data science, and written deliverables. Rather than ad hoc prompts per task, it promotes a GSD-inspired operating model: output-first expectations, unified session rules, and enforcement when the agent drifts from the agreed plan. Keywords emphasize handoff clarity, validation, verification, and deviation handling—useful when you chain multi-hour agent sessions on a SaaS feature, an experiment notebook, or a technical article. Solo developers benefit because the same rule shell wraps different domains, reducing context renegotiation every time you switch modes. Install it when you want predictable agent behavior and reviewable checkpoints instead of free-form chat while you build. The bundle is narrow in plugin count but deep in process semantics, making it a methodology layer on top of vanilla Claude Code rather than a grab bag of unrelated integrations.
Highlights
- Single-plugin marketplace for development, data science, and writing workflows
- GSD-style unified sessions with output-first and explicit handoff rules
- Deviation enforcement plus validation and verification checkpoints
- Session-oriented rules so agents stay on contract across long tasks
- Cross-domain coverage: dev builds, science analysis, and writing deliverables
Why builders use it
Agent sessions fall apart when there are no enforced handoffs, output contracts, or verification steps across dev, data science, and writing work.
After adding the workflows marketplace, Claude Code sessions follow output-first rules, deviation checks, and validated handoffs suited to mixed builder tasks.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 7 stars, 0 votes.
FAQ
Who is edwinhu-workflows for?
Developers and indie builders using Claude Code who juggle coding, data science, and writing and want shared session rules and verification.
When should I use edwinhu-workflows?
Use it at the start of multi-step agent sessions when you need output-first deliverables, strict handoffs, and validation before you merge or publish.
How do I add edwinhu-workflows to my agent?
Register the edwinhu/workflows marketplace in Claude Code, enable the workflow plugin, and apply its session and rules configuration to your project.
Comments
Share how you use edwinhu-workflows, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.