project-standard-audit

Big Emotion Project Standard Audit

Read-only audit of the project defined in this repo. Produces a scored, evidence-based report and refreshes docs/PRODUCTION-READINESS-AUDIT.md.

This skill never modifies source, never bumps versions, never tags, never pushes, never deploys, never writes to external services. It only reads, runs the repo's own gates, and writes the audit doc. Fixing anything it finds is deferred to normal ticketed work or /project-standard-release.

Footprint disclosure: the full audit runs npm ci (refreshes node_modules from the lockfile), npm test, and npm run check:templates — none of which touch tracked files. The only tracked-file change the audit produces is docs/PRODUCTION-READINESS-AUDIT.md (the docs/ directory is created on first run).

When to Activate

• User asks: "is the plugin production-ready", "is it ready to ship", "audit project-standard", "score the project".
• User asks specifically about security posture, template coherence, or overall score.
• User invokes /project-standard-audit.

Preconditions

Run from the repo root (package.json with "name": "@big-emotion/agent-atelier" — the scoped npm name). If not, stop and tell the user to cd into the repo.

Inputs

Optional argument: --quick — skip the long/costly gates (test suite, template checker via a fresh npm ci). Rely instead on the most recent CI run (gh run list --workflow ci.yml) and the newest local artifacts, and mark any domain scored from stale data as such.

Default: full audit.

Workflow

Step 1 — Snapshot the repo state

Run in parallel via Bash:

• git status --porcelain — a dirty tree is auditable but must be reported.
• git log --oneline -15 — recent cadence.
• git tag --sort=-creatordate | head -5 — no tags yet is expected pre-launch; say so explicitly.
• jq '{name, version, private, packageManager, scripts}' package.json — version, scripts, package manager.
• ls .github/workflows/ — workflow surface.
• ls plugins/project-standard/skills/setup/templates/ plugins/project-standard/skills/setup/references/ — the product's structural map (this repo has no docs/ until the first audit writes it).