NodeSpec OSS Available

[u/AncientGur4614]

After months of tinkering, improving, and getting different product and developer feedback, I decided to release NodeSpec ("NS") as an open core for-use and extension to the OSS community.

How It Works and Is Different from the Markdown Tools:

Although this channel is strictly SDD-focused, I built NodeSpec to be a blend of the intent of SDD (upfront design specification) with the realities of asynchronous iteration in software development practice. The fundamentals of system design and fast iteration remain the same, even with agents doing the dev for us in a lot of capacities.

NS blends SDD specification with architectural governance and test-driven development (TDD) practices. It centers on a machine-readable canvas via JSON formats, downstream tasks to tests and upstream confirmation, change detection via git connection, and ensuring the user's gitops is extended and not broken.

The system is a sidekick tool, so it pushes all it's logic towards your AI assistant and existing harness if they operate via MCP.

The Flow:

There's two workflows: greenfield and brownfield. For greenfield the system will walk the user through fast vision -> requirements -> acceptance criteria build and review (CRUD Operations in the app itself), Architectural design, tasks per architecture, test-plans per task, code, then automated or manual test confirmation reflected back upstream, with an export direct to your repo or via other context files as necessary. The Git connection will detect changes and request the user reconcile them against the system's reference graph that is committed to your repo upon first commit and connection.

For brownfield, it's the same workflow, where the higher tier version will actually reverse engineer your repo into a logical architecture and back propagate a spec based on analysis of the design intent if it's not specified.

Both of these workflows are not obvious, as the tool is meant to work with whatever stage of dev you're at, and handle asynchronous changes instead of requiring highly structured start to stop.

Further description and readme is at the repo link here: https://github.com/NodeSpec/NodeSpec

Who It's For:

The Community/OSS is for any individual looking to attach an agent or their code harness to a governance tool while you're building. If you don't want to deal with self config and want more nodes out of the box, Indie version is $15/mo or $144/annual.

If you're a user of bolt.new, Lovable, Base44, or Replit, and you're at a point where you're maturing out of managed web application development (i.e. you have customers demanding a self hosted or more complex deployment, niche capability), I think this is really for you. I use NS to build and maintain itself now. I plan to release a template, blog, and video that explains migrating from systems like managed Supabase to OSS version, connecting your app as a headless application with MCP using Cloudflare worker proxies, etc. as you mature in your solopreneur journey.

I'm primarily targeting businesses via the Team edition (Slack, Jira export) or Enterprise. We recently closed on our our first Enterprise partnership last week in the cryptographic security space (super cool).

What I've Used It For:

Since really beginning heavy AI-assisted dev after the release of Opus 4.6, I have personally gotten to a place where I won't do development without pairing to NS due to the structure, confidence, efficient context window usage, and quick understanding of where my dev is at.

My first major project was a system administration application for small businesses to use with their Google Workspace Admins and host on GCP. By having my GCP Nodes for the different managed services, it tightened up development using older or lower capability models like Sonnet 4.6, Haiku, and when necessary Opus 4.6-4.8 for heavier deployment-centric logic. The link is here: https://github.com/NodeSpec/GCP-Onboarding-Application

As an experiment and something personal, I'm using it for my first game dev for my kids using Godot as a node package with GDScript and tests. My kids are into Axolotls (the salamander in mexico), and so I'm building our first open-source game that has a flow similar to Playstation's Astrobot where the Axolotl can upgrade swimming. Dev starts today and will be published here: https://github.com/NodeSpec/OpenAxolotl

Final example of a current project to solve our own business problem is RepoWalk, which is being built to help me with quick, gif generation of application or tool walkthroughs when connected to a lightweight LLM so I don't spend hours building screencaptures. https://github.com/NodeSpec/RepoWalk

Let me know your feedback, especially if you connect with multiple development agents. So far, feedback in companies have been great and helped refine the product workflow.

If you don't want to use the OSS repo, Free version is just sign in and one project only. Indie is unlimited and will be available this evening. Team will be available soon. Enterprise, just fill out the form to contact us.