archlang-brief-to-plan
Use when the user gives a written brief for a new floor plan (rooms, areas, how rooms connect, a plot size) and wants the drawing, e.g. "design a two-bedroom flat of about 75 m²" or "lay out a small office with four rooms". Writes an ArchLang .arch file from the brief, checks it against the brief with the archlang CLI, and finishes it as a sheet. Not for changing an existing plan (archlang-edit-plan) or for exporting one (archlang-export).
How do I install this agent skill?
npx skills add https://github.com/chanmeng666/archlang --skill archlang-brief-to-planIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill automates the creation of architectural floor plans using the archlang CLI. It involves executing shell commands and downloading a specific NPM package. The primary security consideration is the handling of user-provided briefs, which could potentially contain malicious instructions.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Brief to plan
Turn a written brief into a checked .arch floor plan. Every step is a CLI call; never judge the
plan from the SVG markup.
If archlang is not on the path, write npx -y @chanmeng666/archlang in its place.
Never run a bare arch: on Linux, macOS and Git Bash that name is the coreutils command.
This skill is a workflow, not a language reference. The language is whatever archlang spec prints.
Scope
- Run the
archlangCLI commands below and no other program. - Write one new plan file,
plan.archhere or the name the user gives, in the user's working directory, plus the drawings the CLI renders beside it. If a file of that name already exists, ask the user before replacing it. - The user's explicit instructions take priority over these steps.
Steps
- Read the language. Run
archlang specand read all of it before writing a line. For one command's flags and examples runarchlang <cmd> --help, for examplearchlang finish --help. - List what the brief asks for. Write down each room, each stated area, each stated connection ("opens off the hall"), each stated window, and any outer size. Keep numbers exactly as the brief states them. If two requirements cannot both hold, stop and tell the user which ones; do not quietly change a number.
- Write
plan.arch. Give every room anid, alabeland auses. Attach doors and windows to walls and place furniture by anchor, asarchlang specshows, instead of computing coordinates. Give every room a door or an opening. - Compile.
archlang compile plan.arch -o plan.svg --json. Ifokis false, read eachdiagnostics[].fix. Preview the mechanical fixes witharchlang fix plan.arch --dry-run --json, then apply them witharchlang fix plan.arch. Fix the rest by hand and compile again. - Check the plan against your list.
archlang describe plan.arch --select rooms,doors,windows,totals --json. Compare room count, labels, each area, what each door connects and which rooms have windows with the list from step 2. Edit and repeat from step 4 until they match.area_m2is measured on wall centrelines;net_area_m2is the floor no wall stands on. - Check soundness.
archlang lint plan.arch --json. Fix each warning, or keep it on purpose and say why. If a room cannot be reached or a bedroom has no window,archlang suggest plan.arch --jsonreturns door and window statements you can paste. - Finish the drawing.
archlang finish plan.arch --dry-run --jsonshows the furniture and sheet statements it would add;archlang finish plan.archapplies them. Readunresolved: it names each room left empty and each statement left out, with the reason. - Gate and show.
archlang validate plan.arch --strict --jsonmust exit0, or you must be able to name each remaining warning as deliberate. Thenarchlang preview plan.arch -o plan.pngto show the user.
Report to the user
- The file you wrote and the drawing you rendered.
- Every requirement of the brief the plan does not meet, or "none".
- Which area you quote:
net_area_m2is the floor no wall stands on,area_m2the larger centreline figure. If a room has nonet_area_m2, say its net area could not be computed. - Every lint warning still present, with the reason it stays.
When something goes wrong
- Exit code
2is a fault in the source. Read the diagnostic and fix it; do not run the same command again unchanged.3is a wrong flag: runarchlang <cmd> --help. - For an unfamiliar code, run
archlang explain <CODE> --json. - To gate on the brief as data instead of by eye, write it as an intent file and run
archlang validate plan.arch --intent intent.json --feedback --json. The archlang-review-plan skill covers this.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/chanmeng666/archlang/archlang-brief-to-plan">View archlang-brief-to-plan on skillZs</a>