mismagent-method

mismAgent — agentic flow in three movements, portable (generic core + per-project profile in <output_dir>/profile.md). This is the KERNEL: enough on its own for single-side projects; modules (e.g. mismagent-cross-deploy) are enabled by necessity. explore: mism-explore (dialogue, profile bootstrap) + subagents mism-researcher + mism-challenger (demolishes the idea cold) + mism-analyst (strategic + ubiquitous language in the domain language). model: mism-tactical-modeler (aggregates/invariants/events/commands) + mism-ux-designer (UI -> views) + mism-architect (architecture+ADRs; stack decisions deliberated with the user; guarantor of the boundaries and their projection) + mism-build-manifest (tactical -> building-block manifest, types PINNED at the boundaries). build: /mismagent:composer (owner-first waves, D1 green on its own, merge=composition, D2 contract test on the boundary) -> mism-worker xN (skill = block-type realize-* x projection seam-* + per-side memory) -> mism-verifier (fresh context) + mism-code-review. State = the folder, executable boundary (contract tests), handoff=file, release=tag<->feature-flag, no sprints.

Cross-deploy module of mismAgent (requires the core `mismagent` plugin). When a Bounded Context boundary crosses a deploy boundary (side(consumer) != side(supplier)), the Port is projected into OpenAPI + per-side generated types + CDC publish/verify. Skills: seam-cross-deploy (loaded by the worker when boundary.projection = cross-deploy) and mism-create-contract (reconciles the OpenAPI from the blocks, names from the ubiquitous language). Enable it on demand: a single-side project does not need it.