m2c1-worker

Orchestrate a 12-phase M2C1 software build lifecycle with human checkpoints.

88|108|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/grandamenium/cortextos --skill m2c1-worker-grandamenium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m2c1-worker
Source: https://github.com/grandamenium/cortextos/tree/main/templates/analyst/.claude/skills/m2c1-worker
Command: npx skills add https://github.com/grandamenium/cortextos --skill m2c1-worker-grandamenium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a large, multi-phase software build into a controlled autonomous workflow without you manually babysitting every step.

Core Features & Use Cases

  • Dedicated M2C1 worker orchestration: Creates and manages an isolated Claude Code worker session that runs through all 12 M2C1 phases, while you act as the human supervisor.
  • Brain dump to execution lifecycle: Guides you to provide BRAINDUMP.md, define success criteria, and ensure the worker has everything needed to start, discover, build, test, and iterate.
  • Bus-based communication and validation gates: Uses cortextOS bus messages for discovery Q&A, progress monitoring, phase-gated validation, and reliable cleanup on success or failure.
  • Tooling and credential setup support: Provides a human-style checklist for installing/configuring tools (e.g., browser automation), setting environment variables, and verifying them iteratively before execution.

Quick Start

Tell the agent to set up a new isolated project directory, create BRAINDUMP.md and AGENTS.md, then spawn the worker with cortextos spawn-worker and manage it via bus messages through the full M2C1 workflow.

Frequently Asked Questions about m2c1-worker

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

FAQPage Schema
How do I orchestrate autonomous software builds without manually supervising every step?

Autonomous build orchestration is handled by spawning an isolated Claude Code worker session that runs through a 12-phase lifecycle, letting you act as a human supervisor at decision checkpoints instead of babysitting each step.

What is a phase-gated build lifecycle and when do I need it for software development?

A phase-gated build lifecycle is a structured development process that requires validation before moving between stages, needed for large builds like new projects or major features that require isolated execution and human decision checkpoints.

How do I set up an autonomous worker session for a multi-phase development project?

Setting up an autonomous worker session requires creating an isolated project directory, writing BRAINDUMP.md and AGENTS.md specification files, then spawning the worker and managing it through bus-based messages for progress and discovery.

Can I use bus-based communication to monitor progress and handle questions during autonomous builds?

Bus-based communication supports discovery Q&A, progress monitoring, and phase-gated validation throughout the build lifecycle, ensuring reliable cleanup on either success or failure.

What tooling and credential setup is required before starting an autonomous build workflow?

Tooling setup requires a human-style checklist to install and configure tools like browser automation, set environment variables, and iteratively verify them before execution begins.

Does autonomous agent orchestration work for isolated execution of large feature implementations?

Autonomous agent orchestration suits large builds including new projects, major feature implementations, and structured development tasks that require isolated execution plus human decision checkpoints throughout the 12-phase workflow.