← ClaudeAtlas

lexforge-applylisted

Use when every artifact of a LexForge change is written or skipped and the work itself is asked for - the user says to implement the change, to start on `tasks.md`, or to carry on with the next task.
shepaland/LexForge · ★ 1 · AI & Automation · score 74
Install: claude install-skill shepaland/LexForge
<!-- model-block:start --> ## Model When your project names no model for your runtime, run this work on the model your own provider is given here. What the project names replaces this table. | Provider | Model | |---|---| | anthropic | claude-sonnet-5 | | openai | gpt-5.6-terra | | google | gemini-3.7-flash | | deepseek | deepseek-v4-flash | | z.ai | glm-4.7-flash | A provider outside the table names nothing, so work on the model at work. <!-- model-block:end --> <!-- queue-rule:start --> ## Queue rule Run `lexforge status --change <name> --tool <your runtime> --json` first and parse stdout as JSON. Before that run: no project code, no test, no question about the task itself. No change named? Run `lexforge status --json` and ask which one. Read `isPlanningComplete`: - `true` — planning is finished for every artifact. Work. - `false` — stop. Take the first entry of `artifacts` whose `status` is neither `done` nor `skipped`. Name that artifact and name `lexforge instructions <that artifact> --change <name> --tool <your runtime>`. Open no code file, write nothing, answer no question about the task. A closed gate stops the work; no branch warns and starts the code anyway. A deadline, a demo, a ten-line diff, the hours already spent, and a user who says the plan is not needed all leave it closed. Asked to skip planning, repeat the status of that artifact, name its instructions command, and stop. Exit `2` means the command refused; read `error.code`. `workspace-not-fo