メニュー
Consolidated view of the add-pro ecosystem - commands, skills, relationships and dependencies. Loaded by /add as source of truth.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Source of truth for ADD doc rules, depth floors, IDs, refs, validation gate. Load before any doc write.
Use when running agent-judged QA validation (read-PNG by default; the playwright plugin adds live driving) — the Level C judge rubric, severity taxonomy, dual-judge (@ux-agent review ∥ @qa-agent) method, report schema/template, and the config.json/screens.json formats. Consumed by /add.qa and both judges.
Use when a state-materializing command starts or is asked to upgrade — reads the setup receipt, compares the recorded contract against the shipped one, executes the declared upgrade deltas sequentially, and rewrites the receipt even on a verified-current no-op. Consumed by /add.qa-setup STEP 1.5 and STEP 11.
Internal skill for developing ADD framework artefacts (commands, skills, agents, scripts). Use when add-framework--plan analyzes viability of new framework features, when add-framework--build implements framework artefacts, or when creating/modifying commands, skills, or agents. Always use this skill before proposing or implementing changes to the framework itself.
Use when building, styling, or theming UI components, pages, layouts, dashboards, charts, tables, or forms for SaaS products.
Generate a code-free QA/E2E specification (reachability intent, UX acceptance criteria, functional E2E scenarios, capture states, target viewports, a11y expectations) from about.md + design.md + plan-*.md, and author the _tests/screens.json screen catalog by read-merge-write. Loaded by add.plan's qa-pipeline QA-Spec step.
| name | code-addiction-ecosystem |
| description | Consolidated view of the add-pro ecosystem - commands, skills, relationships and dependencies. Loaded by /add as source of truth. |
add-skill-creator.add-resource-path-convention.| Command | Purpose | Skills Loaded |
|---|---|---|
| add | Intelligent gateway - answers questions, guides flows, suggests next command | add-ecosystem, add-dev-environment-setup |
| add.audit | Complete technical analysis of project (security, architecture, data, docs). Escalates to add-investigation on ambiguous findings | add-doc-schemas, add-health-check, add-ecosystem, add-investigation |
| add.autopilot | Autonomous Feature Coordinator | add-backend-development, add-database-development, add-frontend-development, add-ux-design, add-tasks-checklist |
| add.brainstorm | Explore ideas (READ-ONLY) | add-doc-schemas, add-ecosystem |
| add.build | Development Execution Specialist. STEP 1.5 create-or-checkout of the feature branch via build-setup.sh (F[NNNN] + --worktree args). QA-Fix mode (/add.build qa) when qa-pipeline feature enabled | add-backend-development, add-database-development, add-frontend-development, add-ux-design, add-code-review, add-ecosystem, add-id-convention, add-tasks-checklist |
| add.design | Thin dispatcher for the UX design contract — @ux-flow-agent → @ux-layout-agent → @ux-agent (critique), then coordinator consolidation into design.md. Manual entry point to the same pipeline add.plan 8.1 runs automatically; epic-aware (writes to the subfeature dir) | add-ux-design, add-doc-schemas, add-id-convention |
| add.diagnose | Pre-decision investigative triage for ambiguous symptoms. Applies 5-phase methodology in agent-dispatched mode: parallel @feature-history-agent ∥ @git-history-agent, then sequential @architecture-agent. Recommends route (hotfix/feature/extend/no-action). READ-ONLY | add-investigation, add-ecosystem |
| add.done | Finalize feature, generate changelog. Validates epics + requirements. Detects branch protection and routes to PR or direct merge | add-ecosystem, add-id-convention |
| add.hotfix | Urgent fix with global ID ([NNNN]H). Discovery via parallel @feature-history-agent ∥ @git-history-agent before code investigation. Creates isolated doc in docs/features/[NNNN]H-*, documents relationships in related.md. Escalates to add-investigation when root cause not obvious | add-ux-design, add-ecosystem, add-investigation, add-id-convention |
| add.init | Project onboarding - 3 questions (name, level, language), flat owner.md, optional product.md | add-product-discovery |
| add.new | Feature discovery, creates about.md (records branch: frontmatter — branch created later by add.build) | add-feature-discovery, add-feature-specification, add-doc-schemas, add-ecosystem, add-id-convention |
| add.plan | Technical Planning Orchestrator. OWNS the design contract: gated STEP 8.1 UX pipeline (@ux-flow-agent → @ux-layout-agent → @ux-agent critique → consolidated design.md, provenance-hash idempotency). QA-Spec subagent (STEP 10.0) when qa-pipeline feature enabled | add-backend-development, add-database-development, add-frontend-development, add-ux-design, add-feature-discovery, add-ecosystem, add-id-convention, add-tasks-checklist, add-qa-spec (qa-pipeline) |
| add.pull-request | Create or update PR for current branch (idempotent). On feature branches, generates the permanent feature changelog before opening the PR | add-commit, add-doc-schemas, add-id-convention |
| add.qa | Agent-judged QA validation — runs persisted specs + reads PNGs (live-drives with the playwright plugin), validates UX (vs design.md) AND functional delivery (vs about.md), writes versioned _tests/run-NNN/qa-validation-NNN.md (audit, not a gate). Dispatches a dual judge per SF in parallel — @ux-agent (review) for the judgement axes ∥ @qa-agent for functional + deterministic conformance + ALL a11y + failure forensics; the coordinator reconciles coverage and merges. Plugin optional (degrades to read-PNG) | add-qa (default), add-doc-schemas |
| add.qa-setup | End-to-end-verified QA bootstrap — installs the @playwright/test runner (mandatory) + chromium + Playwright MCP (optional, confirm-then-execute), generates a project-specific qa-project skill, scaffolds docs/qa/config.json + reachability-aware FEATURE_DIR/_tests/screens.json, migrates an existing QA flow on first run (--migrate, confirm-then-dogfood), reconciles the setup contract against the receipt (--upgrade), and ends with a /add.qa smoke test + bounded correction loop. Base command (runs before the plugin is enabled) | add-dev-environment-setup, add-doc-schemas, add-qa-migration, add-setup-contract, add-subagent-driven-development |
| add.review | Feature Code Review Specialist | add-code-review, add-delivery-validation, add-backend-development, add-database-development, add-frontend-development, add-ux-design, add-security-audit, add-investigation |
| add.test | Automated test generation. Parallel subagents per area; reports coverage (informational). Dispatches @e2e-agent when qa-pipeline feature enabled | add-backend-development, add-frontend-development, add-ecosystem |
| add.ux | Quick UX - loads add-ux-design and applies to user's free-form instruction | add-ux-design |
| add.wiki | Map project architecture, classify apps, generate portable project wiki (.codeadd/wiki/) with hub, spine, and per-domain pages. /add.wiki update runs incremental maintenance | add-doc-schemas, add-architecture-discovery, add-claude-md-style, add-wiki-maintenance |
| Skill | Purpose |
|---|---|
| add-architecture-discovery | Map architecture, detect patterns, dispatch domain analyzers for the project wiki |
| add-backend-architecture | Backend architecture consultant: Simple Modular, Vertical Slice, Clean Architecture, Combined Strategy |
| add-backend-development | Backend architecture: SOLID, Clean Arch, DTOs, Services, Repository — stack-agnostic |
| add-claude-md-style | CLAUDE.md generation guide: content rules, format (JSON/markdown), line budget — load before any CLAUDE.md write |
| add-code-review | Code review: IoC, RESTful, Contracts, Security (OWASP), Clean Architecture, SOLID |
| add-commit | Knowledge reference for mid-workflow commits: adaptive message logic, type detection, staging rules |
| add-database-development | Data architecture: entities, repositories, migrations, naming — stack-agnostic |
| add-delivery-validation | Product validation: Requirements 100% implemented, prerequisites exist, acceptance criteria pass |
| add-dev-environment-setup | Detect OS, diagnose missing tools, install WSL/git/jq/gh, configure VS Code |
| add-doc-reviewer | Fresh-stakeholder review of a just-written ADD doc — surfaces gaps, clarity and scope questions, never reads the conversation that produced it |
| add-doc-schemas | Canonical schemas, stable IDs, universal doc rules, validation gate (incl. the setup-receipt schema) — single source of truth for all generated docs |
| add-ecosystem | Consolidated ecosystem view (source of truth) |
| add-feature-discovery | Feature discovery process, codebase analysis |
| add-feature-specification | about.md structure with requirements, rules, acceptance criteria |
| add-frontend-architecture | Frontend architecture consultant: Simple Component-Based, Feature-Based, FSD — React/Vue/Angular-aware |
| add-frontend-development | Frontend architecture: state, data fetching, components, forms, routing — stack-agnostic |
| add-gitnexus | [plugin-bound] Code knowledge-graph navigation via GitNexus MCP — call graph, refs, blast-radius, trace flows, safe refactors. Enabled by codeadd plugins enable gitnexus |
| add-health-check | Health check of environment and project dependencies |
| add-id-convention | Canonical [NNNN][L] ID and branch naming convention for features, hotfixes, refactors, chores, and docs — enforced by scripts (next-id.sh, get-branch-metadata.sh, build-setup.sh, done.sh) |
| add-investigation | Rigorous investigation methodology (5 phases with Iron Law) for vague symptoms and information-flow bugs. Adapted from systematic-debugging. Reusable by any command needing RCA before acting |
| add-knowledge-discovery | Consult the project wiki (and code knowledge graph) at the context/discovery step for minimal token cost — loaded by add.plan, add.hotfix, add.new, add.diagnose, add.review |
| add-optimizing-git-workflow | Git patterns, commits, branches, aliases |
| add-plan-based-features | Implement subscription plan-based features |
| add-planning | Technical planning orchestration |
| add-product-discovery | Product discovery (macro level) |
| add-project-scaffolding | Create projects from scratch: Starter/Scale, multi-stack Node.js, Starter-to-Scale migration |
| add-qa | QA methodology (default-shipped); the playwright plugin adds live browser driving — Level C judge rubric, severity taxonomy, dual-judge (@ux-agent review ∥ @qa-agent) axis ownership, root-cause taxonomy, report schema/template, config.json/screens.json formats. references/coordinator.md holds the coordinator-only merge rules + Fix Routing — loaded by /add.qa, never by a judge |
| add-qa-migration | Adopt the code-addiction QA pipeline in a project that already runs Cypress/Jest/Vitest/custom QA — autonomous dogfooding sequence (add.new → add.plan → add.build → add.review) and its checkpoints; consumed by /add.qa-setup |
| add-qa-spec | Generate a code-free QA/E2E spec (reachability intent, UX acceptance, functional scenarios, capture states, viewports, a11y expectations) from about.md + design.md + plan-*.md, and author the _tests/screens.json screen catalog by read-merge-write — loaded by add.plan's qa-pipeline QA-Spec step |
| add-resource-path-convention | Path convention for referencing commands/skills/scripts across providers |
| add-security-audit | OWASP checklist, RLS, secrets, multi-tenancy |
| add-setup-contract | Reconcile a project's materialized state with the shipped setup contract — compare recorded vs current, execute declared upgrade deltas sequentially, refuse on a chain hole |
| add-skill-creator | Create and test skills under real pressure |
| add-stripe | Stripe integration, price versioning, grandfathering |
| add-subagent-driven-development | Subagent coordination with quality gates |
| add-tasks-checklist | tasks.md schema: 5 sections, tick rules, [!] semantics, "non-trivial change" rule, architect prompt template — single source of truth |
| add-tdd | RED-GREEN-REFACTOR execution discipline: failing test confirmed for the right reason before code |
| add-test-specification | Generate contract test cases (RF/RN → testable cases) into plan-test-spec.md |
| add-token-efficiency | Compression, compact JSON, minimal tokens |
| add-ux-design | Components, mobile-first, SaaS patterns, shadcn, Tailwind |
| add-wiki-maintenance | Incremental project-wiki updates — diff-driven surgical edits, never full rewrites — loaded by /add.wiki update and add.done STEP 4.9 |
| Agent | Purpose | Dispatched by |
|---|---|---|
| ux-flow-agent | Flow & interaction architect — design-system inspection (tokens, shell, component audit, visual patterns) then screen inventory, action classification, entry points, state transitions. Writes temp design-context.md + design-flow.md; early-exits frontend_false | add.plan (8.1.1), add.design |
| ux-layout-agent | Layout & component specialist — layout tree + component composition + Design Contract per screen, new-component specs, states, every classified action served by a UI element. Writes temp design-layout.md (needs design-flow.md) | add.plan (8.1.2), add.design |
| ux-agent | UX design owner (three modes) — critique mode: adversarial review of the flow/layout pair vs the Critique Rubric in add-ux-design (writes temp design-review.md); review mode: post-delivery judgement of shipped screens vs the ## Design Contract (judgement axes + spec-gap); fix mode: amends design.md's Design Contract + Design Review on a routed design-spec finding (the ONLY mode that writes, and the only agent permitted to write design.md); free-form UX assistance on direct use. No memory | add.plan (critique), add.design, add.qa (review, ∥ qa-agent), add.build qa (routed design-spec fixes) |
| backend-agent | Backend implementation specialist | add.build, add.autopilot |
| frontend-agent | Frontend implementation specialist | add.build, add.autopilot |
| reviewer-agent | Code review (read-only) | add.review |
| discovery-agent | Feature discovery and specification (read-only) | add.new |
| architecture-agent | Architecture consultant, layer/module advice (read-only) | add.plan, add.diagnose (Fase B), add.hotfix |
| system-design-agent | System design, data flows, infrastructure | add.plan, add.audit |
| database-agent | Schema design, migrations, queries | add.build, add.plan |
| doc-reviewer-agent | Fresh-context doc review (read-only) | add.new, add.brainstorm |
| feature-history-agent | Scans docs/features/ for symptom-relevant features (read-only, docs only) | add.diagnose (Fase A.1), add.hotfix |
| git-history-agent | Correlates recent git history with a symptom (read-only git) | add.diagnose (Fase A.2), add.hotfix |
| qa-agent | Deterministic + forensic QA judge (the qa-agent half of the dual panel) — functional delivery vs about.md, deterministic Design Contract conformance from measured computed styles, ALL a11y (axe-core), and root-caused failure forensics; judges from persisted run evidence (read-PNG), live-drives with the playwright plugin. No memory | add.qa (per SF, parallel, ∥ ux-agent review) |
| e2e-agent | Cross-cutting E2E spec author — authors <surface>.qa.spec (functional assertions + multi-viewport capture + axe a11y), finalizes screens.json reachability recipe, green-confirms via @playwright/test (no MCP, test files only) | add.test (qa-pipeline feature), add.build qa (routed selector-drift / spec-defect / coverage fixes) |
| Feature | Default | Injects into | Purpose |
|---|---|---|---|
| tdd | enabled | add.plan, add.build, add.review | RED-GREEN-REFACTOR discipline + contract-test specs |
| qa-pipeline | disabled | add.plan, add.test, add.build | E2E spec authoring + agent QA validation |
Enable/disable via codeadd features enable|disable|list <name> — fragments are injected into the installed commands post-install. qa-pipeline (feature) governs whether QA artefacts are authored; the playwright plugin below only adds live driving to the judge — enabling the plugin does not enable the pipeline (canonical statement in add-qa).
| Plugin | Type | Description | Injects into | Plugin skill |
|---|---|---|---|---|
| gitnexus | mcp | Code knowledge-graph navigation (calls, refs, blast-radius) via MCP | add.new, add.diagnose, add.hotfix, add.done | add-gitnexus |
| playwright | mcp | Adds live browser driving (screenshots + console/network) to the already-present QA validation via Playwright MCP | add.qa (command), qa-agent (agent) | — (add-qa is now default) |
Enable/disable via codeadd plugins enable|disable|list <name>. Plugins are disabled by default and require the external tool to be installed.
| If you modify... | It impacts... |
|---|---|
| add-backend-development | add.build, add.autopilot, add.plan, add.review, add.test |
| add-frontend-development | add.build, add.autopilot, add.plan, add.review, add.test |
| add-database-development | add.build, add.autopilot, add.plan, add.review, add.test |
| add-ux-design | add.design, add.ux, add.build, add.autopilot, add.review, add.hotfix, add.plan; the three UX agents (ux-flow-agent, ux-layout-agent, ux-agent) declare it as a skill — its critique-rubric.md is the critic's canonical rubric and design-contract.md the layout/contract notation |
| add-code-review | add.review, add.build |
| add-security-audit | add.audit, add.review |
| add-setup-contract | add.qa-setup (STEP 1.5 reconciliation + STEP 11 receipt rewrite) |
| add-qa-migration | add.qa-setup (STEP 5, first-run migration + --migrate) |
| add-subagent-driven-development | add.qa-setup (STEP 9 dispatch template, reused by migration + correction dispatch) |
| add-doc-reviewer | add.new, add.brainstorm (via doc-reviewer-agent) |
| add-feature-discovery | add.new, add.plan |
| add-feature-specification | add.new |
| add-doc-schemas | add.new, add.design, add.brainstorm, add.audit, add.plan, add.build, add.autopilot, add.hotfix, add.done, add.pull-request, add.init, add.wiki, add.diagnose |
| add-architecture-discovery | add.audit, add.wiki |
| add-ecosystem | add (loses full view), all commands that route to next steps |
| add-wiki-maintenance | add.wiki (update mode), add.done (STEP 4.9) |
| add-knowledge-discovery | add.plan, add.hotfix, add.new, add.diagnose, add.review |
| add-investigation | add.diagnose (primary, agent-dispatched mode), add.hotfix (STEP 6.1 escalation, agent-dispatched mode), add.review (STEP 5.1 ambiguous findings), add.audit (STEP 7.1 ambiguous findings) |
| feature-history-agent | add.diagnose (STEP 4 Fase A.1), add.hotfix (STEP 4) |
| git-history-agent | add.diagnose (STEP 4 Fase A.2), add.hotfix (STEP 4) |
| qa-agent | add.qa (dispatched per SF, parallel with ux-agent review) |
| e2e-agent | add.test (dispatched when qa-pipeline feature enabled), add.build qa (routed test-file fixes) |
| ux-flow-agent | add.plan (STEP 8.1.1), add.design (STEP 3) — and everything downstream of design.md: add.plan 8.4 frontend, add.qa UX axis, add-qa-spec |
| ux-layout-agent | add.plan (STEP 8.1.2), add.design (STEP 4) — depends on ux-flow-agent's design-flow.md |
| ux-agent | add.plan (STEP 8.1.3 critique), add.design (STEP 5), add.qa (STEP 4.5 review mode, ∥ qa-agent), add.build qa (fix mode — routed design-spec amendments), free-form direct use |
| add-qa-spec | add.plan (STEP 10.0, qa-pipeline feature) — owns plan-qa-spec.md AND _tests/screens.json authoring |
| add-feature-specification (about.md) | add.qa (functional axis reads acceptance criteria — QA quality is bounded by spec quality) |
| add-ux-design (design.md) | add.qa (@ux-agent review judges the judgement axes vs the ## Design Contract; @qa-agent checks deterministic conformance vs the computed-style rows) |
| playwright (plugin) | add.qa (drive), qa-agent (drive) — enhancement/live arm; add.qa runs without it (read-PNG) |
| add-id-convention | add.plan, add.design, add.build, add.hotfix, add.done, add.pull-request (all ID allocation and branch naming; SF-qualified design IDs cover the feature-design doc type from add-doc-schemas' references/new-feature.md; add.build's build-setup.sh enforces the format at branch creation) |
| add-tasks-checklist | add.plan, add.build, add.autopilot (tasks.md schema and tick rules) |
| add-tdd | add.plan, add.build, add.review, add.test |
| add-test-specification | add.plan (STEP 9) |
| Flow | Sequence | When to use |
|---|---|---|
| Complete | brainstorm → new → design → plan → build → review → done | Complex features with UI |
| QA-validated | new → plan → build → test → qa ⇄ build qa → review → done | UI features with the qa-pipeline feature on. QA loops until clean; review runs LAST so it judges the tree the fix waves produced |
| Standard | new → plan → build → review → done | Features without complex UI |
| Lean | new → build → done | Small changes, quick tasks |
| Autonomous | new → autopilot → done | Want zero-interaction implementation |
| Emergency | hotfix → done | Critical production bug |
| Exploration | brainstorm → new → ... | Don't know where to start |
| Triage | diagnose → (hotfix OR new OR no-action) | Vague symptom, unsure if bug/feature |
| New Project | init → build → done | Create new project/feature |
| Analysis | wiki / audit | Check project health |
Branch creation: the documental steps (brainstorm → new → design → plan) make no git writes —
/add.newonly records the branch name inabout.md(branch:). The branch is created at the build (or autopilot) step viabuild-setup.sh.
Conditions evaluated top-to-bottom — use FIRST match.
| After | Condition | Suggest | Why |
|---|---|---|---|
| add.init | always | /add.new | Onboarding done, start first feature |
| add.brainstorm | idea ready to formalize | /add.new | Capture as feature |
| add.brainstorm | needs more exploration | continue brainstorm | Not ready to commit |
| add.brainstorm | bug suspected, needs investigation | /add.diagnose | Structured triage needed |
| add.brainstorm | clear bug discovered | /add.hotfix | Urgent fix needed |
| add.diagnose | route=hotfix | /add.hotfix | Confirmed bug requiring urgent fix |
| add.diagnose | route=feature | /add.new | Confirmed functional gap |
| add.diagnose | route=extend | /add.new or /add.plan | Extend existing feature — load prior context |
| add.diagnose | route=no-action | done | No real problem — stop here |
| add.new | feature has complex UI (3+ screens) | /add.design | Produce the UX contract up front. Optional now — /add.plan STEP 8.1 runs the same pipeline automatically whenever a screen is involved; route here when the user wants the design settled before planning, or wants to regenerate it standalone |
| add.new | feature needs technical planning | /add.plan | Architect before building |
| add.new | feature is simple (1-2 files) | /add.build | Skip planning, build directly |
| add.new | user wants zero interaction | /add.autopilot | Autonomous end-to-end |
| add.design | always | /add.plan or /add.build | UX spec done, plan or implement |
| add.plan | default | /add.build | Most common path |
| add.plan | user wants zero interaction | /add.autopilot | Autonomous implementation |
| add.build | mode=QA-FIX (/add.build qa) | /add.qa | Re-run the audit — writes the next run-NNN for side-by-side comparison. Loop until clean, THEN /add.review |
| add.build | mode=DEVELOPMENT, wants tests | /add.test | Validate with automated tests |
| add.build | mode=DEVELOPMENT, skip tests | /add.review | Code review before merge |
| add.build | mode=CORRECTION | /add.review | Re-validate after fixes |
| add.build | epic, more subfeatures pending | /add.build feature N | Next subfeature in epic |
| add.autopilot | always | /add.done | Autopilot includes review; finalize |
| add.test | tests passing, feature has UI (design.md resolved) | /add.qa | Validate the rendered result BEFORE code review — the QA fix wave writes code, so review must judge the post-fix tree |
| add.test | tests passing | /add.review | Validate code quality |
| add.test | tests failing | fix + /add.test | Iterate until green |
| add.review | status=PASSED, has UI, no _tests/run-*/ for the scope | /add.qa | The rendered result was never validated (review reached directly, e.g. tests skipped) — run the QA loop, then return here |
| add.review | status=PASSED | /add.done | All gates green, finalize |
| add.review | status=BLOCKED | fix + /add.review | Iterate until PASSED |
| add.hotfix | always | /add.done | Hotfix ready, finalize branch |
| add.review | needs team review before merge | /add.pull-request | PR for human review |
| add.pull-request | PR open, awaiting review | wait for review | Human review pending |
| add.pull-request | PR merged on GitHub | /add.done | Cleanup local branch + tags |
| add.pull-request | scope grew, need to update PR | /add.pull-request | Idempotent — appends update section |
| add.done | was feature, back on main | /add.new | Start next feature |
| add.done | was epic, more subfeatures | /add.build feature N | Next subfeature |
| add.done | was hotfix | /add.new | Return to feature work |
| add.ux | within active feature | return to current flow | UX applied, resume workflow |
| add.ux | standalone | done | One-off UX task |
| add.wiki | issues found | /add.audit | Deep health check |
| add.wiki | context mapped, ready to build | /add.new | Start building with context |
| add.wiki | standalone analysis | done | Analysis delivered |
| add.audit | critical issues found | /add.new per issue | Create features to fix findings |
| add.qa-setup | prereqs + config ready | /add.qa | Validate the rendered result (UX + functional) — optionally codeadd plugins enable playwright first for live driving |
| add.qa | findings present | /add.build qa | Audit is non-blocking — the report's ## Fix Routing table routes each finding to the responsible agent; /add.build qa dispatches by route, then re-run /add.qa |
| add.qa | clean (no findings) | /add.review | QA audit clean — code review is the LAST gate, so it judges the tree the QA fix waves produced |
| add.audit | project healthy | done | No action needed |