Spec-Driven Develop — Spec-First Agent Skill (2026)

Main

• The README is explicit about multi-platform packaging: Claude Code plugin metadata, Codex plugin marketplace files, Cursor install scripts, and a generic SKILL.md fallback for other agents.
• Because it’s spec-first, it’s best used on transformations (rewrite/migrate/overhaul) where you want a checklist-driven gate before code changes proceed.
• A pragmatic adoption path is to install it in one tool first (Claude Code or Codex), run it on a small module, then scale to whole-repo migrations once the workflow feels predictable.
• Treat it as a process tool: you are buying repeatable checkpoints (spec → execute → tests) rather than a single prompt; the value is consistency across big changes.

FAQ

• Is it tied to one agent platform?: No. It ships plugin packaging for multiple tools and also provides a generic SKILL.md path for any agent that reads Markdown instructions.
• What is a good first use case?: Try a focused refactor or migration on one directory; verify the spec/checkpoint loop before attempting an entire project rewrite.
• How do I install for Codex?: The README documents adding the GitHub marketplace to Codex, then enabling the plugin (or configuring it in ~/.codex/config.toml).