mismagent-model

Conducts the model movement by sequencing tactical modeling, architecture, and manifest generation with three human checkpoints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an explored product idea into a buildable architecture requires coordinating tactical modeling, UX design, stack decisions, and manifest generation without losing human control over key decisions. This Skill conducts that entire model movement as one command, stopping only at the three checkpoints where human judgment is required. ## Core Features & Use Cases - Thin conductor orchestration: Sequences the tactical modeler, UX designer, architect (two-pass), build-manifest, and contract creation skills while writing no artifacts itself. - Three human checkpoints: Stops for NEEDS-INPUT ambiguities, the stack/architecture/infra deliberation, and the tests_nl elicitation, never adding extra gates. - Re-entrant execution: Resumes at the first missing artifact by re-reading files, so the movement can span sessions safely. - Use Case: After running the explore movement on a feature, invoke this command to produce a tactical model, foundational architecture ADRs, a building-blocks.yaml manifest, and OpenAPI contracts for cross-deploy boundaries, all deliberated with you at the decision points. ## Quick Start Run the mismagent-model command with your feature name to conduct the full model movement from the explore outputs through to the building-blocks manifest.

Frequently Asked Questions about mismagent-model

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

FAQPage Schema
How do I run the mismagent model movement on a feature?

Invoke the model command with the feature name after completing the explore movement. It requires the feature's product-brief.md and the project's context-map.md, then sequences tactical modeling, architecture, and manifest generation automatically.

What are the three human checkpoints in the model movement?

The conductor stops for NEEDS-INPUT ambiguities from the tactical modeler, the foundational stack/architecture/infra deliberation, and the tests_nl elicitation for high-value blocks. It never skips these and never adds extra gates.

Does the model command rewrite architecture decisions for each feature?

No. Foundational decisions happen once per project. When the project trunk exists, the architect runs a feature dispatch writing only feature-scoped decisions, and reopening the trunk requires an explicit user-requested amendment ADR.

Can the model movement resume after an interrupted session?

Yes, it is re-entrant by design. Every invocation re-reads the artifact files and resumes at the first missing one, since all handoffs between steps are files rather than in-memory messages.

When does the model movement create an OpenAPI contract?

Only when at least one boundary is declared cross-deploy with contract_form openapi. If the contract module is not enabled, it reports BLOCKED instead of improvising a projection.