plainlang/plain-forge

***plain spec writing tool

55Stars on the repository
35Mods indexed here, across every type
yesterdayLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

init-config-file

25

plainlang/plain-forge

Skill Claude CodeCodex

Build / finalize the config.yaml file(s) that the codeplain renderer consumes. Pulls together every decision made during Phase 3 of forge-plain (script paths, template directory, build folders, copy/dest behavior, log settings) and emits one canonical config.yaml per part of the project. Run this at the end of…

not rated 55 yesterday A 127 tokens original MIT

init-plain-project

26

plainlang/plain-forge

Skill Claude CodeCodex

Lightweight initializer for a new plain project. Asks about the base technology and project kind, asks whether conformance testing is enabled, then scaffolds a template import module (with base implementation reqs and test reqs), a stub top-level module, the unit testing script, and (optionally) the conformance and…

not rated 55 yesterday A 114 tokens original MIT

plainlang/plain-forge

Skill Claude CodeCodex

Loads the full codeplain CLI reference into context: the render command and its positional plain-file argument, every flag (render control, config, folders, test-script wiring, output copying, API, logging, headless mode), path-resolution rules, the CODEPLAINAPIKEY environment variable, the config.yaml mapping, and…

not rated 55 yesterday A 128 tokens original MIT

plainlang/plain-forge

Skill Claude CodeCodex

Loads the applicable plain authoring rules and operational references for the current task. Covers section ownership, concepts, modules, resources, integrations, rendering, testing, and codeplain CLI behavior without loading unrelated guidance. Use when authoring, editing, reviewing, or debugging .plain files, or…

not rated 55 yesterday A 75 tokens original MIT

plain-healthcheck

29

plainlang/plain-forge

Skill Claude CodeCodex

Verification gate for a plain project. Verifies that every config.yaml exists, points at scripts that actually live in testscripts/, and that codeplain .plain --dry-run passes for every top module in the project. Run this whenever anything in the project is finalized — including (but not limited to) the end of…

not rated 55 yesterday A 131 tokens original MIT

refactor-module

30

plainlang/plain-forge

Skill Claude CodeCodex

Split a large plain module into smaller modules grouped by logical domain. The resulting modules are connected via a requires chain so that functionality is 100% preserved. Use when a module has grown too large and its functional specs span multiple distinct concerns that would be clearer as separate modules.

not rated 55 yesterday A 60 tokens original MIT

plainlang/plain-forge

Skill Claude CodeCodex

Route every fact in a .plain bullet, section, or file to the section that owns it — splitting a bullet that carries several kinds of fact, and moving a misplaced one to where the renderer will read it. Use when a bullet answers more than one of what it is / what it does / how it is built / how it is tested, when a…

not rated 55 yesterday A 128 tokens original MIT

plainlang/plain-forge

Skill Claude CodeCodex

Resolve a conflict between two functional specs in a plain spec file. Use when conformance tests for a previously passing spec start failing after a new spec is rendered, or when a potential conflict is detected while adding a new functional spec (via add-functional-spec or add-functional-specs).

not rated 55 yesterday A 65 tokens original MIT

run-codeplain

33

plainlang/plain-forge

Skill Claude CodeCodex

Launch a codeplain render and supervise it end-to-end. Tails the log file, watches generated code appear under plainmodules/, and inspects the live TUI/process. Detects pathologies (stuck conformance loops, complexity errors, missing concepts, render failures), and — with user approval — stops the renderer, hands off…

not rated 55 yesterday A 111 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: