# _workflow — shared references for the BA skills (repo-only)

This folder holds the **shared conventions** the `business-analyse/` skills are
written against. It is NOT deployed: the installer skips `_workflow/` (and any
`CLAUDE.md` index) because Claude Code only registers skills that are direct
children of the skills root. Each `ba-*` skill **inlines** what it needs from
these files, so it is self-contained at runtime — these docs are the source of
truth used when authoring/maintaining the skills.

## The model in one line

There is no Studio, no database, no `[ACTION]`/`[QUESTION]` blocks, no injected
`--- CURRENT X ---` state. **The `.smartstack/ba/` markdown tree IS the state.**
Skills read it (Read/Glob/Grep), ask closed choices with **AskUserQuestion**, and
persist by **writing `.md` files** with the Write tool.

## Files here

| File | Role |
|------|------|
| `ba-files.md` | The file model: `.smartstack/ba/` layout, the Application→Module→Section→Resource tree, the six docs per node, the authority matrix (one authoritative level per concept, rollups are one-line pointers), `<!-- ba:* -->` anchors, read-as-state + Write-overwrites semantics. |
| `doc-templates.md` | Canonical markdown skeletons for every doc (`index`, `acteur`, `use-case`, `règles-métier`, `rbac`, `entité`, `screen`) + the rollup variant + the `_audit/<dimension>.md` verdict shape. The single parse target shared by authors, audits and `create-prd`. |
| `communication.md` | Cross-phase communication rules + ACK shape + safety (use your tools; talk like a business analyst, not a tool). |
| `proposal-method.md` | Canonical client-proposal method: mandatory domain research → internal draft → self-audit → presentation in 3 tiers (Obligatoire / Suggestion / Élargissement). Tier table drift-locked to `lib/proposal-tiers.ts` across create-menu, create-use-case, create-business-rules, create-screen. |
| `code-discipline.md` | Verbatim copy rule + the identifier universe + the 7 historical code drifts. Source of truth = the files (Grep), not memory. |
| `context-documents.md` | How to use user-provided reference docs (read them with the Read tool). |
| `completeAuto-discipline.md` | Anti-hallucination guard for "complete (auto)" coverage runs — every proposal needs a verbatim trace in the tree. |
| `detail-cadence.md` | Cadence of the SECOND pass of the two-pass phases (use cases, business rules): `Pas à pas` / `Par lot` (default) / `Enchaîné` — pinned once by the user at the entry of the pass, derived worklist, ONE write per batch, arbitrations published. Table drift-locked to `lib/detail-cadence.ts` across create-use-case (detail) and create-business-rules (elaborate). |

## Phase order (fixed)

`menu → actors → use cases → rules → RBAC → data model → screens`, then
`/ba-create-prd` → `/ba-audit-pre-dev` (GO) → `/ba-develop`.
Each per-dimension `/ba-audit-*` reads the tree and writes a `_audit/<dim>.md`
verdict; the definer does a light self-check before writing and hands off to the
next phase.