Sk8metalme Michi Old
- Updated May 3, 2026
- sk8metalme/michi-old
sk8metalme-michi-old is a Claude Code plugin that provides the legacy Michi spec-driven workflow from the michi-old repository.
About
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 developers 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 developers 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.
- 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
Sk8metalme Michi Old by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install sk8metalme-michi-old@sk8metalme/michi-oldAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| Last updated | May 3, 2026 |
|---|---|
| Repository | sk8metalme/michi-old ↗ |
What it does
Use the legacy Michi plugin only when you are pinned to the older sk8metalme/michi-old repo for spec-driven Claude workflows.
Who is it for?
Best when you're maintaining existing projects or docs that explicitly reference sk8metalme/michi-old.
Skip if: Greenfield projects that should install the current sk8metalme-michi plugin instead of a deprecated line.
What you get
Keeping michi-old registered preserves spec-driven workflow behavior for legacy projects until you move to sk8metalme/michi.
- Continued legacy Michi workflow via one plugin
- Stable spec-driven sessions for old-configured projects
- Migration path clarity toward the current michi repo
By the numbers
- [object Object]
- [object Object]
- [object Object]
Recommended Plugins
0oastro Kawai Girl Output StyleTransform Claude's responses into kawaii anime girl style\!3
0xbigboss Claude CodeComprehensive configuration system for Claude Code51
2lab Ai Oh My ClaudeClaude Code plugin for AI-powered iterative development loops.37
45ck Claude Sdlc PluginClaude Code plugin for SDLC workflow automation with Storybook planning hub1
70 10 Claude Code Plugins70-10's Claude Code plugins
Aaronbassett Agent FoundryMy personal plugin marketplace for Claude Code4How it compares
Legacy sibling of sk8metalme-michi—same workflow intent, older repo pin—not a separate dev-tools bundle.
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.