map-emitter

Assemble map.json from extracted document data and validate its structure.

3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ForgePlan/marketplace --skill map-emitter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-emitter
Source: https://github.com/ForgePlan/marketplace/tree/main/plugins/forgeplan-map-pack/skills/map-emitter
Command: npx skills add https://github.com/ForgePlan/marketplace --skill map-emitter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The map-emitter Skill automates the assembly and validation of the map.json file for forgeplan-map-pack's EMIT stage, ensuring accurate and reliable map data generation.

Core Features & Use Cases

  • Document-assembly: Assemble meta, canvas, composition, zones, nodes, and edges from input data.
  • Invariant Guard: Implements pre-write checks to ensure no zone-cell overlap and every edge endpoint is in nodes.
  • Atomic Write: Ensures a safe and atomic tmp-rename write of the map.json document.
  • Use Case: This Skill is used by the map-emitter agent to generate a map.json file that represents the structure of a project within the forgeplan-map-pack.

Quick Start

Execute the map-emitter Skill with the following command: map-emitter -i .forgeplan/map/.work/.extract.json .forgeplan/map/.work/.edges.json

Frequently Asked Questions about map-emitter

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

FAQPage Schema
How do I automate map.json assembly and validation for a project structure?

Map.json assembly is automated by processing extracted document data to compile meta, canvas, zones, nodes, and edges. The map-emitter Skill executes this generation algorithmically, using input files to output the final validated map structure.

How do I validate zone-cell overlap and edge endpoints when generating a map document?

Validating zone-cell overlap and edge endpoints requires pre-write invariant checks. The map-emitter Skill performs these invariant guards to verify no zone-cell overlap exists and every edge endpoint is registered in nodes before writing the file.

What are the input requirements for map.json document generation?

Input requirements for map.json document generation include proper extracted document data files. You must provide inputs like .extract.json and .edges.json so the algorithmic processing can assemble the project structure without manual intervention.

Can I ensure atomic file writing when generating a map.json document?

Atomic file writing for map.json is achieved through a safe tmp-rename mechanism. The map-emitter Skill ensures this atomic write process to prevent corruption, writing the map document only after all invariant checks pass.

Does map generation work without manual intervention?

Map generation works entirely without manual intervention if proper input files are provided. The map-emitter Skill executes the EMIT stage autonomously, performing structural validation against RFC-023 and ADR-016 standards before atomically writing the output.

Why does map.json validation fail on missing node zone existence?

Map.json validation fails on missing node zone existence because invariant checks require strict structural integrity. The map-emitter Skill enforces node zone existence as a pre-write guard, rejecting any document where nodes reference non-existent zones.