AST-127864 - CX Spec Kit Deployment

[cx-anurag-dalke]

📝 Almost There!

1. Review the .cx-spec/memory/ folder carefully - This is the source of truth for all specifications. Accurate memory files lead to accurate specs.
2. Merge this PR to enable CX Spec Kit in your repository
3. Start spec-driven development in Claude with cx-spec.specify <what you want to build> (/cx-spec.specify in command-based clients)

---

🚀 Quick Start

Basic:
  📝 specify  →  📋 plan  →  ✅ tasks  →  🔨 implement

Recommended:
  📝 specify  →  🔍 clarify  →  📋 plan  →  ✅ tasks  →  🔬 analyze  →  🔨 implement
       │             │             │            │             │              │
    Define        Refine        Create       Break        Review         Execute
    feature        spec          plan         down        artifacts
    (WHAT)                       (HOW)

Commands: /cx-spec.architect map, /cx-spec.constitution, /cx-spec.specify, /cx-spec.clarify, /cx-spec.plan, /cx-spec.tasks, /cx-spec.analyze, /cx-spec.implement

---

📖 Example: Adding Login Feature

1️⃣  /cx-spec.specify "AST-123456 add login with email and password"
    → Creates: specs/ast-123456-add-login/spec.md

2️⃣  /cx-spec.clarify
    → AI asks: "OAuth support? Remember me? Max login attempts?"
    → You answer, `spec.md` is updated

3️⃣  /cx-spec.plan
    → Creates: specs/ast-123456-add-login/plan.md
    → Defines: tech stack, API endpoints, components, DB schema

4️⃣  /cx-spec.tasks
    → Creates: specs/ast-123456-add-login/tasks.md
    → Breaks plan into ordered, actionable tasks

5️⃣  /cx-spec.analyze
    → Reviews spec + plan + tasks for consistency
    → Reports: gaps, conflicts, missing edge cases

6️⃣  /cx-spec.implement
    → Executes tasks one by one
    → You review each step before proceeding

---

📂 Spec Folder Structure

After running /cx-spec.specify, your repo will have a specs/ folder:

specs/
└── ast-123456-add-login/
    ├── spec.md          # Feature specification (from /cx-spec.specify)
    ├── plan.md          # Technical implementation plan (from /cx-spec.plan)
    ├── architecture.md  # Feature-specific architecture (from /cx-spec.plan)
    └── tasks.md         # Ordered task breakdown (from /cx-spec.tasks)

Each feature gets its own folder and branch named <jira-id>-<short-name>

---

📁 Files Added

• .claude/commands/ - Claude AI commands
• .cx-spec/scripts/ - Automation scripts
• .cx-spec/templates/ - Specification templates
• .cx-spec/config.json - Toolkit configuration

---

📋 Deployment Details

• JIRA ID: AST-127864

• AI Targets: claude

• Constitution Generated: true

• Workflow Run: #23303182924

• Triggered by: @cx-anurag-dalke

[github-actions]

Checkmarx One – Scan Summary & Details – 2de6d9ce-1af0-4845-9628-5806d88d125a

---

New Issues (1)

Checkmarx found the following issues in this Pull Request

#	Severity	Issue	Source File / Package	Checkmarx Insight
1		CVE-2026-33186	Go-google.golang.org/grpc-v1.75.0	details Description: In versions prior to 1.79.3, gRPC-Go contains an authorisation bypass caused by improper input validation of the HTTP/2: path pseudo-header. The se... Attack Vector: NETWORK Attack Complexity: LOW Vulnerable Package