TypeScript Early release MIT

FeatureBuilder

A local-first desktop workspace for writing structured hardware feature specifications and connecting requirements to design-verification scenarios.

Understanding the project

The idea in plain language.

FeatureBuilder gives hardware and RTL teams a structured alternative to a long specification document. A feature carries its intent, owner, priority, requirements, design detail, verification strategy, scenarios, dependencies, and open questions in one reviewable model.

Projects remain ordinary directories of readable JSON files. That keeps confidential design material local, makes changes suitable for Git review, and avoids tying the specification to a hosted service or proprietary database.

Core capabilities

What the project can do.

  • Organizes features into a searchable, reorderable parent-child hierarchy with stable keys.
  • Separates atomic requirements from architecture, interfaces, behavior, reset/error handling, and performance constraints.
  • Captures verification strategy, assertions, coverage, exclusions, and scenarios using simulation, formal, emulation, or inspection.
  • Links scenarios to requirements and reports requirements that have no verification path.
  • Calculates feature readiness and reports missing intent, ownership, behavior, requirements, and verification planning.
  • Writes one project manifest and one JSON file per feature using validated identifiers and atomic file replacement.

Typical workflow

How someone uses it.

  1. 1

    Create or open a local project directory and define its name and feature-key prefix.

  2. 2

    Build the feature hierarchy, then capture requirements and the corresponding design behavior for each feature.

  3. 3

    Add verification scenarios and link them to the requirements they cover.

  4. 4

    Use readiness and validation findings to close gaps before review, then commit the project directory to Git if appropriate.

Under the hood

Technology and design choices.

  • Electron
  • React
  • TypeScript
  • Vite
  • Local JSON files
  • Vitest

Important considerations

What to know before using it.

  • The current release focuses on specification authoring; execution milestones and live regression or coverage results are roadmap items.
  • Project folders can contain confidential hardware information and should be reviewed before they are committed or shared.
  • Distributable builds are currently unsigned and may trigger operating-system security warnings.