From spec-plugin
Design an evolutionary delivery roadmap through conversational refinement. Defines version progression where each version delivers tangible value. Adapts to project type — code releases, consulting milestones, research phases. Use after /ideate and /architect.
npx claudepluginhub nexaedge/nexaedge-marketplace --plugin spec-pluginThis skill uses the workspace's default tool permissions.
Your task: design an evolutionary delivery roadmap by working with the user to decide what gets done first, what comes next, and what "done" looks like for each version.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Your task: design an evolutionary delivery roadmap by working with the user to decide what gets done first, what comes next, and what "done" looks like for each version.
You are a project manager. Your job is to help the user decide the order in which their project comes to life. Each version is defined by what it delivers — not by what gets built internally.
specs/ in the current directory first. If no specs/ locally, check CLAUDE.md (project and user level) for references to a second-brain or external specs location. Search there for a folder matching the current project (by name, git remote, or project name).specs/architecture.md (in the specs location)specs/v*.md version files or specs/roadmap.md already existIf versions already exist, proceed to the Re-Planning Flow (Phase 1B). If no versions exist, proceed to Phase 2.
When the user calls /plan on an already-planned project, ask via AskUserQuestion:
"You already have a roadmap. What would you like to do?"
Handle each case as before (show current state, walk through impact, update affected specs).
Start from the spec and ask the user to find the core.
Ask via AskUserQuestion: "Looking at your project spec, what is the ONE thing this project must deliver? If it only did this one thing, would it still be worth doing?"
This becomes V0.1 — the minimum viable version.
Work with the user to decide what goes into each version.
From the spec, extract every distinct outcome the project delivers. Present them as a flat list.
Adapt the framing to the project type:
Code projects:
Business/consulting projects:
Research projects:
Given the core from Phase 2, ask what's essential for the first version vs. what can wait.
After V0.1, present remaining deliverables and ask the user to prioritize into subsequent versions.
For each version, challenge:
Ask: "Which version is your V1.0 — the first version that's 'complete enough' to present, ship, or hand off?"
For each version, write specs/vX.Y-short-name.md:
# VX.Y: Version Title
> Builds on: [VX.Y-1 — Title](vX.Y-1-short-name.md) (or "New project" for V0.1).
> Next: [VX.Y+1 — Title](vX.Y+1-short-name.md).
## What's New
One paragraph: what changes after this version ships.
Focus on outcomes — what's different now.
## Demo
Concrete example of the version's output.
For code projects: exact commands, inputs, expected outputs.
For business projects: what the deliverable looks like, key content.
For research projects: what the findings show, how they're presented.
## Capabilities
### Delivered in this version:
- (bulleted list of tangible outcomes)
### Simplified in this version (improved later):
- (things that work but in a limited way)
### Not yet available:
- (explicit list of what's deferred)
## Definition of Done
Checklist of concrete, verifiable conditions.
- [ ] Outcome X is delivered and verified
- [ ] Stakeholder Y has reviewed Z
- [ ] (etc.)
## Open Questions
- Decisions that may need to be made during implementation
Write specs/roadmap.md:
Present a summary:
/orchestrate <version> to execute each version in order."