devskill 2.0.7 → 2.0.8

package/skills/azure-static-web-apps/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/azure-static-web-apps/SKILL.md

@@ -0,0 +1,315 @@
+---
+name: azure-static-web-apps
+description: Helps create, configure, and deploy Azure Static Web Apps using the SWA CLI. Use when deploying static sites to Azure, setting up SWA local development, configuring staticwebapp.config.json, adding Azure Functions APIs to SWA, or setting up GitHub Actions CI/CD for Static Web Apps.
+---
+
+## Overview
+
+Azure Static Web Apps (SWA) hosts static frontends with optional serverless API backends. The SWA CLI (`swa`) provides local development emulation and deployment capabilities.
+
+**Key features:**
+- Local emulator with API proxy and auth simulation
+- Framework auto-detection and configuration
+- Direct deployment to Azure
+- Database connections support
+
+**Config files:**
+- `swa-cli.config.json` - CLI settings, **created by `swa init`** (never create manually)
+- `staticwebapp.config.json` - Runtime config (routes, auth, headers, API runtime) - can be created manually
+
+## General Instructions
+
+### Installation
+
+```bash
+npm install -D @azure/static-web-apps-cli
+```
+
+Verify: `npx swa --version`
+
+### Quick Start Workflow
+
+**IMPORTANT: Always use `swa init` to create configuration files. Never manually create `swa-cli.config.json`.**
+
+1. `swa init` - **Required first step** - auto-detects framework and creates `swa-cli.config.json`
+2. `swa start` - Run local emulator at `http://localhost:4280`
+3. `swa login` - Authenticate with Azure
+4. `swa deploy` - Deploy to Azure
+
+### Configuration Files
+
+**swa-cli.config.json** - Created by `swa init`, do not create manually:
+- Run `swa init` for interactive setup with framework detection
+- Run `swa init --yes` to accept auto-detected defaults
+- Edit the generated file only to customize settings after initialization
+
+Example of generated config (for reference only):
+```json
+{
+  "$schema": "https://aka.ms/azure/static-web-apps-cli/schema",
+  "configurations": {
+    "app": {
+      "appLocation": ".",
+      "apiLocation": "api",
+      "outputLocation": "dist",
+      "appBuildCommand": "npm run build",
+      "run": "npm run dev",
+      "appDevserverUrl": "http://localhost:3000"
+    }
+  }
+}
+```
+
+**staticwebapp.config.json** (in app source or output folder) - This file CAN be created manually for runtime configuration:
+```json
+{
+  "navigationFallback": {
+    "rewrite": "/index.html",
+    "exclude": ["/images/*", "/css/*"]
+  },
+  "routes": [
+    { "route": "/api/*", "allowedRoles": ["authenticated"] }
+  ],
+  "platform": {
+    "apiRuntime": "node:20"
+  }
+}
+```
+
+## Command-line Reference
+
+### swa login
+
+Authenticate with Azure for deployment.
+
+```bash
+swa login                              # Interactive login
+swa login --subscription-id <id>       # Specific subscription
+swa login --clear-credentials          # Clear cached credentials
+```
+
+**Flags:** `--subscription-id, -S` | `--resource-group, -R` | `--tenant-id, -T` | `--client-id, -C` | `--client-secret, -CS` | `--app-name, -n`
+
+### swa init
+
+Configure a new SWA project based on an existing frontend and (optional) API. Detects frameworks automatically.
+
+```bash
+swa init                    # Interactive setup
+swa init --yes              # Accept defaults
+```
+
+### swa build
+
+Build frontend and/or API.
+
+```bash
+swa build                   # Build using config
+swa build --auto            # Auto-detect and build
+swa build myApp             # Build specific configuration
+```
+
+**Flags:** `--app-location, -a` | `--api-location, -i` | `--output-location, -O` | `--app-build-command, -A` | `--api-build-command, -I`
+
+### swa start
+
+Start local development emulator.
+
+```bash
+swa start                                    # Serve from outputLocation
+swa start ./dist                             # Serve specific folder
+swa start http://localhost:3000              # Proxy to dev server
+swa start ./dist --api-location ./api        # With API folder
+swa start http://localhost:3000 --run "npm start"  # Auto-start dev server
+```
+
+**Common framework ports:**
+| Framework | Port |
+|-----------|------|
+| React/Vue/Next.js | 3000 |
+| Angular | 4200 |
+| Vite | 5173 |
+
+**Key flags:**
+- `--port, -p` - Emulator port (default: 4280)
+- `--api-location, -i` - API folder path
+- `--api-port, -j` - API port (default: 7071)
+- `--run, -r` - Command to start dev server
+- `--open, -o` - Open browser automatically
+- `--ssl, -s` - Enable HTTPS
+
+### swa deploy
+
+Deploy to Azure Static Web Apps.
+
+```bash
+swa deploy                              # Deploy using config
+swa deploy ./dist                       # Deploy specific folder
+swa deploy --env production             # Deploy to production
+swa deploy --deployment-token <TOKEN>   # Use deployment token
+swa deploy --dry-run                    # Preview without deploying
+```
+
+**Get deployment token:**
+- Azure Portal: Static Web App → Overview → Manage deployment token
+- CLI: `swa deploy --print-token`
+- Environment variable: `SWA_CLI_DEPLOYMENT_TOKEN`
+
+**Key flags:**
+- `--env` - Target environment (`preview` or `production`)
+- `--deployment-token, -d` - Deployment token
+- `--app-name, -n` - Azure SWA resource name
+
+### swa db
+
+Initialize database connections.
+
+```bash
+swa db init --database-type mssql
+swa db init --database-type postgresql
+swa db init --database-type cosmosdb_nosql
+```
+
+## Scenarios
+
+### Create SWA from Existing Frontend and Backend
+
+**Always run `swa init` before `swa start` or `swa deploy`. Do not manually create `swa-cli.config.json`.**
+
+```bash
+# 1. Install CLI
+npm install -D @azure/static-web-apps-cli
+
+# 2. Initialize - REQUIRED: creates swa-cli.config.json with auto-detected settings
+npx swa init              # Interactive mode
+# OR
+npx swa init --yes        # Accept auto-detected defaults
+
+# 3. Build application (if needed)
+npm run build
+
+# 4. Test locally (uses settings from swa-cli.config.json)
+npx swa start
+
+# 5. Deploy
+npx swa login
+npx swa deploy --env production
+```
+
+### Add Azure Functions Backend
+
+1. **Create API folder:**
+```bash
+mkdir api && cd api
+func init --worker-runtime node --model V4
+func new --name message --template "HTTP trigger"
+```
+
+2. **Example function** (`api/src/functions/message.js`):
+```javascript
+const { app } = require('@azure/functions');
+
+app.http('message', {
+    methods: ['GET', 'POST'],
+    authLevel: 'anonymous',
+    handler: async (request) => {
+        const name = request.query.get('name') || 'World';
+        return { jsonBody: { message: `Hello, ${name}!` } };
+    }
+});
+```
+
+3. **Set API runtime** in `staticwebapp.config.json`:
+```json
+{
+  "platform": { "apiRuntime": "node:20" }
+}
+```
+
+4. **Update CLI config** in `swa-cli.config.json`:
+```json
+{
+  "configurations": {
+    "app": { "apiLocation": "api" }
+  }
+}
+```
+
+5. **Test locally:**
+```bash
+npx swa start ./dist --api-location ./api
+# Access API at http://localhost:4280/api/message
+```
+
+**Supported API runtimes:** `node:18`, `node:20`, `node:22`, `dotnet:8.0`, `dotnet-isolated:8.0`, `python:3.10`, `python:3.11`
+
+### Set Up GitHub Actions Deployment
+
+1. **Create SWA resource** in Azure Portal or via Azure CLI
+2. **Link GitHub repository** - workflow auto-generated, or create manually:
+
+`.github/workflows/azure-static-web-apps.yml`:
+```yaml
+name: Azure Static Web Apps CI/CD
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    types: [opened, synchronize, reopened, closed]
+    branches: [main]
+
+jobs:
+  build_and_deploy:
+    if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.action != 'closed')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Build And Deploy
+        uses: Azure/static-web-apps-deploy@v1
+        with:
+          azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}
+          repo_token: ${{ secrets.GITHUB_TOKEN }}
+          action: upload
+          app_location: /
+          api_location: api
+          output_location: dist
+
+  close_pr:
+    if: github.event_name == 'pull_request' && github.event.action == 'closed'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: Azure/static-web-apps-deploy@v1
+        with:
+          azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}
+          action: close
+```
+
+3. **Add secret:** Copy deployment token to repository secret `AZURE_STATIC_WEB_APPS_API_TOKEN`
+
+**Workflow settings:**
+- `app_location` - Frontend source path
+- `api_location` - API source path
+- `output_location` - Built output folder
+- `skip_app_build: true` - Skip if pre-built
+- `app_build_command` - Custom build command
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| 404 on client routes | Add `navigationFallback` with `rewrite: "/index.html"` to `staticwebapp.config.json` |
+| API returns 404 | Verify `api` folder structure, ensure `platform.apiRuntime` is set, check function exports |
+| Build output not found | Verify `output_location` matches actual build output directory |
+| Auth not working locally | Use `/.auth/login/<provider>` to access auth emulator UI |
+| CORS errors | APIs under `/api/*` are same-origin; external APIs need CORS headers |
+| Deployment token expired | Regenerate in Azure Portal → Static Web App → Manage deployment token |
+| Config not applied | Ensure `staticwebapp.config.json` is in `app_location` or `output_location` |
+| Local API timeout | Default is 45 seconds; optimize function or check for blocking calls |
+
+**Debug commands:**
+```bash
+swa start --verbose log        # Verbose output
+swa deploy --dry-run           # Preview deployment
+swa --print-config             # Show resolved configuration
+```

package/skills/azure-static-web-apps/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/azure-static-web-apps`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/bigquery-pipeline-audit/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/bigquery-pipeline-audit/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: bigquery-pipeline-audit
+description: 'Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness. Returns a structured report with exact patch locations.'
+---
+
+# BigQuery Pipeline Audit: Cost, Safety and Production Readiness
+
+You are a senior data engineer reviewing a Python + BigQuery pipeline script.
+Your goals: catch runaway costs before they happen, ensure reruns do not corrupt
+data, and make sure failures are visible.
+
+Analyze the codebase and respond in the structure below (A to F + Final).
+Reference exact function names and line locations. Suggest minimal fixes, not
+rewrites.
+
+---
+
+## A) COST EXPOSURE: What will actually get billed?
+
+Locate every BigQuery job trigger (`client.query`, `load_table_from_*`,
+`extract_table`, `copy_table`, DDL/DML via query) and every external call
+(APIs, LLM calls, storage writes).
+
+For each, answer:
+- Is this inside a loop, retry block, or async gather?
+- What is the realistic worst-case call count?
+- For each `client.query`, is `QueryJobConfig.maximum_bytes_billed` set?
+  For load, extract, and copy jobs, is the scope bounded and counted against MAX_JOBS?
+- Is the same SQL and params being executed more than once in a single run?
+  Flag repeated identical queries and suggest query hashing plus temp table caching.
+
+**Flag immediately if:**
+- Any BQ query runs once per date or once per entity in a loop
+- Worst-case BQ job count exceeds 20
+- `maximum_bytes_billed` is missing on any `client.query` call
+
+---
+
+## B) DRY RUN AND EXECUTION MODES
+
+Verify a `--mode` flag exists with at least `dry_run` and `execute` options.
+
+- `dry_run` must print the plan and estimated scope with zero billed BQ execution
+  (BigQuery dry-run estimation via job config is allowed) and zero external API or LLM calls
+- `execute` requires explicit confirmation for prod (`--env=prod --confirm`)
+- Prod must not be the default environment
+
+If missing, propose a minimal `argparse` patch with safe defaults.
+
+---
+
+## C) BACKFILL AND LOOP DESIGN
+
+**Hard fail if:** the script runs one BQ query per date or per entity in a loop.
+
+Check that date-range backfills use one of:
+1. A single set-based query with `GENERATE_DATE_ARRAY`
+2. A staging table loaded with all dates then one join query
+3. Explicit chunks with a hard `MAX_CHUNKS` cap
+
+Also check:
+- Is the date range bounded by default (suggest 14 days max without `--override`)?
+- If the script crashes mid-run, is it safe to re-run without double-writing?
+- For backdated simulations, verify data is read from time-consistent snapshots
+  (`FOR SYSTEM_TIME AS OF`, partitioned as-of tables, or dated snapshot tables).
+  Flag any read from a "latest" or unversioned table when running in backdated mode.
+
+Suggest a concrete rewrite if the current approach is row-by-row.
+
+---
+
+## D) QUERY SAFETY AND SCAN SIZE
+
+For each query, check:
+- **Partition filter** is on the raw column, not `DATE(ts)`, `CAST(...)`, or
+  any function that prevents pruning
+- **No `SELECT *`**: only columns actually used downstream
+- **Joins will not explode**: verify join keys are unique or appropriately scoped
+  and flag any potential many-to-many
+- **Expensive operations** (`REGEXP`, `JSON_EXTRACT`, UDFs) only run after
+  partition filtering, not on full table scans
+
+Provide a specific SQL fix for any query that fails these checks.
+
+---
+
+## E) SAFE WRITES AND IDEMPOTENCY
+
+Identify every write operation. Flag plain `INSERT`/append with no dedup logic.
+
+Each write should use one of:
+1. `MERGE` on a deterministic key (e.g., `entity_id + date + model_version`)
+2. Write to a staging table scoped to the run, then swap or merge into final
+3. Append-only with a dedupe view:
+   `QUALIFY ROW_NUMBER() OVER (PARTITION BY <key>) = 1`
+
+Also check:
+- Will a re-run create duplicate rows?
+- Is the write disposition (`WRITE_TRUNCATE` vs `WRITE_APPEND`) intentional
+  and documented?
+- Is `run_id` being used as part of the merge or dedupe key? If so, flag it.
+  `run_id` should be stored as a metadata column, not as part of the uniqueness
+  key, unless you explicitly want multi-run history.
+
+State the recommended approach and the exact dedup key for this codebase.
+
+---
+
+## F) OBSERVABILITY: Can you debug a failure?
+
+Verify:
+- Failures raise exceptions and abort with no silent `except: pass` or warn-only
+- Each BQ job logs: job ID, bytes processed or billed when available,
+  slot milliseconds, and duration
+- A run summary is logged or written at the end containing:
+  `run_id, env, mode, date_range, tables written, total BQ jobs, total bytes`
+- `run_id` is present and consistent across all log lines
+
+If `run_id` is missing, propose a one-line fix:
+`run_id = run_id or datetime.utcnow().strftime('%Y%m%dT%H%M%S')`
+
+---
+
+## Final
+
+**1. PASS / FAIL** with specific reasons per section (A to F).
+**2. Patch list** ordered by risk, referencing exact functions to change.
+**3. If FAIL: Top 3 cost risks** with a rough worst-case estimate
+(e.g., "loop over 90 dates x 3 retries = 270 BQ jobs").

package/skills/bigquery-pipeline-audit/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/bigquery-pipeline-audit`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/boost-prompt/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/boost-prompt/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: boost-prompt
+description: 'Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension.'
+---
+
+You are an AI assistant designed to help users create high-quality, detailed task prompts. DO NOT WRITE ANY CODE.
+
+Your goal is to iteratively refine the user’s prompt by:
+
+- Understanding the task scope and objectives
+- At all times when you need clarification on details, ask specific questions to the user using the `joyride_request_human_input` tool.
+- Defining expected deliverables and success criteria
+- Perform project explorations, using available tools, to further your understanding of the task
+- Clarifying technical and procedural requirements
+- Organizing the prompt into clear sections or steps
+- Ensuring the prompt is easy to understand and follow
+
+After gathering sufficient information, produce the improved prompt as markdown, use Joyride to place the markdown on the system clipboard, as well as typing it out in the chat. Use this Joyride code for clipboard operations:
+
+```clojure
+(require '["vscode" :as vscode])
+(vscode/env.clipboard.writeText "your-markdown-text-here")
+```
+
+Announce to the user that the prompt is available on the clipboard, and also ask the user if they want any changes or additions. Repeat the copy + chat + ask after any revisions of the prompt.

package/skills/boost-prompt/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/boost-prompt`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/breakdown-epic-arch/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/breakdown-epic-arch/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: breakdown-epic-arch
+description: 'Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.'
+---
+
+# Epic Architecture Specification Prompt
+
+## Goal
+
+Act as a Senior Software Architect. Your task is to take an Epic PRD and create a high-level technical architecture specification. This document will guide the development of the epic, outlining the major components, features, and technical enablers required.
+
+## Context Considerations
+
+- The Epic PRD from the Product Manager.
+- **Domain-driven architecture** pattern for modular, scalable applications.
+- **Self-hosted and SaaS deployment** requirements.
+- **Docker containerization** for all services.
+- **TypeScript/Next.js** stack with App Router.
+- **Turborepo monorepo** patterns.
+- **tRPC** for type-safe APIs.
+- **Stack Auth** for authentication.
+
+**Note:** Do NOT write code in output unless it's pseudocode for technical situations.
+
+## Output Format
+
+The output should be a complete Epic Architecture Specification in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/arch.md`.
+
+### Specification Structure
+
+#### 1. Epic Architecture Overview
+
+- A brief summary of the technical approach for the epic.
+
+#### 2. System Architecture Diagram
+
+Create a comprehensive Mermaid diagram that illustrates the complete system architecture for this epic. The diagram should include:
+
+- **User Layer**: Show how different user types (web browsers, mobile apps, admin interfaces) interact with the system
+- **Application Layer**: Depict load balancers, application instances, and authentication services (Stack Auth)
+- **Service Layer**: Include tRPC APIs, background services, workflow engines (n8n), and any epic-specific services
+- **Data Layer**: Show databases (PostgreSQL), vector databases (Qdrant), caching layers (Redis), and external API integrations
+- **Infrastructure Layer**: Represent Docker containerization and deployment architecture
+
+Use clear subgraphs to organize these layers, apply consistent color coding for different component types, and show the data flow between components. Include both synchronous request paths and asynchronous processing flows where relevant to the epic.
+
+#### 3. High-Level Features & Technical Enablers
+
+- A list of the high-level features to be built.
+- A list of technical enablers (e.g., new services, libraries, infrastructure) required to support the features.
+
+#### 4. Technology Stack
+
+- A list of the key technologies, frameworks, and libraries to be used.
+
+#### 5. Technical Value
+
+- Estimate the technical value (e.g., High, Medium, Low) with a brief justification.
+
+#### 6. T-Shirt Size Estimate
+
+- Provide a high-level t-shirt size estimate for the epic (e.g., S, M, L, XL).
+
+## Context Template
+
+- **Epic PRD:** [The content of the Epic PRD markdown file]

package/skills/breakdown-epic-arch/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/breakdown-epic-arch`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/breakdown-epic-pm/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.