DimonSmart.IntentDrivenDevelopment.Tool 1.0.5

Prefix Reserved
.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet tool install --global DimonSmart.IntentDrivenDevelopment.Tool --version 1.0.5
This package contains a .NET tool you can call from the shell/command line. 
dotnet new tool-manifest
                    


                            if you are setting up this repo
                        

                    

                
dotnet tool install --local DimonSmart.IntentDrivenDevelopment.Tool --version 1.0.5
This package contains a .NET tool you can call from the shell/command line. 
#tool dotnet:?package=DimonSmart.IntentDrivenDevelopment.Tool&version=1.0.5
                    


                    

                
nuke :add-package DimonSmart.IntentDrivenDevelopment.Tool --version 1.0.5

Intent-Driven Development

If the codebase disappeared, an AI agent should be able to rebuild the product from the specifications.

That only works when specifications contain product truth, not task noise.

AI can generate code quickly.

Long-term software development fails in a different place: project memory turns into garbage. Specifications get mixed with tasks, generated plans, implementation notes, temporary fixes and old decisions. After a while, nobody knows what is still true and what was just part of yesterday's AI session.

Intent-Driven Development is a specification system for long-running AI-assisted development.

Its goal is simple:

Keep specifications clean enough that any AI coding agent can recreate the product from scratch, using only what actually helps to build the product.

Why not just Spec-Driven Development?

Spec-Driven Development made the right move: start from a spec.

Intent-Driven Development keeps that idea, but adds a stricter rule:

The spec is not a task tracker.

Spec-Driven Development Intent-Driven Development
Spec, plan and tasks often live too close together Product intent and temporary work are separated
Generated tasks can start looking like truth Generated artifacts are disposable
The workflow is often tied to one tool Product intent stays independent from AI agents
Good for starting features Better for keeping a project coherent over time

Core idea

A specification should answer:

What product are we building?

Not:

What did the agent do today?

Tasks change.
Plans change.
Agents change.
Product intent should stay stable.

Documentation

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
1.0.17 81 6/9/2026
1.0.16 83 6/9/2026
1.0.15 85 6/9/2026
1.0.14 83 6/9/2026
1.0.13 78 6/9/2026
1.0.12 85 6/9/2026
1.0.11 85 6/9/2026
1.0.10 100 6/8/2026
1.0.9 93 6/8/2026
1.0.8 98 6/8/2026
1.0.7 92 6/8/2026
1.0.6 107 6/8/2026
1.0.5 88 6/7/2026
1.0.4 88 6/7/2026
1.0.3 100 6/6/2026