Sk8metalme Michi Old
sk8metalme-michi-old is a Claude Code plugin for the Validate phase that provides the legacy Michi spec-driven workflow from the michi-old repository.
by sk8metalme · github.com/sk8metalme/michi-old
Use the legacy Michi plugin only when you are pinned to the older sk8metalme/michi-old repo for spec-driven Claude workflows.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install sk8metalme-michi-old@sk8metalme/michi-oldBuilt 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:sk8metalme/michi-old") and the paste-ready config with skillselion.get_install_config("plugin:sk8metalme/michi-old").
What it does
sk8metalme-michi-old is the prior-generation Claude Code plugin entry for the Michi spec-driven, AI-driven development workflow hosted under sk8metalme/michi-old. It mirrors the current Michi positioning—helping builders define scope and follow a structured workflow with Claude—but exists for compatibility with setups that still reference the old repository slug or discovery timestamp. New solo builders should default to the non-old Michi plugin unless a fork or internal policy requires this artifact. Functionally it supports validation and scoping conversations that precede implementation, with continued relevance during lightweight build PM when tasks must honor earlier specs. Catalog metadata is sparse on version deltas versus michi, so treat this entry as a legacy mirror with identical keyword signals rather than a distinct methodology. Use it to avoid breaking existing Claude Code configurations while planning migration to the current repo.
Highlights
- Legacy single-plugin packaging from sk8metalme/michi-old
- Same keyword cluster as Michi: aidriven, specdriven, workflow, claude
- Suitable for repos already locked to the old plugin manifest
- Community category listing with one plugin count
- Prefer sk8metalme/michi for new installs unless migration is blocked
Why builders use it
Older Claude Code setups still point at michi-old and break when you swap to the current plugin without a deliberate migration plan.
Keeping michi-old registered preserves spec-driven workflow behavior for legacy projects until you move to sk8metalme/michi.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is sk8metalme-michi-old for?
It is for Claude Code users still tied to the michi-old repository who need continuity for spec-driven workflows without immediate migration.
When should I use sk8metalme-michi-old?
Use it only when your project or team standard still installs from sk8metalme/michi-old; otherwise choose the current Michi plugin.
How do I add sk8metalme-michi-old to my agent?
Register the plugin from sk8metalme/michi-old in Claude Code the same way as other plugins, then plan a move to sk8metalme/michi when feasible.
Comments
Share how you use sk8metalme-michi-old, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.