@kudusov.takhir/ba-toolkit 3.10.1 → 3.10.4

package/CHANGELOG.md

@@ -11,6 +11,49 @@ Versions follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
+## [3.10.4] — 2026-04-11
+
+### Changed
+
+- **Glossary links added to README, USAGE.md, and COMMANDS.md.** Abbreviation chains (`FR → US → UC → AC → ...`) now include a parenthetical link to the glossary so first-time readers can look up unfamiliar acronyms without leaving the page.
+- **Website sidebar reordered.** "Example project" and "Glossary" now appear immediately after "Getting started" — before the Documentation group — so new users find them early.
+
+---
+
+## [3.10.3] — 2026-04-11
+
+### Added
+
+- **`docs/GLOSSARY.md`** — plain-English glossary covering core concepts (artifact, slug, pipeline, skill, domain, traceability, subcommands), requirement types (FR, US, UC, AC, NFR, SRS, ADR, DAG), and standards (IEEE 830, MoSCoW, BABOK, INVEST, Cockburn, ISO 25010, ISO 31000, PMBOK 7, Michael Nygard ADR format). Synced to the documentation website.
+- **Prerequisites section in getting-started.md** — explains what Node.js is, how to check/install it, what npm/npx is, and what AI agents are with links to Claude Code, Cursor, Codex, Gemini, and Windsurf.
+- **Pipeline diagram in README** — ASCII visual showing the full pipeline flow, optional steps, utility skills sidebar, and lean vs full path distinction.
+- **8 new troubleshooting entries** for first-time users — `/brief` not responding, skill not found, `npx` not found, init fails on Windows, agent timeout, AGENTS.md not found, empty artifacts.
+- **Example project page on the website** — Lumen Goods artifact inventory with GitHub links and "What to look for" callouts (cross-references, traceability, domain-specific content, terminology consistency).
+- **"How to choose your domain" section in DOMAINS.md** — decision table mapping project types to the 13 available domains.
+- **4 beginner FAQ entries** — "Can I use BA Toolkit without technical skills?", "What happens if I skip a pipeline step?", "What if the AI generates something wrong?", "How long does the full pipeline take?"
+
+### Changed
+
+- **README opening rewritten.** Tagline and "What is this" section now lead with a value proposition accessible to both technical and non-technical users. Pointers to getting started guide, example project, and glossary added.
+- **Website landing page simplified.** New tagline, "Industry-standard rigour" card no longer lists raw standard names, "How it works" uses plain English instead of abbreviation chains, new "What does the output look like?" link card added.
+
+---
+
+## [3.10.2] — 2026-04-11
+
+### Changed
+
+- **Standardized "Utility skills" terminology across the project.** All 9 utility skills (`/trace`, `/clarify`, `/analyze`, `/estimate`, `/glossary`, `/risk`, `/sprint`, `/export`, `/publish`) now consistently use "Utility skill" as their opener and description label. Previously the codebase mixed "Cross-cutting command", "Cross-cutting utility", "Utility command", and "Cross-cutting Tools" — now unified under a single term that pairs naturally with "Pipeline skills". Updated in 9 SKILL.md files, `closing-message.md`, `agents-template.md`, `handoff-template.md`, `handoff/SKILL.md`, `publish/SKILL.md`, and `prerequisites.md`.
+- **README pipeline table split into two sections.** The single 24-row table is now two: a "Pipeline" table (15 numbered steps) and a "Utility skills" table (9 unnumbered skills) with an explanatory paragraph between them.
+
+### Added
+
+- **USAGE.md § 9 "Utility skills"** — new section with a mental-model paragraph, a quick-reference table (skill / purpose / when to use), a "When to use which" decision tree, and a note explaining how `/analyze` relates to `/clarify`, `/trace`, and `/glossary`.
+- **FAQ: 2 new entries** — "What is the difference between pipeline skills and utility skills?" and "When should I use /analyze vs /clarify vs /trace vs /glossary?"
+- **prerequisites.md: 6 new utility skill sections** — `/estimate`, `/glossary`, `/risk`, `/sprint`, `/export`, `/publish`. Previously only `/trace`, `/clarify`, and `/analyze` had prerequisite entries; now all 9 utility skills are covered. Existing entries relabeled from "(Cross-cutting)" to "(Utility)".
+
+---
+
 ## [3.10.1] — 2026-04-10
 
 ### Fixed
@@ -742,6 +785,9 @@ CI scripts that relied on the old behaviour (`init` creates files only, `install
 ---
 
 [Unreleased]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.10.1...HEAD
+[3.10.4]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.10.3...v3.10.4
+[3.10.3]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.10.2...v3.10.3
+[3.10.2]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.10.1...v3.10.2
 [3.10.1]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.10.0...v3.10.1
 [3.10.0]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.9.0...v3.10.0
 [3.9.0]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.8.1...v3.9.0

package/COMMANDS.md

@@ -1,6 +1,6 @@
 # BA Toolkit — Command Reference
 
-Quick reference for all 24 skills and subcommands.
+Quick reference for all 24 skills and subcommands. For term and acronym definitions (FR, US, AC, IEEE 830, etc.), see the [glossary](docs/GLOSSARY.md).
 
 ---
 

package/README.md

@@ -2,7 +2,7 @@
 
 # 📋 BA Toolkit
 
-Structured BA pipeline for AI coding agents — concept to a phase-and-DAG implementation plan, 24 skills, 12 domains, one-command Notion + Confluence publish.
+Turn a rough project idea into a complete, structured specification — then hand it to a developer or AI coding agent to build.
 
 <img src="https://img.shields.io/badge/skills-24-blue" alt="Skills">
 <img src="https://img.shields.io/badge/domains-12-green" alt="Domains">
@@ -22,12 +22,18 @@ Structured BA pipeline for AI coding agents — concept to a phase-and-DAG imple
 
 ## What is this
 
-BA Toolkit is a set of 24 interconnected skills that run a full business-analysis pipeline inside your AI coding agent. You can start as early as `/discovery` (a brain-storm step for users who don't yet know what to build) or jump straight to `/brief` if you already have a project in mind, then work all the way through to a development handoff package. Each skill reads the output of the previous ones — maintaining cross-references between artifacts along the chain `FR → US → UC → AC → NFR → Entity → ADR → API → WF → Scenario`. After `/handoff`, run `/implement-plan` to produce a phase-and-DAG implementation plan an AI coding agent (Claude Code, Cursor, Codex) can execute step by step — every task references the FR / US / AC it implements and carries its own Definition of Done. When you're ready to share with non-developer stakeholders, `/publish` (or `ba-toolkit publish`) bundles every artifact into import-ready folders for Notion and Confluence — drag-and-drop, no API tokens.
+BA Toolkit turns a rough project idea into a complete, structured specification — requirements, user stories, acceptance criteria, API contracts, wireframes, and a step-by-step implementation plan. It runs as **24 AI-powered skills** inside your coding agent (Claude Code, Cursor, Codex CLI, Gemini CLI, or Windsurf) and produces Markdown documents that are cross-referenced, traceable, and ready for development or stakeholder review.
 
-Unlike one-shot prompting, every artifact is written to disk as Markdown, every ID links back to its source, and `/trace` verifies coverage across the whole pipeline. `/clarify` and `/analyze` catch ambiguities and quality gaps with CRITICAL/HIGH severity ratings. Domain references for 12 industries (SaaS, Fintech, E-commerce, Healthcare, Logistics, On-demand, Social/Media, Real Estate, iGaming, EdTech, GovTech, AI/ML) plug in automatically at `/brief`.
+**How it works:** you type a slash command (e.g., `/brief`), the agent asks you a series of focused questions about your project, and generates a structured document. Each step builds on the previous ones — requirements link to user stories, stories link to acceptance criteria, and so on through the entire chain. After the last step, you have a complete specification package that a developer or AI coding agent can execute.
+
+**For non-developer stakeholders:** `/publish` bundles every document into import-ready folders for Notion and Confluence — drag-and-drop, no API tokens, no network calls.
+
+**Quality built in:** `/trace` verifies that every requirement is covered end-to-end. `/clarify` and `/analyze` catch ambiguities and quality gaps before they become expensive rework. Domain references for 12 industries (SaaS, Fintech, E-commerce, Healthcare, Logistics, On-demand, Social/Media, Real Estate, iGaming, EdTech, GovTech, AI/ML) add industry-specific questions and terminology automatically.
 
 Artifacts are generated in whatever language you write in — ask in English, get English docs; ask in any other language, the output follows.
 
+> **New to BA Toolkit?** Start with the [getting started guide](https://takhirkudusov.github.io/ba-toolkit/getting-started/) or browse a [complete example project](https://takhirkudusov.github.io/ba-toolkit/example/). For acronyms and standards referenced in the artifacts, see the [glossary](docs/GLOSSARY.md).
+
 ---
 
 ## Install
@@ -173,7 +179,7 @@ A complete example project — **Lumen Goods** (sustainable home-goods D2C onlin
 | Risk Register | [`00_risks_lumen-goods.md`](example/lumen-goods/00_risks_lumen-goods.md) |
 | Sprint Plan | [`00_sprint_lumen-goods.md`](example/lumen-goods/00_sprint_lumen-goods.md) |
 
-Full traceability: FR → US → UC → AC → NFR → Entity → ADR → API → WF → Scenario, plus risk register and sprint plan.
+Full traceability: FR → US → UC → AC → NFR → Entity → ADR → API → WF → Scenario, plus risk register and sprint plan. (See [glossary](docs/GLOSSARY.md) for acronym definitions.)
 
 ---
 
@@ -196,15 +202,22 @@ Full traceability: FR → US → UC → AC → NFR → Entity → ADR → API
 | 10 | `/scenarios` | End-to-end Validation Scenarios — user journeys linking US, AC, WF, API | `10_scenarios_{slug}.md` |
 | 11 | `/handoff` | Development Handoff Package — artifact inventory, MVP scope, open items | `11_handoff_{slug}.md` |
 | 12 | `/implement-plan` | Implementation Plan for AI coding agents — phase ladder + Task DAG, every task references the FR/US/AC it implements | `12_implplan_{slug}.md` |
-| — | `/trace` | Traceability Matrix + coverage gaps | `00_trace_{slug}.md` |
-| — | `/clarify [focus]` | Targeted ambiguity resolution for any artifact | _(updates existing artifact)_ |
-| — | `/analyze` | Cross-artifact quality report with severity table | `00_analyze_{slug}.md` |
-| — | `/estimate` | Effort estimation — Fibonacci SP, T-shirt sizes, or person-days | `00_estimate_{slug}.md` |
-| — | `/glossary` | Unified project glossary with terminology drift detection | `00_glossary_{slug}.md` |
-| — | `/export [format]` | Export User Stories to Jira / GitHub Issues / Linear / CSV | `export_{slug}_{format}.json` / `.csv` |
-| — | `/publish [format]` | Bundle artifacts for Notion (Markdown) and Confluence (HTML) — drag-and-drop import, no API tokens | `publish/notion/`, `publish/confluence/` |
-| — | `/risk` | Risk register — probability × impact matrix, mitigation per risk | `00_risks_{slug}.md` |
-| — | `/sprint` | Sprint plan — stories grouped by velocity and capacity with sprint goals | `00_sprint_{slug}.md` |
+
+### Utility skills
+
+Available at any pipeline stage, not tied to a fixed position. Use them to verify, estimate, publish, or export artifacts whenever needed. Start with `/analyze` for a broad quality sweep, then deep-dive with `/clarify`, `/trace`, or `/glossary` for specific concerns.
+
+| Command | What it generates | Output file |
+|---------|-------------------|-------------|
+| `/trace` | Traceability Matrix + coverage gaps | `00_trace_{slug}.md` |
+| `/clarify [focus]` | Targeted ambiguity resolution for any artifact | _(updates existing artifact)_ |
+| `/analyze` | Cross-artifact quality report with severity table | `00_analyze_{slug}.md` |
+| `/estimate` | Effort estimation — Fibonacci SP, T-shirt sizes, or person-days | `00_estimate_{slug}.md` |
+| `/glossary` | Unified project glossary with terminology drift detection | `00_glossary_{slug}.md` |
+| `/risk` | Risk register — probability × impact matrix, mitigation per risk | `00_risks_{slug}.md` |
+| `/sprint` | Sprint plan — stories grouped by velocity and capacity with sprint goals | `00_sprint_{slug}.md` |
+| `/export [format]` | Export User Stories to Jira / GitHub Issues / Linear / CSV | `export_{slug}_{format}.json` / `.csv` |
+| `/publish [format]` | Bundle artifacts for Notion (Markdown) and Confluence (HTML) — drag-and-drop import, no API tokens | `publish/notion/`, `publish/confluence/` |
 
 The project **slug** (e.g., `nova-analytics`) is set at `ba-toolkit init` (derived from the project name) and reused across all files automatically — every skill reads it from `AGENTS.md`.
 
@@ -253,11 +266,62 @@ Adding a new domain = creating one Markdown file in `skills/references/domains/`
 
 ---
 
+## Pipeline at a glance
+
+```
+  ┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
+  │ /discovery  │────▶│   /brief    │────▶│    /srs     │────▶│  /stories   │
+  │  (optional) │     │  Goals &    │     │ Requirements│     │ User Stories│
+  └─────────────┘     │ Stakeholders│     │  (IEEE 830) │     │  by Epic    │
+                      └─────────────┘     └─────────────┘     └──────┬──────┘
+                                                                     │
+                 ┌───────────────────────────────────────────────────┘
+                 │
+                 ▼
+  ┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
+  │  /usecases  │────▶│    /ac      │────▶│    /nfr     │────▶│  /datadict  │
+  │  (optional) │     │ Acceptance  │     │ Performance,│     │  Entities & │
+  │             │     │  Criteria   │     │  Security…  │     │   Fields    │
+  └─────────────┘     └─────────────┘     └─────────────┘     └──────┬──────┘
+                                                                     │
+                 ┌───────────────────────────────────────────────────┘
+                 │
+                 ▼
+  ┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
+  │  /research  │────▶│/apicontract │────▶│ /wireframes │────▶│ /scenarios  │
+  │  (optional) │     │  Endpoints  │     │   Screens   │     │  (optional) │
+  │  Tech ADRs  │     │ & Schemas   │     │ & Navigation│     │  E2E Flows  │
+  └─────────────┘     └─────────────┘     └─────────────┘     └──────┬──────┘
+                                                                     │
+                 ┌───────────────────────────────────────────────────┘
+                 │
+                 ▼
+  ┌─────────────┐     ┌─────────────┐
+  │  /handoff   │────▶│/implement-  │     ╔═══════════════════════════════╗
+  │  Dev-ready  │     │   plan      │     ║  UTILITY SKILLS (any stage)  ║
+  │  Package    │     │ Task DAG    │     ║                               ║
+  └─────────────┘     │ for AI Agent│     ║  /trace    — coverage matrix  ║
+                      └─────────────┘     ║  /clarify  — fix ambiguities  ║
+                                          ║  /analyze  — quality report   ║
+                                          ║  /estimate — story points     ║
+                                          ║  /glossary — term consistency ║
+                                          ║  /risk     — risk register    ║
+                                          ║  /sprint   — sprint plan      ║
+                                          ║  /export   — Jira/GitHub/CSV  ║
+                                          ║  /publish  — Notion/Confluence║
+                                          ╚═══════════════════════════════╝
+```
+
+**Lean path** (~3–4 hours): skip the steps marked "(optional)" and go straight from `/brief` to `/implement-plan`.
+**Full path** (~5–8 hours): run every step for maximum coverage and traceability.
+
+---
+
 ## How it works
 
 Most pipeline skills follow the same cycle: **Command → Context → Interview → Generate → Refine**. Each skill loads all previous artifacts plus the domain reference and project principles, asks a few rounds of targeted questions, writes a Markdown artifact, and offers refinement subcommands before moving on. `/handoff`, `/trace`, and `/analyze` skip the interview — they extract everything from existing artifacts automatically.
 
-Every artifact links back to its predecessors, forming the chain `FR → US → UC → AC → NFR → Entity → ADR → API → WF → Scenario`. Run `/trace` to verify coverage and `/analyze` for severity-rated findings (duplicates, ambiguous terms, terminology drift, invalid references).
+Every artifact links back to its predecessors, forming the chain `FR → US → UC → AC → NFR → Entity → ADR → API → WF → Scenario` (see [glossary](docs/GLOSSARY.md) for definitions). Run `/trace` to verify coverage and `/analyze` for severity-rated findings (duplicates, ambiguous terms, terminology drift, invalid references).
 
 ### Subcommands
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kudusov.takhir/ba-toolkit",
-  "version": "3.10.1",
+  "version": "3.10.4",
   "description": "AI-powered Business Analyst pipeline — 24 skills from concept discovery to a sequenced implementation plan an AI coding agent can execute, with one-command Notion + Confluence publish. Works with Claude Code, Codex CLI, Gemini CLI, Cursor, and Windsurf.",
   "keywords": [
     "business-analyst",

package/skills/analyze/SKILL.md

@@ -6,7 +6,7 @@ description: >
 
 # /analyze — Cross-Artifact Quality Analysis
 
-Cross-cutting command. Performs a read-only analysis across all existing pipeline artifacts and generates a structured finding report. Does not modify artifacts — use `/clarify` or `/revise` to act on findings.
+Utility skill. Performs a read-only analysis across all existing pipeline artifacts and generates a structured finding report. Does not modify artifacts — use `/clarify` or `/revise` to act on findings.
 
 ## Context loading
 

package/skills/clarify/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: clarify
 description: >
-  Targeted ambiguity-resolution pass over a BA Toolkit artifact. Use on /clarify command, or when the user asks to "clarify requirements", "find ambiguities", "what is unclear", "check vague terms", "resolve ambiguities", "what needs clarification". Can be focused on a specific area: /clarify security, /clarify FR-012. Cross-cutting command available at any pipeline stage after the first artifact exists.
+  Targeted ambiguity-resolution pass over a BA Toolkit artifact. Use on /clarify command, or when the user asks to "clarify requirements", "find ambiguities", "what is unclear", "check vague terms", "resolve ambiguities", "what needs clarification". Can be focused on a specific area: /clarify security, /clarify FR-012. Utility skill available at any pipeline stage after the first artifact exists.
 ---
 
 # /clarify — Targeted Ambiguity Resolution
 
-Cross-cutting command. Performs a post-generation scan of the target artifact, surfaces specific ambiguities as questions, collects answers from the user, and updates the artifact.
+Utility skill. Performs a post-generation scan of the target artifact, surfaces specific ambiguities as questions, collects answers from the user, and updates the artifact.
 
 ## Syntax
 

package/skills/estimate/SKILL.md

@@ -6,7 +6,7 @@ description: >
 
 # /estimate — Effort Estimation
 
-Analyses User Stories, assigns effort estimates using the chosen scale, and produces an estimation table with rationale. Can update the stories artifact in-place or output a standalone estimation report.
+Utility skill. Analyses User Stories, assigns effort estimates using the chosen scale, and produces an estimation table with rationale. Can update the stories artifact in-place or output a standalone estimation report.
 
 ## Syntax
 

package/skills/export/SKILL.md

@@ -6,7 +6,7 @@ description: >
 
 # /export — Artifact Export
 
-Converts User Stories (and optionally Acceptance Criteria) into structured output files ready for import into issue trackers and project management tools.
+Utility skill. Converts User Stories (and optionally Acceptance Criteria) into structured output files ready for import into issue trackers and project management tools.
 
 ## Syntax
 

package/skills/glossary/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: glossary
 description: >
-  Unified project glossary extraction and maintenance for BA Toolkit projects. Use on /glossary command, or when the user asks to "build a glossary", "extract terms", "create a glossary", "consolidate terminology", "find terminology drift", "what terms are defined". Cross-cutting command — can run at any pipeline stage once at least one artifact exists.
+  Unified project glossary extraction and maintenance for BA Toolkit projects. Use on /glossary command, or when the user asks to "build a glossary", "extract terms", "create a glossary", "consolidate terminology", "find terminology drift", "what terms are defined". Utility skill — can run at any pipeline stage once at least one artifact exists.
 ---
 
 # /glossary — Unified Project Glossary
 
-Cross-cutting command. Scans all existing artifacts and the domain reference file, extracts defined and used terms, detects terminology drift (same concept, different names), and produces or updates a single `00_glossary_{slug}.md` file.
+Utility skill. Scans all existing artifacts and the domain reference file, extracts defined and used terms, detects terminology drift (same concept, different names), and produces or updates a single `00_glossary_{slug}.md` file.
 
 ## Syntax
 

package/skills/handoff/SKILL.md

@@ -59,7 +59,7 @@ No interview. All content is derived from the existing artifacts. The full templ
 | 11 | Handoff | `11_handoff_{slug}.md` | This document | — |
 | 12 | Implementation Plan | `12_implplan_{slug}.md` | ✓ / ✗ Missing / — Not run | {n} phases, {n} tasks |
 
-### Cross-cutting artifacts
+### Utility artifacts
 
 | Tool | File | Status | Key numbers |
 |------|------|--------|-------------|

package/skills/publish/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: publish
 description: >
-  Bundle BA Toolkit artifacts into import-ready files for documentation tools — Notion (markdown bundle) and Confluence (HTML bundle). Use on /publish command, or when the user asks to "export to Notion", "export to Confluence", "publish artifacts", "share with stakeholders", "import into Notion", "import into Confluence", "send the docs to product team". Cross-cutting utility — does not advance the pipeline.
+  Bundle BA Toolkit artifacts into import-ready files for documentation tools — Notion (markdown bundle) and Confluence (HTML bundle). Use on /publish command, or when the user asks to "export to Notion", "export to Confluence", "publish artifacts", "share with stakeholders", "import into Notion", "import into Confluence", "send the docs to product team". Utility skill — does not advance the pipeline.
 ---
 
 # /publish — Notion / Confluence Publish
 
-Cross-cutting utility skill. Wraps the `ba-toolkit publish` CLI subcommand, which converts the markdown artifacts in the current `output/<slug>/` folder into folders ready to be dragged into Notion's **Import → Markdown & CSV** dialog or zipped and uploaded via Confluence's **Space settings → Content tools → Import → HTML** tool.
+Utility skill. Wraps the `ba-toolkit publish` CLI subcommand, which converts the markdown artifacts in the current `output/<slug>/` folder into folders ready to be dragged into Notion's **Import → Markdown & CSV** dialog or zipped and uploaded via Confluence's **Space settings → Content tools → Import → HTML** tool.
 
 The conversion happens entirely on disk — **no API calls, no tokens, no network**. The user does the actual upload manually using each tool's native importer.
 
@@ -62,7 +62,7 @@ Capture stdout from the command and report it back to the user. The CLI prints a
 
 ### 5. Closing message
 
-Cross-cutting closing block (no `Next step:` line — see `references/closing-message.md` "Cross-cutting commands" section). Show:
+Utility skill closing block (no `Next step:` line — see `references/closing-message.md` "Utility skills" section). Show:
 
 - Saved bundle paths and counts per format (taken verbatim from the CLI's stdout summary).
 - The two static "Next steps" lines:

package/skills/references/closing-message.md

@@ -59,7 +59,7 @@ Skills use this table as the single source of truth for the `Next step:` block.
 | /handoff     | /implement-plan | Sequenced implementation plan for AI coding agents              | 10–20 min    | (pipeline complete — hand to Claude Code / Cursor)  |
 | /implement-plan | (none)       | Pipeline complete                                               | —            | Hand 12_implplan_<slug>.md to your AI coding agent  |
 
-## Cross-cutting commands (no Next step line)
+## Utility skills (no Next step line)
 
 These skills do not advance the pipeline — they update or report on existing artifacts. Their closing block omits the `Next step:` block entirely (omit it cleanly — don't write "Next step: none"):
 
@@ -79,7 +79,7 @@ Their closing block ends after the "Available commands" table. Optionally, they
 
 - `{file_path}` is the full path where the artifact was saved (typically `output/<slug>/{NN}_{name}_{slug}.md`).
 - The summary line is generated dynamically — do not repeat boilerplate; mention actual numbers and decisions ("18 FRs across 3 roles, 4 risks captured", not "the artifact was generated").
-- The "Available commands" table is fixed (5 rows for pipeline skills). Cross-cutting skills omit `/done` from the table since they don't have a "finalize" state.
+- The "Available commands" table is fixed (5 rows for pipeline skills). Utility skills omit `/done` from the table since they don't have a "finalize" state.
 - The "Next step" block is built from the lookup table above. Do not hardcode it in individual SKILL.md files.
 - The "If you're stuck" section is a 2–3-line nudge for users who don't know what to do next. Keep it short.
 - The block is a chat message, not part of the saved Markdown file.

package/skills/references/prerequisites.md

@@ -148,7 +148,7 @@ Prerequisites marked **Required** block execution — the skill should prompt th
 
 ---
 
-## /trace (Cross-cutting)
+## /trace (Utility)
 
 | Prerequisite | Status | Notes |
 |-------------|--------|-------|
@@ -158,7 +158,7 @@ Prerequisites marked **Required** block execution — the skill should prompt th
 
 ---
 
-## /clarify (Cross-cutting)
+## /clarify (Utility)
 
 | Prerequisite | Status | Notes |
 |-------------|--------|-------|
@@ -167,7 +167,7 @@ Prerequisites marked **Required** block execution — the skill should prompt th
 
 ---
 
-## /analyze (Cross-cutting)
+## /analyze (Utility)
 
 | Prerequisite | Status | Notes |
 |-------------|--------|-------|
@@ -176,6 +176,71 @@ Prerequisites marked **Required** block execution — the skill should prompt th
 
 ---
 
+## /estimate (Utility)
+
+| Prerequisite | Status | Notes |
+|-------------|--------|-------|
+| `03_stories_*.md` | **Required** | Primary input — stories to estimate |
+| `05_ac_*.md` | Recommended | AC scenario count is a key complexity signal |
+| `02_srs_*.md` | Recommended | Integration points and technical constraints affect estimates |
+| `07a_research_*.md` | Recommended | ADR-driven complexity signals |
+| `00_principles_*.md` | Optional | Estimation conventions |
+
+---
+
+## /glossary (Utility)
+
+| Prerequisite | Status | Notes |
+|-------------|--------|-------|
+| At least one pipeline artifact | **Required** | Needs terms to extract |
+| `00_principles_*.md` | Optional | Language and naming conventions |
+
+---
+
+## /risk (Utility)
+
+| Prerequisite | Status | Notes |
+|-------------|--------|-------|
+| `01_brief_*.md` | **Required** | Primary source of risks and constraints |
+| `02_srs_*.md` | Recommended | Assumptions, constraints, out-of-scope items |
+| `06_nfr_*.md` | Recommended | Aggressive NFR targets signal risk |
+| `07a_research_*.md` | Recommended | Technology risks, integration unknowns |
+| `08_apicontract_*.md` | Recommended | Third-party API dependencies, SLA gaps |
+| `00_principles_*.md` | Optional | |
+
+---
+
+## /sprint (Utility)
+
+| Prerequisite | Status | Notes |
+|-------------|--------|-------|
+| `00_estimate_*.md` or inline estimates in `03_stories_*.md` | **Required** | Sprint planning needs effort estimates |
+| `03_stories_*.md` | **Required** | Stories to assign to sprints |
+| `00_risks_*.md` | Recommended | Risk scores elevate priority of mitigating stories |
+| `02_srs_*.md` | Recommended | Sequencing constraints beyond explicit dependencies |
+| `00_principles_*.md` | Optional | Team capacity defaults |
+
+---
+
+## /export (Utility)
+
+| Prerequisite | Status | Notes |
+|-------------|--------|-------|
+| `03_stories_*.md` | **Required** | Stories to export |
+| `05_ac_*.md` | Recommended | AC scenarios embedded in issue descriptions |
+| `00_estimate_*.md` | Recommended | Story points included in the export if available |
+| `00_principles_*.md` | Optional | ID conventions, language settings |
+
+---
+
+## /publish (Utility)
+
+| Prerequisite | Status | Notes |
+|-------------|--------|-------|
+| At least one pipeline artifact (`01_brief_*.md` or later) | **Required** | Nothing to publish without artifacts |
+
+---
+
 ## Quick reference: minimum viable pipeline
 
 To reach a development-ready handoff with the smallest number of steps:

package/skills/references/templates/agents-template.md

@@ -32,9 +32,9 @@
 | 11 | /handoff | ⬜ Not started | — |
 | 12 | /implement-plan | ⬜ Not started | — |
 
-## Cross-cutting Tools
+## Utility Skills
 
-Utilities available throughout the pipeline. No fixed stage — invoke whenever they help. See README.md for the prerequisites of each.
+Available at any pipeline stage — no fixed position. Invoke whenever they help. See COMMANDS.md for descriptions and prerequisites.md for input requirements.
 
 | Tool | Purpose |
 |------|---------|

package/skills/references/templates/handoff-template.md

@@ -32,7 +32,7 @@
 | 11 | Handoff | `11_handoff_[SLUG].md` | This document | [DATE] |
 | 12 | Implementation Plan | `12_implplan_[SLUG].md` | ✅ Complete / — Not run | [DATE] |
 
-### Cross-cutting artifacts
+### Utility artifacts
 
 | Tool | File | Status | Last Updated |
 |------|------|--------|--------------|

package/skills/risk/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: risk
 description: >
-  Dedicated risk register for BA Toolkit projects. Use on /risk command, or when the user asks to "identify risks", "create a risk register", "assess project risks", "list risks", "risk matrix". Cross-cutting command — can run at any pipeline stage once Brief or SRS exists. Re-run after Research to capture technical risks.
+  Dedicated risk register for BA Toolkit projects. Use on /risk command, or when the user asks to "identify risks", "create a risk register", "assess project risks", "list risks", "risk matrix". Utility skill — can run at any pipeline stage once Brief or SRS exists. Re-run after Research to capture technical risks.
 ---
 
 # /risk — Risk Register
 
-Cross-cutting command. Extracts risks from existing artifacts, classifies them by category, scores them by probability × impact, and produces or updates `00_risks_{slug}.md` with a full risk register.
+Utility skill. Extracts risks from existing artifacts, classifies them by category, scores them by probability × impact, and produces or updates `00_risks_{slug}.md` with a full risk register.
 
 ## Syntax
 

package/skills/sprint/SKILL.md

@@ -6,7 +6,7 @@ description: >
 
 # /sprint — Sprint Plan
 
-Utility command. Reads estimated User Stories, applies team capacity and velocity constraints, groups stories into sprints by priority and risk weight, and produces `00_sprint_{slug}.md` with a complete sprint breakdown.
+Utility skill. Reads estimated User Stories, applies team capacity and velocity constraints, groups stories into sprints by priority and risk weight, and produces `00_sprint_{slug}.md` with a complete sprint breakdown.
 
 ## Syntax
 

package/skills/trace/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: trace
 description: >
-  Build and update the traceability matrix across all BA Toolkit pipeline artifacts: FR ↔ US ↔ UC ↔ AC ↔ NFR ↔ Data Entity ↔ API Endpoint ↔ Wireframe. Use on /trace command, or when the user asks for "traceability matrix", "requirements traceability", "coverage check", "uncovered requirements", "artifact links", "check coverage", "find missing requirements", "what is not covered". Cross-cutting command available at any stage after /stories.
+  Build and update the traceability matrix across all BA Toolkit pipeline artifacts: FR ↔ US ↔ UC ↔ AC ↔ NFR ↔ Data Entity ↔ API Endpoint ↔ Wireframe. Use on /trace command, or when the user asks for "traceability matrix", "requirements traceability", "coverage check", "uncovered requirements", "artifact links", "check coverage", "find missing requirements", "what is not covered". Utility skill available at any stage after /stories.
 ---
 
 # /trace — Traceability Matrix
 
-Cross-cutting command of the BA Toolkit pipeline. Available after `/stories` is complete. Builds a traceability matrix across all existing artifacts.
+Utility skill. Available after `/stories` is complete. Builds a traceability matrix across all existing artifacts.
 
 ## Context loading