@torus-engineering/tas-kit 1.10.0 → 1.12.0

package/.tas/commands/tas-apitest.md

@@ -0,0 +1,143 @@
+# /tas-apitest $ARGUMENTS
+
+Role: SE - Software Engineer
+Generate .NET xUnit automation test project for REST API from API Test Spec file (Markdown).
+
+## Always / Ask / Never
+
+| | Action |
+|---|---|
+| **Always** | Read entire API Test Spec file before generating any test |
+| **Always** | Organize tests by API version — each version separate folder |
+| **Always** | Append-only: don't modify files in existing old version folder |
+| **Always** | URL and credentials in `appsettings.json` — not hardcoded in code |
+| **Always** | XML doc comment on each test method |
+| **Ask** | When test spec unclear about expected response schema |
+| **Never** | Modify or delete old version test files |
+| **Never** | Hardcode base URL, API key, credentials in test code |
+| **Never** | Skip error path — each endpoint needs ≥1 happy path + ≥1 error path |
+
+## Actions
+
+### Step 1 — Locate Input
+
+`$ARGUMENTS` is path to API Test Spec file: `docs/tests/API-Test-Spec-{slug}.md`.
+
+If not provided → ask user:
+```
+Enter path to API Test Spec file (e.g., docs/tests/API-Test-Spec-users.md)
+```
+
+### Step 2 — Parse API Test Spec
+
+Read `.tas/rules/csharp/api-testing.md` for conventions before generating.
+
+From API Test Spec file, collect:
+- API version
+- Endpoints with method, path, params
+- Test cases per endpoint (TC-XXX)
+- Request/response schemas
+- Auth requirements
+- Test data requirements
+- Setup/teardown notes
+
+### Step 3 — Detect Existing Test Project
+
+Glob find `**/ApiTests/*.csproj`, `**/Api.Tests/*.csproj`, `**/IntegrationTests/*.csproj`.
+
+- **Found**: Read current framework (xUnit/NUnit/MSTest), glob `v*/` folders to know existing versions.
+- **Not found**: Create new at `tests/ApiTests/` with xUnit + FluentAssertions (per `csharp/testing.md`).
+
+### Step 4 — Get API Version from Spec
+
+Read version from API Test Spec file (find frontmatter `api_version` or section headers `## v{N}`).
+
+Version folder: lowercase, no dot — `v1`, `v2` (not `v1.0`).
+
+### Step 5 — Generate Infrastructure (only when creating new project)
+
+Read `.tas/rules/csharp/api-testing.md` section **Project Structure** and **Config Pattern** to generate:
+- `ApiTests.csproj` with standard packages
+- `appsettings.json` (base) + `appsettings.Test.json` + `appsettings.Staging.json` with values from spec
+- `Shared/TestBase.cs` — load config, HttpClient, helper methods
+- `Shared/ApiTestSettings.cs` — strongly typed settings
+- `.gitignore` for `appsettings.*.local.json`
+
+### Step 6 — Generate Test Classes from Spec
+
+Group endpoints by resource. Each group → `tests/ApiTests/{version}/{Resource}ApiTests.cs`.
+
+For each test case (TC-XXX) in spec:
+1. Read test case details
+2. Map to test method with naming: `{HttpMethod}_{Resource}_Returns{Status}_When{Condition}`
+3. Generate XML doc from test case title
+4. Generate assertions from expected response
+5. Add AC reference comment if any
+
+Test class header comment:
+```csharp
+// ============================================================
+// {Resource} API Tests — v{N}
+// Spec: docs/tests/API-Test-Spec-{slug}.md
+// Generated: {YYYY-MM-DD}
+// Story: {ID} (if applicable)
+// APPEND-ONLY: don't modify existing methods.
+// ============================================================
+```
+
+### Step 7 — Append-Only Guard
+
+Before writing file: check if file already exists.
+- **File doesn't exist** → create normally.
+- **File exists** in version folder → check each test method:
+  - Method exists (same name) → **SKIP**, don't overwrite
+  - Method doesn't exist → append to end of class
+
+### Step 8 — Generate Test Data Files (if spec requires)
+
+If spec has `test-data.{env}.json` references:
+- Create `tests/ApiTests/data/test-data.Test.json` with sample data from spec
+- Guide user to create `test-data.Staging.json` and `test-data.local.json`
+
+### Step 9 — Post-Generate Review
+
+Launch `csharp-reviewer` agent:
+> Review `tests/ApiTests/{version}/`. Read `.tas/rules/csharp/testing.md` + `.tas/rules/csharp/api-testing.md`.
+> Focus: async/await, HttpClient disposal, assertion completeness, XML doc coverage.
+> Format: Critical / High / Medium / Low with file:line.
+
+Gate: Critical/High → fix immediately. Medium/Low → list suggestions.
+
+### Step 10 — Summary
+
+Display:
+1. Test project path
+2. Number of test classes generated
+3. Number of test methods generated
+4. Coverage matrix (vs spec)
+5. Next steps to run tests
+
+```
+## API Tests Generated
+
+**Project**: `tests/ApiTests/`
+**Version**: v{N}
+**Test Classes**: {N}
+**Test Methods**: {N}
+
+### Generated Files
+- tests/ApiTests/{version}/{Resource}ApiTests.cs
+- tests/ApiTests/Shared/TestBase.cs (if new project)
+
+### Coverage (vs Spec)
+[Print coverage table: spec test cases vs generated methods]
+
+### Next Steps
+1. Configure test environment: edit tests/ApiTests/appsettings.Test.json
+2. Add test data: tests/ApiTests/data/test-data.Test.json
+3. Run tests: `dotnet test tests/ApiTests/`
+```
+
+## Final Step — Token Log
+
+Follow `.tas/rules/common/token-logging.md`: write AI Usage Log to API Test Spec file.

package/.tas/commands/tas-brainstorm.md

@@ -0,0 +1,19 @@
+# /tas-brainstorm $ARGUMENTS
+
+Role: Any
+Structured brainstorming before coding or designing.
+
+## Actions
+1. $ARGUMENTS is the brainstorming topic
+2. Guide through 4 steps:
+   a. **Clarify**: Ask 3-5 questions to clarify the problem
+   b. **Explore**: Propose 3+ solution directions, each with pros/cons
+   c. **Evaluate**: Compare directions by criteria: complexity, maintainability, cost, time
+   d. **Decide**: Recommend best direction and reasoning
+
+3. If brainstorming result leads to architecture decision, suggest user run /tas-adr
+
+## Principles
+- DO NOT jump straight to solution
+- Ask first, suggest later
+- Always consider at least 2 alternatives

package/.tas/commands/tas-bug.md

@@ -0,0 +1,113 @@
+# /tas-bug $ARGUMENTS
+
+Manage entire bug lifecycle: create, analyze, fix, verify.
+Bug status determines next step — no role declaration needed.
+
+## Always / Ask / Never
+
+| | Action |
+|---|---|
+| **Always** | Display current status and next action before doing anything |
+| **Always** | Write regression test BEFORE fixing |
+| **Always** | Launch independent review agent after fix — no review in same session |
+| **Ask** | When needing to read files outside Bug file (Status = Committed) |
+| **Never** | Patch symptom — must fix root cause |
+| **Never** | Skip review step after fix |
+| **Never** | Auto-commit or push — wait for user manual testing first |
+
+## Stack Detection
+Read `.tas/rules/common/stack-detection.md`.
+
+## Actions
+
+### Step 1 — Determine mode
+
+`$ARGUMENTS` is new bug description → **CREATE mode**
+`$ARGUMENTS` is Bug ID (e.g., `Bug-001`) → **UPDATE mode**
+
+---
+
+### CREATE mode
+
+Role: PE or SE (whoever discovered the bug)
+
+1. Read `project.code` from root/`tas.yaml`
+2. Ask user:
+   - Which Feature does this bug belong to?
+   - Severity: `Critical` | `High` | `Medium` | `Low`
+   - Steps to reproduce
+   - Expected vs Actual behavior
+   - Environment where discovered: Test | Staging | Production
+3. Create `docs/bugs/{code}-Bug-{NNN}-{slug}.md` from template `.tas/templates/Bug.md`
+4. Initial bug status: `New`
+
+---
+
+### UPDATE mode
+
+Find Bug file via glob `docs/bugs/*-Bug-{ID}-*.md`, read current status.
+
+**Display before acting:**
+> "Bug-{NNN} is currently at status: **{status}** — next step is {action}. Continue?"
+
+---
+
+#### Status = `New` — Analyze (SE)
+
+1. Read error logs/stack trace from Bug file
+2. Trace code flow, identify file and line causing error
+3. Write Root Cause Analysis into Bug file
+4. Write Regression Test Cases (test that reproduces bug)
+5. Update status: `New` → `Committed`
+
+---
+
+#### Status = `Committed` — Fix (SE)
+
+**File reading rule:** ONLY read Bug file. DO NOT read PRD, SAD, ADR, Design-Spec, DO NOT scan directories.
+If additional files needed → ask user confirmation first.
+
+Before fixing, read:
+- `.tas/rules/common/security.md` — fix must not create new security risks
+- `.tas/rules/common/testing.md` — regression test writing patterns
+- `.tas/rules/[lang_agent stack]/coding-style.md` — follow conventions
+
+**Fix workflow:**
+a. Run regression test case → confirm **FAIL** (reproduces bug)
+b. Fix code at root cause
+c. Run regression test → confirm **PASS**
+d. Run full test suite → no new regressions
+→ If build fails or test compile errors: launch `build-resolver` agent with error output before continuing.
+
+**After fix — Post-Fix Review (Isolated Agent):**
+
+Follow `.tas/rules/common/post-implementation-review.md`.
+Pass in: Bug file path, changed files list, stack (from CLAUDE.md), lang_agent.
+
+After review passes:
+- Update status: `Committed` → `Deploy Test`
+- Output suggested commit message: `fix: {short description} - resolves Bug-{NNN}`
+- Ask: "Have you tested manually? Want to commit and deploy to Test?"
+
+---
+
+#### Status = `Verify Test` / `Verify Stag` — Verify (PE)
+
+1. PE verifies on corresponding environment:
+   - Run Steps to Reproduce again → confirm bug no longer exists
+   - Check regression test case has passed
+2. **Pass** → update to next status (`Deploy Stag` or `Done`)
+3. **Fail** → document reason, update status back to `Committed`, SE fixes again
+
+---
+
+## Principles
+- DO NOT patch symptom — must fix root cause
+- MUST have regression test case BEFORE fixing
+- Review must run through independent Agent — not inline in current session
+- `Critical`/`High` bugs must be fixed before Feature is Verified
+- Flow: `New` → `Committed` → `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 Bug file.

package/.tas/commands/tas-design.md

@@ -0,0 +1,37 @@
+# /tas-design $ARGUMENTS
+
+Role: PE - Product Engineer
+Create or update Design Specification document (UI/UX flows, wireframe descriptions).
+
+## Prerequisite
+- docs/prd.md must exist
+
+## Actions
+1. Need context from root/tas.yaml and docs/prd.md
+2. Check if docs/design-spec.md already exists:
+
+### CREATE mode (file doesn't exist):
+3. Need context from .tas/templates/Design-Spec.md
+4. $ARGUMENTS is design scope description. If not provided, base on PRD.
+5. Create file docs/design-spec.md containing:
+   - User flows (Mermaid flowchart)
+   - Screen descriptions
+   - Navigation structure
+   - Interaction patterns
+   - Responsive behavior notes
+6. Update `project-status.yaml` per `.tas/rules/common/project-status.md` — add `artifacts.design_spec`.
+
+### UPDATE mode (file exists):
+3. Need context from current docs/design-spec.md
+4. $ARGUMENTS is change description. If not provided, ask user which section to update.
+5. Update file, add changelog
+6. Update `project-status.yaml` per `.tas/rules/common/project-status.md` — update `artifacts.design_spec`.
+
+## Principles
+- Focus on flows and behavior, not pixel-perfect design
+- Each screen needs: purpose, key elements, actions available
+- Mermaid compliance: :::mermaid wrapper, no () in node labels
+
+## Final Step — Token Log
+
+Follow `.tas/rules/common/token-logging.md`: write AI Usage Log to `docs/design-spec.md`.

package/.tas/commands/tas-dev.md

@@ -0,0 +1,125 @@
+# /tas-dev $ARGUMENTS
+
+Role: SE - Software Engineer
+Implement a User Story per approved Technical Plan.
+
+## Always / Ask / Never
+
+| | Action |
+|---|---|
+| **Always** | Check `plan_status` before implementing |
+| **Always** | Follow tasks in Story's `## Technical Plan` |
+| **Always** | Launch independent review agent after implement — no review in same session |
+| **Ask** | When discover plan needs significant changes during coding |
+| **Ask** | When need to read files outside plan scope |
+| **Never** | Implement outside Story scope |
+| **Never** | Skip review step after implement |
+
+## IMPORTANT - File Reading Rules
+- ONLY read Story file — Technical Plan has enough technical context.
+- Don't auto-read PRD, SAD, ADR, Design-Spec unless user confirms.
+- Don't list directories, don't scan project structure.
+- Don't read `.tas/rules/common/story-done.md` at first step (only at final step).
+
+## Stack Detection
+Read `.tas/rules/common/stack-detection.md`.
+
+## Actions
+
+### Step 1 — Identify Story
+
+`$ARGUMENTS` is Story ID or file path.
+If none: read `project-status.yaml`, find stories with `status: Committed` or `status: In Progress`. If more than one, list for user to choose.
+Read Story file.
+
+### Step 1.5 — Gate: Check plan_status
+
+Read `plan_status` from Story frontmatter.
+
+**If `plan_status: pending`:**
+Read `require_plan` from root/`tas.yaml`:
+- `require_plan: true` (or field doesn't exist) → **STOP**:
+  > "This Story has no Technical Plan. Run `/tas-plan {Story-ID}` before implementing."
+- `require_plan: false` → continue, show warning and wait for confirmation:
+  > "⚠️ Quick mode: Story has no Technical Plan. Continue implementing?"
+
+**If `plan_status: completed`:** continue normally.
+
+### Step 2 — Read Technical Plan
+
+From Story file, read `## Technical Plan` section:
+- Chosen approach
+- Files to Change / Files to Create
+- Database Changes, Config Changes
+- Tasks list (checklist to follow in order)
+
+If no Technical Plan (quick mode) → analyze AC and implement directly per AC.
+
+### Step 3 — Implement
+
+**If stack is Node.js/Express/Next.js** → Read `.tas/rules/typescript/patterns.md` and `.tas/rules/typescript/security.md` for repository pattern, N+1 prevention, error handler, caching, JWT/RBAC before coding.
+
+#### If `use_tdd = true` in `tas.yaml`:
+
+Read `.tas/rules/common/tdd.md` for Red-Green-Refactor discipline + Test Naming Convention.
+
+Platform-specific test stacks (from stack detection):
+- **Mobile (React Native)**: Jest + React Testing Library — Components (`render`, `fireEvent`, `screen`), Hooks (`renderHook`), Services/API (Jest mocks + MSW), Utils, Zustand stores. File: `src/**/*.test.ts(x)`
+- **Web (React + Node)**: Vitest/Jest + React Testing Library — Components, Hooks, Services (MSW/Nock), Backend services (Jest). File: `src/**/*.test.ts(x)`
+- **Backend (.NET)**: xUnit — Unit (services, repositories), Integration (TestServer), API (WebApplicationFactory). File: `tests/Unit/`, `tests/Integration/`, `tests/Api/`
+
+#### If `use_tdd = false`:
+a. Implement code per AC + Tasks in Technical Plan
+b. Write unit tests covering cases in `## Unit Test Cases`
+c. Run tests, fix if fail
+→ If tests still fail after 1 self-fix: launch `build-resolver` agent with error output to diagnose.
+
+During implementation, tick each completed task in Story file: `- [x] Task 1: ...`
+
+If discover plan needs significant changes → notify user before changing direction.
+
+### Step 4 — Post-Implementation Review (Isolated Agent)
+
+Follow `.tas/rules/common/post-implementation-review.md`.
+Pass in: Story file path, changed files list, stack (from CLAUDE.md), lang_agent.
+
+### Step 5 — Definition of Done
+
+Read `.tas/rules/common/story-done.md`, verify each item, tick in Story:
+- `- [x] Technical plan completed` — if plan_status: completed (or quick mode confirmed)
+- `- [x] Code implemented` — if implementation done
+- `- [x] Unit tests pass` — if tests passed
+- `- [x] No regression` — if full test suite passed
+- `- [x] Documentation updated (if needed)` — if updated
+- `- [x] Code review passed` — if review gate passed (no Critical/High)
+- `- [ ] Acceptance criteria verified` — DO NOT tick, let PE verify
+
+**Optional — if Story changes public API, database schema, or setup:**
+Launch `doc-updater` agent: update related docs (README, SAD section, API docs).
+> Scope: [changed files list]. Story: [Story ID + title].
+> Only update outdated docs — don't rewrite from scratch.
+
+### Step 6 — Wrap up
+
+Update Story status → `In Progress` (if not already).
+Create commit message per conventions in `CLAUDE.md`.
+Ask: "Tests OK and review passed — have you tested manually? Want to move to Deploy Test?"
+
+If Yes:
+- Update Story status → `Deploy Test`
+- Add Changelog entry
+- Update `project-status.yaml`
+- Suggest: `/ado-update story {ado-id} --status "Deploy Test"` if using ADO
+
+## Principles
+- DO NOT implement outside Story scope
+- Each public method MUST have XML doc comment (C#) or JSDoc (TypeScript) or docstring (Python)
+- Review must run through independent Agent — not inline in current session
+- **When to create ADR** (if Technical Plan didn't mention):
+  - Architecture changes affecting multiple components
+  - New design pattern or framework
+  - Important technical trade-off decisions
+
+## Final Step — Token Log
+
+Follow `.tas/rules/common/token-logging.md`: write AI Usage Log to working Story file.