$npx -y skills add adobe/skills --skill technical-advisoryProvide advisory guidance for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM 6.5 / AMS workflows only, with public-doc citations and AMS-specific MCP verification plans. Use for conceptual questions such as statfileslevel, filter rules, UR
| 1 | # Dispatcher Technical Advisory (AMS) |
| 2 | |
| 3 | Provide deterministic guidance for AEM 6.5/AMS use cases involving the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration. |
| 4 | |
| 5 | ## Variant Scope |
| 6 | |
| 7 | - This skill is AMS-only. |
| 8 | - Scope is fixed by this skill directory; do not ask the user to choose deployment variant. |
| 9 | |
| 10 | ## MCP Tool Contract |
| 11 | |
| 12 | Use only these Dispatcher MCP tools when producing verification plans: |
| 13 | |
| 14 | - `validate` |
| 15 | - `lint` |
| 16 | - `sdk` |
| 17 | - `trace_request` |
| 18 | - `inspect_cache` |
| 19 | - `monitor_metrics` |
| 20 | - `tail_logs` |
| 21 | |
| 22 | ## Workflow |
| 23 | |
| 24 | 1. Confirm scope and assumptions. |
| 25 | 2. If the repo layout or execution path is unclear, start with [quick-start-execution-path.md](./references/dispatcher-foundation/quick-start-execution-path.md) and [repo-layout-workflows.md](./references/dispatcher-foundation/repo-layout-workflows.md). |
| 26 | 3. Use [capability-coverage-map.md](./references/technical-advisory/capability-coverage-map.md) to route prompt/tool/resource intents to the right dispatcher skill flow. |
| 27 | 4. Select a scenario path from [core7-capability-playbook.md](./references/technical-advisory/core7-capability-playbook.md) for development/debugging requests. |
| 28 | 5. For conceptual questions (e.g. statfileslevel, filter order, URL decomposition, cache invalidation), use [concepts.md](./references/technical-advisory/concepts.md) and cite official docs. |
| 29 | 6. Apply [ams-6-5-guardrails.md](./references/dispatcher-foundation/ams-6-5-guardrails.md) before recommendations (tier boundaries, variables, flush ACL, immutable constraints). |
| 30 | 7. Convert the selected playbook to exact MCP commands with [playbook-command-linkage.md](./references/dispatcher-foundation/playbook-command-linkage.md). |
| 31 | 8. Use curated public references for recommendations in this variant. |
| 32 | 9. Produce MCP verification steps for this variant when needed. |
| 33 | 10. Route execution-heavy changes to this variant's execution skills. |
| 34 | |
| 35 | ## Verification Scope Selection |
| 36 | |
| 37 | Use shared references for deterministic coverage: |
| 38 | |
| 39 | - [mode-specific-verification-matrix.md](./references/dispatcher-foundation/mode-specific-verification-matrix.md) |
| 40 | - [test-case-catalog.md](./references/dispatcher-foundation/test-case-catalog.md) |
| 41 | |
| 42 | ## Output Contract |
| 43 | |
| 44 | Use one of these output shapes: |
| 45 | |
| 46 | - Explanation-only question: recommendation summary + citation list from curated public-docs index. |
| 47 | - Recommendation/change question: recommendation summary + citation list + MCP verification plan with expected evidence + risk/rollback guidance and open risks. |
| 48 | |
| 49 | ## Guardrails |
| 50 | |
| 51 | - Do not claim a check was executed unless tool evidence exists. |
| 52 | - Keep variant assumptions explicit for every recommendation. |
| 53 | - For migration/cross-variant requests, produce a side-by-side variant delta plan from the verification matrix and flag when the companion variant plugin must be run separately. |
| 54 | - Follow citation discipline from `public-doc-citation-rules.md`. |
| 55 | |
| 56 | ## References |
| 57 | |
| 58 | - [core7-capability-playbook.md](./references/technical-advisory/core7-capability-playbook.md) – high-value development/debugging playbooks for the current core-7 MCP contract |
| 59 | - [capability-coverage-map.md](./references/technical-advisory/capability-coverage-map.md) – prompt/tool/resource coverage map to current dispatcher skill workflows |
| 60 | - [concepts.md](./references/technical-advisory/concepts.md) – key concepts (filter last-match, URL decomposition, statfileslevel, invalidate vs flush) for explanations |
| 61 | - [quick-start-execution-path.md](./references/dispatcher-foundation/quick-start-execution-path.md) – single entry path for broad or first-time requests |
| 62 | - [repo-layout-workflows.md](./references/dispatcher-foundation/repo-layout-workflows.md) – normalize repos to the dispatcher `src` root and likely file families |
| 63 | - [playbook-command-linkage.md](./references/dispatcher-foundation/playbook-command-linkage.md) – deterministic linkage from playbooks to MCP commands and tests |
| 64 | - [ams-6-5-guardrails.md](./references/dispatcher-foundation/ams-6-5-guardrails.md) – AMS topology/variables/flush and immutable-file constraints |
| 65 | - [public-docs-index.md](./references/dispatcher-foundation/public-docs-index.md) |
| 66 | - [public-doc-citation-rules.md](./references/dispatcher-foundation/public-doc-citation-rules.md) |
| 67 | - [mode-specific-verification-matrix.md](./references/dispatcher-foundation/mode-specific-verification-matrix.md) |
| 68 | - [test-case |