@kudusov.takhir/ba-toolkit 3.12.0 → 3.13.1

package/CHANGELOG.md

@@ -11,6 +11,24 @@ Versions follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
+## [3.13.1] — 2026-04-11
+
+### Added
+
+- **3 skill-template regression tests.** Protect the post-v3.5.0 template discipline from drift: (1) 10 pipeline-stage templates must carry a "Forward traceability" section, (2) the `/nfr` template must have at least 7 ISO 25010 characteristic section headings, (3) the `/stories` template must carry an `**INVEST self-check:**` field. Test count: 188 → 191.
+
+---
+
+## [3.13.0] — 2026-04-11
+
+### Added
+
+- **`[parallel]` marker in `/implement-plan` task DAG.** Tasks that share the same prerequisites and do not depend on each other are now marked `[parallel]` in the title and `✓` in a new `parallel` column in the Task DAG appendix. The "How to use this plan" section instructs AI coding agents that `[parallel]` tasks can be executed concurrently. Inspired by Spec Kit's parallel execution markers.
+- **`/analyze` recommended as quality gate in closing messages.** The "If you're stuck" block in closing messages is replaced with a "Quality check before moving on" block that recommends `/analyze` for a cross-artifact quality sweep, especially after `/srs`, `/stories`, and before `/handoff`.
+- **Cascading artifact update added to ROADMAP.md.** New "Cascading artifact update" item in the Next section — a future `/cascade` utility skill (or `/revise` extension) to propagate requirement changes through downstream artifacts.
+
+---
+
 ## [3.12.0] — 2026-04-11
 
 ### Changed
@@ -829,6 +847,8 @@ 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.13.1]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.13.0...v3.13.1
+[3.13.0]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.12.0...v3.13.0
 [3.12.0]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.11.0...v3.12.0
 [3.11.0]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.10.6...v3.11.0
 [3.10.6]: https://github.com/TakhirKudusov/ba-toolkit/compare/v3.10.5...v3.10.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kudusov.takhir/ba-toolkit",
-  "version": "3.12.0",
+  "version": "3.13.1",
   "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/implement-plan/SKILL.md

@@ -106,6 +106,7 @@ Each task is one atomic, AI-actionable unit of work. Rules:
 - **id:** `T-<phase>-<seq>`, e.g. `T-04-007`. Phase number → first segment; sequence → second segment, zero-padded to 3 digits.
 - **title:** imperative, ≤ 10 words ("Create `users` table with email-unique constraint", "Implement `POST /auth/login` handler").
 - **dependsOn:** list of task ids that must complete first. Defaults to the previous task in the same phase, plus any explicit cross-phase prerequisites. Empty for the first task in Phase 1.
+- **parallel:** if this task has the same `dependsOn` as one or more sibling tasks (i.e., they share the same prerequisites and do not depend on each other), mark all of them with `**[parallel]**` next to the title. An AI coding agent can execute `[parallel]` tasks concurrently. Only mark tasks parallel when they are genuinely independent — touching different files, different entities, or different API endpoints with no shared state.
 - **references:** list of `FR-NNN`, `US-NNN`, `UC-NNN`, `AC-NNN-NN`, `NFR-NNN`, `Entity:Name`, `Endpoint: METHOD /path`, `WF-NNN`, `SC-NNN` ids that this task implements. **Always at least one.** Phase 1 tasks (Foundation) are the only exception and may reference `01_brief` or `00_principles` as their source.
 - **files:** list of file paths the AI agent should create or modify (best-effort; framework-dependent). Optional. Examples: `src/db/schema.sql`, `apps/api/src/auth/login.controller.ts`. **If unknown, omit rather than guess.**
 - **definitionOfDone:** bullet list of acceptance hooks. Pull from the linked AC where possible ("AC-001-03 passes", "endpoint returns 401 on invalid credentials"). Always include a type-check / lint hook on backend tasks and a render-state hook on UI tasks.
@@ -146,6 +147,7 @@ Within a phase, order tasks so each task's `dependsOn` list points only at tasks
 
 - Phases are ordered. Do not start phase N+1 until every task in phases 1..N is complete (or explicitly waived in writing).
 - Within a phase, follow task ids in ascending order unless `dependsOn` says otherwise.
+- Tasks marked **[parallel]** share the same prerequisites and do not depend on each other — they can be executed concurrently.
 - Every task has a `references` list — read those BA artifact sections before writing code.
 - Every task has a `definitionOfDone` — do not mark a task complete until every box is checked.
 - The Task DAG appendix is the machine-readable source of truth for dependencies.
@@ -233,12 +235,13 @@ Items the plan could not resolve from existing artifacts. The AI coding agent mu
 
 Machine-readable dependency graph. A topological sort of this table yields a valid execution order.
 
-| id | phase | title | dependsOn | references |
-|----|-------|-------|-----------|------------|
-| T-01-001 | 1 | {title} | — | {ids} |
-| T-01-002 | 1 | {title} | T-01-001 | {ids} |
-| T-02-001 | 2 | {title} | T-01-003 | Entity:User, FR-001 |
-| … | … | … | … | … |
+| id | phase | title | dependsOn | parallel | references |
+|----|-------|-------|-----------|----------|------------|
+| T-01-001 | 1 | {title} | — | — | {ids} |
+| T-01-002 | 1 | {title} | T-01-001 | ✓ | {ids} |
+| T-01-003 | 1 | {title} | T-01-001 | ✓ | {ids} |
+| T-02-001 | 2 | {title} | T-01-002, T-01-003 | — | Entity:User, FR-001 |
+| … | … | … | … | … | … |
 ```
 
 ### 8. AGENTS.md update

package/skills/references/closing-message.md

@@ -31,8 +31,9 @@ Next step: /{next_command}
   → Time estimate:    {min}–{max} minutes
   → After that:       /{step_after_next} ({one-line of what it does})
 
-If you're stuck on the next step:
-  - Run `/clarify` here first to surface ambiguities while context is fresh.
+Quality check before moving on:
+  - Run `/analyze` for a cross-artifact quality sweep — catches duplicates, coverage gaps, and terminology drift across all existing artifacts. Especially recommended after `/srs`, `/stories`, and before `/handoff`.
+  - Run `/clarify` to surface ambiguities while context is fresh.
   - Run `/validate` to confirm this artifact is internally consistent.
   - The next skill reads this artifact automatically, so you don't need to paste anything.
 ```