***plain spec writing tool
This repository also configures its own agents. See what plain-forge tells them →
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…
Skill Claude CodeCodex
Loads the applicable plain authoring rules and operational references for the current task. Covers section ownership, concepts, modules, resources, integrations, rendering, and testing without loading unrelated guidance. Use when authoring, editing, reviewing, or debugging .plain files, or before invoking another…
Skill Claude CodeCodex
Verification gate for a plain project. Verifies that every config.yaml exists and points at scripts that actually live in testscripts/, parses every top module with plain-parser check, and checks every module for what the parser can't judge (section ownership, bullets, linked resources). Run this whenever anything in…
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.
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…
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).
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: