@cubis/foundry 0.3.81 → 0.3.83

package/workflows/workflows/agent-environment-setup/platforms/codex/workflows/spec.md

@@ -1,81 +0,0 @@
----
-command: "/spec"
-description: "Create or refresh a Git-tracked spec pack for non-trivial work, including acceptance criteria, traceability, architecture impact, and next-route handoff."
-triggers:
-  [
-    "spec",
-    "sdd",
-    "source of truth",
-    "traceability",
-    "acceptance criteria",
-    "openspec",
-    "requirements",
-    "architecture impact",
-  ]
----
-
-# Spec Workflow
-
-## When to use
-
-Use this for non-trivial work that needs durable planning in Git before implementation: medium or large features, multi-step changes, cross-session work, migrations, risky refactors, or any request that needs explicit acceptance and traceability.
-
-## Routing
-
-- Primary coordinator: `the project-planner posture`
-- Traceability and requirements support: `the researcher posture`
-- Cross-domain coordination: `the orchestrator posture`
-- Documentation and structure support: `the documentation-writer posture`
-
-## Skill Routing
-
-- Primary skills: `spec-driven-delivery`, `sadd`
-- Supporting skills (optional): `system-design`, `architecture-doc`, `deep-research`, `api-design`, `database-design`, `tech-doc`
-- Start with `spec-driven-delivery` for the pack structure and handoff contract. Add `sadd` when mining requirements into testable assertions, `system-design` or `architecture-doc` when the spec changes structure, and `deep-research` only when repo-local evidence is insufficient.
-
-## Workflow steps
-
-1. Determine whether the task is non-trivial enough to justify a spec pack.
-2. Find an existing `docs/specs/<spec-id>/` pack or create a new stable `spec_id`.
-3. Write or refresh the spec pack with brief, acceptance, tasks, traceability, and handoff files.
-4. Record `architecture_impact`, `doc_impact`, and any required updates to `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, `ENGINEERING_RULES.md`, or `docs/foundation/TECH.md`.
-5. Identify the next execution route and hand off without replanning the same work.
-
-## Context notes
-
-- Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist because they define the accepted product direction, architecture contract, and current state.
-- Prefer repo evidence first; escalate to `deep-research` only when freshness, public comparison, or explicit research requests require it.
-- Keep spec packs lean. Trivial one-step tasks should stay on the lightweight path with no new spec directory.
-
-## Verification
-
-- `spec_id` and `spec_root` are stable and explicit.
-- Acceptance criteria are testable and traceable.
-- Task dependencies form a valid execution order.
-- `architecture_impact`, `doc_impact`, and `traceability_status` are present.
-
-## Output Contract
-
-```yaml
-SPEC_WORKFLOW_RESULT:
-  primary_agent: project-planner
-  supporting_agents: [researcher?, orchestrator?, documentation-writer?]
-  primary_skills: [spec-driven-delivery, sadd]
-  supporting_skills: [system-design?, architecture-doc?, deep-research?, api-design?, database-design?, tech-doc?]
-  spec_id: <string>
-  spec_root: docs/specs/<spec-id>
-  architecture_impact:
-    summary: <string>
-    affects_structure: true | false
-    affects_design_system: true | false
-    affects_testing_strategy: true | false
-  doc_impact: none | tech | rules | both
-  traceability_status: complete | partial | blocked
-  documents:
-    created: [<path>] | []
-    updated: [<path>] | []
-  next_route: </create | /implement-track | /orchestrate | /architecture | direct>
-  gaps: [<string>] | []
-```
-
-> **Codex note:** Prefer native Codex delegation when the host exposes it. Otherwise follow AGENTS.md specialist postures inline while keeping the same routing and verification contract.

package/workflows/workflows/agent-environment-setup/platforms/codex/workflows/test.md

@@ -1,66 +0,0 @@
----
-command: "/test"
-description: "Design and execute verification strategy aligned to user risk, release confidence, and regression evidence."
-triggers: ["test", "verify", "coverage", "qa", "regression"]
----
-
-# Test Workflow
-
-## When to use
-
-Use this when writing new tests, improving coverage, debugging test failures, or designing a testing strategy.
-
-## Routing
-
-- Primary specialist: `the test-engineer posture`
-- Automation support: `the qa-automation-engineer posture`
-- Domain support: `the backend-specialist posture`, `the frontend-specialist posture`
-- Verification support: `the validator posture`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach the code under test, existing test files, coverage reports, and any failing test output.
-
-## Skill Routing
-
-- Primary skills: `unit-testing`, `integration-testing`
-- Supporting skills (optional): `playwright-interactive`, `observability`, `systematic-debugging`, `code-review`, `code-review`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`
-- Start with `unit-testing` for test strategy and architecture. Add `integration-testing` for implementation. Add `playwright-interactive` for E2E automation. Add `observability` for testing error states.
-
-## Workflow steps
-
-1. Assess current test coverage and identify gaps.
-2. Design test strategy (which layers, what to test, what to skip).
-3. Implement tests with clear arrange/act/assert structure.
-4. Run tests and verify they pass.
-5. Review coverage improvement and remaining gaps.
-
-## Verification
-
-- All new tests pass reliably (no flakiness).
-- Tests cover the identified risk areas.
-- Coverage metrics improved or maintained.
-- Test naming clearly describes the scenario being verified.
-
-## Output Contract
-
-```yaml
-TEST_WORKFLOW_RESULT:
-  primary_agent: test-engineer
-  supporting_agents: [qa-automation-engineer?, backend-specialist?, frontend-specialist?, validator?]
-  primary_skills: [unit-testing, integration-testing]
-  supporting_skills: [playwright-interactive?, observability?, systematic-debugging?]
-  test_strategy:
-    unit: <number of tests>
-    integration: <number of tests>
-    e2e: <number of tests>
-  tests_written: [<test-file-path>]
-  coverage:
-    before: <percentage or description>
-    after: <percentage or description>
-  gaps_remaining: [<string>] | []
-  follow_up_items: [<string>] | []
-```
-
-> **Codex note:** Prefer native Codex delegation when the host exposes it. Otherwise follow AGENTS.md specialist postures inline while keeping the same routing and verification contract.

package/workflows/workflows/agent-environment-setup/platforms/codex/workflows/vercel.md

@@ -1,76 +0,0 @@
----
-command: "/vercel"
-description: "Drive Vercel implementation and operations via vercel-expert with deployment, runtime, security, and observability guardrails."
-triggers:
-  [
-    "vercel",
-    "deployment",
-    "preview",
-    "edge",
-    "functions",
-    "domains",
-    "vercel cli",
-  ]
----
-
-# Vercel Workflow
-
-## When to use
-
-Use this for Vercel-specific deployment, configuration, runtime optimization, or platform operations.
-
-## Routing
-
-- Primary specialist: `the vercel-expert posture`
-- Infrastructure support: `the ci-cd-pipeline posture`
-- Verification support: `the test-engineer posture`
-
-## Context notes
-
-- This workflow file, active platform rules, and selected agents or skills guide execution.
-- Attach the Vercel project config, deployment target, and any specific Vercel feature requirements.
-
-## Skill Routing
-
-- Primary skills: `nextjs`, `ci-cd-pipeline`
-- Supporting skills (optional): `performance-testing`, `react`, `frontend-design`, `javascript-best-practices`, `typescript-best-practices`, `javascript-best-practices`
-- Start with `nextjs` for Next.js on Vercel and `ci-cd-pipeline` for runtime behavior. Add `performance-testing` for performance optimization.
-
-## Workflow steps
-
-1. Assess deployment requirements and runtime selection (Edge vs Serverless vs Static).
-2. Configure project settings and environment variables.
-3. Set up deployment pipeline with preview deployments.
-4. Verify deployment health and performance.
-5. Configure monitoring and alerting.
-
-## Verification
-
-- Deployment successful with no build errors.
-- Runtime selection appropriate for each route.
-- Environment variables correctly configured per environment.
-- Preview deployments working for PRs.
-- Performance metrics within acceptable ranges.
-
-## Output Contract
-
-```yaml
-VERCEL_WORKFLOW_RESULT:
-  primary_agent: vercel-expert
-  supporting_agents: [ci-cd-pipeline?, test-engineer?]
-  primary_skills: [nextjs, ci-cd-pipeline]
-  supporting_skills: [performance-testing?, react?]
-  deployment:
-    project: <string>
-    runtime: <edge | serverless | static>
-    environment: <development | preview | production>
-    status: success | failure
-  configuration:
-    env_vars: [<string>]
-    domains: [<string>]
-    caching: <string>
-  monitoring: <string>
-  follow_up_items: [<string>] | []
-```
-
-> **Codex note:** Prefer native Codex delegation when the host exposes it. Otherwise follow AGENTS.md specialist postures inline while keeping the same routing and verification contract.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-accessibility.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /accessibility
-
-Run a structured accessibility audit on web UI code with WCAG 2.2 AA compliance checks, ARIA validation, keyboard navigation testing, and screen reader verification.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/accessibility.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `code-review`, `frontend-design`, `performance-testing`, `react`, `nextjs`, `playwright-interactive`, `typescript-best-practices`, `javascript-best-practices`.
-- Local skill file hints if installed: `.github/skills/code-review/SKILL.md`, `.github/skills/frontend-design/SKILL.md`, `.github/skills/performance-testing/SKILL.md`, `.github/skills/react/SKILL.md`, `.github/skills/nextjs/SKILL.md`, `.github/skills/playwright-interactive/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-architecture.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /architecture
-
-Refresh the core project foundation docs in docs/foundation/PRODUCT.md, docs/foundation/ARCHITECTURE.md, docs/foundation/TECH.md, and ADR scaffolds with explicit structure, product context, testing, and flow guidance.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/architecture.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `architecture-doc`, `system-design`, `tech-doc`, `frontend-design`, `api-design`, `database-design`, `sadd`, `deep-research`.
-- Local skill file hints if installed: `.github/skills/architecture-doc/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/frontend-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/sadd/SKILL.md`, `.github/skills/deep-research/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-backend.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /backend
-
-Drive backend architecture, API operations, and Postman-oriented execution with API, data, and reliability focus.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/backend.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `api-design`, `javascript-best-practices`, `owasp-security-review`, `database-design`, `nestjs`, `fastapi`, `microservices-design`, `drizzle-orm`, `stripe-integration`, `ci-cd-pipeline`, `frontend-design`, `typescript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/api-design/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/owasp-security-review/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/nestjs/SKILL.md`, `.github/skills/fastapi/SKILL.md`, `.github/skills/microservices-design/SKILL.md`, `.github/skills/drizzle-orm/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-create.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /create
-
-Implement feature work with minimal blast radius and clear verification checkpoints.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/create.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`, `csharp-best-practices`, `kotlin-best-practices`, `rust-best-practices`, `php-best-practices`, `expo-app`, `swift-best-practices`, `api-design`, `nestjs`, `fastapi`, `drizzle-orm`, `database-design`, `mcp-server-builder`, `stitch`, `react`, `nextjs`, `frontend-design`, `performance-testing`, `skill-creator`, `stripe-integration`, `ci-cd-pipeline`.
-- Local skill file hints if installed: `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`, `.github/skills/java-best-practices/SKILL.md`, `.github/skills/csharp-best-practices/SKILL.md`, `.github/skills/kotlin-best-practices/SKILL.md`, `.github/skills/rust-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-database.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /database
-
-Design or review schema, queries, and migrations with performance and integrity controls.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/database.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `database-design`, `drizzle-orm`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`.
-- Local skill file hints if installed: `.github/skills/database-design/SKILL.md`, `.github/skills/drizzle-orm/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-debug.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /debug
-
-Isolate root cause quickly, apply the smallest safe remediation, and leave behind regression evidence.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/debug.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `systematic-debugging`, `observability`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`, `csharp-best-practices`, `kotlin-best-practices`, `rust-best-practices`, `integration-testing`, `playwright-interactive`, `skill-creator`.
-- Local skill file hints if installed: `.github/skills/systematic-debugging/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`, `.github/skills/java-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-devops.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /devops
-
-Plan and execute deployment, CI/CD, incident response, and operational safety changes with rollback controls.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/devops.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `ci-cd-pipeline`, `kubernetes-deploy`, `observability`, `git-workflow`, `systematic-debugging`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/ci-cd-pipeline/SKILL.md`, `.github/skills/kubernetes-deploy/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/git-workflow/SKILL.md`, `.github/skills/systematic-debugging/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-implement-track.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /implement-track
-
-Execute large work in milestones with explicit quality gates and status updates.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/implement-track.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `system-design`, `api-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `react`, `nextjs`.
-- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`, `.github/skills/react/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-migrate.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /migrate
-
-Plan and execute technology migrations, framework upgrades, and dependency updates with rollback safety, incremental verification, and zero-downtime transition.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/migrate.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `system-design`, `code-review`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/code-review/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-mobile.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /mobile
-
-Drive mobile implementation decisions for Flutter/cross-platform behavior and reliability.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/mobile.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `expo-app`, `react-native`, `stitch`, `frontend-design`, `swift-best-practices`, `kotlin-best-practices`.
-- Local skill file hints if installed: `.github/skills/expo-app/SKILL.md`, `.github/skills/react-native/SKILL.md`, `.github/skills/stitch/SKILL.md`, `.github/skills/frontend-design/SKILL.md`, `.github/skills/swift-best-practices/SKILL.md`, `.github/skills/kotlin-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-onboard.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /onboard
-
-Survey an unfamiliar codebase, map its architecture, identify patterns and conventions, and produce a structured orientation report for new contributors.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/onboard.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `deep-research`, `system-design`, `database-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`.
-- Local skill file hints if installed: `.github/skills/deep-research/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-orchestrate.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /orchestrate
-
-Coordinate multiple specialists to solve cross-cutting tasks with explicit ownership, validation gates, and repeat-until-good iteration.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/orchestrate.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`.
-- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/deep-research/SKILL.md`, `.github/skills/mcp-server-builder/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/prompt-engineering/SKILL.md`, `.github/skills/skill-creator/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-plan.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /plan
-
-Build a decision-complete implementation plan with interfaces, failure modes, and acceptance criteria.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/plan.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, `skill-creator`.
-- Local skill file hints if installed: `.github/skills/system-design/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/deep-research/SKILL.md`, `.github/skills/mcp-server-builder/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/prompt-engineering/SKILL.md`, `.github/skills/skill-creator/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-refactor.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /refactor
-
-Improve maintainability while preserving behavior through incremental safe refactoring.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/refactor.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `code-review`, `system-design`, `unit-testing`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/code-review/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-release.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /release
-
-Prepare and execute release with rollout guardrails, verification, and rollback plan.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/release.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `ci-cd-pipeline`, `git-workflow`, `tech-doc`, `observability`, `kubernetes-deploy`, `typescript-best-practices`, `javascript-best-practices`.
-- Local skill file hints if installed: `.github/skills/ci-cd-pipeline/SKILL.md`, `.github/skills/git-workflow/SKILL.md`, `.github/skills/tech-doc/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/kubernetes-deploy/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-review.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /review
-
-Run a strict review for bugs, regressions, accessibility issues, security risk, and code quality with prioritized findings.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/review.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `code-review`, `unit-testing`, `owasp-security-review`, `performance-testing`, `react`, `nextjs`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`.
-- Local skill file hints if installed: `.github/skills/code-review/SKILL.md`, `.github/skills/unit-testing/SKILL.md`, `.github/skills/owasp-security-review/SKILL.md`, `.github/skills/performance-testing/SKILL.md`, `.github/skills/react/SKILL.md`, `.github/skills/nextjs/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-security.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /security
-
-Run security-focused analysis and remediation planning with exploitability-first triage.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/security.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `owasp-security-review`, `code-review`, `api-design`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `rust-best-practices`.
-- Local skill file hints if installed: `.github/skills/owasp-security-review/SKILL.md`, `.github/skills/code-review/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`, `.github/skills/python-best-practices/SKILL.md`, `.github/skills/golang-best-practices/SKILL.md`, `.github/skills/rust-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-spec.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /spec
-
-Create or refresh a Git-tracked spec pack for non-trivial work, including acceptance criteria, traceability, architecture impact, and next-route handoff.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/spec.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `spec-driven-delivery`, `sadd`, `system-design`, `architecture-doc`, `deep-research`, `api-design`, `database-design`, `tech-doc`.
-- Local skill file hints if installed: `.github/skills/spec-driven-delivery/SKILL.md`, `.github/skills/sadd/SKILL.md`, `.github/skills/system-design/SKILL.md`, `.github/skills/architecture-doc/SKILL.md`, `.github/skills/deep-research/SKILL.md`, `.github/skills/api-design/SKILL.md`, `.github/skills/database-design/SKILL.md`, `.github/skills/tech-doc/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.

package/workflows/workflows/agent-environment-setup/platforms/copilot/prompts/workflow-test.prompt.md

@@ -1,18 +0,0 @@
-# Workflow Prompt: /test
-
-Design and execute verification strategy aligned to user risk, release confidence, and regression evidence.
-
-Use this prompt with the matching workflow file:
-- Workflow: ../copilot/workflows/test.md
-
-Execution contract:
-1. Treat route selection as already resolved by this prompt; do not begin with skill discovery.
-2. Read `docs/foundation/PRODUCT.md`, `ENGINEERING_RULES.md`, `docs/foundation/ARCHITECTURE.md`, and `docs/foundation/TECH.md` in that order when they exist before non-trivial execution.
-Attached skills:
-- Load these exact skill IDs first: `unit-testing`, `integration-testing`, `playwright-interactive`, `observability`, `systematic-debugging`, `code-review`, `typescript-best-practices`, `javascript-best-practices`, `python-best-practices`, `golang-best-practices`, `java-best-practices`.
-- Local skill file hints if installed: `.github/skills/unit-testing/SKILL.md`, `.github/skills/integration-testing/SKILL.md`, `.github/skills/playwright-interactive/SKILL.md`, `.github/skills/observability/SKILL.md`, `.github/skills/systematic-debugging/SKILL.md`, `.github/skills/code-review/SKILL.md`, `.github/skills/typescript-best-practices/SKILL.md`, `.github/skills/javascript-best-practices/SKILL.md`.
-- Treat the skill bundle as already resolved for this workflow. Do not start with route discovery.
-3. Apply workflow sections in order: When to use, Workflow steps, Context notes, Verification.
-4. Route to the workflow's primary specialist and only add supporting specialists when needed.
-5. If freshness or public comparison matters, run `deep-research` before implementation and use official docs as primary evidence.
-6. Return actions taken, verification evidence, and any gaps.