Annuaire des skills Business AnalyseBusiness Analysis skills directory

business-analyse 32

• /ba-audit-actors Audits the actors of a `.smartstack/ba/` project — existence, duplicate names (case-insensitive), missing type (ACT-001, ACT-002, ACT-006 — ACT-003..005 retired).
• /ba-audit-cross-dimension Cross-dimension coherence audit of one `.smartstack/ba/` module — verifies that data-model fields with state semantics have matching business rules, use cases and screens, that use-case actors exist in RBAC, that screen entity refs resolve, that a kanban is a view of its list and not its own section, that transition-captured attributes are not asked at creation, that a dated child can be born, and that a 360 related tab onto a ≥ confidentiel entity (lib/ba-sensitivity) carries its backticked permission AND its list target — the « first 4 attributes » fallback is the leak (XD-001..009).
• /ba-audit-cross-ref-code Cross-references the BA data model of a module against the EXISTING project code — detects entities that extend an existing class, reference a Core/existing entity as FK, duplicate one, collide with the SmartStack Core catalogue, re-implement a platform capability (file storage, search, …), or model a PERSON without the auth_Users extension link (CODE-007, err — fail-closed mirror of C-4/DM-018c), and — ownership at the APPLICATION grain (2026-10-03) — reads WHO owns a homonymous class (own module ok, same application other module err, another application warn → reuse) and whether the columns asked of another application are carried by `<APP>/demande-extension.md` (CODE-008, err; pending/refused request = development frozen, warn) — and, data sensitivity at the entity grain (lib/ba-sensitivity), whether REACHING a ≥ confidentiel entity of another application (cross-module FK, 360 tab, 4-segment permission) is carried by an ACCESS request in the same document (CODE-009, err; pending/refused = frozen, warn) (CODE-001..009).
• /ba-audit-data-model Audits the conceptual data model (MCD) of a `.smartstack/ba/` module — attributes, FK integrity, cycles, naming, orphans, traceability, indexes, implicit FKs, unreferenced lookups, classification conventions, code-pattern numbering, Core-entity duplication, platform-capability steering, no file content in the MCD, derived declarations, and code-like classification — near-miss Code-pattern declarations + unclassified synonym attributes (Référence/Numéro/Matricule…) — plus, moved LEFT of the readiness GO: index integrity (every **Index** column exists, never TenantId in a unique — the scaffolder's own error, six phases earlier), complete attribute types (string maxLength, decimal precision/scale, enum values), no framework field listed, tenancy declared (**Portée** → tenantMode), and the model retaining what the BA no longer uses — dead columns (attribute grain) and leftover state values (value grain), and the business TEST DATASET `jeu-de-test.md` — present where the module carries business entities, coherent with the MCD, the rules, the actors and the cited modules' datasets, never on a reference table, every Flow status represented — and, since 2026-10-03, the DEFINITION CARTOUCHE of every entity (**Description** everywhere, **Périmètre** on business entities, **Hors périmètre** optional — DM-033), the cross-APPLICATION equivalence of entity definitions (DM-034, hybrid: candidates by name, by definition, by shared attributes or by the same Core artefact, settled mechanically when a Hors périmètre names the other side, judged otherwise), the intra-application duplicate — one declaring module per application (DM-035, err) — and the DATA SENSITIVITY at the entity grain (lib/ba-sensitivity): the `**Sensibilité**` declaration due where a name or attribute looks sensitive + its near-miss (DM-036), the split doctrine — a sensitive attribute inside an interne entity is a split, never a column tag; `public` on a person / sensitive entity is an err (DM-037), and the public API never carrying a restreint entity nor a confidentiel one without the client's dated decision (DM-038) (DM-001..038).
• /ba-audit-menu Audits the menu (Application / Module) of a `.smartstack/ba/` project — module semantics, cross-app duplicates, SmartStack Core collisions, orphans/empty, out-of-scope coherence, hierarchy code distinctness (MENU-001..008).
• /ba-audit-prd Audits the on-disk PRD of ONE module in a `.smartstack/ba/` project — checks across 7 dimensions: structure, completeness, clarity, consistency, traceability, feasibility, slices + per-page contract + custom-action contract + related-tabs contract (PRD-103..105 + PRD-108 route families, the 360 view) + the file-upload guard (PRD-107 — no `type:file` custom action; attachments pattern instead) + list elegance (PRD-109 column visibility budget, PRD-110 filter tiers) + form/detail sections (PRD-111 well-formed `sections[]`, PRD-112 grouping authored where warranted) + view-set completeness (PRD-114 a mutable list declares its form/detail siblings) + cards representation folding (PRD-117 viewModes on the list pagespec, never a standalone SmartCard pagespec) + quick segments (PRD-116 cohort tabs: labelled, defaulted, wirable) + sort/density/empty-state coherence (PRD-118) + detail summary integrity (PRD-119) + form lifecycle (PRD-120 well-formed status-anchored `lifecycle` block — CLI `create-prd/cli/derive-lifecycle --mode check`; PRD-121 lifecycle authored where the entity lives one) + action-permission binding (PRD-128 — a kind:api action's permission roots at its OWN module.section, section grain; engine = derive-action-specs' blocking rejected[]) + business-rule links (PRD-129 every enforceable rule linked / PRD-130 cited codes resolve — CLI `create-prd/cli/derive-rule-links --mode check`) + use-case coverage (PRD-131 every user-goal UC reaches the pagespecs — CLI `create-screen/cli/derive-uc-coverage`) + coded-entity parity (PRD-132 entité.md `**Code pattern**` ⇔ pagespec `codedEntity` flag both ways — facets `label`/`supplied` included, unusable line = err, unparsable near-miss declaration (table cell / wrong casing) = err, supplied+{SEQ} = warn — CLI `ba-develop/cli/derive-code-specs --mode check`) + tab budget (PRD-133 — rendered strip ≤ 7 warn / ≤ 9 err, band cartouches excluded, unified fiche honoured; same derive-related-tabs run, RTV-108) + summary demanded (PRD-134 — ≥ 4 rendered strip triggers and no `summary` = warn, CLI `create-prd/cli/derive-detail-summary --mode check`) + kanban representation (PRD-135 — the `kanban` block folded on the LIST pagespec: columns ⊆ status enum verbatim, BR Flow ⇄ transitions parity both ways, viewModes coherence, no standalone kanban pagespec, labels seeded — CLI `create-prd/cli/derive-kanban-spec --mode check`).
• /ba-audit-pre-dev Pre-development readiness orchestrator for a `.smartstack/ba/` project.
• /ba-audit-rbac Audits the RBAC permission matrix of a `.smartstack/ba/` module — minimum permissions, segregation of duties, actor coverage, reference integrity, data-scope coherence, derived-lookup freshness, permission-floor mirror freshness, unmaterialized `team`/`custom` Portées said out loud, and — data sensitivity at the entity grain (lib/ba-sensitivity) — the need-to-know on a section bound to a ≥ confidentiel entity (a use case names the actor, or a dated décision client on the row; an external actor on restreint is an err — RBAC-011) and the derived lookup grants a sensitive producer holds for a HUMAN row (RBAC-012) (RBAC-001..012).
• /ba-audit-rules Audits the business rules of a `.smartstack/ba/` module — completeness, conflicts, redundancy, example quality, entity/UC references, per-ruleType edge-case coverage, and — at app/project scope only — cross-application similarity (warn) (BR-001..012).
• /ba-audit-run ONE deterministic pass over the whole `.smartstack/ba/` corpus — the audit-ba CLI loads every doc once, runs the ~134 MECHANICAL audit rules of all 11 dimensions (menu, sections, actors, use-cases, rules, rbac, data-model, screens, cross-dimension, cross-ref-code, sources), publishes the parse totals, writes every `_audit/<dim>.md` verdict and `_audit/audit-ba.json`, and FAILS CLOSED on parser/control divergence (exit 3 « parsing suspect »). [APP[/MODULE]] [--strict] [--project-root <dir>]
• /ba-audit-screens Audits the screen specs of a `.smartstack/ba/` section — coverage, entity refs, SmartComponent coherence, navigation integrity, related-tabs (360 view), home-page hierarchy, UC traceability, custom-actions structure, coded-entity code fields, attachment screens bound to a metadata entity, list column/filter inflation, form field grouping (Section/Onglet), create-form phase discipline, mandatory SmartSectionHome on multi-resource sections, observable action results, dashboard/entity binding, instance-verb confirmation, use-case coverage — every user-goal UC served by a surface, and the shared tab-bar budget — inner + related tabs ≤ 7/9, band cartouches excluded (SCR-001..025).
• /ba-audit-sections Audits the menu sections of a `.smartstack/ba/` project — module-section coverage, duplicate/ambiguous sections, sibling state-variant sections (same primary subject), cross-module and cross-app duplication (SEC-001..008 — SEC-006 retired, XAPP-001..003).
• /ba-audit-sources Audits the client-sources registry (`.smartstack/sources/`, SIBLING root of the BA tree) and the `SRC-NNN §n` citations the BA specs carry — registry coherence, source completeness, web-extract contract, citation resolution, scope coverage, dead and superseded sources (SRC-001..007, all mechanical, fail-closed: « no citation » is only acceptable when no in-scope source exists).
• /ba-audit-use-cases Audits the use cases of a `.smartstack/ba/` module — completeness, step quality, vague language, scope respect, actor references, redundancy, acceptance-criteria contract, exception ↔ AC parity, and — at app/project scope only — cross-application similarity (warn) (UC-001..023).
• /ba-change Change request on a FINISHED business-analysis scope — add or modify ONE element after the fact (a use case, a business rule, an actor, a permission row, an entity attribute, an entity, a screen) without re-running a whole phase. [<APP>/<MODULE>[/<section>]] [--kind use-case|business-rule|actor|permission|attribute|entity|screen] [--modify <CODE>]
• /ba-create-actors Phase 2 of business analysis.
• /ba-create-ba-order After Phase 1 (menu), produces a BA creation order plan — a topologically-sorted ordering of modules showing which modules to work on first across all BA phases (actors → use cases → rules → RBAC → data model → screens). [APP1] [APP2] …
• /ba-create-business-rules Phase 4 of business analysis.
• /ba-create-data-model Phase 6 of business analysis.
• /ba-create-menu Phase 1 of business analysis.
• /ba-create-plan-development Generates a phased development plan ordering modules by their cross-module data-model dependencies. <APP1> [APP2] …
• /ba-create-prd Synthesises the upstream BA `.md` tree of ONE module (menu, actors, use cases, business rules, RBAC, data model, screens) into a Product Requirements Document on disk: `prd.md` (product framing: context, goals, non-goals, MoSCoW, technical constraints), three phase slices, per-screen `pagespecs/*.md` (each carrying a machine spec block), and `claude.md`.
• /ba-create-rbac Phase 5 of business analysis.
• /ba-create-screen Phase 7 of business analysis (the LAST BA phase).
• /ba-create-sources Ingests the CLIENT-PROVIDED source material of a project (cahiers des charges, PDF, Word/Excel, notes, emails, screenshots — and RETAINED web findings) into the committed registry `.smartstack/sources/`: each source gets a stable greppable code `SRC-NNN`, judgment tags, a precise summary and §-anchored extracts, so every BA phase can pull exactly what it needs and CITE it (`- **Sources** : SRC-001 §2`) in the written spec.
• /ba-create-test-data Phase 6.5 of business analysis (OPTIONAL, after the data model).
• /ba-create-use-case Phase 3 of business analysis.
• /ba-loop Autonomous BA pipeline orchestrator. [APP1] [APP2] … [--from-phase N] [--module APP/MODULE]
• /ba-modeling-detail Pass 2 of the optional Two-Pass fast-modeling path.
• /ba-modeling-inventory Pass 1 of the optional Two-Pass fast-modeling path.
• /ba-reconcile-menu Reconciles the `.smartstack/ba/` menu tree (sections/modules currently in `index.md`) against the codes embedded in downstream documents (`use-case.md`, `screen.md`, `règles-métier.md`, `rbac.md`). [--dry-run] [--app APPCODE]
• /ba-translate-prd Backfills the i18n translations of an already-written PRD.