Intent.ModuleBuilder.AI.SDD

This module does not generate application code. It drops two AI context files into the repo it is installed in, which together describe and enforce the module-building experience over Intent Architect's native Spec-Driven Development (SDD) lifecycle (/sdd-requirements → /sdd-design → /sdd-tasks → /sdd-implement → /sdd-verify) — with a golden sample, built or documented before any spec exists, as the one prerequisite. It generates no C# and has no designer model dependency — the files it writes are always overwritten on install/update.

Note

The intention is to install this module once in your solution and in a dedicated Intent Architect application which would allow you the flexibility of controlling where the output gets generated by adjusting the Output Location inside the application settings.

What This Module Generates

  • .agents/skills/sdd-build-module/SKILL.md — the module-building experience end to end. Routes on "do you have a reference golden sample?"; a missing sample is built in a planning session (a prepared prompt hands the developer into /plan, the plan is co-owned and explicitly approved, and it finishes in Golden Sample Reference form — the document the spec phases derive from). Requirements start only once the Reference exists; the developer stipulates the module's surface; extrapolation beyond the sample is flagged in plain language; variations are proven by generated test applications, never by growing the sample.
  • .agents/instructions/sdd-wave-evidence.instructions.md — the obligations that must reach implementation sessions automatically (instruction files are injected into every session, including wave sub-agents and external ACP agents): the wave evidence contract, the find-the-Reference-first step, and the GOLDEN-SAMPLE: marker sweep.

Why a skill plus an instruction file, and no agent definition: skills follow the user across agents and modes — including Plan mode, where the experience starts, and ACP sessions, whose system prompts receive the solution's skill manifest — while an agent definition is only loaded while that agent is selected. The instruction file carries the pieces that must arrive even in sessions where nobody invoked anything.

Bundled Output

The content is bundled once, in this module's own source, and always overwritten on every install or update. Local edits to the bundled content are not a supported use case — standardization across consuming repos is the goal, not per-repo customization.

None. This module has no dependency on any designer, domain, or output-target module beyond the Intent Architect core infrastructure required to run any Software Factory template.