@torus-engineering/tas-kit 1.11.1 → 1.13.0

package/.tas/templates/Security-Report.md

@@ -1,27 +1,27 @@
-# Security Report
-
-> **Last Scan:** {Date}
-> **Scope:** {Full scan | File/Module specific}
-> **Scanned by:** {DSE name}
-
-## Summary
-| Severity | Open | Fixed | Accepted Risk | Total |
-|----------|------|-------|---------------|-------|
-| Critical | 0 | 0 | 0 | 0 |
-| High | 0 | 0 | 0 | 0 |
-| Medium | 0 | 0 | 0 | 0 |
-| Low | 0 | 0 | 0 | 0 |
-
-## Findings
-
-### SEC-001: {Title}
-- **Severity:** Critical | High | Medium | Low
-- **Status:** Open | In Progress | Fixed | Accepted Risk
-- **Location:** {file:line}
-- **Description:** {Issue description}
-- **Recommended Fix:** {Specific fix approach}
-- **Fixed Date:** {Date, if fixed}
-
-## Scan History
-| Date | Scope | New Findings | Fixed | Remaining |
-|------|-------|-------------|-------|-----------|
+# Security Report
+
+> **Last Scan:** {Date}
+> **Scope:** {Full scan | File/Module specific}
+> **Scanned by:** {DSE name}
+
+## Summary
+| Severity | Open | Fixed | Accepted Risk | Total |
+|----------|------|-------|---------------|-------|
+| Critical | 0 | 0 | 0 | 0 |
+| High | 0 | 0 | 0 | 0 |
+| Medium | 0 | 0 | 0 | 0 |
+| Low | 0 | 0 | 0 | 0 |
+
+## Findings
+
+### SEC-001: {Title}
+- **Severity:** Critical | High | Medium | Low
+- **Status:** Open | In Progress | Fixed | Accepted Risk
+- **Location:** {file:line}
+- **Description:** {Issue description}
+- **Recommended Fix:** {Specific fix approach}
+- **Fixed Date:** {Date, if fixed}
+
+## Scan History
+| Date | Scope | New Findings | Fixed | Remaining |
+|------|-------|-------------|-------|-----------|

package/.tas/tools/tas-ado-readme.md

@@ -1,169 +1,169 @@
-# TAS Kit Skill Specification: ado-integration
-
-**Skill name**: ado-integration
-**Version**: 0.2 (concept & spec date: March 17, 2026)
-**Purpose**:
-Allows AI agent in coding environment (Claude Code, Cursor, VS Code + terminal) to perform **CRUD** and two-way sync between Markdown (.md) files in repository and work items on Azure DevOps (Epic, Feature, User Story, Bug), including automatic hierarchy management (parent-child relations).
-
-Main objectives:
-- Transform AI into "team member" capable of self-managing backlog without leaving editor
-- Ensure .md file is single source of truth (local ↔ ADO sync)
-- Record sync timestamp so agent knows data freshness
-
-## 1. Environment Requirements & Dependencies
-
-**Required**:
-- Azure CLI installed + extension `azure-devops`
-  ```bash
-  az extension add --name azure-devops --upgrade
-  ```
-- Python 3.8+
-- Package: `pyyaml` (`pip install pyyaml`)
-
-**Configuration** (file `tas.yaml` at repo root):
-```yaml
-ado:
-  organization: https://dev.azure.com/your-org-name
-  project: Your-Project-Name
-  # pat: PAT with scope Work Items (Full) + optional Read & manage wiki
-  # If no pat in file → use environment variable AZURE_DEVOPS_PAT
-```
-
-## 2. Main Files to Create
-
-- `tools/tas-ado.py`          → Python script executing all commands
-- `skills/ado-integration.md` → usage documentation (like this file)
-
-## 3. Supported CLI Commands
-
-All commands run in form:
-
-```bash
-python tools/tas-ado.py <command> [arguments]
-```
-
-### Create commands (create new + auto rename file + optional parent)
-
-```bash
-create-epic   <temp-id> [--parent-id <id>]
-create-feature <temp-id> [--parent-id <id>]
-create-story   <temp-id> [--parent-id <id>]
-create-bug     <temp-id> [--parent-id <id>]
-```
-
-Example:
-```bash
-python tools/tas-ado.py create-story 789 --parent-id 456
-# → reads epic-789-*.md → creates User Story → renames to story-1234-*.md → adds parent relation to 456
-```
-
-### Pull / Get commands
-
-```bash
-get  <ado-id>
-pull <ado-id>          # alias
-```
-
-Example:
-```bash
-python tools/tas-ado.py get 5345
-# → creates/recreates file epic-5345-slug-title.md with frontmatter + content
-```
-
-### Update commands
-
-```bash
-update-epic   <ado-id> [--assign <name/email>] [--status <state>]
-update-feature <ado-id> [--assign <...>] [--status <...>]
-update-story   <ado-id> [--assign <...>] [--status <...>]
-update-bug     <ado-id> [--assign <...>] [--status <...>]
-
-update-status <ado-id> --status <state> [--assign <name/email>]
-```
-
-### Delete commands
-
-```bash
-delete-epic   <ado-id>
-delete-feature <ado-id>
-delete-story   <ado-id>
-delete-bug     <ado-id>
-```
-
-## 4. File .md Convention
-
-- File name pattern: `{type}-{ado_id or temp_id}-{slug-title}.md`
-  - type: epic / feature / story / bug
-  - slug-title: lowercase, replace spaces with -, remove special characters
-
-- Frontmatter YAML (always at file start):
-
-```yaml
----
-ado_id: 5345
-ado_type: Epic           # Epic / Feature / User Story / Bug
-ado_title: Landing Page Redesign
-ado_state: Active
-ado_assigned_to: Nguyen Van A <email@domain.com>
-ado_created: 2026-03-10
-last_ado_sync: 2026-03-17 15:42:08
-# optional: parent_ado_id: 100   (if want to support auto detect parent later)
----
-# Title (must match ado_title)
-
-Content description, acceptance criteria, steps to reproduce, etc.
-```
-
-**Important**:
-- Every time **create / pull / update / update-status** succeeds → **update** (or add) `last_ado_sync` field with current time (format: YYYY-MM-DD HH:MM:SS)
-
-## 5. Detailed Logic Requirements
-
-### When create:
-1. Find file by pattern `{type}-{temp_id}-*.md`
-2. Extract title (first # line), description (remaining content)
-3. Create work item using `az boards work-item create`
-4. Get new ID → rename file to `{type}-{new_id}-*.md`
-5. If `--parent-id` → run `az boards work-item relation add --id <new_id> --relation-type parent --target-id <parent_id>`
-6. Auto detect parent_id from frontmatter `parent_ado_id` or file name
-7. Update `last_ado_sync` in frontmatter
-
-### When pull/get:
-1. Get work item using `az boards work-item show --id <id> --expand fields`
-2. Convert description (HTML → basic Markdown)
-3. Create file `{type}-{id}-{slug}.md`
-4. Write frontmatter + content
-5. Update `last_ado_sync`
-
-### When update:
-1. Find file by pattern `*-<id>-*.md`
-2. Read title & description from file
-3. Update using `az boards work-item update`
-4. Update `last_ado_sync`
-
-### When update-status:
-1. Find file by pattern
-2. Only update state &/or assigned-to
-3. Update `last_ado_sync` if file found
-
-### When delete:
-- Only delete on ADO, don't touch local files
-
-## 6. Extension Suggestions (not required for v0.2)
-
-- Support additional fields: priority, effort, labels, acceptance criteria
-- Auto git add/commit/push after sync
-- Better HTML → Markdown conversion (table, code block, list)
-
-## 7. How to Use in Agent Prompt
-
-Example prompt template for AI agent:
-
-```
-/ado-create-feature 042 --parent-id 100
-/ado-create-story 789 --parent-id <feature-id just created>
-/ado-get 1234          # fetch new bug to fix
-/ado-update-bug 1234 --status Resolved
-```
-
-This skill is designed to integrate smoothly into agentic frameworks like TAS Kit, Superpowers, BMAD.
+# TAS Kit Skill Specification: ado-integration
+
+**Skill name**: ado-integration
+**Version**: 0.2 (concept & spec date: March 17, 2026)
+**Purpose**:
+Allows AI agent in coding environment (Claude Code, Cursor, VS Code + terminal) to perform **CRUD** and two-way sync between Markdown (.md) files in repository and work items on Azure DevOps (Epic, Feature, User Story, Bug), including automatic hierarchy management (parent-child relations).
+
+Main objectives:
+- Transform AI into "team member" capable of self-managing backlog without leaving editor
+- Ensure .md file is single source of truth (local ↔ ADO sync)
+- Record sync timestamp so agent knows data freshness
+
+## 1. Environment Requirements & Dependencies
+
+**Required**:
+- Azure CLI installed + extension `azure-devops`
+  ```bash
+  az extension add --name azure-devops --upgrade
+  ```
+- Python 3.8+
+- Package: `pyyaml` (`pip install pyyaml`)
+
+**Configuration** (file `tas.yaml` at repo root):
+```yaml
+ado:
+  organization: https://dev.azure.com/your-org-name
+  project: Your-Project-Name
+  # pat: PAT with scope Work Items (Full) + optional Read & manage wiki
+  # If no pat in file → use environment variable AZURE_DEVOPS_PAT
+```
+
+## 2. Main Files to Create
+
+- `tools/tas-ado.py`          → Python script executing all commands
+- `skills/ado-integration.md` → usage documentation (like this file)
+
+## 3. Supported CLI Commands
+
+All commands run in form:
+
+```bash
+python tools/tas-ado.py <command> [arguments]
+```
+
+### Create commands (create new + auto rename file + optional parent)
+
+```bash
+create-epic   <temp-id> [--parent-id <id>]
+create-feature <temp-id> [--parent-id <id>]
+create-story   <temp-id> [--parent-id <id>]
+create-bug     <temp-id> [--parent-id <id>]
+```
+
+Example:
+```bash
+python tools/tas-ado.py create-story 789 --parent-id 456
+# → reads epic-789-*.md → creates User Story → renames to story-1234-*.md → adds parent relation to 456
+```
+
+### Pull / Get commands
+
+```bash
+get  <ado-id>
+pull <ado-id>          # alias
+```
+
+Example:
+```bash
+python tools/tas-ado.py get 5345
+# → creates/recreates file epic-5345-slug-title.md with frontmatter + content
+```
+
+### Update commands
+
+```bash
+update-epic   <ado-id> [--assign <name/email>] [--status <state>]
+update-feature <ado-id> [--assign <...>] [--status <...>]
+update-story   <ado-id> [--assign <...>] [--status <...>]
+update-bug     <ado-id> [--assign <...>] [--status <...>]
+
+update-status <ado-id> --status <state> [--assign <name/email>]
+```
+
+### Delete commands
+
+```bash
+delete-epic   <ado-id>
+delete-feature <ado-id>
+delete-story   <ado-id>
+delete-bug     <ado-id>
+```
+
+## 4. File .md Convention
+
+- File name pattern: `{type}-{ado_id or temp_id}-{slug-title}.md`
+  - type: epic / feature / story / bug
+  - slug-title: lowercase, replace spaces with -, remove special characters
+
+- Frontmatter YAML (always at file start):
+
+```yaml
+---
+ado_id: 5345
+ado_type: Epic           # Epic / Feature / User Story / Bug
+ado_title: Landing Page Redesign
+ado_state: Active
+ado_assigned_to: Nguyen Van A <email@domain.com>
+ado_created: 2026-03-10
+last_ado_sync: 2026-03-17 15:42:08
+# optional: parent_ado_id: 100   (if want to support auto detect parent later)
+---
+# Title (must match ado_title)
+
+Content description, acceptance criteria, steps to reproduce, etc.
+```
+
+**Important**:
+- Every time **create / pull / update / update-status** succeeds → **update** (or add) `last_ado_sync` field with current time (format: YYYY-MM-DD HH:MM:SS)
+
+## 5. Detailed Logic Requirements
+
+### When create:
+1. Find file by pattern `{type}-{temp_id}-*.md`
+2. Extract title (first # line), description (remaining content)
+3. Create work item using `az boards work-item create`
+4. Get new ID → rename file to `{type}-{new_id}-*.md`
+5. If `--parent-id` → run `az boards work-item relation add --id <new_id> --relation-type parent --target-id <parent_id>`
+6. Auto detect parent_id from frontmatter `parent_ado_id` or file name
+7. Update `last_ado_sync` in frontmatter
+
+### When pull/get:
+1. Get work item using `az boards work-item show --id <id> --expand fields`
+2. Convert description (HTML → basic Markdown)
+3. Create file `{type}-{id}-{slug}.md`
+4. Write frontmatter + content
+5. Update `last_ado_sync`
+
+### When update:
+1. Find file by pattern `*-<id>-*.md`
+2. Read title & description from file
+3. Update using `az boards work-item update`
+4. Update `last_ado_sync`
+
+### When update-status:
+1. Find file by pattern
+2. Only update state &/or assigned-to
+3. Update `last_ado_sync` if file found
+
+### When delete:
+- Only delete on ADO, don't touch local files
+
+## 6. Extension Suggestions (not required for v0.2)
+
+- Support additional fields: priority, effort, labels, acceptance criteria
+- Auto git add/commit/push after sync
+- Better HTML → Markdown conversion (table, code block, list)
+
+## 7. How to Use in Agent Prompt
+
+Example prompt template for AI agent:
+
+```
+/ado-create-feature 042 --parent-id 100
+/ado-create-story 789 --parent-id <feature-id just created>
+/ado-get 1234          # fetch new bug to fix
+/ado-update-bug 1234 --status Resolved
+```
+
+This skill is designed to integrate smoothly into agentic frameworks like TAS Kit, Superpowers, BMAD.