mismagent-worker-composer

Coordinates parallel worker agents to build and merge manifest-defined building blocks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an architecture manifest into working, merged code requires coordinating many parallel implementation tasks, keeping each piece green on its own, and verifying that every boundary between components actually holds — doing this by hand is error-prone and slow. ## Core Features & Use Cases - Wave-based composition: Reads a building-blocks manifest and dispatches specialized worker agents in waves — boundary owners first, then consumers in parallel, one git worktree per block. - Readiness gate: Validates the manifest before any build starts, checking pinned boundary types, contract tests, executable and discriminating test gates, and bouncing incomplete specs back to the modeling step. - D1/D2 quality gates: Verifies each block green on its own (build, tests, code review) and welds each boundary with a real contract test before merging into the integration line. - Use Case: After modeling a feature into a building-blocks.yaml manifest, run this skill to have workers implement all blocks in parallel worktrees, merge them onto the feature branch, and confirm the release with a green tag and feature flag. ## Quick Start Run the worker-composer on my feature manifest to build all blocks in waves and merge them into the integration branch.

Frequently Asked Questions about mismagent-worker-composer

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

FAQPage Schema
How do I build a feature from a building-blocks manifest?

Invoke the worker-composer with the feature name; it reads building-blocks.yaml, runs a readiness gate, then dispatches worker agents in waves — boundary owners first, consumers in parallel — merging each green block into the integration line.

How does the worker-composer run parallel implementation tasks?

It creates one git worktree per ready block, cut from the integration line, and spawns one worker subagent per block (via spawn_agents_on_csv on Codex). Each worker returns a status token that routes the block to verification, parking, or rework.

What happens when a contract test fails between two components?

A red D2 contract test means the composition failed, so the boundary's consumer block is bounced back to doing for rework. After two failed rework cycles the block is parked with findings recorded in open-questions for a human decision.

Can the worker-composer resume after an interrupted run?

Yes, it is re-entrant by design: all state lives in the blocks/<context>/{todo,doing,doing,done} folders and git, not in session memory. Each firing reconciles orphaned blocks from git history and resumes where the folders indicate.

When does the readiness gate reject a manifest?

The gate rejects manifests with missing acceptance criteria, unpinned boundary types, absent contract files, or a test gate that cannot go red. It bounces back to the modeling command or profile with the specific gap named rather than patching by hand.