@torus-engineering/tas-kit 1.14.0 → 2.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@torus-engineering/tas-kit",
-  "version": "1.14.0",
+  "version": "2.1.0",
   "description": "TAS Kit - Turbo Agentic SDLC toolkit for modern AI-first software teams.",
   "type": "module",
   "bin": {

package/.tas/commands/tas-epic.md

@@ -1,35 +0,0 @@
-# /tas-epic $ARGUMENTS
-
-Role: PE - Product Engineer
-Create or update Epic document.
-
-## Prerequisite
-- docs/prd.md must exist
-
-## Actions
-1. Need context from root/tas.yaml and docs/prd.md
-2. Need context from .tas/templates/Epic.md
-3. Determine mode based on $ARGUMENTS:
-
-### CREATE mode ($ARGUMENTS is new Epic description, or no $ARGUMENTS):
-4. If no $ARGUMENTS, ask user for Epic description.
-5. Read project.code from root/tas.yaml. Scan docs/epics/ to determine sequence number.
-6. Create directory docs/epics/{code}-Epic-{NNN}-{slug}/
-7. Create file docs/epics/{code}-Epic-{NNN}-{slug}/{code}-Epic-{NNN}-{slug}.md
-8. Update `project-status.yaml` per `.tas/rules/common/project-status.md` — add entry to `epics`.
-
-### UPDATE mode ($ARGUMENTS is Epic ID, e.g., "Epic-001"):
-4. Find directory docs/epics/{code}-Epic-001-*/
-5. Need context from current Epic file
-6. Ask user what needs changing (update scope, add feature, change status...)
-7. Update file, add changelog
-8. Update `project-status.yaml` per `.tas/rules/common/project-status.md` — update `epics.{EPIC_ID}.status`.
-
-## Principles
-- Each Epic maps to one business capability in PRD
-- Epic does NOT contain technical details, only business value
-- Effort estimation at T-shirt size level: S/M/L/XL
-
-## Final Step — Token Log
-
-Follow `.tas/rules/common/token-logging.md`: write AI Usage Log to working Epic file.

package/.tas/commands/tas-story.md

@@ -1,91 +0,0 @@
-# /tas-story $ARGUMENTS
-
-Role: PE - Product Engineer
-Create or update User Story document.
-
-**Scope:** Business logic, user experience, acceptance criteria, test cases.
-**Out of scope:** Technical implementation, files to modify, database schema — that's `/tas-plan`'s job.
-
-## Always / Ask / Never
-
-| | Action |
-|---|---|
-| **Always** | Write AC in Given/When/Then format |
-| **Always** | Set `plan_status: pending` for new Story |
-| **Ask** | When Story > 8h — suggest splitting |
-| **Never** | Read SAD, ADR — technical is `/tas-plan`'s job |
-
-## Prerequisite
-- At least one Feature must exist
-
-## Actions
-
-### CREATE mode ($ARGUMENTS is new Story description, or no $ARGUMENTS)
-
-**Step 1 — Identify Feature**
-- Read `project.code` from root/`tas.yaml`
-- Prioritize in order:
-  1. If `$ARGUMENTS` contains Feature ID → use it
-  2. If context has `parent_id` → use it
-  3. Ask user: "Which Feature does this Story belong to?" — no directory scan
-
-**Step 2 — Gather business context**
-- Read identified Feature file (get business context, scope, existing Stories list)
-- Read PRD (if exists) — only business requirements, user goals
-
-**Step 3 — Determine Story ID**
-- Read Stories section in Feature file → determine next index from that list
-- DO NOT scan directory
-
-**Step 4 — Draft Story with user**
-
-Discuss to fill in:
-
-a) **User Story**: "As a [role], I want [goal], so that [benefit]"
-
-b) **Business Requirements** (if any): specific business rules, stakeholder constraints
-
-c) **Design Notes** (if any): UI/UX specs, mockup links, flow diagrams
-
-d) **Prerequisites** (if any): other Stories that must be done first
-
-e) **Acceptance Criteria**: each AC is a clear Given/When/Then scenario
-
-**Step 5 — Test Case Prompting**
-
-After AC confirmed, ask more:
-- "Besides happy path, any edge cases to test?" (empty input, boundary values, concurrent)
-- "Any negative cases to cover?" (unauthorized, invalid data, timeout, not found)
-- "Any external dependencies to mock when testing?" (external APIs, database state)
-
-Write all to `## Unit Test Cases` section.
-
-**Step 6 — Create file**
-- Read `.tas/templates/Story.md` for format
-- Create `docs/epics/{code}-Epic-{NNN}-{slug}/{code}-Feature-{NNN}-{slug}/{code}-Story-{NNN}-{slug}.md`
-- Frontmatter: `plan_status: pending`, `plan_date:` left empty
-
-**Step 7 — Update project-status.yaml**
-Per `.tas/rules/common/project-status.md` — add entry to `epics.{EPIC_ID}.features.{FEATURE_ID}.stories`.
-
-**Step 8 — Notify next step**
-> "Story created. Before SE starts coding, run `/tas-plan {Story-ID}` for technical planning."
-
----
-
-### UPDATE mode ($ARGUMENTS is Story ID, e.g., "Story-005")
-
-1. Find file via glob `docs/epics/**/{code}-Story-{ID}-*.md`
-2. Read current Story file
-3. Ask user what needs changing (update AC, change status, add test cases, fix business rule...)
-4. Update file, add entry to Changelog
-5. Update `project-status.yaml` per `.tas/rules/common/project-status.md`.
-
-## Principles
-- Story must be small enough to complete in **4-8 hours**; if larger → split into multiple Stories
-- Story file = **product artifact**: describes *what* and *why*, not *how*
-- Story status: New → Committed → In Progress → Deploy Test → Verify Test → Deploy Stag → Verify Stag → Deploy Prod → Verify Prod → Done
-
-## Final Step — Token Log
-
-Follow `.tas/rules/common/token-logging.md`: write AI Usage Log to working Story file.

package/.tas/rules/common/story-done.md

@@ -1,30 +0,0 @@
-# Definition of Done
-
-Workflow gate used by `/tas-dev` Step 5 — verify each item before marking Story complete.
-
-## Code
-
-- [ ] Code implemented per acceptance criteria
-- [ ] Follows conventions in CLAUDE.md
-- [ ] Each public method has doc comment (XML doc / JSDoc / docstring)
-
-## Testing
-
-- [ ] Unit tests pass (happy path + edge cases + negative cases)
-- [ ] No regression on existing tests
-
-## Review
-
-- [ ] Code review passed (per `.tas/rules/common/code-review.md`)
-- [ ] If `auto_review = true`, passed automated review
-
-## Documentation
-
-- [ ] Technical notes in Story updated
-- [ ] If API changes, corresponding docs updated
-
-## Status
-
-- [ ] Story status updated in Story file
-- [ ] `project-status.yaml` updated
-- [ ] Commit message follows correct format

package/.tas/templates/Epic.md

@@ -1,46 +0,0 @@
----
-ado_id:
-ado_type: Epic
-ado_title: "{Title}"
-ado_state: New
-ado_assigned_to:
-ado_created:
-last_ado_sync:
----
-# Epic-{NNN}: {Title}
-
-> **Status:** New | Pending | In Design | In Progress | In Monitoring | In Closing | Done | Removed
-> **Owner:** {PE name}
-> **Created:** {Date}
-> **PRD Reference:** {link to PRD section}
-
-## Business Value
-{Business value description}
-
-## Scope
-### In Scope
-- Item 1
-- Item 2
-
-### Out of Scope
-- Item 1
-
-## Acceptance Criteria (High-level)
-- [ ] Criteria 1
-- [ ] Criteria 2
-
-## Features
-| ID | Feature | Priority | Estimate |
-|----|---------|----------|----------|
-| Feature-001 | {name} | Must | M |
-| Feature-002 | {name} | Should | L |
-
-## Dependencies
-- {dependency 1}
-
-## Risks
-- {risk 1}
-
-## Changelog
-| Date | Changes | Author |
-|------|---------|--------|

package/.tas/templates/Story.md

@@ -1,90 +0,0 @@
----
-ado_id:
-ado_type: User Story
-ado_title: "{Title}"
-ado_state: New
-ado_assigned_to:
-ado_created:
-last_ado_sync:
-parent_ado_id:
-plan_status: pending
-plan_date:
----
-# Story-{NNN}: {Title}
-
-> **Status:** New | Committed | In Progress | Deploy Test | Verify Test | Deploy Stag | Verify Stag | Deploy Prod | Verify Prod | Done
-> **Feature:** Feature-{NNN}
-> **Assigned to:** {SE name}
-> **Estimate:** {S/M/L}
-> **Created:** {Date}
-
-## User Story
-As a {role}, I want {goal}, so that {benefit}.
-
----
-## Business Requirements (if any)
-*(Special business requirements, business rules, constraints from stakeholders — add only when needed)*
-
----
-## Design Notes (if any)
-*(UI/UX specs, mockup links, design decisions, flow diagrams — add only when needed)*
-
----
-## Prerequisites (if any)
-*(Dependencies from other Stories or required conditions — add only when needed)*
-
----
-## Acceptance Criteria
-
-### AC-1: {title}
-- **Given** {precondition}
-- **When** {action}
-- **Then** {expected result}
-- **Functional Tests**: *(fill FT IDs after running `/tas-functest` — e.g.: `{PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_001_H`, `FT_002_N`)*
-
-### AC-2: {title}
-- **Given** {precondition}
-- **When** {action}
-- **Then** {expected result}
-- **Functional Tests**: *(fill FT IDs after running `/tas-functest`)*
-
----
-## Unit Test Cases
-*(PE designs happy path + edge cases + negative cases. SE implements in code.)*
-
-### Happy Path
-| ID | AC Ref | Description | Input | Expected Output |
-|----|--------|-------------|-------|-----------------|
-| UT-1 | AC-1 | {description} | {input} | {expected} |
-
-### Edge Cases
-| ID | AC Ref | Description | Input | Expected Output |
-|----|--------|-------------|-------|-----------------|
-| UT-E1 | AC-1 | {description} | {input} | {expected} |
-
-### Negative Cases
-| ID | AC Ref | Description | Input | Expected Output |
-|----|--------|-------------|-------|-----------------|
-| UT-N1 | AC-1 | {description} | {input} | {expected} |
-
-### Dependencies to Mock
-- {external API, database state, third-party service...}
-
----
-<!-- ═══════════════════════════════════════════════════════════════════
-     TECHNICAL PLAN — generated by /tas-plan, do not edit manually
-     ═══════════════════════════════════════════════════════════════════ -->
-
----
-## Definition of Done
-- [ ] Technical plan completed (`/tas-plan`)
-- [ ] Code implemented
-- [ ] Unit tests pass
-- [ ] Code review passed
-- [ ] Acceptance criteria verified
-- [ ] No regression
-- [ ] Documentation updated (if needed)
-
-## Changelog
-| Date | Changes | Author |
-|------|---------|--------|