@ngocsangairvds/vsaf 4.1.8 → 4.1.9

package/skills/vds-skill/vds-scripts/docs/agents/reference/tasks-orchestrator.md

@@ -1,53 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Tasks Orchestrator
-
-> Manage and track tasks across VDS phases and work packages.
-
-## Scope
-
-- **Does:** Create tasks, update status, track completion, generate task reports.
-- **Does NOT:** Replace Jira for complex project management, auto-assign tasks.
-- **Primary users:** AI agents (task tracking), human leads (progress review).
-
-## CLI Entry
-
-```bash
-# Via unified router
-vds-cli tasks --help
-
-# Direct entry
-vds-cli tasks --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `list` | List active tasks | `--phase`, `--status` |
-| `create` | Create new task | `--title`, `--owner` |
-| `update` | Update task status | `--id`, `--status` |
-| `report` | Generate task report | `--format` |
-
-## Common Workflows
-
-### Workflow: Track Phase Tasks
-
-1. Run `vds-cli tasks list --phase 174` to see active tasks
-2. Update task status: `vds-cli tasks update --id ORCH-001 --status in_progress`
-3. Mark complete: `vds-cli tasks update --id ORCH-001 --status completed`
-4. Generate report: `vds-cli tasks report --phase 174`
-
-## Related
-
-- **Orchestrators:** [spec](spec-orchestrator.md), [progress](progress-orchestrator.md), [audit](audit-triage-playbook.md)
-- **Skills:** [cli-development-skill](../../../../vds-skills/skills/cli-development-skill/SKILL.md)
-- **Confluence:** [WHO Tasks](http://confluence.digital.vn/display/TTCN24/WHO-Project+Ecosystem+Documentation)
-
-## Troubleshooting
-
-| Issue | Cause | Resolution |
-|-------|-------|------------|
-| Command not found | Orchestrator not installed | Run `uv sync --all-packages` |
-| Config missing | `~/.vds/.env` unset | Add required credentials per [AGENTS.md](../../../AGENTS.md) |
-| Permission denied | Insufficient privileges | Check Bitbucket/Confluence token scope |

package/skills/vds-skill/vds-scripts/docs/agents/reference/validation-and-sync-notes.md

@@ -1,54 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Validation And Sync Notes
-
-This note records the remaining validation steps for the WHO ecosystem alignment work.
-
-## Worktree-safe implementation status
-
-Current edits are isolated in dedicated repo worktrees for:
-- `vds-scripts`
-- `vds-skills`
-
-## Remaining validation steps
-
-1. Review capability coverage against `docs/agents/reference/who-capability-inventory.md`
-2. Review routing consistency against `docs/agents/reference/who-capability-routing-matrix.md`
-3. Re-run skills alignment from the monorepo root when it is safe to touch generated surfaces:
-   - `./WHO-project/vds-skills/scripts/verify-alignment.sh`
-4. Regenerate root `AGENTS.md` from canonical WHO skills source when it is safe to update root generated outputs:
-   - `vds-cli skills sync --agent claude`
-
-## Important constraint
-
-The root generated `AGENTS.md` lives outside these two repo worktrees. It should be synced only in a controlled follow-up step so isolated worktree implementation does not unintentionally mix with the main monorepo working tree.
-
-## Validation Commands
-
-```bash
-# Run full docs validation
-vds-cli docs validate --repo-root . --check-diataxis --check-orchestrators
-
-# Check Vietnamese translations
-vds-cli docs validate --check-vi
-
-# Fix auto-fixable issues
-vds-cli docs validate --fix
-```
-
-## Sync Commands
-
-```bash
-# Sync docs to Confluence
-vds-cli docs confluence-sync --dry-run
-
-# Generate ecosystem index
-vds-cli docs ecosystem-index --output ECOSYSTEM-DOCS.md
-```
-
-## Related
-
-- [Audit Triage Playbook](audit-triage-playbook.md)
-- [Spec Orchestrator](spec-orchestrator.md)
-- [VDS CLI](vds-cli-reference.md)
-- [Confluence](http://confluence.digital.vn/display/TTCN24/WHO-Project+Ecosystem+Documentation)

package/skills/vds-skill/vds-scripts/docs/agents/reference/vds-ai-memory-api.md

@@ -1,51 +0,0 @@
-<!-- diátaxis: reference -->
-
-# VDS AI Memory API
-
-Operational usage currently centers on the skill contract and captured decision records.
-
-## Sources
-
-- `vds-ai-memory-skill` (`WHO-project/vds-skills/skills/vds-ai-memory-skill/SKILL.md`)
-- [Use VDS AI memory](../how-to/02-using-vds-ai-memory.md)
-- [WHO project baseline](../../../AGENTS.md)
-
-## CLI Commands (Primary)
-
-The `vds-cli memory` subcommand wraps the REST API with session management, auth, and error formatting.
-
-```bash
-vds-cli memory search "auth patterns" --limit 5
-vds-cli memory store "decision text" --category code --importance high --tags tag1,tag2
-vds-cli memory get <memory_id>
-vds-cli memory sessions
-vds-cli memory health
-vds-cli memory --json-only stats
-```
-
-Use the routed form for normal execution. Place global flags like `--json-only` before the subcommand. For detailed subcommand help, use `./scripts/worktree_uv.sh run --project memory_orchestrator vds-memory --help`.
-
-## REST API (curl fallback)
-
-Base URL (`/api/v1`) resolves in this order:
-
-1. `VDS_MEMORY_API_URL`
-2. `http://localhost:${API_PORT}` (when `API_PORT` is set)
-3. `http://localhost:8000`
-
-| Endpoint | Method | Description |
-|----------|--------|-------------|
-| `/sessions` | POST | Create a session |
-| `/memories` | POST | Store a memory |
-| `/memories/search` | POST | Search memories |
-| `/memories/<id>` | GET | Retrieve memory by ID |
-| `/health` | GET | Health check |
-| `/hooks/session-context` | POST | **Phase 6 HX.2** — Hook proxy for SessionStart pre-load (returns `{additionalContext}`) |
-| `/hooks/session-persist` | POST | **Phase 6 HX.2** — Hook proxy for Stop auto-persist (session summary + decisions) |
-
-See the skill file (`WHO-project/vds-skills/skills/vds-ai-memory-skill/SKILL.md`) for curl examples. The two `/hooks/*` endpoints are registered as `"type": "http"` hooks in `.claude/settings.local.json` alongside the corresponding `vds-cli memory-*` command hooks as a dual-path safety net (HTTP non-2xx is non-blocking in Claude Code, so the command path is the fallback).
-
-## Practical Contract
-
-- Read and write memory through the approved skill workflow.
-- Store concise, durable decisions with supporting evidence.

package/skills/vds-skill/vds-scripts/docs/agents/reference/vds-cli-reference.md

@@ -1,34 +0,0 @@
-<!-- diátaxis: reference -->
-
-# VDS CLI Reference
-
-`vds-cli` is the unified router for workspace orchestrators.
-
-## Primary Source
-
-- [vds_cli README](../../../vds_cli/README.md)
-
-## Common Entry Points
-
-- `vds-cli env status`
-- `vds-cli status`
-- `vds-cli scheduler ...`
-- `vds-cli version`
-- `vds-cli regenerate-manifest`
-- `vds-cli jira ...`
-- `vds-cli confluence ...`
-- `vds-cli bitbucket ...`
-- `vds-cli git ...`
-- `vds-cli openapi ...`
-- `vds-cli spec ...`
-- `vds-cli schema ...`
-- `vds-cli diagrams ...`
-- `vds-cli google-sheets ...`
-
-Direct package executables may use different names than the routed `vds-cli` subcommands. **Direct executables are internal implementation detail — always use `vds-cli`.**
-
-As of the current Phase 2 lane, `vds-schema-convert --help` and `vds-cli diagrams --help` now expose structured Typer-based discovery surfaces rather than ad hoc manual output, which makes them safer entrypoints for AI-agent command discovery.
-
-For command-family routing, start with `vds-scripts-skill`. For deep specialist workflows, route to the corresponding specialist skill.
-For shared env/config/cache path behavior, see `portable-paths-and-config.md`.
-For the verified routed command inventory, see `cli-help-matrix.md`.

package/skills/vds-skill/vds-scripts/docs/agents/reference/who-capability-inventory.md

@@ -1,96 +0,0 @@
-<!-- diátaxis: reference -->
-
-# WHO Capability Inventory
-
-This document records the current WHO ecosystem capability surface for routing, documentation, and validation.
-
-## 1. Routed command surfaces
-
-These are the primary user-facing command families exposed through `vds-cli`.
-
-### Bootstrap and discovery
-- `vds-cli env ...`
-- `vds-cli status`
-- `vds-cli doctor`
-- `vds-cli docs ...`
-
-### Integrations
-- `vds-cli jira ...`
-- `vds-cli confluence ...`
-- `vds-cli bitbucket ...`
-- `vds-cli git ...`
-- `vds-cli elastic ...`
-- `vds-cli grafana ...`
-- `vds-cli sonarqube ...`
-
-### Documentation and validation
-- `vds-cli openapi ...`
-- `vds-cli links ...`
-- `vds-cli structure ...`
-- `vds-cli schema ...`
-- `vds-cli pdf ...`
-- `vds-cli diagrams ...`
-- `vds-cli excel ...`
-- `vds-cli google-sheets ...`
-
-### Development and workflow
-- `vds-cli intellij ...`
-- `vds-cli tasks ...`
-- `vds-cli lsp ...`
-- `vds-cli spec ...`
-- `vds-cli audit ...`
-- `vds-cli circular-dependency ...`
-
-## 2. Standalone workspace capabilities
-
-These WHO packages matter operationally even if they are not all presented as primary routed command families inside one platform skill.
-
-- `markdown_orchestrator`
-- `hexagonal_orchestrator`
-- `mcp_server`
-- `multi_agent_orchestrator`
-
-## 3. Shared and internal support layers
-
-These shape the ecosystem but are not primary user task entrypoints.
-
-- `vds_cli_common`
-
-## 4. Skills ecosystem linkage
-
-The WHO skills catalog provides specialist workflow ownership alongside the scripts workspace.
-
-### Platform-routing skill
-- `vds-scripts-skill`
-
-### Specialist skills
-- `audit-orchestrator-skill`
-- `llm-analysis-skill`
-- `spec-creation-skill`
-- `cli-development-skill`
-- `lsp-skill`
-- `circular-dependency-skill`
-- `research-skill`
-- `code-review-graph-skill`
-- `app-config-discovery-skill`
-- `repomix-skill`
-- `grepai-skill`
-- `hexagonal-compliance-skill`
-- `vds-ai-memory-skill`
-
-## 5. Derived and generated surfaces
-
-These are important for agents and operators but are not canonical authoring roots.
-
-- `WHO-project/vds-skills/registry.yaml`
-- `WHO-project/vds-skills/AGENTS.md`
-- root generated `AGENTS.md`
-- `.agent/skills/`
-
-## 6. Validation use
-
-Use this inventory with:
-- `vds-scripts-skill` references
-- `docs/agents/reference/who-capability-routing-matrix.md`
-- `WHO-project/vds-skills/registry.yaml`
-- alignment/sync checks before closure

package/skills/vds-skill/vds-scripts/docs/agents/reference/who-capability-routing-matrix.md

@@ -1,14 +0,0 @@
-<!-- diátaxis: reference -->
-
-# WHO Capability Routing Matrix
-
-| Intent | Human Doc Surface | Command Family / CLI | Skill Owner |
-|-------|--------------------|----------------------|-------------|
-| Bootstrap workspace | `reference/vds-cli-reference.md` | `vds-cli env/status/doctor` | `vds-scripts-skill` |
-| Use Jira/Confluence/Bitbucket/Git | `reference/cli-commands.md` | `vds-cli jira/confluence/bitbucket/git` | `vds-scripts-skill` |
-| Validate docs or platform artifacts | `reference/cli-commands.md` | `vds-cli openapi/links/structure/schema/pdf/diagrams/excel/google-sheets` | `vds-scripts-skill` |
-| Run audit workflow | `reference/cli-commands.md` + audit docs | `vds-cli audit` | `audit-orchestrator-skill` |
-| Create or validate spec | scripts/spec docs | `vds-cli spec` | `spec-creation-skill` |
-| Configure LSP | specialist docs | `vds-cli lsp` | `lsp-skill` |
-| Analyze dependency cycles | specialist docs | `vds-cli circular-dependency` | `circular-dependency-skill` |
-| Research a problem | skills references | mixed tools | `research-skill` |

package/skills/vds-skill/vds-scripts/docs/agents/tutorials/feature-progression-guide.md

@@ -1,112 +0,0 @@
-<!-- diátaxis: tutorial -->
-
-# Feature Progression Guide
-
-Continue your WHO ecosystem journey beyond the [Zero to Productive Developer](../tutorials/zero-to-productive-developer.md) tutorial.
-
-## Day 8 — Multi-Project Audit
-
-Run audits across multiple repositories in a single command.
-
-```bash
-# Audit all projects in a department
-vds-cli audit --department INSURANCE --checklist DEP-001
-
-# Audit specific repos
-vds-cli audit --repo repo-a,repo-b,repo-c --checklist PAR-001
-```
-
-**Learn:** Audit configuration, checklist selection, report interpretation.
-
-## Day 9 — Confluence Integration
-
-Upload audit evidence and reports to Confluence automatically.
-
-```bash
-# Sync evidence after audit
-vds-cli docs confluence-sync --repo my-service
-
-# Generate quality score report
-vds-cli docs quality-score
-```
-
-**Learn:** Confluence sync targets, evidence format, page structure.
-
-## Day 10 — Hexagonal Compliance
-
-Verify your service follows clean architecture principles.
-
-```bash
-# Check hexagonal compliance
-vds-cli hexagonal --repo my-service
-
-# View detailed boundary report
-vds-cli hexagonal --repo my-service --format json
-```
-
-**Learn:** Port/adapter boundaries, dependency direction, violation patterns.
-
-## Day 11 — Circular Dependency Detection
-
-Identify risky dependency cycles across microservices.
-
-```bash
-# Detect cycles in a project
-vds-cli circular-dependency --project INSURANCE
-
-# Export graph for visualization
-vds-cli circular-dependency --project INSURANCE --format mermaid
-```
-
-**Learn:** Dependency manifests, cycle classification, remediation strategies.
-
-## Day 12 — Git Worktree Management
-
-Use worktrees for parallel feature development without branch switching.
-
-```bash
-# Create a worktree for a feature
-vds-cli git worktree-create --branch feature/my-change
-
-# List all worktrees
-vds-cli git worktree-list
-```
-
-**Learn:** Worktree lifecycle, repair, cleanup, multi-repo workflows.
-
-## Day 13 — Custom Orchestrator Exploration
-
-Explore advanced orchestrators for specialized tasks.
-
-```bash
-# Research a topic combining local and web search
-vds-cli research --query "best practices for API pagination"
-
-# Generate a diagram from code
-vds-cli diagrams --repo my-service --format png
-
-# Convert schema formats
-vds-cli schema --input openapi.yaml --output jsonschema
-```
-
-**Learn:** Orchestrator selection, output formats, chaining commands.
-
-## Day 14 — Multi-Agent Workflows
-
-Coordinate parallel agent teams for complex tasks.
-
-```bash
-# Run a multi-agent workflow
-vds-cli multi-agent --workflow spec-to-impl --spec my-spec.md
-
-# Monitor agent progress
-vds-cli multi-agent --status
-```
-
-**Learn:** Workflow definitions, agent roles, result aggregation.
-
-## Beyond Day 14
-
-- [Contribute a new orchestrator](../how-to/contribute-new-orchestrator.md)
-- [Author a custom skill](../how-to/add-a-skill.md)
-- [Explore the full orchestrator index](../../reference/orchestrator-index.md)

package/skills/vds-skill/vds-scripts/docs/agents/tutorials/index.md

@@ -1,36 +0,0 @@
-<!-- diátaxis: tutorial -->
-
-# Tutorial Index
-
-> Step-by-step tutorials for WHO ecosystem newcomers.
-
-## Available Tutorials
-
-| Tutorial | Goal | Duration |
-|----------|------|----------|
-| [Zero to Productive Developer](zero-to-productive-developer.md) | Day 0 to Day 7 onboarding | ~2 hours |
-| [VDS AI Memory](02-using-vds-ai-memory.md) | Cross-session memory basics | ~15 min |
-
-## Recommended Path
-
-### Day 1
-1. Read [Agent Operational Contract](../reference/agent-operational-contract.md)
-2. Complete [Install Guide](../how-to/install-and-bootstrap-who-scripts-and-skills.md)
-
-### Day 2-3
-3. Run first audit with [Audit Triage Playbook](../reference/audit-triage-playbook.md)
-
-### Day 4-7
-4. Explore skills with [Skills Reference](../reference/skills-reference.md)
-5. Learn orchestrators with [Orchestrator Index](../reference/orchestrator-index.md)
-
-```bash
-# Quick check: onboarding status
-vds-cli progress report --phase onboarding
-```
-
-## Related
-
-- [How-To Guides](../how-to/index.md)
-- [Reference Docs](../reference/index.md)
-- [Orchestrator Index](../reference/orchestrator-index.md)

package/skills/vds-skill/vds-scripts/docs/agents/tutorials/quick-start.md

@@ -1,50 +0,0 @@
-<!-- diátaxis: tutorial -->
-
-# Quick Start
-
-Get the WHO ecosystem running in under 5 minutes.
-
-## Prerequisites
-
-- Python 3.14+
-- [uv](https://docs.astral.sh/uv/getting-started/installation/)
-- Docker (for Postgres and Redis)
-
-## Install
-
-```bash
-# Clone the main repository
-git clone https://bitbucket.org/viettel-digital-services/vds-scripts
-cd vds-scripts
-
-# Sync dependencies
-uv sync
-
-# Verify installation
-vds-cli --help
-```
-
-## First Command
-
-```bash
-# Run a health check
-vds-cli docs validate --help
-
-# Check ecosystem status
-vds-cli docs ecosystem-report
-```
-
-## Common Workflows
-
-After installation, most developers follow one of these common workflows to get productive quickly:
-
-- [Run an audit with the orchestrator](../how-to/audit-orchestrator.md) — end-to-end project audit.
-- [Sync skills across agents](../how-to/skill-sync.md) — keep skills up to date.
-- [Validate documentation quality](../how-to/docs-quality.md) — check docs before a release.
-- [Schedule recurring jobs with the scheduler](../how-to/scheduler-workflow.md) — cron-like task management.
-
-## Next Steps
-
-- [System Requirements](../reference/system-requirements.md)
-- [Install and Bootstrap](../how-to/install-and-bootstrap-who-scripts-and-skills.md)
-- [Zero to Productive Developer](../tutorials/zero-to-productive-developer.md)

package/skills/vds-skill/vds-scripts/docs/agents/tutorials/who-skills-and-scripts-onboarding.md

@@ -1,47 +0,0 @@
-<!-- diátaxis: tutorial -->
-
-# WHO Skills And Scripts Onboarding
-
-This tutorial gives new human contributors and AI agents a fast orientation to the current WHO ecosystem.
-
-## 1. Understand the canonical model
-
-`WHO-project` is the authoritative home for:
-- reusable skills in `WHO-project/vds-skills/skills/`
-- routed scripts and orchestrators in `WHO-project/vds-scripts/`
-
-## 2. Know the two main entry styles
-
-- use `vds-scripts-skill` to route platform tasks and command-family selection
-- use specialist skills for deep workflow guidance
-
-## 3. Install and bootstrap first
-
-Before deeper task routing, follow `../how-to/install-and-bootstrap-who-scripts-and-skills.md` so both the scripts workspace and the skills catalog are verifiably ready.
-
-## 4. Start with these commands
-
-If you are inside a dedicated `vds-scripts` worktree, prefer the worktree-safe wrapper:
-
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli env status`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli spec --help`
-
-## 5. Edit only canonical sources
-
-- edit skills under `WHO-project/vds-skills/skills/`
-- keep `.agent/skills/` as mirror/symlink-only
-- sync generated agent surfaces from the monorepo root after skill changes
-
-## 6. Learn the routing model
-
-If the task is broad and platform-oriented, start with `vds-scripts-skill`.
-If the task is specialist or phase-sensitive, route to the appropriate specialist skill.
-
-## Related Documents
-
-- [VDS CLI Reference](vds-cli-reference.md)
-- [Orchestrator Index](orchestrator-index.md)
-- [Skills Reference](skills-reference.md)
-- [Confluence Hub](http://confluence.digital.vn/display/TTCN24/WHO-Project+Ecosystem+Documentation)