sdtk-kit 0.3.7 → 0.3.9

package/assets/toolkit/toolkit/templates/handoffs/BA_TO_ARCH.md

@@ -0,0 +1,28 @@
+# BA to ARCH Handoff
+
+## Required Inputs
+- `docs/specs/BA_SPEC_[FEATURE_KEY].md`
+- `docs/product/PRD_[FEATURE_KEY].md`
+- `docs/product/BACKLOG_[FEATURE_KEY].md`
+- current `SHARED_PLANNING.md`
+
+## Required Outputs
+- `docs/architecture/ARCH_DESIGN_[FEATURE_KEY].md`
+- API, DB, and UI design artifacts when in scope
+- updated `SHARED_PLANNING.md`
+- updated `QUALITY_CHECKLIST.md`
+
+## Mandatory Checks
+- `REQ -> UC/BR/AC` traceability exists in BA output.
+- unresolved `OQ-xx` items are visible to ARCH.
+- ARCH knows whether API, DB, and UI scope are required.
+
+## Forbidden Shortcuts
+- Do not jump into implementation details before architecture scope is mapped.
+- Do not hide unresolved business rules inside architecture assumptions.
+
+## Handoff Message Shape
+- Feature: `[FEATURE_KEY]`
+- In-scope use cases: `UC-xx`
+- Key business rules: `BR-xx`
+- Blocking open questions: `OQ-xx` or `None`

package/assets/toolkit/toolkit/templates/handoffs/DEV_STAGE1_SPEC_REVIEW.md

@@ -0,0 +1,26 @@
+# DEV Stage 1 Spec Review
+
+## Required Inputs
+- implementation diff or changed files
+- `docs/specs/BA_SPEC_[FEATURE_KEY].md`
+- `docs/api/[FeaturePascal]_API.yaml` and `docs/api/[FEATURE_KEY]_ENDPOINTS.md` when API scope exists
+- `docs/specs/[FEATURE_KEY]_FLOW_ACTION_SPEC.md` when UI scope exists
+- `docs/database/DATABASE_SPEC_[FEATURE_KEY].md` when data scope exists
+
+## Required Outputs
+- PASS or FAIL verdict
+- mismatch table with exact file references
+- explicit handoff decision to Stage 2 or back to DEV
+
+## Mandatory Checks
+- code matches BA, API, DB, and flow-action requirements line by line
+- missing mappings and drift are called out explicitly
+- unresolved assumptions that affect behavior are treated as blockers
+
+## Verification Evidence
+- quote the exact specification text before declaring a match or mismatch
+- use: `Spec says: "[exact quote]" -> Evidence: [match/mismatch + file reference]`
+
+## Forbidden Shortcuts
+- Do not start with style or maintainability feedback.
+- Do not trust the implementer report without checking artifacts directly.

package/assets/toolkit/toolkit/templates/handoffs/DEV_STAGE2_CODE_QUALITY_REVIEW.md

@@ -0,0 +1,20 @@
+# DEV Stage 2 Code Quality Review
+
+## Required Inputs
+- Stage 1 review result marked PASS
+- implementation diff or changed files
+- relevant test or lint outputs
+
+## Required Outputs
+- PASS or FAIL verdict
+- quality findings with file references
+- recommendation for QA handoff readiness
+
+## Mandatory Checks
+- Stage 1 spec review already passed
+- naming, structure, tests, and maintainability are reviewed
+- verification commands cited are fresh and relevant to the current diff
+
+## Forbidden Shortcuts
+- Do not reopen Stage 1 requirement matching as a substitute for quality review.
+- Do not declare QA-ready without confirming Stage 1 PASS and fresh verification evidence.

package/assets/toolkit/toolkit/templates/handoffs/DEV_TO_QA.md

@@ -0,0 +1,23 @@
+# DEV to QA Handoff
+
+## Required Inputs
+- `docs/dev/FEATURE_IMPL_PLAN_[FEATURE_KEY].md`
+- implementation diff summary
+- Stage 1 spec review PASS evidence
+- Stage 2 code-quality review PASS evidence
+- fresh test or lint outputs used for QA handoff
+
+## Required Outputs
+- QA test scope
+- explicit release-risk notes
+- updated `SHARED_PLANNING.md`
+- updated `QUALITY_CHECKLIST.md`
+
+## Mandatory Checks
+- both DEV review gates are PASS
+- verification evidence is fresh
+- known limitations or assumptions are recorded, not hidden
+
+## Forbidden Shortcuts
+- Do not hand off to QA with only one review gate complete.
+- Do not describe expected behavior as if it were verified runtime evidence.

package/assets/toolkit/toolkit/templates/handoffs/PM_TO_BA.md

@@ -0,0 +1,26 @@
+# PM to BA Handoff
+
+## Required Inputs
+- `docs/product/PROJECT_INITIATION_[FEATURE_KEY].md`
+- source requirement notes or attachments
+- current `SHARED_PLANNING.md`
+
+## Required Outputs
+- `docs/specs/BA_SPEC_[FEATURE_KEY].md`
+- updated `SHARED_PLANNING.md`
+- updated `QUALITY_CHECKLIST.md`
+
+## Mandatory Checks
+- `REQ-xx` scope is explicit and testable.
+- in-scope and out-of-scope are visible.
+- unresolved ambiguities are logged as `OQ-xx`, not hidden.
+
+## Forbidden Shortcuts
+- Do not skip glossary, BR, UC, AC, or traceability expectations.
+- Do not invent missing stakeholder decisions without logging them.
+
+## Handoff Message Shape
+- Feature: `[FEATURE_KEY]`
+- PM scope summary: 3 to 7 bullets
+- Known open questions: `OQ-xx` list or `None`
+- Expected BA focus: rules, use cases, acceptance criteria, NFRs

package/assets/toolkit/toolkit/templates/handoffs/QA_RELEASE_DECISION.md

@@ -0,0 +1,21 @@
+# QA Release Decision
+
+## Required Inputs
+- `docs/qa/QA_RELEASE_REPORT_[FEATURE_KEY].md`
+- Stage 1 and Stage 2 DEV review PASS evidence
+- fresh proving checks or benchmark-mode evidence
+- open defect list with severity
+
+## Required Outputs
+- `APPROVED` or `REJECTED`
+- explicit evidence summary
+- unresolved risks and assumptions list
+
+## Mandatory Checks
+- verdict is backed by fresh command evidence or benchmark policy
+- specification quotes are used for requirement-based validation
+- defects and known gaps are visible in the decision
+
+## Forbidden Shortcuts
+- Do not issue `APPROVED` based on planned checks.
+- Do not hide environment limitations; state when runtime verification was not possible.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "sdtk-kit",
-    "version": "0.3.7",
+    "version": "0.3.9",
     "description": "SDTK CLI toolkit for deterministic software documentation workflows",
     "bin": {
         "sdtk": "./bin/sdtk.js"