[Extension]: Add AgentDocxV2 :AgentDocx evolved: same pipeline + far more autonomous Ticket Manager

[ahmed200346]

Extension ID

agentdocx-speckitv2

Extension Name

AgentDocx SpecKit V2

Version

0.0.7

Description

AgentDocx evolved: same pipeline + far more autonomous Ticket Manager (5 CLI, per-project Kanban, bulk sync, auto-switch, Auditor).

Author

Ahmed Aziz Ammar

Repository URL

https://github.com/ahmed200346/Extension_GithubSpecKit

Download URL

https://github.com/ahmed200346/Extension_GithubSpecKit/archive/refs/tags/v0.0.7.zip

License

MIT

Homepage (optional)

https://github.com/ahmed200346/Extension_GithubSpecKit

Documentation URL (optional)

https://github.com/ahmed200346/Extension_GithubSpecKit/blob/main/README.md

Changelog URL (optional)

https://github.com/ahmed200346/Extension_GithubSpecKit/blob/main/agentdocx-speckit/CHANGELOG.md

Required Spec Kit Version

=0.1.0

Required Tools (optional)

- python (>=3.10) - required
- node (>=18) - required
- postgresql - required

Number of Commands

0

Number of Hooks (optional)

No response

Tags

integration, kanban, ticket-management, vscode-extension, multi-agent

Key Features

• Ticket Manager 0.0.7 autonome : Dual Watchers (StructureWatcher + StatusWatcher) + bulk sync tasks map + Auditor (75) — vs V1 mono-watcher racine .task_runtime + Copilot-only
• 5 CLI unifiés (Claude Code, Codex, Copilot, Cursor, Windsurf) via Universal Contract specs/{project}/.task_runtime — vs V1 Copilot-only
• Isolation par projet specs/{project}/.task_runtime (plus de conflit racine, plus de BOM bloquant)
• 3 providers LLM (ollama gemma4:31b-cloud, gemini 3.1-flash-lite, nvidia) via llm_client.py Strategy — vs V1 ollama seul
• Auto-création BDD FinalDB (ticket_metrics) + cascade Project→tickets + scrollbar light fix

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on: Windows 11 + Spec Kit 0.12 + VS Code 1.125
Test project: 001-mini-notes (6 tasks) + 002-course-manager (22 tasks)
Scenarios: 1) spec → plan → tasks → current-task.json 29 todo 2) bulk T001-T003 done → Kanban 3/29 + Metrics 85.5 COMPLIANT 3) Copilot + Claude Code via AGENTS.md/CLAUDE.md

Example Usage

# 1. Install V2
specify extension add agentdocx-speckitV2 --from https://github.com/ahmed200346/Extension_GithubSpecKit/archive/refs/tags/v0.0.7.zip

# 2. Clone + env (RepoSigma main, agentdocx-speckit/ au même niveau)
git clone https://github.com/ahmed200346/Extension_GithubSpecKit.git
cd Extension_GithubSpecKit
cp .env.example .env  # remplir GEMINI_API_KEY

# 3. VS Code : AgentDocx: Start Server + Start Watcher
# 4. Spec Kit flow
/specify "Mini notes app"  # ou /speckit-specify
/speckit-tasks             # → current-task.json 6×todo
# 5. Implement + Kanban auto
/speckit-implement T001    # → current-task.json in_progress → done → Kanban 1/6 + Metrics 85.5

Proposed Catalog Entry

schema_version: "1.0"
extension:
  id: "agentdocx-speckitv2"
  name: "AgentDocx SpecKit V2"
  version: "0.0.7"
  description: "Full-stack multi-agent specification pipeline with VS Code extension control, automated Kanban/Jira sync, and React monitoring dashboard."
  author: "ahmed200346"
  repository: "https://github.com/ahmed200346/Extension_GithubSpecKit"
  license: "MIT"
  homepage: "https://github.com/ahmed200346/Extension_GithubSpecKit"
  category: "integration"
  effect: "read-write"
requires:
  speckit_version: ">=0.1.0"
  tools:
    - name: python
      version: ">=3.10"
      required: true
    - name: node
      version: ">=18"
      required: true
    - name: postgresql
      version: ">=12"
      required: true
provides:
  scripts:
    - name: "agentdocx-doc-pipeline"
      file: "agentdocx-speckit/scripts/bash/create-doc-pipeline.sh"
      description: "Runs the AgentDocx multi-agent documentation pipeline"
      runtimes:
        - "bash"

Additional Context

No response

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Thanks for submitting AgentDocx SpecKit V2! I've run the automated validation checks and found several issues that need to be fixed before this extension can be added to the catalog.

---

❌ Validation Failed

The following checks did not pass:

1. Version format (version)

Submitted: V2.0.0
Required: semver format X.Y.Z with no prefix (e.g., 2.0.0)

The version field must be plain digits separated by dots — no v or V prefix.

Fix: Change the version to 2.0.0 (or whichever version you intend to publish).

---

2. Missing LICENSE file in repository

The repository at https://github.com/ahmed200346/Extension_GithubSpecKit does not contain a LICENSE file in the root directory. This is a required file for catalog inclusion.

Fix: Add a LICENSE file to the root of your repository (e.g., an MIT license text file named LICENSE).

---

3. Download URL is not a direct zip download

Submitted: https://github.com/ahmed200346/Extension_GithubSpecKit/releases/tag/ExtensionAgentDocxV2

This is a releases page URL, not a downloadable .zip file. The download URL must point directly to an archive or asset that can be downloaded, following one of these patterns:

• https://github.com/<owner>/<repo>/archive/refs/tags/v<version>.zip
• https://github.com/<owner>/<repo>/releases/download/<tag>/<asset>.zip

Fix: Provide the direct zip download URL. For your existing release, this would look like:
https://github.com/ahmed200346/Extension_GithubSpecKit/archive/refs/tags/ExtensionAgentDocxV2.zip

However, we also recommend creating a new release with a semver-compliant tag (see next point).

---

4. Release tag does not follow vX.Y.Z convention

Current tag: ExtensionAgentDocxV2
Expected: A semver tag like v2.0.0

The release tag should follow the vX.Y.Z convention so the download URL can be derived predictably.

Fix: Create a new GitHub release with tag v2.0.0 (matching your submitted version), then update the download URL accordingly:
https://github.com/ahmed200346/Extension_GithubSpecKit/archive/refs/tags/v2.0.0.zip

---

✅ Checks That Passed

• Extension ID format (agentdocx-speckitv2) — valid lowercase-with-hyphens format
• Repository exists and is publicly accessible
• extension.yml manifest present in repository root
• README.md present in repository root
• All submission checklists are checked

---

How to Resubmit

Please:

1. Add a LICENSE file to your repository root
2. Create a new release with tag v2.0.0
3. Update your submission with:
   • Version: 2.0.0
   • Download URL: https://github.com/ahmed200346/Extension_GithubSpecKit/archive/refs/tags/v2.0.0.zip

Once you've made these fixes, you can edit this issue to update the fields and a maintainer can re-trigger validation.

---

Posted on behalf of @KSchlobohm by GitHub Copilot (model: claude-sonnet-4.6, autonomous)

Generated by 🧩 Add Community Extension from Issue Submission for issue #4342 · 70.9 AIC · ⌖ 10.9 AIC · ⊞ 35.3K · ◷

[ahmed200346]

Thank you for your verification please reverify now if all the required fields are corrected

[github-actions]

Pull request created: #4347

Generated by Add Community Extension from Issue Submission · 224.6 AIC · ⌖ 16.4 AIC · ⊞ 35.3K

[KSchlobohm]

@ahmed200346 Thanks for the submission. A catalog entry has to match the extension as actually published, and the specify CLI enforces version parity between the release manifest and the catalog entry — so this can't be listed while they disagree.

Please work through Copilot's review and make sure the published release and the catalog entry line up. Ping me once it's updated and I'll re-check. Thanks!

[ahmed200346]

Thanks again please review again now with this issue and the version in extension are aligned