build

Execute approved plans via sub-agents with phase ordering and build-time gates.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill build-atlas-memory-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build
Source: https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools/tree/main/.cursor/skills/implement
Command: npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill build-atlas-memory-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures implementation follows the approved plan artifact with strict delegation, phase ordering, and build-time gates so execution doesn’t drift from intended scope or decisions.

Core Features & Use Cases

  • Strict plan-to-execution authority: Treats the compiled registry/validated overlays as authoritative for routing in registry-first mode and prevents “markdown as execution truth” mistakes.
  • Delegated sub-agent execution: Builds a delegation matrix, runs work in sub-agents by agent type, and enforces ownership and merge-point discipline.
  • Preflight + build-time conformance gates: Blocks execution until the plan status is Approved (or overridden), blockers are cleared, and planning/privacy reviews are complete.
  • Parallelism with explicit merge points: Allows parallel work only when the plan defines it, with integrator-owned merge steps.

Quick Start

Ask the system to run /build to execute the current approved plan with sub-agent orchestration and required gates.

Frequently Asked Questions about build

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

FAQPage Schema
How do I execute an approved plan with sub-agent orchestration and build-time gates?

To execute an approved plan with sub-agent orchestration, you can trigger the /build workflow, which delegates work based on a delegation matrix and enforces strict phase ordering and validation gates.

What is registry-first mode for plan execution and how does it prevent scope drift?

Registry-first mode treats the compiled registry and validated overlays as the authoritative routing source for plan execution, preventing scope drift by ensuring implementation does not rely on markdown as execution truth.

How do sub-agents handle parallel implementation tasks and merge points?

Sub-agents handle parallel implementation by following a delegation matrix that defines ownership, allowing parallel work only when explicitly planned, and enforcing integrator-owned merge steps at defined merge points.

Why does my plan execution get blocked before implementation starts?

Plan execution gets blocked by preflight conformance checks because the plan status is not Approved, blockers are not cleared, or required planning and privacy reviews are incomplete.

Do I need an approved plan artifact to run the /build workflow?

Yes, you need an approved plan artifact to run the /build workflow, as preflight conformance gates block execution until the plan status is Approved or explicitly overridden.

What happens when decisions or details are missing during gated plan execution?

When decisions or details are missing during gated plan execution, the system enters a blocked state and sends messaging that requests the minimal plan patch to resolve the missing information.