mcpField
R
requirements-generator

requirements-generator

github.com/nextstage-brasilDevelopment045 installsUpdated 4d ago
Repository

About requirements-generator

Requirements Generator creates a structured requirements.md for a specified product version. It is intended for project planning workflows and can use a generic or applicable stack profile to shape the requirements document.

Key features

  1. 01Generate a version-specific requirements.md
  2. 02Select from generic and stack-specific profiles
  3. 03Include research in non-functional requirements or acceptance criteria
  4. 04Add frontend UI/UX requirements when a design brief applies
  5. 05Specify data models, table order, and endpoints

Use cases

  1. 01Draft requirements for a new product version
  2. 02Adapt requirements to a known technology stack
  3. 03Turn research into acceptance criteria
  4. 04Document frontend and data-model requirements

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nextstage-brasil/skills --skill requirements-generator

After installing, type/requirements-generatorin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

evals/
evals.json
references/stacks/
generic.md
intelligent-saas.md
laravel-react.md

Details

From the project README

Requirements Generator

Produce a structured requirements.md for {product_root}/docs/versions/{version_san}/.

Harness discovery

See ../nextstage-harness/references/harness-discovery.md and ../nextstage-harness/references/artifact-layout.md. Create {product_root}/docs/versions/{version_san}/ before writing.

Inputs

  • Scope description (possibly enriched by clarify-requirements)
  • {product_root}, {version_san}
  • Optional: design-brief.md, stack profile, brownfield map, web research from orchestrator

Stack profiles

Load one profile from references/stacks/ when stack is known:

ProfileWhen
generic.mdDefault — stack-agnostic structure
laravel-react.mdLaravel + React monorepo detected or confirmed
intelligent-saas.mdBackend + frontend + agent-api

Do not mention framework-specific tooling unless the profile or detected stack applies.

Document structure

Generate only the markdown document (no conversational preamble):

## Main objective of the version:

{executive summary}

## Technology stack:

{confirmed stack — reference applicable rules when harness has them}

## UI/UX guidelines:

{from design-brief when frontend in scope — omit if backend-only}

## Data model and APIs:

{tables, FK order, key endpoints — source of truth for tasks}

## Feature grouping:

### Feature 001 - TITLE

**Precedence:** None | Feature NNN
**Layers:** Backend | Frontend | Infrastructure | Tests
**Detailed description:** ...

#### Acceptance criteria:

- [ ] ...

## Non-functional requirements (NFRs):

...

New project ordering

When the project is greenfield, infrastructure/setup features come before domain features (per stack profile): infra → database → cache/queues → backend modules → frontend → tests.

Language

English unless the user explicitly requests another language for the deliverable.

Rules

  • Work only under confirmed {product_root}
  • Incorporate research into NFRs or acceptance criteria when provided
  • For frontend features: include UI/UX section from design brief; acceptance criteria for visual tokens when applicable
  • Data model section is critical — explicit table creation order and endpoints

Integration

  • After generation: Gate 1 (requirements_confirmed) — see ../nextstage-harness/references/gates.md
  • Next: analyze-consistency after Gate 2

References

FileWhen
references/stacks/generic.mdDefault
references/stacks/laravel-react.mdLaravel/React stack
references/stacks/intelligent-saas.mdAgent-augmented SaaS

Comments

Markdown supported