An AI-powered skill that transforms a JIRA epic or BRD into a publication-ready Solution Design Document.
200+ Capillary endpoints across v1.1 / v2 / v3. The SA must identify which exact endpoint fits — then set up OAuth2 auth, craft a test payload, and execute a live call to confirm it works before a single SDD line is written.
Every SA structures sections, tables, and diagrams differently. Missing ADRs, incomplete NFRs, no Data Mapping — peer review and client handoff become inconsistent and require rework.
Before writing a single line, the SA pieces together context from JIRA epics, BRD PDFs, past Confluence SDDs, email threads, and colleague notes. There is no single source of truth — context is routinely incomplete or contradictory.
Many requirements can be satisfied through native Capillary product config (Tier 1) with no code needed. But there is no structured catalog — SAs manually check menus, confirm valid values, and chase the Config Team to verify what is configurable vs. what needs a custom integration.
The skill solves all four. It queries Confluence + JIRA for full context, checks the Capillary Docs MCP to resolve product configs, discovers and live-validates APIs, and enforces a 25-item structure checklist — all automatically.
User pastes a BRD, opens a JIRA epic in IDE, or discusses integration requirements — skill fires without the slash command.
These test scenarios verify the skill routes to the correct SDD mode and solution tier. Each can be run by providing the input text and checking the skill's Step 3 + Step 4 decisions.
Auto-fetch epic stories · search existing SDDs for reuse
Verify every endpoint schema, version, headers before writing
Validate every Mermaid diagram for syntax before including
atlassian, jira, cap-docs, capillary_docs — resolved by role, not exact name
Health check runs at Step 0 — before any work begins. Capillary Docs unavailable = full stop (no unverified APIs can be written). Other MCP failures = proceed with tagged notes in the SDD.
mcp__capillary_docs__search-specs for endpoint[UNVERIFIED] · no curl · client must confirm pathCustom APIs designed by the SA — no MCP lookup needed. Tagged ✓ VALIDATED after live HTTP test in Step 4b.
Key Notes: ✓ VERIFIED (Capillary Docs). Curl with realistic sample data included.
Key Notes: [UNVERIFIED — not found in Capillary Docs]. No curl. Client must confirm before implementation.
--headers arg — explicit override, highest priorityCAPILLARY_BEARER_TOKEN env → Authorization: BearerCAPILLARY_API_KEY + SECRET → OAuth2 POST → JWT cached for session[SKIPPED — set credentials]| Status | Meaning | SDD Tag |
|---|---|---|
| 200–299 | Confirmed live | ✓ VALIDATED |
| 401 / 403 | Endpoint exists; test auth | ✓ VALIDATED |
| 404 | Path may be wrong | ⚠ FAILED |
| Network err | Timeout / unreachable | ⚠ FAILED |
| No creds | User skipped | ⚠ SKIPPED |
Before asking for test data, the skill checks for CAPILLARY_BEARER_TOKEN, CAPILLARY_API_KEY, and SECRET. If none found → explicitly asks user. Never silently skips. User can type "skip validation" to proceed without credentials.
CAPILLARY_CLUSTER env: in → in.api.capillarytech.com · eu, apac2, apac, us — token cached per session.
Core rule: Assign every requirement to the LOWEST viable tier. Each escalation must be justified with an ADR.
Section 9 elements (Tier + Rationale, Process Flow, Sequence Diagram, API Spec, Data Mapping) are identical depth in both formats — Lite SDD = same rigour, smaller scope.
All 7 interview questions sent in a single message — never spread across turns. Prevents multi-turn friction. Unanswered → tagged [ASSUMPTION - TO BE CONFIRMED].
India / APAC / EU / US — cluster, currency, data residency
New org or existing? Any active config?
Mobile / POS / web / CRM / ecommerce?
OTP, SSO, social, guest?
Members, TPS, batch sizes?
Phase exclusions, deferred features?
Test customer ID, mobile, till ID — needed for Step 4b live API calls
Never publish without explicit user confirmation. The skill proposes the path, waits for "confirm", then calls Atlassian MCP. Local Markdown is always written first — Confluence is entirely optional.
The Capillary Docs MCP searches 200+ endpoints to find the exact API that fits the requirement — no manual docs digging.
validate_api.py calls endpoints live before documenting. HTTP 200 or 4xx proves the path exists. 404 flags a bad path immediately.
25-item checklist enforces all 11 sections, ADRs, NFRs, data mapping columns, and realistic JSON samples — every time.
Full SDD for new integrations. Lite SDD for additive changes. 5-tier Golden Path assigns the lowest viable architecture per requirement.
Type the slash command or just paste a BRD — the skill auto-detects context and routes to the correct path automatically.
New project Full SDD: 1–1.5 weeks → hours. Change Request Lite SDD: 2–3 days → under an hour. From JIRA to publication-ready Markdown.
Connect the client's or Capillary's custom-logic git repos so the skill understands existing implementation patterns, past Neo/Connect+ jobs, and reusable code — avoiding re-documenting what is already built and surfacing integration constraints early.
Auto-search Confluence for related SDDs during generation and surface dependency links ("this flow reuses the auth pattern from ADAC SDD §4.2") — reducing duplicate design work and keeping the document graph consistent across clients.
Automatically fire the skill when a JIRA epic transitions to In Progress or a custom SDD Required status — zero-touch initiation, SDD draft in Confluence before the SA's kickoff call even begins.
Capture org-specific defaults — preferred cluster, naming conventions, standard NFR targets, approved tech stack — per client region (India / US / EMEA / APAC) so every SDD starts closer to the finished state.
/capillary-sdd-review <URL> — skill reads an existing SDD from Confluence, runs the full 25-item checklist, and outputs a structured gap report with prioritised fix suggestions ready for the author to act on.