ns-sdd-version-partitioner
(NS) Partition a large master requirements.md into executable subversions with version-roadmap.md and slice requirements excerpts — without generating tasks. Use when a version has too many features for one planning cycle or the user asks to split a version — after Gate 1 requirements confirmed. Do NOT generate task-NNN files (planning per slice comes later).
- Installs
- 67
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/nextstage-brasil/skills --skill ns-sdd-version-partitioner- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ns-sdd-version-partitioner automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Version Partitioner
Split master requirements.md into subversions for sequential planning.
Harness discovery
See ../ns-harness/references/artifact-layout.md and ../ns-harness/references/harness-discovery.md. Read core-subversions rule from harness when present.
Scope
- Read only: master
{product_root}/docs/versions/{version_san}/requirements.md - Do not: generate tasks, execution-handoff, or re-run Gate 1
- Do not load product backend/frontend rules — structural partition only
Algorithm
- Parse master — Features, precedences, data model hints, layer tags
- Build DAG — default order: schema → API → FE → tests; honor explicit precedence
- Group by bounded context — cluster by domain/entity
- Split oversized groups when:
- > 12 features with cross-dependencies, or
- ~50 estimated tasks, or
- ~600k token heuristic
- Consolidate undersized — merge adjacent slices below ~4 tasks when safe; target 4–7 tasks per subversion
- Topological sort — folders
01-slug,02-slug, … - Emit artifacts:
version-roadmap.mdat version rootsubversions/{subversion_san}/requirements.md— excerpt + link to master../requirements.md#Feature-ID- Empty
subversions/{subversion_san}/tasks/per slice
Roadmap table columns
| NN | slug | Features | deps | tasks est. | tokens est. | status |
Start status as pending.
Output checklist
-
version-roadmap.mdsaved - All subversion folders with excerpt requirements + empty
tasks/ - No
task-*.mdcreated - Human can review before slice planning loop
References
| File | When |
|---|---|
references/version-roadmap.template.md | Roadmap structure |
references/partition-workflow.md | Orchestrator loop after partition |
Integration
After partition → Gate Roadmap (human confirms) → plan each slice (Gates 2–3, tasks) without repeating Gate 1.
FAQ
What does the ns-sdd-version-partitioner skill do?
(NS) Partition a large master requirements.md into executable subversions with version-roadmap.md and slice requirements excerpts — without generating tasks. Use when a version has too many features for one planning cycle or the user asks to split a version — after Gate 1 requirements confirmed. Do NOT generate task-NNN files (planning per slice comes later).
How do I install ns-sdd-version-partitioner?
Run npx skills add https://github.com/nextstage-brasil/skills --skill ns-sdd-version-partitioner in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ns-sdd-version-partitioner/ (personal) or .claude/skills/ns-sdd-version-partitioner/ (project).
Which AI agents can use ns-sdd-version-partitioner?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ns-sdd-version-partitioner safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ns-sdd-version-partitioner?
It is published by nextstage-brasil in nextstage-brasil/skills. It has 67 recorded installs.
More from nextstage-brasil/skills
ns-gitlab-board-sync
nextstage-brasil/skills
(NS) Sync existing GitLab issues with local planning/execution — milestone, RF labels, status, assignee, estimates, spent time. Use during implementation when tasks link to GitLab issues or after plan-version-from-gitlab sync — not for creating new issues (use mcp-gitlab-usage). Always atomic setissuelabels and three-step status cycle.
ns-spec-driven
nextstage-brasil/skills
Open the skill to read its SKILL.md instructions.
ns-gitlab-ci-generator
nextstage-brasil/skills
Open the skill to read its SKILL.md instructions.
ns-project-manager
nextstage-brasil/skills
Open the skill to read its SKILL.md instructions.
mcp-gitlab-usage
nextstage-brasil/skills
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.