forge▌

Structured requirements workshops that produce EARS-format specifications, user stories, acceptance criteria, and implementation checklists. \n \n Conducts systematic discovery interviews from both product and engineering perspectives, using structured questioning to elicit requirements before writing specifications \n Outputs comprehensive specifications including functional requirements in EARS format, non-functional requirements, Given/When/Then acceptance criteria, error handling tables, and

Build and manage Claude Code plugins with correct structure, manifests, and marketplace integration. Includes workflows, automation scripts, and reference docs.

Typically runs automatically via SessionEnd hook.

IRON LAW: Every line in a skill must justify its token cost. If it doesn't make the model's output better, more consistent, or more reliable — cut it.

Forge is a full-stack Rust framework. Everything compiles into a single binary backed by PostgreSQL. There is no separate API server, job runner, or cron scheduler -- one binary does it all.

IRON LAW: Every line in a skill must justify its token cost. If it doesn't make the model's output better, more consistent, or more reliable — cut it.

Scaffold, structure, and manage Claude Code plugins with automated manifest generation and version control. \n \n Includes Python scripts for creating plugins and bumping semantic versions across both plugin.json and marketplace.json manifests \n Supports four component types: commands (with namespace-based naming), skills, agents, and hooks, each with defined directory structures \n Provides three plugin patterns (framework, utility, domain) with reference documentation covering structure, mark