mcpField
N
ns-sdd-version-partitioner

ns-sdd-version-partitioner

github.com/nextstage-brasilDevelopment067 installsUpdated 1w ago
Repository

About ns-sdd-version-partitioner

A skill that partitions a master requirements.md into sequentially plannable subversions and emits a roadmap and requirement excerpts. It is for teams using this document-based version-planning workflow.

Key features

  1. 01Parse features, dependencies, and data-model hints
  2. 02Build a dependency DAG
  3. 03Group by domain and split oversized slices
  4. 04Generate roadmap and subversion requirement excerpts
  5. 05Create an empty tasks directory for each slice

Use cases

  1. 01Break a large release specification into sequential planning slices
  2. 02Review the roadmap before planning tasks for each slice

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nextstage-brasil/skills --skill ns-sdd-version-partitioner

After installing, type/ns-sdd-version-partitionerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

evals/
evals.json
references/
partition-workflow.md
version-roadmap.template.md

Details

From the project README

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

  1. Parse master — Features, precedences, data model hints, layer tags
  2. Build DAG — default order: schema → API → FE → tests; honor explicit precedence
  3. Group by bounded context — cluster by domain/entity
  4. Split oversized groups when:
    • > 12 features with cross-dependencies, or
    • ~50 estimated tasks, or
    • ~600k token heuristic
  5. Consolidate undersized — merge adjacent slices below ~4 tasks when safe; target 4–7 tasks per subversion
  6. Topological sort — folders 01-slug, 02-slug, …
  7. Emit artifacts:
    • version-roadmap.md at version root
    • subversions/{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.md saved
  • All subversion folders with excerpt requirements + empty tasks/
  • No task-*.md created
  • Human can review before slice planning loop

References

FileWhen
references/version-roadmap.template.mdRoadmap structure
references/partition-workflow.mdOrchestrator loop after partition

Integration

After partition → Gate Roadmap (human confirms) → plan each slice (Gates 2–3, tasks) without repeating Gate 1.

Comments

Markdown supported