realize-scaffold

Creates the minimal buildable project skeleton so the side's gate runs green on an empty tree.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lucolucus/mismagent --skill realize-scaffold-lucolucus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: realize-scaffold
Source: https://github.com/lucolucus/mismagent/tree/main/plugins/mismagent/skills/realize-scaffold
Command: npx skills add https://github.com/lucolucus/mismagent --skill realize-scaffold-lucolucus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Greenfield features need a compilable project skeleton before any domain block (aggregate, port, UI) can be built, and the build gate must be proven to actually detect failures rather than passing vacuously. ## Core Features & Use Cases - Skeleton generation: Creates the build entry (wrapper, build descriptor), module structure from the architecture map, and pinned plugins/dev-dependencies required by the stack ADR, with zero domain code. - Gate discriminating-power proof: Plants a deliberately failing probe test in each guarded module, verifies the gate goes red then green, and records the evidence in a gate-proof file. - Contract and UI wiring: Honors the profile's run binding for UI sides and creates event-schema contract locations declared by cross-deploy boundaries. - Use Case: As the wave-0 block of a mismAgent build, scaffold a new backend side so its Gradle gate compiles and tests an empty module tree before owner blocks begin. ## Quick Start Ask the worker to realize the scaffold block for the current feature side so the gate runs green on the empty skeleton.

Frequently Asked Questions about realize-scaffold

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a greenfield project skeleton before writing domain code?

Create only the build entry, module structure from the architecture map, and the plugins the gate needs, then run the side's gate until it passes on the empty tree. No aggregates, ports, or business rules belong in the scaffold.

How do I verify a build gate actually fails when tests fail?

Plant a trivially failing probe test in each module the gate claims to guard, run the gate to see it red, then remove the probe and confirm green. Record the proof in a gate-proof file so later blocks' results are meaningful.

When is a scaffold block needed in a feature build?

Only for greenfield sides where the project does not yet build. If the project already compiles, the scaffold block does not exist and owner blocks proceed directly against the existing skeleton.

Why does a Gradle build pass even when module tests fail?

A task like :app:build may never execute dependency modules' tests, leaving them compiled but never run. Probe each guarded module with a failing test to expose this vacuously green gate and report it against the profile's gate string.

What are the limitations of the scaffold block?

It writes no domain logic, no acceptance criteria, and no contract tests, and it must not add dependencies beyond the stack ADR and infra-notes. Its only acceptance is the side's gate running green on the empty skeleton.