mcpField
N
ns-sdd-task-generator

ns-sdd-task-generator

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

About ns-sdd-task-generator

This skill turns an atomic slice of a feature into a detailed task document for engineers or coding agents. It follows project architecture rules and requirements, with validation criteria for backend, frontend, or infrastructure work.

Key features

  1. 01Write detailed tasks with probable paths and validation criteria
  2. 02Read architecture rules and requirements first
  3. 03Handle backend, frontend, and infrastructure tasks
  4. 04Order tasks according to dependencies
  5. 05Add UI and backend-specific requirements

Use cases

  1. 01Turn an atomic feature slice into an actionable engineering task
  2. 02Prepare task instructions with implementation locations and acceptance criteria for coding agents

Install

Copy the command and run it in a terminal.

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

After installing, type/ns-sdd-task-generatorin Claude Code to confirm it loaded.

Bundled filesevals/evals.jsonreferences/task-schema.md

Details

From the project README

Task Generator

Convert one atomic slice of a Feature into a detailed task-NNN-slug.md for engineers or coding agents.

Orchestrators (MUST spawn task-writer-agent when that bridge exists — ../ns-harness/references/subagent-dispatch.md). This file = worker body, not invite to inline from ns-spec-driven.

Harness discovery

See ../ns-harness/references/harness-discovery.md. Load rules from {harness_root}/rules/*.md. Read architecture-rules.md first. Legacy: .cursor/rules/*.mdc only if {harness_root} is absent. Read requirements.md strictly — do not invent tables or endpoints.

Scope

  • Layers: Backend, Frontend, Infrastructure
  • Not this skill: E2E → ns-pm-e2e-test-task-generator; Backend unit tests → ns-pm-unit-test-task-generator

Golden rule

No one-line summaries. The implementer must know what to do, where (probable paths), which stack/rules apply, and validation criteria. Never repeat the summary verbatim in the detailed section.

Inputs

  • Atomic task description (from orchestrator)
  • Layer type: Backend | Frontend | Infra
  • {product_root}/docs/versions/{version_san}/requirements.md
  • Task number NNN and dependency tasks

Dependencies

  • FK parents before children — task order reflects migration/API order
  • Frontend consuming an API → backend task precedes frontend task
  • See references/task-schema.md for full file template

Frontend extras

When task touches UI:

  • data-testid contract — kebab-case, prefixed (btn-, input-, form-, etc.)
  • Auth forms: marketing panel, PasswordInput, i18n keys per frontend rules when present
  • i18n: all strings via translation keys; useFormat() for dates/currency
  • Navigation: groupKey when adding menu items (if nav rules exist)

Backend extras

When uses_grogoo: false (default): Sanctum, manual modules — no Grogoo references.

When multitenancy: explicit company_id / ownership validation in criteria.

Output path

{product_root}/docs/versions/{version_san}/tasks/task-NNN-slug.md

For subversions: under subversions/{subversion_san}/tasks/.

References

FileWhen
references/task-schema.mdFull markdown template and header fields

Related skills

  • ns-pm-unit-test-task-generator — after backend implementation tasks
  • ns-pm-e2e-test-task-generator — after frontend tasks with UI
  • ns-sdd-execution-handoff-generator — after all tasks for the version are written (planning closure)

Comments

Markdown supported