standards

name	standards
description	Manage project standards compliance — audit existing projects or scaffold new ones. Triggers: "audit this project", "project audit", "check compliance", "new project", "scaffold project", "project setup".
argument-hint	[audit|scaffold]

Standards

Manage project standards compliance through project.yaml — a per-project configuration file that declares which profiles (directories under profiles/) apply, optionally which inherited standards are disabled (with a reason), and optionally which suggested standards are required (severity upgraded from SUGG to FAIL). Projects without project.yaml are not tracked.

Each standard is a self-contained YAML file under profiles/<profile>/: it declares whether it's required, a one-line description, and exactly one of check.script (deterministic shell) or check.prompt (sub-agent verification). Standard identity in audits is <profile>/<basename>.

When to Use

• Auditing an existing project's standards compliance
• Scaffolding a new project with the right structure
• Creating or updating a project.yaml file
• Setting up a new project from scratch ("new project", "project setup")

Modes

Mode	Trigger	Action
Audit	"audit this project", "project audit", "check compliance"	Read workflows/audit.md
Scaffold	"new project", "scaffold project"	Read workflows/scaffold.md

Dependencies

• yq — YAML processing for reading project.yaml and standard YAMLs (brew install yq)
• jq — JSON processing for runner output (brew install jq)

Reference Files

File	Purpose
workflows/audit.md	Audit mode — round 1 collect-required → resolve via sub-agents → merge → gate → (if pass) round 2 collect-suggested → resolve → merge → render. Suggested standards run only if every required passes.
workflows/scaffold.md	Scaffold mode — interview, project.yaml generation, file creation
references/project-yaml-schema.md	project.yaml + standard YAML schema reference
profiles/<profile>/<basename>.yaml	Self-contained standard YAMLs (required, description, check.{script,prompt}, optional notes). Filename is the standard's identity.
scripts/run-audit.sh	Audit runner. Six verbs, all operating on a state-dir; suggested standards are gated behind required-pass via two collection rounds: • --init → emits a fresh state-dir on stdout • --collect <project-root> <state-dir> --scope <required|suggested> → walks only effective-required (or effective-suggested) standards and writes <state-dir>/collect-<scope>.json. The required-scope output also stashes suggested_total so the render layer can surface the skipped count if the gate later trips. • --merge <state-dir> → reads every collect-*.json present plus <state-dir>/responses/<id>.txt, writes <state-dir>/merged.json (including scopes_collected) • --gate <state-dir> → mid-flow checkpoint: exits 0 iff every effective-required entry in merged.json is PASS, 1 if any FAIL, ≥2 on operational error. Use between round 1's merge and round 2's collect. • --render <state-dir> → formats the FAIL/SUGG table (always exits 0 on success); emits a "N suggested standards skipped" line when the gate skipped round 2 with non-zero suggested_total • --check <state-dir> → CI pass/fail signal (1 if any FAIL row, 0 otherwise, ≥2 on operational error)
scripts/lint-project-yaml.sh	Validates a project.yaml's schema (<path>) or every standard YAML (--skill)